In the spirit of moving more logic to the client I have been working on this:
https://experts4solutions.com/collection2/default/examples
https://github.com/mdipierro/collection2
This is not a standard procotol. It is inspired by collection+json but the latter is too verbose for my taste.
The idea is to give the DBAPI object the ability to acquire a form template and a grid template and generate its own form which can work with or without ajax.
Thoughts? Comments? Suggestions? Does this file belong to pydal? it not really web2py specific.
Massimo
--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
DALAPI?
DALPI?
DAPI?
APIDAL?
APIMaker?
APIGenerator?
APIHandler?
For me it is another piece of the puzzle but I do not know what will come out form the puzzle.
In my ideal world I would simplify web2py and move more stuff to the client.
w3 was an approach from the client side.
this is an approach on the server side.
My short term goal is to come out with a reduce version of web2py (faster, leaner core, less contrib packages, no forms and grid server side) and have forms and grid customizable in html and talking through an API.
My longer term goal is be able to have a single api and point and build the app as a finite state machine where the state sets api policies. Each node of the machine contains widgets and each widget has its own template. But small steps.
Massimo