On Thu, Oct 30, 2008 at 11:09 AM, Maurizio la Cecilia
<[EMAIL PROTECTED]> wrote:

> None of the existing GUI can be elected to a "standard".

What I meant was:
what we'll answer when a user will ask
"Which is the Harbour's GUI lib?"

Also in Java there are Swing, SWT and many others but if you buy a
book about Java you'll find that Swing IS the Java GUI for desktop
apps.

> A choice is very hard and will result to disagree the developers that
> don't use the elected one.

For elected I don't mean that everyone has to use it.
Simply that after saying "Harbour can create Terminal and GUI apps" we
need to add how it can do it. For terminals we've GT for GUI we have
... and saying "there are a lot of them choose the one you like" is
good for skilled Harbour users but not for a new user that is
evaluating it.

> In HwGUI, i.e., this isn't true even if a great effort was done to obtain
> an high degree of compatibility between WinAPI and GTK.
> Only a project giving strong headlines, including the type of
> implementation and clear rules for syntax and behaviour of the code,
> could interest the community of programmers currently developing GUI
> Libraries, otherwise each developer will continue to talk his dialect.

This is why I think that xHGtk has more chances to survive than other
solutions.
Following closely Gtk standards they somewhat inherited the doc, the
tools and the "already proven" from it.

A complex GUI lib without a clean architecture, a tutorial and
complete doc is hard to pick up unless there is an existing code base
that require it.

best regards,
Lorenzo
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to