"Abandoned" is a bit strong; it'll still be supported. The feedback we've had is that customers and partners much prefer us to build APIs to enable remote clients to be built (of which Share is one) rather than tying everything in to one monolithic web application.
But explorer is a good piece of software. Just lacks more use of Ajax an be skinnable (for branding reason). Maintaining both is a good idea. All the other Alfresco clients that I know about, lack the support for workflow.
Perhaps, but "maintaining" is very different to "refactoring". Again, our priority is on delivering the Repository as a platform rather than a product, hence the focus on APIs rather than UI.
And by maintaining would you consider removing mootools in prol of jquery (respect other js libraries), allowing full support of richfaces? many of Gavinc ajax components had to be replaced (category picker,etc..)…but I think it worth the effort.
richfaces would add easy Ajax support and cool components for a web 2.0 UI.
I think you know the answer to that :wink: That's definitely "refactoring" rather than "maintaining".
Remember: Alfresco Community is 100% Open Source… if you contribute the changes to the product, you'll get full credit and help make the product better for the rest of the community.
