I can cleanup the php gunk + mod_python if there is a place to put it… In other words from where should the gunk used by the jsonrpc examples be hosted? I don't have a site for them; may/should they be hosted from a separate git repo on pyjs--that need not be updated much.
--Jeff On Jan 24, 2012 12:01 PM, "lkcl luke" <[email protected]> wrote: > On Tue, Jan 24, 2012 at 5:09 PM, Michael Yang <[email protected]> > wrote: > > hey - Is anyone working on HTML5 directory upload? I was thinking of > > branching this but didn't know if it's in GWT or standardized enough yet. > > So far it only works in chrome and you need some plugin in firefox. Not > > sure of its status in IE but google relies on this functionality for > google > > docs. > > yeah it has to be around somewhere.... > > aw my gawd.... do a quick search and you get this: > http://code.google.com/p/gwt-upload/ > http://code.google.com/p/gwt-examples/wiki/DemoGAEMultiFileBlobUpload > http://code.google.com/p/gwtupload/ > http://gwt-ext.com/forum/viewtopic.php?f=6&t=1581 > > dozens of the bloody things. > > ok, the rule regarding "plugins" is this: if you want to add > something that supports a feature but adds a "plugin" to provide the > missing functionality on other platforms you MUST NOT add the > proprietary or the binary-compiled plugin to the pyjamas code-base. > > you CAN however provide a "download script" - see > examples/employeeadmin/download.sh - which people must run (on their > local system) in order to obtain the plugin. > > we have a number of places where ridiculously-large pee aitch pee > scripts are being cut/paste copied across multiple examples and this > isn't really on: those are libraries that are maintained and bug-fixed > by other people, and should *not* be included in pyjamas. > > also, you _should_ try to make sure that, where practical, things > work with the various pyjamas-desktop ports. if it's not even > remotely possible i'm reluctant to have it in the main pyjamas > libraries but it could go into "contrib". > > l.
