[EMAIL PROTECTED] wrote: > Emile has considered solutions for this problem but hasn't > identified a WYSIWYG publishing tool that definitively addresses the > problem of integrating in a way that takes advantage of the Style system. > Is the solution to integrate a tool into Midgard, build an integrated tool > find a way to export, edit and import the generated html? I'm not capable > of answering the question. Sorry! Any of those solutions would be a boon. But as you said, I haven't yet found a tool that matches the midgard philosophy, so for the while being, online editing is going to be the main way. > I'm told that Aurora has a GPL Java editor laying around, developed in > house. I've asked about the tool but haven't recieved any useful > responses. I know other people have looked at available tools that could > be integrated but nothing has ever come from these efforts. I've been working on a module that will accept content from frontapge express. It's nowhere near finished, and the end result (being editing content with FPE) will still be clunky. > If 1.4 is going to compete with E-Grail in the Style management > realm, we'll need to develope the solution independently of Aurora. How does E-Grail do style management anyway? Is it inherently different from Midgard? > Solution, part1; an Admin Site, PHP, interface to manage a MySQL dump that > encapsolates the relevant style-element within an html template > (<html><body><[style-element]></body></html>) allowing it to be opened in > an independent editor? (Graceful because you can use any editor you want) > > Problem; if the style-element is contstructed on the fly using CSS > to format, then the element to be edited doesn't have any formating tags > in it. To produce a stye-element that is comprehensive for DreamWeaver, > will pollute the style-element with formating tags that must be cleaned > out prior to the update. > > The dump is written to the file system and transported to client localhost > via anonymous ftp. (not graceful) > > Solution, part2; the edited style-element must be written back to the > database. > > Localhost, client, uses ftp to upload the edited style-element, replacing > the original dump on the server. (efffective, not graceful) > > Updating the database; style-element must be cleaned of formating > tags before the edited dump is written back into the database using > Midgard's authentication and SiteGroup ids. Is that the xml guid problem > we see discussed in reguards to Repligard?. > > Problem; HTML could be cleaned with a Perl script but one > webmasters dirt is another's gold. > > Solution, option for clean all formating tags or clean none. (graceful) > > If this scenario is useful then I imagine it could be incorporated into > the 1.4 administration site. Then there's filetemplates. Easily editable, no import/export issues. Emile -- This is The Midgard Project's mailing list. For more information, please visit the project's web site at http://www.midgard-project.org To unsubscribe the list, send an empty email message to address [EMAIL PROTECTED]
