Also, Apple's announcement today about iPhone development using AJAX and exposing internal phone functions as web services to the iPhone's safari browser is tipping everything in the same direction.<br><br>Cheers Adrian
<br><br><div><span class="gmail_quote">On 6/11/07, <b class="gmail_sendername">Matthew S. Hamrick</b> <<a href="mailto:mhamrick@cryptonomicon.net">mhamrick@cryptonomicon.net</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;">
Yeah... we're thinking that we were going to totally separate the<br>model and domain processing from the view/controller part of the<br>application. That way we could have a couple different HTML<br>interfaces as well as a SVG/ECMAScript interface. I'm not terribly
<br>familiar with XAML or XUL, but I understand that most (if not all) of<br>the Firefox / Mozilla / Navigator interface was written in XUL.<br><br>This is one of the benefits to this approach, IMHO. Separating the<br>interface allows us to experiment with a number of different
<br>interface technologies. And the only thing the experimenters need to<br>know is the semantics and syntax of the XML interface.<br><br>-Cheers!<br>-Matt H.<br><br>On Jun 11, 2007, at 9:18 AM, Tim Newsom wrote:<br><br>> If we are heading in the direction of web interfaces, I think we
<br>> should look at XAML or XUL or something similar. From what I can<br>> tell, they will be adding silverlight support to mono, so using<br>> XAML will be possible. This also separates the code for<br>> functionality from the interface and can allow skinning of the
<br>> entire application interface set.<br>><br>> This will abstract you from every widget set. Each action could be<br>> exported and called from the UI without needing to worry about all<br>> that.<br>>
<br>> At least, that's my take on it currently.<br>><br>> --Tim<br>> On Mon, 11 Jun 2007 8:44, Florent THIERY wrote:<br>>> Here's a little look-and-feel example that could be done with an<br>>> opensource AJAX framework [javascript required]:
<br>>><br>>> <a href="http://demo.qooxdoo.org/current/showcase">http://demo.qooxdoo.org/current/showcase</a><br>>><br>>> This may allow easier separation between apps and GUIs. Of course, as<br>>> usual we have no idea how well such an app would perform (little &
<br>>> gratuitous prediction: very bad), benchmarking is needed but ... who<br>>> knows ?<br>>><br>>> This is going along with the ongoings gdk webkit port and gsmd<br>>> XmlHttpRequest interface (was topic: embedded webserver).
<br>>><br>>> What do you think ? Is it REALLY unrealistic ? Could anybody try the<br>>> url on it's Nokia N770 (lots of happy owners here, right?) and rough<br>>> feedback the responsiveness ?<br>
>><br>>> Cheers<br>>><br>>> Florent<br>>><br>><br>> _______________________________________________<br>> OpenMoko community mailing list<br>> <a href="mailto:community@lists.openmoko.org">
community@lists.openmoko.org</a><br>> <a href="http://lists.openmoko.org/mailman/listinfo/community">http://lists.openmoko.org/mailman/listinfo/community</a><br><br><br>_______________________________________________<br>
OpenMoko community mailing list<br><a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br><a href="http://lists.openmoko.org/mailman/listinfo/community">http://lists.openmoko.org/mailman/listinfo/community
</a><br></blockquote></div><br>