Well, the client-side web2py-like code is not as new as i thought. I'll check the slice, it looks good. However, instead of a web2py- slice, wouldn't be a good feature for web2py to expose script tools like those by default?
On 16 feb, 11:21, simon <simo...@gmail.com> wrote: > I think it would be helpful too. I try to minimise the amount of > clientside script. > > There are some tools I found > here:http://www.web2pyslices.com/slices/take_slice/8 > > On Feb 16, 1:22 pm, Alan Etkin <spame...@gmail.com> wrote: > > > > > > > > > What if web2py provided an in-the-middle interface to web2pyify jQuery > > features and, where possible, unify the usual server-side command > > syntax of the web2py apps? > > > I am aware that web2py currently supports a set of javascript > > functions that handle jQuery and other javascript-related stuff, but I > > am talking about a more extensive set of javascript tools, as for > > example. > > > -accessing safe data in storage objects client-side. > > -query the database with a client pseudo DAL instance > > -perhaps javascript helper and validator classes? > > -cannot think of anything else by now, but surely there has to be > > more. > > > Note that this not a enhancement request or defect report, I just > > wanted to share the issue to know if this would be a good feature or > > not, wheter this is or is not suited for the framework design, or if > > this kind of features would follow good software practices or it > > wouldn't.
