2.0 Roadmap Thoughts

I made some progress tonight converting from Paul Wilson's MasterPages to the built in ASP.NET 2.0 MasterPages. I got the Default.aspx page converted and working on Windows, it was pretty straightforward given that Paul modelled his version from early specs for the real thing. Now it will just be a machanical repetitious task to update the remaining pages and skins, but not tonight, I'm spent.  I tested on mono at demo2.mojoportal.com, it did load the MasterPage but something went wrong loading the rest of the page content as you can see. I'll follow up with that and see if I can pin down the problem.

I've been getting very excited learning about the Web Part framework. I know I said I would pace my changes with mono support but I think what I will do is keep a separate branch in step with mono support until the mono support catches up so I can move forward taking advantage of 2.0 ASP.NET features. Some of them are just too compelling to wait and besides it will take some time to make the changes and figure out exactly how I want to do it. Right now I'm thinking the Web Part model will replace the existing implementation for Feature Modules.

I definitely will try and help implement some of the missing mono features if I can, or at least provide testing and feedback for the guys who are doing it.

Posted by mojoPortal Tuesday, January 3, 2006 2:39:20 PM Categories: Development Releases

Comments

Paulo Aboim Pinto

re: 2.0 Roadmap Thoughts

Tuesday, January 3, 2006 6:52:03 PM
Hello ....

I've been reading all your effort to export the mojoPortal to .NET 2.0 and using the Master Pages of the FrameWork.

I do have a "some how" Content Manager System to manager my WebSite. With this CMS I can load WebUserControls managed by information in a MySQL database. In my WebPages I create a Region, where the SkinManager load all the WebUserControls defined to her.

With this I can change the database and other WebUserControl can be loaded in the same place. I can change my skin, locating the Regions somewhere else in the page and everything works in tha same way.

I would like to know who do you manager to load the controls and load User Costum Controls made by any one that implements your CMS.

Hope we can help each other...

tkx in advance
Paulo Aboim Pinto
Odivelas - Portugal
Joe

re: 2.0 Roadmap Thoughts

Wednesday, January 4, 2006 12:56:39 PM
Yes controls or Feature Modules as they are called in mojoportal are loaded dynamically into ContentRegions based on the database similar as you describe your own CMS to work.

You can login as Administrator at http://demo.mojoportal.com to see how it works if you like, feel free to create pages and add modules to them to see how it works. demo.mojoportal.com is running under mono using the 1.1 framework features. I also have http://demo2.mojoportal.com running on the 2.0 runtime version of mono. Its kind of broken at the moment due to some testing I was doing last night but I will put it back to a working version under mono in just a little while and move my cutting edge tests for mono over to http://dev.mojoportal.com

Cheers,

Joe
Paulo Aboim Pinto

re: 2.0 Roadmap Thoughts

Wednesday, January 4, 2006 3:50:01 PM
Looks like we are doing the same thing .... :) that's good, because this looks like the better ideia.

Tell me, if you are loading the WebUserControls dynamically, how do you keep the state of the several loaded controls? I use the QueryString in some cases and session variables in another cases.

I have too an Target Region. For example I have a module that simulate a menu. When I click in the menu I want that page don't open in the module place but in the target region.
What is your implementation of that ?

tkx in advance
Paulo Aboim Pinto
Odivelas - Portugal
Comments are closed on this post.