Hi Ilario,
I hope I am not mistaken and the thing under consideration is whether to use portal engine or portal framework.
I guess the answer will be: it depends.
Portal framework is a "vertical portal". At any point in time there is only one page (that you can customize) with coplets. It is true that there is a nice interface for adding and removing coplets and as well as for user management. But it lacks a lot of very useful features: support for multiple tabs, skins, extensible authentication mechanism.
Portal engine is a fully functional portal, not limited to just a single vertical layout. If in your project you will ever need multiple pages with different coplets presented, it would be reasonable to employ the portal engine.
Of course, there are some limitations of portal engine. As you said, it lacks the user management and coplet customization support, but these functions can be implemented with a bit of work (user management is easier to implement, coplet customization is slightly harder).
Sincerely, Nick.
javascript wrote:
Hello list,
I am starting to work to a e-learning platform for a test plan.
The structure will use the coplets and I am trying to use the two examples included in the documentation (portale and portale-portal-fw).
The second example it is more complete but it seems to be slow, the first one seems better, but it is incomplete (there is not a management console).
The plan is much simple (Portal+CMS+SCORM) and not there are members of JSP (JSR168 is not important).
Can someone suggest to me if it is better to begin with portal or with portal-fw?
Thanks
Ilario
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
