Hi, All the points made have been excellent. When all of this is brought together and the work done, we should end up with an excellent product.
Just to clarify point 5: >5. Evaluate, please. Aegir calls attachments as images in few places but, >nevertheless you can do anything with attachments no matter if they are >calles images or not. I don't quite get your point. The one is more of aesthetics than technical. Most of the people adding content have very little if any technical experience of designing pages. They use the HTML editor exclusivly to maintain and add new content to the multitude of sites we run. Confusion often arises over this one as people tend to separate images and documents mentally and get a little lost. So the simplest solution would be to change the 'insert image text' to 'insert image or document'. The other thing of course when you click on the image of a document is that it will insert the URL ok, but with the default document name. I have shown them several ways to change the text of the URL from the editor, but having to do this is one of the biggest complaints. What would be very useful to have a very simplified document manager as part of Aegir where documents are listed by file name, file date and displayed name, with a simple way of editing the displayed name (maybe when the DM opens, the names are editable in a form with a save names button at the bottom). The listing should be just that, a list and not an icon view which makes finding the document easier. It could be that it is simply a second view on attachments with images listed as well? Just ideas. I agree that everything should be under one roof so to speak - a complete administration and editing package. For Aegirs future development (and survival), it must keep up to date with the state of Midgard/MidCom to enable future developments to be made easily. Developments at the moment seem to be like trying to get a square peg into a round hole rather than an easy blending of the base Midgard/Midcom platform. Cheers Mike. -----Original Message----- From: Marcin Soltysiak [mailto:[EMAIL PROTECTED] Sent: 27 April 2005 10:28 To: [email protected] Subject: RE: [midgard-user] Future Aegir Development Hi, > - The HTML Area interface to be brought up to date and to be > XHTML compliant > (and to be given a bit of an aesthetic makeover) 1. There were some issues about HTMLArea discussed a while ago. 2. HTMLArea breaks javascript code in content 3. If any, should be the same as MidCOM uses - why double it? > - Site wide defined maximum age for news and articles i.e. > when a page is > created or updated a date is stored that reflects when the > page will be out > of date as defined by a configuration setting (rather than > through approve). > Out of date pages would be automatically suspended and a > holding page put in > place. The owner of the page and the site administrator would be > automatically emailed a set number of days before the page is > suspended and > again when the page is suspended. Keeps people on their toes and the > content of the site up to date. 4. That sound more like Editor UI feature that Admin one and seems dependant on local policy of content aging. Besides, I think it would require some midgard-core changes. > - Image and document management needs to be refined a bit. > At the moment we > treat all documents as images and this poses some issues, > especially with > the renaming and organisation of documents. 5. Evaluate, please. Aegir calls attachments as images in few places but, nevertheless you can do anything with attachments no matter if they are calles images or not. I don't quite get your point. > - Easier way to link between internal pages to avoid > duplication of a page. > Page links at the moment have bee depreciated haven't they? 6. Hard to achievie. When you use MidCOM - a well known system, you can use its hooks (or simply sitemap component) to create a sort of list of pages to pick a URL from but in any other, individual application you would need to define your own hooks. The advantage of Midgard is that it never make its user to use a predefined way of building sites, so you can have as many content control application (like MidCOM) as you can invent. However, in a way it's also a vice. > - Improve the efficiency and speed of the Aegir core? Faster ways of > displaying the lists of pages and site groups etc? That is true. I think HTMLTree would make a great performance boost. > - Anyway to take ownership to the granularity of a single > page, rather than > a topic? You mean article? Well... it could be done basing on author field. Anyway we need an answer on one question. What should it be? We now have a great editor's UI that does all principal tasks common sites need. As Torben said, it is a bit uncomfortable to open two UI's - one for content editing and one for layout and system configuration. I'd said that we need to make Aegir an complete Admin UI that provides a full access to any object in raw. This way, if you want to use MidCOM you just prepare styles and local component configs and schema databases etc. If you want to run your own application you got chance to alter all objects in a way you want/need. BR Solt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
