Last call for 2.5 feature wish list

Hi all,

 

Here are the feature wish list so far sent in by you all on my call for change requests.

1. A new GUI design with a new menu system and a new advanced tree with rightclick and draggable features. This is big but perhaps we could manage it now.
   
2. A translation GUI which lets you have two languages between each other so you can read the original as you translate. A fun feature would be to include a translate through babelfish or similar
   
3. A validate html-feature from the structure view and from content version view.
   
4. A label system that can be managed from management tool and where you can add new languages as modules dynamically. Would also like all images containing text to be replaced with css-controlled classes or dynamic rendering to simplify language handling.
   
5. A lot more usability features that makes it easier for end users and developers.
   
6. A trashcan feature.
   
7. On my part, I'd like to see a more lightweight UI based on full CSS, frameset is just a pain, we can't bookmark any pages.
   
8. The most important issue for InfoGlue is to widen its user base. For 2.5 I would therefore like to see improvments concerning usability issues. Improving usability is something I consider cruscuíal for widening the InfoGlue user base. I would be happy to provide Mattias or any other developer with a list of usability issues collected from ”my” users.
   
9. On another note I would also like to suggest that InfoGlue.org is developed. What I miss is documentation. I also miss a road map for the next release. Maybe examples of best practice, etc.
   
10. Export/import: for our purpose, we have to work on that part. We want to move structures versions, contents versions, etc from db to db, with replacement/merge system. Maybe, we couldn't do that with the actual functionality. We plan to work on this. We clearly prefer to do this inside a global community plan to improve IG. To not disturb the head development, we could work on specific CVS branch?
    
11. Ordering site nodes: we have developed a functionality to manually order site nodes (structures). It's working and we can submit it to community.
    
12. Repository fallback. A repository can be parent of another (this feature exists). To fulfil our specific integration of IG in our system, we are working and implementing structure and content inheritance between repositories.
    
13. Upgrade and cleanup all library. For example: castor 1.0, Servlet 2.4, JSP 2.0 + taglib 1.2 (current taglib implementation is 1.1 style), hibernate3, etc
    
14. Change persistent framework to Hibernate
    
15. Impove cache update system
    
16. Intergrate Search engine to both CMS and deliver
    
17. JSR 170 support

Please send in comments and more ideas ASAP as we plan on having a developer meeting pretty soon deciding on what to include in 2.5.

Best Regards
Mattias Bogeblad