Hi!
Results from today's brainstorming session...
Style Editor
============
## Requirements
* Show list of elements for the MidCOM component whose style is being
edited
* Develop naming conventions for elements:
- namespacing
- check if we can use dots and dashes inside style name
* Style editor should be connected to the site hierarchy to enable
users connect substyles to directories, and to see appropriate
element
lists for that directory
* Make importing "web designer" -made styles into Midgard easier
## Style editor
* "Set style" button in edit-this-page
- "Set style to directory" editor in AIS
- Selection list of available substyles and option "create new
style"
- Checkbox for making the selection inherited
* "Edit style"
- List all styles of the pages' style stack, and their element
- Clicking element shows its default value in <pre /> and
provides textarea for changing, which will create the element
into the local style
- CSS classes showing which elements have been overridden
Mockup:
de.linkm.newsticker
* show-list-header (overridden in "Edi's blog")
* show-article
template_Kubrick
* ROOT
* footer
Edi's blog
* show-list-header
## Style importer
* Import zip/tarball containing a style
- Place the HTML/PHP file as <(ROOT)>
- Upload images as style attachments, replace all image refs with
attachment URL
- Create CSS/JS files as elements, replace URLS
- Parse the ROOT element via DOM, add "mandatory" elements:
- HTMLAREA loaders <(head-extra)>, <(bodytag-extra)> or something
- Look for <div id="content-main"></div>, replace contents with <
(content)>
- Replace <title /> contents with $_MIDCOM->show_pagetitle();
- Replace appropriate Microformats with dynamically loaded
component output
- Hook hojuruku's Mambo template parser here
Henri Bergius
Consultant Partner, Nemein
henri.bergius@neme...
Midgard CMS
www.midgard-project.org
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@midg...
For additional commands, e-mail:
dev-help@midg...
opensubscriber is not affiliated with the authors of this message nor responsible for its content.