Yes, totally agree with all these points. And agree, too, we need and want you to help bassel.
More below... On Sun, Feb 26, 2012 at 5:45 PM, Roger Martín <[email protected]> wrote: > hi bassel! > > The first time i worked around widget and engine i made the same mistake: > when i wanted to push changes i needed merge with revisions. A extra work, > and probably, i overwritten some bugs fix. Now, i'm using a hack that allows > aiki work with old and new engine. At the same time i am making the new > engine, i can correct and improve old engine. > > So, if you want work; > - over form: add a new markup called (form( --as john suggested. > In this case, please, include it in engine2: i have some ideas about code > but no time to explore them. Roger, what file is in this in and/or should there be a new file created for this work? So you view the new form code as a new markup that would be parsed and then connect with another class. I like this idea that is not UI dependent. I think the more clear the markup/code, the better for making updated forms. > - over admin: make a site called admin (i already have one for testing > purpose) Ok, how is this done? Or, maybe your new admin code has this already? > - over old aiki engine: Use the new engine as start-point. I totally agree with this, lets work out the new engine. If bassel wanted to create a new/different engine, what file would he create? Cheerz! Jon -- 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
