well, one possibility is php gtk, see <a href="http://gtk.php.net/">http://gtk.php.net/</a> (there is a data persistence layer in gears)<br>But I wasn't speaking only of using Gears itself, but rather of the paradigm shift to rich clients, with offline support.
<br>On the one hand stuff like Apollo, on the other ... if we have Drupal on a stick, we can have Drupal on a rich client. <br>The paradigm shift of web apps recycled as rich client apps can be seen on many fronts, for example in the world of light, agile J2EE, the Spring Framework has the Rich Client sub-project (see
<a href="http://www.springframework.org/spring-rcp">http://www.springframework.org/spring-rcp</a>).<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br><div><span class="gmail_quote">
On 5/31/07, <b class="gmail_sendername">adrian rossouw</b> <<a href="mailto:adrian@bryght.com">adrian@bryght.com</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;">
<div style=""><span class="q"><br><div><div>On 31 May 2007, at 11:05 AM, Victor Kane wrote:</div><br><blockquote type="cite"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
use case is manage content, prepare a new edition of a site all ready to synchronize with on line edition...</span></blockquote></div></span>except that all the pages used to manage content are generated and validated via php.
<br><div><br></div><div>we'd have to move that all to the javascript layer.</div></div></blockquote></div><br>