<br><div><span class="gmail_quote">On 12/29/06, <b class="gmail_sendername">Jesse Vincent</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>In the long run, I'd like to get there. We've also been playing with<br>Template::Declare, but still targeting running in a browser. If you're<br>interested in working on Desktop Jifty, what sort of widget
<br>set/templating system would be ideal?<br></blockquote></div><br><br>If Jifty could handle events(I know the namespace Jifty::Event is being used), then my imaginary picture is like this:<br><br>1. write an order sheet in XML(Jifty Vocabulary)
<br> <xml><br> <mainWindow><br> <menuBar><br> <menu><br> <menuItem><br> <name/><br> <id/><br> <action/><br> <event/>
<br> ... <br> </menuItem><br> </menu><br> </menuBar><br> <leftPanel/><br> <rightPanel/><br> <statusPanel/><br> </mainWindow>
<br><br>2. feed the XML file to the Jifty wrapper to GUI widgets( or Jifty Desktop Platform)<br><br>3. pull them down to dispatcher and action, model, template, event(Jifty Homeground)<br><br>4. reuse the functions(Jifty Natural Resource); login, session, channel, and so on.
<br><br>Well, this is a very common scenario, I think. For example, Firefox, Netbeans, and Eclipse(maybe), they are taking this way. That's it. We can clearly and easily predict ...<br><br><br><br> <br>