From: "Henri Bergius" <[EMAIL PROTECTED]> > Marcin Soltysiak wrote: >>>1) Create a script that MidCOMizes them >> >> That would require some addotional components to be invented. On one >> hand it's good - the more components the more features we can >> advertise. But on the other - it takes time. > > Another point to consider here is that after "MidCOMizing", your > sites will no longer be custom-made, but instead using a shared > and commonly maintained platform. > > This means that ideally it will be the last conversion hassle you have > to face as from then on you can live easily with future MidCOM versions, > or even convert to other CMS using Exorcist if required. MidCOM's > content model is the defacto standard, so there will definitely > be conversion tools for it, no matter how much Midgard's structure > will change.
Good point. > >>>4) Develop "old school" article and topic management add-on for New >>> Aegir(TM) >> >> Isn't OB a tool that lists objects in their hierarchy with all >> properties like title, author,revisor and parameters? > > Yep, and present the data in format editable with datamanager. To > make it more Aegir-like, we might add some DHTML to make Aegir-like > tabs out of the <fieldset>s of the editing form. I think it is the matter of amount of data when you access a raw object with all of it properties and parameters than making anything more Aegir-like. For example, I got articles with dozens of parameters containing technical specifications of a product. Entering an editing form of such aricle would require a lot of data in one screen. On the other hand some parts of data could be hidden in DHTML div's (Aegir-like) to save space and make editing less confusing. Other idea is to have separate pages for "main" parts like names, titles etc. and separate for the other stuff. Solt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
