@xpix
The bad news: If his project goes (hard)core, I#m afraid it will have an impact on your work. The good news: It might become easier.
just an example from the generated source:
<fieldset class="tab-page" id="settings_general" >
<legend class="tab">General</legend>
<!-- ppb: Insert javascript to show/hide settings_general fieldset content -->
<script type="text/javascript">tpSettings.addTabPage( document.getElementById( "settings_general" ) );</script>
<h3>General</h3>
<dl>
<dt class="document_title">
<label>Title</label>
<p>Type the name/title of the document here. Try to avoid using backslashes in the name!</p>
</dt>
<dd class="document_title">
<input name="pagetitle" type="text" maxlength="255" value="" class="inputBox" onchange="documentDirty=true;" spellcheck="true" />
<img class="helpbutton"
src="media/style/MODxGreen/images/icons/b02_trans.gif"
onmouseover="this.src='media/style/MODxGreen/images/icons/b02.gif';"
onmouseout="this.src='media/style/MODxGreen/images/icons/b02_trans.gif';"
alt="Type the name/title of the document here. Try to avoid using backslashes in the name!"
onclick="alert(this.alt);"
/>
</dd>
</dl>
...
...
...
</fieldset
The structure is the same for all field elements within the create/edit form. Each field has it’s own <dt class="fieldname"><label>Fieldname</label></dt> and <dd class="fieldname"><input /></dd> a group of fields is inside <fieldset> element that can be adressed by its unique id (for example "settings_general"). That it. Nice an clean.
I think that’s an improvement.
General question to all: Please have a look at the ugly chunk of code presenting the help button for each form item. How important is it for you to have those buttons? What would you prefer. the css tooltips or the javascrip alert window?
