> A question for you: Why are you interested in Aiki? What is it about the > current aiki that is uniquely different from other frameworks and php > engines? Is it quick access to sql? The approach to building widgets? > > Code all information in sql is ..HELL, (i'm agree with Nathan). but code all information in php files is not a good solution. If you a library for news, its better have the templates for news list and single new in sql. The admin can easily configure the new module, and adapt them to new site, without touching the code.
In my work we use wordpress for some projects: we make the entire site without a IDE,using only wordpress admin. I'm sure that wordpress developers and theme developer use a IDE. > In my opinion, the system for building widgets is completely busted > because there is too much hidden structure and information inside of the > database, and the way for setting up routes requires changes in too many > locations. Then, as for aikimarkup and the use of our own custom > minilanguage, its just too difficult to get other people involved. We > should definitely be using off the shelf php or simple templating system > for our system, and try not to invent a new language where possible. > > Agree, but we talk about it time ago: templates for main layout, use area (now aiki have two areas: head and body), delete widget parent, simplify routes, > > I'm not against each approach doing a bit more exploration, and I wonder > how we can collaborate or share approaches. Soon though, we need to select > the best approach, and plow forward. > > We can mix the two solution in two ways: - convert mustache in a engine. - use the step as arquitecture for new slim-mustache. Meantime i'm working in a new aiki. Roger
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
