Hi folks! some ideas about Jakub blueprint:
1) I do not like the current style of coding aiki admin: there a lot of inline css, javascript, and is very difficult to mantain and debug. I prefer a application that work with minimal javascript and then add js and ajax like a layer to improve usability and speed. For example: the list of widget is visually very good but use a separate file and a lot of javascript to see result..i prefer a widget and a little of not intrusive jquery. Jakub propose user jquery and jquery ui: very good, but use it in correct way. We have few developers (see https://launchpad.net/aikiframework/+topcontributors), so we must prioritize maintainability and readability of code. 2) some ideas of blueprint are were good: the google interface is awesome. We need it for aiki. 3) design interface thinking in task: for example barry's interface is very good for editing widget..but how can we maintain a site with it? where is logs, events, stats, user administration, upgrade, update, translation, plugin, site, view, language, config, users. Top menu can have 5 "task options": - to maintain aiki: config, upgrade, update ->preferences /system ? - assets: plugin, assests, extensions -> complements? - to see how aiki work: logs, events, stats, who is on, cache benchmark -> ? - to create site,views, languages and translation -> sites - to edit a site. -> edit sites () - user managment? -> users? other questions: a interface for complicated items will be complicate in 99% of case. Perhaps if we want an easy editing, first we must clean widgets definition. 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
