Page linking or dynamic content loading?

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
7/15/2009 12:59:43 PM
Gravatar
Total Posts 8

Page linking or dynamic content loading?

My application is an online training app.  Each class is going to consist of a new Feature (module).  I'm breaking up the sections of text into HtmlModules that I can place on the page.  What I need to do is to have a page of text (one or more HtmlModules) and have a Previous and Next button so the user can navigate.  In MojoPortal, is it better to dynamically populate the content in a single page (or the SiteModuleControl) or have a slew of pages that link to eachother?

Thanks,

Evan

7/15/2009 1:19:18 PM
Gravatar
Total Posts 18439

Re: Page linking or dynamic content loading?

I think if I were approaching this, I would not think in terms of a separate module for each class, nor do I think using the existing features and linking together is going to result in a really nice training app experience. Modules/Features are meant to be self contained they are not designed to build apps by orchestrating across them. That would be a very complicated and fragile approach, maybe possible but not what I envision atall for feature development.

What I would think in terms of is making a module that plugs into the page which is basically the list or catalog of classes. Then the user click the link and it goes to its supporting page where you implement whatver you need.

I would think in terms of existing e-learning standards like SCORM and build my courses according to SCORM. If you do some googling for "ASP.NET SCORM" you should be able to find a number of things, also search codeplex for SCORM. One open source one I know of is DotNetScorm.

So basically I'd implement a SCORM course ware player and then implement the class/course content as SCORM so it can run in the player.

Hope it helps,

Joe

7/15/2009 1:30:06 PM
Gravatar
Total Posts 8

Re: Page linking or dynamic content loading?

Thanks!  I'll check it out.

Evan

You must sign in to post in the forums. This thread is closed to new posts.