The summary of those blueprints was not send to mailing list. So: ---------------------------------------------------------------------- Aiki widgets should be organized into tree
https://blueprints.launchpad.net/aikiframework/+spec/widgets-tree Current widget are ordered into a list, which is brain damage since html have a tree structure. In Aiki sites (like on sharism) there are shit like this - one widget have begining of html <div class="content"> <div ....> <div> and another at the end have closing those tags. It can be implemented by introducing [children] marker where children widget will be put into the parent. ---------------------------------------------------------------------- Aiki should have tamplates (and this was not send at all) https://blueprints.launchpad.net/aikiframework/+spec/aiki-template There are lot's of pages where there are bunch of widgets that are created only for layout and they are on all pages, if a page have 10 widgets like this one and you want to add anther page (one widget) that use all this layout you need to create urls for all 10 widgets, which is just stupid. Aiki should have a way to create widgets parent/children - organized into tree (proposed in different blueprint) - that are only for layout like footer, header sidebar etc. set them as template (only the root parent) and then when you create a widget you can select a tamplate - which will be the same as you add new url for all those widgets. -- Jakub Jankiewicz twitter: @jcubic www: http://jcubic.pl _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : aikiframework-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp