Hi folks. The following is incoherent because I haven't formulated my ideas properly yet.
I've been tormented by thoughts about creating wsgi based tools to better support complex ajaxy applications... and then I found the pocoo stuff where you guys have implemented some things very similar to what I was thinking. So I'd like to unload a brain dump and see if you like minded people had any comments, ideas, or "oh yea, we've implemented that already: go here..." THE QUESTION: What's hard about web apps, particularly with ajax? THE ANSWER: Namespaces. Javascript Namespaces. HTTP Namespaces, CSS Namespaces, Server code (Python) namespaces. Form input namespaces. HTML template software namespaces. Backend database namespaces. That's a lot to keep track of. Basically I'd like to arrange it so that all these name spaces "look similar" enough so that they are essentially the same... It's much easier to juggle one ball than 6. Consider a chat application (modelled on commercial ParaChat) which looks a bit like this in abstract outline URL: http://my.server.org/path/to/my/chat/application HTML: [ ./menubar ] ======================= [ ./members ] || [./messages ] ======================== [ ./messageInput ] ======================== [ ./statusBar ] (I hope that looks familiar enough that you know what I mean). What I want to do is marry the notion of an HTML template with the notion of a wsgi-path so that the ./messages area is handled by a little application "located" at http://my.server.org/path/to/my/chat/application/messages Furthermore the form submission for ./messageInput would be handled by little app http://my.server.org/path/to/my/chat/application/statusBar/submit Which might respond with java script which asks the page to replace the content of the area at http://my.server.org/path/to/my/chat/application/messages with new html. Also the whole app would be watched by a poller which might get instructions from the server (as javascript) to -- do nothing or -- replace the contents of http://my.server.org/path/to/my/chat/application/messages with new html or -- replace the contents of http://my.server.org/path/to/my/chat/application/members with new html or -- replace the contents of http://my.server.org/path/to/my/chat/application/statusBar with new html... Note that some other app might re-use the components of the chat the framework to just watch member lists for many chats on the same page... This is just the tip of the iceberg of mad ideas racing around my brain, but I'll stop here because everyone probably stopped reading by now in frustration already... If this makes any sense, what do you think? And have you implemented it? Could it be added easily to one of the pocoo libs if not? Apologies for babbling. -- Aaron Watters === http://www.xfeedme.com/nucular/pydistro.py/go?FREETEXT=coherent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
