Hi,

The latest issue of Linux Journal features an article about Pixel (By Pavel Kanzelsberger). It gives it a very good comment. Pity it's not mentioned that it's written using FPC. (the article is written by a writer/publisher, not a programmer).

For the Lazarus users: Pixel is written using a widget-set developed by Pavel.

Michael.

Greetings,
Is it online?

_____

avast! Antivirus <http://www.avast.com> : Outbound message clean.

Virus Database (VPS): 0653-5, 05/12/2006
Tested on: 8/12/2006 6:46:35 ??
avast! - copyright (c) 1988-2006 ALWIL Software.

The article ? Not that I know of. The program is:
http://www.kanzelsberger.com/

Michael.

I don't see Lazarus mentioned at the splash screen of the windows version (some of you guys are mentioned, but wouldn't harm to mention Lazarus too or instead)
Also didn't notice Lazarus button or something at the website (didn't look much though, maybe have missed it)

----------------
George Birbilis ()
Computer & Informatics Engineer
Microsoft MVP J# for 2004-2006
Borland "Spirit of Delphi"
++ QuickTime, Delphi, ActiveX, .NET components ++
http://www.kagi.com/birbilis
++ Robotics ++
http://www.mech.upatras.gr/~Robotics
http://www.mech.upatras.gr/~robgroup

_____

avast! Antivirus <http://www.avast.com> : Outbound message clean.

Virus Database (VPS): 0653-5, 05/12/2006
Tested on: 8/12/2006 11:17:33 ??
avast! - copyright (c) 1988-2006 ALWIL Software.

.
.

As far as I know, the reason is as simple as
this: it isn't created using Lazarus, just FPC.
Pixel is available for much more platforms than
Lazarus. According to my knowledge, the widgetset
is based on SDL.

Tomas

Tomas Hajny wrote

Lazarus. According to my knowledge, the widgetset is based on SDL.

I have thought of that as well for fpGUI.... Can anybody confirm if eLiquid (I think that is what Pixel's widget set is called) is actually built using SDL? Does the windows version ship with the SDL libraries?

I did a bit of Google'ing and answered my own question.... :-) eLiquid is not based on SDL.

------------- Quote -----------------
by: gamehack
I think the GUI is based on libSDL, am I right?

by: Pavel
eLiquid is not really based on SDL, this backend can be changed anytime. You can see that in DOS version, there's another backend for VBE video cards.
------------- End Quote -----------

Regards,
- Graeme -

I did a bit of Google'ing and answered my own question.... :-) eLiquid is not based on SDL.

or is it? :-)

------- Quote ----------
Requirements: It is required to install libSDL package to get Pixel working in Linux. Optionally you will need also libfreetype and liblcms packages. For JPEG2000 support it is required to install libjasper library. For printing it is recommended to install CUPS package. For scanning it is recommended to install SANE. If you want OpenEXR support you should install openexr library. ------- End Quote ----------

Regards,
- Graeme -

Graeme Geldenhuys wrote

> I did a bit of Google'ing and answered my own question.... :-) > eLiquid is not based on SDL. or is it? :-)

I think it depends on the target.

Linux => SDL
DOS => not SDL

I'd just like to add that SDL is used for many other platforms as far as I know, not just Linux (at least OS/2, MorphOS, FreeBSD, Mac OS X and Zeta).

Tomas

Tomas Hajny wrote

I'd just like to add that SDL is used for many other platforms as far as I know, not just Linux (at least OS/2, MorphOS, FreeBSD, Mac OS X and Zeta).

I don't know to much about SDL. Does it handle anti-aliased line drawing, transparency, alpha-blending natively, or is SDL just a developer friendly front-end to other libraries?

Visit us on irc and ask Pavel/Kaco, he is there also rather often.

I don't know to much about SDL. Does it handle anti-aliased line drawing, transparency, alpha-blending natively, or is SDL just a developer friendly front-end to other libraries?

SDL is a low level API that is platform independent. It uses the underlying API for the platform it is targetting. So under Windows, it uses GDI, under BeOS it uses (IIRC) BDirectWindow (and the GameKit) and under Linux it uses whatever the base linux drawing API is (Framebuffer for one implementation at least IIRC.) What it gives you is a completely consistent cross platform low level API (even more so than Allegro did last time I used it.)

HTH

I don't know all that much about graphics, but (Jedi-)SDL is a great 2D and 3D library that uses OpenGL. It can also use other platform dependant graphic engines like DirectX on Windows. It is written in C++, but there are versions for Delphi and FPC. Unfortunatly it was never made compatible with TForm or to use with LCL or VCL components.

Andreas

I don't know all that much about graphics, but (Jedi-)SDL is a great 2D and 3D library that uses OpenGL. It can also use other platform dependant graphic engines like DirectX on Windows.

JEDI SDL is a Delphi (ObjectPascal) binding to SDL created by the JEDI project (actually, I used to work for the same company as its lead maintainer.) JEDI has nothing directly to do with SDL. No more than SDL.Net does (a binding for C# and other CLR/.Net languages.)

It is written in C++,

Actually its in plain old C AFAIA; but I may be wrong.. Certainly, it presents a flat C style API interface.

but there are versions for Delphi and FPC.

No, JEDI SDL is what you are thinking of. SDL is a seperate project.

Unfortunatly it was never made compatible with TForm or to use with LCL or

VCL components.

SDL has nothing to do with the TForm hierarchy of components. It is more like the GDI under Windows. It's a low level graphics API. It's not a widget set.

HTH