Download
2016-03-27, 10:57:48
All data goes in data it is how we handle undo and archiving and permission checking and if ever versioning.
Although we allow theme editong i dont want to have a third place to store And edit user data it just becomes too complex.
3.4 already has support for abstracted components, they are called collections and it is how i abstracted components into snippets, i decided to make it scalable, so a plugin would have no problem doing this with barely any code.
I think integrating it with the existing uis and adding a unique flag or filter would be easier to use.
Not sure i understand about php scripts, is this something for theme devs only, like widgets? Or content inputs like components.
Themes already do this manually, they modify the components xml insert their components, and check if they exist etc. I want an interface for that, so core knows whats what. Then we can have standard ones that are usable across themes. A theme says HI GS I USE THE FOLLOWING THINGS AND NEED THEM DEFINED. Gs then provided a ui interface for the user to edit them. They can optionally have default stuff in them, we might even have core components that are read only or hidden or per user, who knows..
so my bootstrap theme says i use a carousel, it has this parent div with these classes and three divs with these classes inside it, and provided the template, this is not as advanced as tokenized widgets, but maybe that can come later, as components will also prpbably eventually get arguments.
Although we allow theme editong i dont want to have a third place to store And edit user data it just becomes too complex.
3.4 already has support for abstracted components, they are called collections and it is how i abstracted components into snippets, i decided to make it scalable, so a plugin would have no problem doing this with barely any code.
I think integrating it with the existing uis and adding a unique flag or filter would be easier to use.
Not sure i understand about php scripts, is this something for theme devs only, like widgets? Or content inputs like components.
Themes already do this manually, they modify the components xml insert their components, and check if they exist etc. I want an interface for that, so core knows whats what. Then we can have standard ones that are usable across themes. A theme says HI GS I USE THE FOLLOWING THINGS AND NEED THEM DEFINED. Gs then provided a ui interface for the user to edit them. They can optionally have default stuff in them, we might even have core components that are read only or hidden or per user, who knows..
so my bootstrap theme says i use a carousel, it has this parent div with these classes and three divs with these classes inside it, and provided the template, this is not as advanced as tokenized widgets, but maybe that can come later, as components will also prpbably eventually get arguments.
