[Alexandria-list] Alexandria on KDE

[Cathal Mc Ginley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 1 Feb 2008 13:11:07 -0500
Henry de Valence <hdevalence at gmail.com> wrote:

> On Friday 01 February 2008 1:04:51 pm Joseph Method wrote:
> > I think it's fine. If you put in a check for the current window
> > manager, it could even have the same executable. 

The (abandoned) OSX GUI did that, and ended up tangling GNOME &
Ruby/COCOA code throughout several files (I disentangled it just
before the 0.6.2 release). If the core is cleanly designed, a separate
application for each GUI front-end would probably be best.

> > I'm actually
> > strongly in favor of this simply because it will help us with
> > getting cleaner separation of concerns. 

Domain analysis would also serve that end. However, I agree that if we
create a well-factored "Application Facade" layer, then both a GNOME
and a KDE front-end could be supported, preferably as a thin display
layer on top of common application code.

I have been developing a proof-of-concept application (in a different
application domain) to try out very clean separation of domain and GUI.
Perhaps a small-scale test of attaching a KDE GUI to a common
application core would be helpful. Perhaps I can ping a few people when
I have my sample app ready to try this out.

> And also, just pointing out, I don't have lots of free time, so it
> would take a while. Also while I know there are QT4 bindings for
> ruby, I don't know what the state of KDE4 bindings for ruby
> (is/are?). 

Korundum and QtRuby only mention KDE/Qt 3.x support on their web page:
http://developer.kde.org/language-bindings/ruby/index.html
But apparently 4.x support is possible, or at least in progress:
http://dot.kde.org/1189467731/1189482359/

There's also some talk of QtRuby being used with Kross, the scripting
framework for KDE 4:
http://www.kdedevelopers.org/node/3187


   -   C.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE

iD8DBQFHo6wwfMAUnRdb+8oRAm+sAJ0b+PVhtRMcGzIRwC72hXVwZW2JOwCeOpUQ
GtaGTmXzsZFaFJFr4Kh6GqY=
=71BV
-----END PGP SIGNATURE-----