Thanks Jon, your feedback give me one idea:
why must we store aiki admin widget in database? Now, aiki admin is 'stored' in create-insert.sql - in few words a beautiful mode for editing ;-)-- and during installation process inserted in database. We can create a array for admin widget, and change parse engine for search widget in database or in hard-coded array. It's not perfect solution but means: - it easier (compared with actual sql) to maintain for aiki-devoleper: $admin["header"] = array ( "permissions=>".." "normal_select" =>".." "widget"=>"....code here....") ; You can edit admin in your ide, see results it in your browser and if crashs control-z, else 'bzr push' - a user can't delete or change admin widget. - a upgrade of aiki means a upgrade of admin. Errors in aiki admin can be corrected easily: bzr pull? - it's another way to distribute aiki apps. - for those brave man and woman who want edit admin widget, we can offer a copy to database option (and our blessings..) i'm not sure..but perhaps this simply solution can solve some of our problems. 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
