Different ? Yes. New ? No.

The missing piece is a nice API to handle all this, and maybe a framework. Oh, then some XSLT to transform XUL <=> XAML. ;^)

It also likely requires a well formed MVC architecture for the application.

BTW: There was an attempt to provide a pTk style mapping for XUL, but it seems to have "withered on the vine".

Some resources:

I'd love to be able to apply all of that, but the lack of a single coherent API to support it makes it a bit difficult (tho XUL::Node might be a start). As to how a server app should behave, I suspect that trying to route everything thru the usual Apache/mod_perl channel might be difficult; you may want to consider HTTP::Daemon. As to threading/forking, I'll offer Thread::Apartment as a possible (albeit immature) solution.

In reply to Re: A different approach to generating a GUI by renodino
in thread A different approach to generating a GUI by qbxk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.