Lush and Qt

The Lush graphic engine is definitely in need of an overhaul.

Having Qt bindings for Lush would certainly be useful to a lot of
people. Whether to make Qt the main underlying graphic/gui engine 
for Lush is something we should discuss.

Any ideas? Volunteers?

  -- Yann


On Monday 08 September 2008, Raymond Martin wrote:
> On 8 September 2008 11:52:50 Ralf Juengling wrote:
> > Hi Everybody,
> >
> > I set up a new svn repository for "Lush 2" this weekend.
> > You may check out code from it with
> >
> > svn co https://lush.svn.sourceforge.net/svnroot/lush/lush2
> >
> > After working alongside on different branches for some
> > time, Yann, Leon and I agreed that working together would
> > be more beneficial. Since the branches have diverged a bit,
> > we decided to start a new development branch and repository.
> >
> > As the name indicates, "Lush 2" is not quite backwards
> > compatible with Lush (it is basically PSU-Lush 1.3 plus
> > a lot of changes under the hood). A new major release is
> > an opportunity to fix things that cannot be fixed without
> > breaking backwards compatibility, and the plan is to do
> > just that. For example, we would like to make Lush 2 case
> > sensitive. So don't expect official Lush 2 releases very
> > soon, we will have to work on it for a while.
> >
> > That said, I hope that you will start working with Lush 2
> > right away. Before drawing up an agenda of changes and
> > improvements we want to make in this release, we should now
> > focus on getting it to work for everybody on the list. You
> > will most likely run into some glitches that I have not
> > stumbled upon myself. Please report what you find broken so
> > that we may fix it.
> >
> > Lush 2 may be installed alongside lush (the executable is
> > named 'lush2').
>
> Nice to hear that things are moving forward.
>
> I would like to make one BIG suggestion. Build a new generation Lush on top
> of Qt.
>
> There are many advantages to this, of which I am sure at least Leon is
> aware from his work on DjView, for instance.
>
> Qt can serve as a platform, rather than just as add on functionality. Lush
> will then be automatically cross-platform and be able to serve up native
> GUIs and services (DBus on Linux, Cocoa on OS X (coming in Qt4.5), WebKit,
> ActiveX on Windows, etc.).
>
> A number of other languages already have Qt support (Java[QtJambi],
> Python[PyQt], Ruby [QtRuby]). Providing Qt would not only put Lush on a par
> with those other languages, but put it above if implemented in the fashion
> of a platform that Lush works over.
>
> There could be separate versions via a configure switch that will either
> build a full Qt enabled version or a lighter weight, more traditional,
> version.
>
> I have already planned to use Qt for my Java/Lush version (via QtJambi),
> which I started months ago working initially by porting from Leon's
> minilisp code in the dejavulibre library.
>
> On top of this, I would also like to suggest that the GNU Toolchain be
> dropped in favor CMake (which has many advanced options, supports Qt
> projects, and makes projects simpler to maintain).
>
> Cheers,
>
> Raymond
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK & win
> great prizes Grand prize is a trip for two to an Open Source event anywhere
> in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Lush-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lush-devel




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/