I'm not nearly as concerned by the technical aspects of this as the interface. We have to make it easier and keep track of for developers. That is far more important than any technical concern.
bt On 12/25/10 4:39 AM, Bassel Safadi wrote: > so in aiki the reason for a user to use inherit instead of just building > the site structure to include the desired widget in its place in the > tree is: to allow multi uses of the the widget with different sql and > css, in sql case it get inherited by default unless the user overwrite > it, but it's much harder to change the css on widget call. for example > in ppl app the inherited widgets are not used by there own without > inheritance but they might be used in the search function for example, > where the original widget has its own css and sql then it get inherited > on ajax search call with different query, but the css is not touched > because there is the page is not refreshed. > -- 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 : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
