From: Aplaws D. L. <apl...@li...> - 2009-05-25 10:17:25
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7408424 By: terry_permeance A few random(ish) observations: 1. Aplaws was too hard to build before. It's now pretty simple with ecdc. Next steps would be to migrate to maven and to embed derby. 2. I think we should replace the output applications with Liferay (or equivalent) which does a much better job at layout, portlets, etc. By "output" I mean the content, navigation and portal applications. 3. The content center needs to be rewritten in a more productive UI framework. GWT might be a good option given Bebop is already Swing-like. In short, Aplaws is pretty solid from a technical perspective, even if it doesn't use Spring, Hibernate and the latest and greatest frameworks. I think the RedHat/Arsdigita/Aplaws community have done a great job. >From a non-technical perspective, Aplaws needs something to differentiate itself from the open-source crowd [http://java-source.net/open-source/content-managment-systems] and attract new users and developers. It could be government compliance but it could be something else. Alfresco + Liferay integration is pretty basic. Aplaws could position itself as a portlet-based CMS. Regards, Terry ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |