OK. I bite the bullet(s) 
.
SInce Alfresco has all its paying clients using JSF based client, there is no risk of "being abandoned" as some people seems to be afraid of. Therefore, I think that what is needed is feedback from the community to help in the migration/transition to new features. My impression is that Alfresco has no other chance that providing a migration path and, probably the "market pressure" will be to "extend 2.X" rather that jump directly into "something new and untested". So, no problem as far as 2.X interface future is concerned.
OK. Stop with "strategy" and back to "bullets"….
a) Support for "smart spaces": one of the strong points of Alfresco is its ease of customization of spaces by means of actions, rules, ftl templates and workflows (simple and advanced). I think that these facilities should be made available in the new 3.0 interface.
b) BPM Support: 2.x has out-of-the-box UI support for Advanced Workflows. Many companies use this facility for supporting its internal BPs. Similar functionality should be made available (as part of a site standard set of options? -as per wikis, blogs, …- i.e. task management?, to-do lists? pending task?). There are some feature requests asking for extension in current 2.x UI BPM support for 2.X that could be a interesting hint on what users want this functionality for.
c) Easy integration between JSF and FTL/HTML: now this is not possible out-of the box (although there is some contributed code that allows it). This does not allow a seamless integration of UI components. Now developers have to choose between JSF/Java or JS/freemarker/HTML. A little bit of 2.x JSF extension in this direction would be of help.
d) Support for "Reporting facilities". This s a new area (i.e. not yet covered in 2.X) that EVERY Alfresco installation need and provides somehow using custom freemarker reports. Some kind of standard reporting API would be of help for everyone. Maybe an approach as the provided by "Open Reports" (oreports.com) would be VERY useful since it has an eclectic approach that allows integration of Jasper Reports, Pentaho and BIRT. There is an interesting project in the forge that being very promising, has not really generated a finished option. In 3.0 lingo, what we need is a "dedicated" reporting "site" that provides access to the new "reporting API".
That´s it for now.
.SInce Alfresco has all its paying clients using JSF based client, there is no risk of "being abandoned" as some people seems to be afraid of. Therefore, I think that what is needed is feedback from the community to help in the migration/transition to new features. My impression is that Alfresco has no other chance that providing a migration path and, probably the "market pressure" will be to "extend 2.X" rather that jump directly into "something new and untested". So, no problem as far as 2.X interface future is concerned.
OK. Stop with "strategy" and back to "bullets"….
a) Support for "smart spaces": one of the strong points of Alfresco is its ease of customization of spaces by means of actions, rules, ftl templates and workflows (simple and advanced). I think that these facilities should be made available in the new 3.0 interface.
b) BPM Support: 2.x has out-of-the-box UI support for Advanced Workflows. Many companies use this facility for supporting its internal BPs. Similar functionality should be made available (as part of a site standard set of options? -as per wikis, blogs, …- i.e. task management?, to-do lists? pending task?). There are some feature requests asking for extension in current 2.x UI BPM support for 2.X that could be a interesting hint on what users want this functionality for.
c) Easy integration between JSF and FTL/HTML: now this is not possible out-of the box (although there is some contributed code that allows it). This does not allow a seamless integration of UI components. Now developers have to choose between JSF/Java or JS/freemarker/HTML. A little bit of 2.x JSF extension in this direction would be of help.
d) Support for "Reporting facilities". This s a new area (i.e. not yet covered in 2.X) that EVERY Alfresco installation need and provides somehow using custom freemarker reports. Some kind of standard reporting API would be of help for everyone. Maybe an approach as the provided by "Open Reports" (oreports.com) would be VERY useful since it has an eclectic approach that allows integration of Jasper Reports, Pentaho and BIRT. There is an interesting project in the forge that being very promising, has not really generated a finished option. In 3.0 lingo, what we need is a "dedicated" reporting "site" that provides access to the new "reporting API".
That´s it for now.
