Hi Duane,

1. The skin you are using (mitchinson-earthy) uses a SuperFish menu which is a jQuery Plug-in but it isn't affected by the same styling that controls the jQuery widgets. To modify the styling of the menus in mojoPortal, use the stylemenu.css and the styletreeview.css (if using treeview style vertical menus).
2. I'm not sure how to answer this as you can use any jQuery widgets you like. The Accordian and Tab widgets require no "extra" scripting to implement them but other widgets probably do require extra script. For instance, if you want to the Slider, you will need to include the javascript necessary to create the slider in the HTML content section that will contain it.

HTH,
Joe D.

I wouldn't include the code for other widgets in the layout.master because it has the potential to slow down your site as it will be loading those scripts every time any page is hit, regardless of whether or not you are actually using the widget on the page. That being the case, I would include the javascript in the content template. The only problem with this is TinyMCE likes to strip script and style tags. To get around this, you could use FCKeditor instead of TinyMCE. You may want to experiment with putting the javascript in a separate file and using the src attribute on the script tag to reference the exteral file. TinyMCE may not strip this out, I am not sure though.

No matter what angle you take, you should have the CSS for the widgets in your style.css file.

HTH,
Joe D.

To use additional jQuery UI plugins you would not want to put the javascript in the content templates. None of the existing content templates have any javascript in them, they have only markup.

We make the tabs and accordion work by using special css class names in conjunction with markup designed for use with the widget. So the markup for the jQuery accordion for example looks like this:

<div class="mojo-accordion">

<h3><a href="#">Section 1</a></h3>

<div>

<p>Section 1 content.</p>

</div>

<h3><a href="#">Section 2</a></h3>

<div>

<p>Section 2 content</p>

</div>

<h3><a href="#">Section 3</a></h3>

<div>

<p>Section 3 content</p>

</div>

<h3><a href="#">Section 4</a></h3>

<div>

<p>Section 4 content</p>

</div>

</div>

 and we inject a little bit of script at the bottom of the page to hook it up (and any others on the page) like this:

<script type="text/javascript" > $('div.mojo-accordion').accordion(); </script>

So, if you were using some other widgets you would have to create a template with the right markup and then add some init script to the bottom of your layout.master page. Our script is injected by our ScriptLoader control but you would put your in layout.master.

We only have a few widgets baked in already but really some widgets require more initialization code and options, so while adding the tabs and accordion was low hanging fruit because they just work and don't require a lot of configuration, other ui widgets may not be quite as easy to add.

Best,

Joe

Hey guys,

I didn't think about the scripts being cached so that pretty much negates my argument. Not having the scripts in the templates is a lot cleaner. Thanks for setting me straight Joe!

-Joe D.