Question 1 - /DIV tags:
Hi,

Here are some basic questions I have as I analyze the doctor's example:

In the doctors example, in the module that lists the physicians, in the details html, why are there no ending </td> tags? Instead, each cell seems to have an ending </div> tag, with no matching <div> anywhere. How does this work?

Question 2 - Style sheet:
Where is the stylesheet that is used in the doctors example? Perhaps this is a DNN question, but I cant find it, I have not figured out where in DNN to put stylesheets for my module content in general.

Question 3 - unknown function:
What is ajaxsave_tinyMCE(); it is called in the onclick of save button when you save a physician in the doctor's example. As far as I can tell, it is not mentioned anywhere in the manual.

Question 4 - tinyMCE:
Do I need tinyMCE? There seems to be a lot of reference to the 3rd party editor tinyMCE, but I cant see what it is used for or needed for in ListX

hello miamiray,

Looks Like Our Developers Concentrated on the functionality of the Module but not on the HTML in the first build.

The newer version of ListX (OWS) we are reworking on our Example to have proper HTML (XHTML 1.0 Transitional).

for Question 3 and 4 yes you will need tinyMCE for this Example to work you can find it in our downloads Area.

Thanks,
DP

What I really was asking is is there some reason I need tiny MCE to work with listx ?

Or is it just this example?

I am getting stuff I need to work, to work so far, based on looking at the examples. I dont think Ive needed tiny MCE yet.

Am I missing something? Is there something special about tiny MCE that makes listx work better?

Ive taken to putting styles at the top of the item detail code. It works, but I dont think thats the right way.

I asked too many questions at once in the first message, didnt get an answer about the style sheets. I know its probably a stupid question, but where are you putting the style sheets for the doctor's module? Where do I put styles for listx?

The doctor module I believe has it's style's defined within the Portal CSS, or it's inline in the pages. I cannot recall. For best practice you should attempt to keep your styles universal to the portal - so sustaining them within the Portal.css file in the Portal root directory is the best, and most appropriate place. However, if you have a lot of skins thrown in your site, meaning your may be changing the look and feel entirely within your site on a page by page basis, i recommend setting your css within the skin.css file.