Hello,

   Allow me to highlight the discussion going on over
at the KDE Dot News site kicked off by Rik Hemsley's
XAML versus Qt tech paper.

   George Staikos comments under the heading "Qt can
even support no-compilation":

   Have a look at some of the KJSEmbed examples, or
even more powerful (and building upon KJSEmbed),
kdenonbeta/kaxul. kaxul takes Mozilla's XUL files and
makes a native Qt GUI for it. The code is interpreted
Javascript so it runs everywhere without modification.
No compiler is required, just an interpreter. KDE has
been ahead of Microsoft on this for over a year now.
Mozilla has been leading the way with this for even
longer, though I still don't like their widgets. :-)


   Mambo-Jumbo comments under the heading "You GOT to
be kidding me!!":

   XAML has the ease of use of XML/HTML, everyone can
write a GUI on XAML with minimal training! That was
the point of it!

  Qt is a C++ toolkit and no matter how simple it is,
it is still a C++ toolkit and the programmer will have
to know how to use the language, compilers, debuggers
and all things that come with it.

  Please people, be objective for once, that "XAML vs
Qt" article is a joke. The author obviously doesn't
get what XAML is and what its goals/advantages are in
the first place.
    
  
   Ez comments under the heading XAML:

   I thought the point of XAML was for microsoft to be
able to replace HTML with something which describes
and renders richer applications - applications which
are more akin to a typical GUI app than a web page
with a form embedded in it.

  Obviously, the key word here is "renders". HTML web
browsers, as we know them, won't render XAML
applications, but isn't XAML intricately bound up with
.NET? I read an article about this a few months back
(sorry, forgotten the link) and I concluded that IE6
is the last visable, seperate browser in windows
because future versions of windows will have this new
superbrowser/.NET capability built in.

  I assume the goal is to be able to download an
interface description in which the screen controls are
bound to server-side event handlers in the same way
ASP.NET works now, the difference being that the
client is running .NET and therefore is able to render
a rich GUI app rather than just an (X)HTML web page.

  Maybe QT/KDE could be similarly extended to make
distributable web apps with a rich interface possible
on Linux. It'll happen eventually, anyway. The Mono
crowd, led by Microsoft-admirerer-in-chief Miguel
d'incaza, are eagerly implementing their own version
of XAML. A nice challenge for Mr. Hemsley et al, I
would have thought...


   Full story @ http://dot.kde.org/1080235389

   What's your take on it? Join the discussion and
post your thoughts and comments to xul-talk.

   - Gerald


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
xul-announce mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xul-announce

Reply via email to