Blueprint changed by Jakub Jankiewicz: Whiteboard changed: Apps are very useful in aiki (captcha, imageviewer, installer). Some apps (admin for example) can sliced in apps and converted in sites: admin, login, and welcome screen. This allow a better separation between user widget and aiki widget. All this apps (as they are sites) can be easily disabled if there is an conflict with user widget, or can be moved (with some restrictions) to other url, only changing the site prefix. Aiki can detect in url if a app must be 'load' (again as site) The restrictions are: - use route for internal link, - never use the widget id in widget: instead, use the widget name - javascript and other auxiliary code must work with this changes. The apps withouts widget don't need to be converted to sites. Upgrade / import aiki apps ------------------------------------------ - As widget of apps have some restrictions if will be possible change the id field, so widget can be added to table aiki_widgest and then the field father_widget can be corrected. + As widget of apps have some restrictions if will be possible change the id field, so widget can be added to table aiki_widgest and then the field father_widget can be corrected. Embeds apps --------------------- - Despite apps are sites they could be embed in your site, with a new markup called (apps(...)apps). + Despite apps are sites they could be embed in your site, with a new markup called (apps(...)apps). For example, if you have a apps for managing comments you can create a widget in yours ite with display /moderator/ and in the widget code add the markup. (apps(comments,moderator)apps), Aiki will load the apps called comments, who must shift the word moderator in url. For example a incoming route as moderator/browse or moderator/delete/2 will be converted in browse and delete/3. + + #### + + I think that is not good idea to have this as sites, it would be nice if + login is shared by few other sites, but creating it as a site is kind of + wierd. And I think that sites should be separated from each other have + different users, different widget and different apps. + + I also think that there should not be distinction with user and aiki + widgets they all should be users widgets, Admin (the user that edit a + site) should have full access to it. If Admin will be app it can be + hidden when editing widgets that belong to the site, but users (admins) + should be able to edit apps if they want they should be fully editable, + when I write Admin Panel (really soon - I'm working now on OCAL and I + will fix some bug that may came up with update from old Aiki) I will + allow users the edit everything nothing will be hidden, + + it's the same as with UNIX system you can edit everything nothing is + hidden if you're root. If you want we can use ModuleGOD (maybe rename it + to something else) for that we can have interface that will allow + ModuleGODs to do what ever SystemGOD will allow them, and by default + they will be able to edit only a one site widgets. + + Also idea we can make SystemGODs users for all the sites and other users + for one site. + + @jcubic
-- Apps and sites https://blueprints.launchpad.net/aikiframework/+spec/apps-sites _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
