I agree that a desktop application would be useful, but not idylic. Although, FireFox is a desktop application! On the flip side, if the cherokee-admin server were able to manage the server config completely asynchronously via HTTP(S), this would make an awesome backend to a desktop client that interfaced with the backend via HTTP(S)/JSON for example. The front end could be developed for any platform knowing that the actual work was being done without any modification to the existing backend.
Along those lines, Java would also be a good fit (Applet/Standalone Application pair), though I am not partial to Java myself (unless it's the brewed sort). This is partly because supporting Java involves accepting licenses some users may not like. Further, there are Free browsers out there that support JavaScript just dandily. Since it seems there's a desire, I'll start hacking away. :) I will assume I should stick to GPL'd libraries for the client side? Ryan On Mon, Jan 26, 2009 at 10:26 AM, Antonio Pérez <[email protected]> wrote: > On Mon, Jan 26, 2009 at 5:22 PM, Alvaro Lopez Ortega <[email protected]> wrote: > >> If we get to improve cherokee-admin usability it should provide almost >> the same user experience as a desktop application, actually. >> >> I don't have anything against a hypothetical desktop application, >> although I do think that we ought to focus our attention and effort on >> improving Cherokee-admin. > > +1 An ajaxified version of cherokee-admin would be an easy-to-mantain > multiplatform desktop application. > > -- > Saludos: > Antonio Pérez > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
