On Tue, 3 Jan 2012 17:55:57 +0800 Jon Phillips <j...@fabricatorz.com> wrote:
> I think its better to not include because: > > * It shows that we mean simplification if you have types it will be more complicated that one widget type > * will help to enforce using hierarchy with widgets > * will help to enforce inheritance with widgets We can force it with proper Admin Panel > * will help developers think more about using aiki to build APIs, > feeds, and other non-html web apps It's suppose to be Web2.0 framework > > I think the list can go on...I would much prefer to see a generic > widget, and then implemented types of widgets that could be more > specific... the option is to have CSS added to the widget aiki_widgets 1----------1,0 aiki_styles and admin panel will have option to add CSS. I want CSS to be part of a widget not separated style widget. There can be 2 types of widgets html and raw. The raw will be like widget with custom output, but it can be the same as custom_output filed true/false. If you want to force on-html web apps then we should have Content-Type field with drop down. So users will select application/json or appication/xml (it can be autocomplete so there can be all Mime that are in RFC). And it should be in aiki_widgets table. > > Jon > > 2012/1/3 Jakub Jankiewicz <jcu...@onet.pl>: > > I think that we should keep CSS. if you design a page is good to > > have both content and css that is associated with that widget in > > one place. > > > > On Tue, 3 Jan 2012 10:48:48 +0800 > > Jon Phillips <j...@fabricatorz.com> wrote: > > > >> Isn't css just content? Seems to me that there is no special need > >> for css, if can have relationship between widgets. > >> > >> I still think type good, for type of output, as in header....not > >> sure on that one. > >> > >> URL/route and/or view, are they the same? rg1024? > >> > >> Jon > >> > >> On Tue, Jan 3, 2012 at 2:45 AM, Jakub Jankiewicz <jcu...@onet.pl> > >> wrote: > >> > Blueprint changed by Jakub Jankiewicz: > >> > > >> > Whiteboard changed: > >> > - I think that widgets should have two fields (except config > >> > ones) Style > >> > - and Content and no types. ~~~~ jcubic > >> > + jcubic> I think that widgets should have two fields (except > >> > config ones) > >> > + Style and Content and no types. > >> > > >> > - In my engine i allready make widget with only five fields: id, > >> > parent, > >> > - site, css, content. > >> > + rg1024> In my engine i allready make widget with only five > >> > fields: id, > >> > + parent, site, css, content. > >> > + > >> > + jcubic> What about URLs > >> > > >> > -- > >> > Vastly Simplify Widgets > >> > https://blueprints.launchpad.net/aikiframework/+spec/simplify-widgets > >> > > >> > _______________________________________________ > >> > 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 > >> > >> > >> > > > > -- > > Jakub Jankiewicz > > twitter: @jcubic > > www: http://jcubic.pl > > > -- 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
