I agree with barry. If one is going to inherit a widget, they should get
the whole thing and not just the content. It makes sense to me.
If this is undesirable, then there should be an option or a different
type of inherit-all or something.
Conceptually, the logic that inherit means give me everything, makes
total sense.
Without this, it essentially means you have to think more high level,
rather than clear at the widget level, when you are forced otherwise to
think small with widgets, or you have to duplicate efforts, which is
silly.
Re-opening...2 against 1 unless I see a better rationale.
If anything you should be able to override the CSS of the widget, just
like you can do with the SQL. That is more rational.
** Changed in: aikiframework
Status: Won't Fix => Confirmed
** Changed in: aikiframework
Assignee: (unassigned) => Bassel Safadi (bassel)
--
You received this bug notification because you are a member of Aiki
Framework Admins, which is subscribed to aikiframework.
https://bugs.launchpad.net/bugs/675060
Title:
css in parent
Status in Aiki Framework:
Confirmed
Bug description:
need some solution for having to put widget css in the parent for inherited
widgets. seems like with the actual widget is the right place for the CSS to go.
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework.admins
Post to : aikiframework.admins@lists.launchpad.net
Unsubscribe : https://launchpad.net/~aikiframework.admins
More help : https://help.launchpad.net/ListHelp
