>Why should we mark them? If there is some warning mark, visually you will in easier way to know that this extension is not compatible with AOO4.0. We can even more. We can (near that mark) add button for link to the version which can run on AOO4.0. Where we can add this marks, buttons?Before you actual go inside some of extension's page, you have page where is some kind list of extensions, what serve as preview. I think that this page with list of extensions, given by search engine, is not page of authors of extensions, so I think that we can freely add this helpful marks, buttons etc. Purpose of this is to save time for end-user when he/she want to find appropriate extension. But, if somebody miss to see marks or he/she using direct link to the author's page of extension, your idea to having pop-ups will solve the potential problem. With this pop-up dialog we will get good warnings and solver system for end-users.
>Who's going to do those changes? That is next step of this discussion. If we have consensus about this basic steps (how we want to manage this problem) than next step is to see who want to take responsibility for that area. Who have skills, time and good will to make changes on site "Extensions", and who want to made corrections inside extensions (if licence of extensions permit that). Regards, Wlada --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
