> * Model to cover adding features to the list pages, i.e. the main Pages, > Snippets and Layouts views, e.g. the existing ReOrder and CopyMove > extensions. > > * Model to cover adding features to the editor pages, i.e. editing > pages, snippets and layouts. Maybe let it select which internal > function to allow the enhancement to show on.
This sounds good on a high level, but how do you go about actually implementing it? Is this a singleton model? one object covers the "page editing interface" and you manipulate that object to change that interface? Or, can you instantiate new page editing interfaces How does this "Model to cover adding features to the editor pages" provide hooks into extensions. If I were to create a "calendar" extension for instance, I would want it to be page type. And when you select calendar as a page type I should see a different page editing interface. And when you click save, there needs to be certain callbacks to my extension. How should all of this work... it's not clear. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
