Totally on both points. The simple system with great API will allow for some simple GUI for adding forms, and the more controlled method that jcubic and rg1024 propose. I like that type of design massively!
Jon On Tue, Feb 28, 2012 at 12:53 PM, Christopher Adams <[email protected]> wrote: > I really like the idea of having forms as just another markup. With Aiki > widgets I can easily get any kind of output I want, but with forms I have to > accept whatever Aiki gives me. I'd like more control over what the form > looks like, where the data comes from, and where/how it gets inserted back > into the database. > > On Tue, Feb 28, 2012 at 2:33 AM, Jakub Jankiewicz <[email protected]> wrote: >> >> And something from completely different: about forms I think that the >> way it can be fix is to remove aiki_forms table and change everything >> into a markup >> >> (form( { data right now in database } )form) >> >> the code will be almost the same, only first few lines will change. and >> instead that weird pipe and colons it will be normal JSON. > > > > Oh, and I believe Roger! > > On Tue, Feb 28, 2012 at 5:02 AM, Roger Martín <[email protected]> wrote: >> >> Disagree. Sites, views, plugins, engines, translations, new config class, >> can't be acceded by old admin. Version 0.9.0 >> is truncated until we have a new admin. We need it. >> > > > Christopher -- Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳ irc: rejon +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
