hello to all,

I'm posting a message on a Saturday, I must an IT worker. Ha!
The menu? The menus?
How difficult to would it be for me to change the existing menu structure/assembly/back-end code to jQuery/mootools or something much more flexible and future modular, so you could use drop-menus etc.
In truth in my humble opinion, asp menu controls are just awful, including Cssfriendly.
Albeit, I am still a newbie after having slogged through my first database project in 1977, but it seems to me that a less hardcoded menu core would be much better and more useful as a mojoportal project grew.
I mean, granted no one has any work to do unless there is a problem to fix (learned that from Microsoft & Novell), but would it not be better to be able to still charge the same developer fees but have easier problems to fix and be able to have the week-ends off? Ha! ;-) (sorry for my sarcasm)
And also, I think the beauty of master pages, is the ability to have multiple master pages with their child pages in one project, and being able to quickly add one of those pages to a site.
In mojoportal (as in many of the current CMS's), modifying the existing layout/master page is to rigid and defeats the purpose of having a flexible master page structure. Working in Fckeditor is good for messing around with a dinky amount of text, but working on a real live big site requires something much more effcient. Otherwise, you're stuck working on the week-ends not getting paid overtime. ;-) ha! 

 Mark
 

.  .  . Thank you! - mark