I am quite enamored with HTMLarea (http://www.dynarch.com/htmlarea/).  I'm trying to incorporate support for it into ad_form/form builder.

The area where I'm stuck is that if you are going to use an HTMLarea on a page, then there is a chunk of javascript that needs to be included at the top of the page.  This chunk needs to be included only once (even if I had multiple HTMLareas).  Ideally simply the call to ad_form and the corresponding formtemplate tag in the adp should be sufficient to get this chunk embedded in the target page, but I'm not sure where to look to make this happen.  I found the formtemplate proc in acs-templating/tcl/tag-init.tcl...suggestions appreciated.

Thanks.

I was able to add this and make it work for IE, but not Mozilla.  Mozilla is a lot more strict about where the JavaScript definitions have to be.  I'm pretty sure that this can't work unless there is support in the master template for the page, since for Mozilla the javascript declarations seem to need to be in the header and the initialization function needs to be called from the body's onLoad handler.

That's all fine if we can guarantee that header_stuff and the attribute multiple are present in the master template.  We'll run into other problems, however, if a page with an ad_form also requires an onLoad handler.

in your.tcl:
    set js {
        ...put your javascript code here...
    }

in your.adp:
    <master>
    <property name="header_stuff">
        <if @header_stuff@ defined>
            @header_stuff;noquote@
        </if>
        @js;noquote@
    </property>

Or, you could put your javascript directly in your.adp where @js@ appears. BTW, this is how you would add css <link...> references also.

Randy

Laides and gentlemen, we will have a WYSIWYG editor for 5.1, for both IE and Mozilla.

Had I known it was this easy, I'd have done it ages ago.

/Lars

Rodrigo, thank you!  I've been fighting with getting HTMLArea 3 to work, and was missing the

  template::multirow append \
  attribute onload "initEditor()"

code snippet.

That was actual part of the original intention of the richtext widget and format, that whenever we'd get a wysiwyg solution, we'd integrate that into the richtext widget.

/Lars

To quickly get it working with ETP this is what I did. There's probably a more elegant way to do it:

http://openacs.org/forums/message-view?message_id=115599

/Lars

Note that it is best to turn off the "Use CSS styles instead of HTML elements and attributes" preference, under the Composer section of Edit Preferences for Mozilla.  Otherwise you get some pretty far out style-based HTML tags that confuse other editors (and sometimes Mozilla itself).

/Lars

Can you give a brief overview of what it might take to retrofit an ad_form to use htmlarea in the textarea instead of the standard textarea widget?  I played with this last night and it didn't work quite right.

I was trying to get the HTML textareas in mailing-lists to use HTMLarea.  In packages/mailing-lists/www/madmin/classes.tcl I changed each ad_form field that I wanted to use HTMLarea to look something like

{html_body:richtext(richtext),optional {label "Default HTML Body"} {html {rows 12 cols 80}}}

but I've noticed that when there are three HTMLareas on the page only the last one actually updates the content.

Suggestions?

Also, does fullscreen mode not work?

To begin with, it's worth mentioning that with ad_form, a richtext widget (HTMLarea or the old richtext) is not the same thing as a simple tcl variable.  A richtext widget presents a two-element list (I think)--the first element is the actual text, and the second element is the content type (always text/html in this case).  So when you are going to expose some value you have to code it as a list or what happens is ad_form only shows the first word (because it sees that as the first list element).

This means you have to massage the stuff that comes in and goes out to the database.  I hacked it and just said

set html_body [list $html_body]

because I couldn't figure out the right syntax for the accessor functions for the richtext widget.  That's for loading the content into the form.  For saving the content from the form, fortunately Malte gave us a well-designed mailing-list api, and it was easy to add "template::util::richtext::get_property contents $html_body" to the right places.

Secondly, I punted and only used HTMLarea for the html_body portion of the mailing list.  I figured that the header and footer would be small enough that you could hand-code them, or skip them all together.

I think I've just about got this all fixed using just one HTMLarea.  Do you want patches?

Was there a reason why you didn't update to the latest CVS of all of HTMLarea?

I'm filing my patches as a bug-tracker item for mailing-lists.  The diff is against the oacs-5-1 tree.  The bug-tracker item is

http://openacs.org/bugtracker/openacs/bug?bug_number=1644

Note I figured most of this out by looking at bug.tcl in the bug-tracker package.

[06/Apr/2004:17:15:33][32318.1086155568][-conn3-] Error: rp_sources_filter: file "/web/openacs/www/resources/acs-templating/htmlarea/htmlarea.js" does not exists trying to
serve as a normal request
[06/Apr/2004:17:15:33][32318.1087208240][-conn4-] Error: rp_sources_filter: file "/web/openacs/www/resources/acs-templating/htmlarea/lang/en.js" does not exists trying to serve as a normal request
[06/Apr/2004:17:15:33][32318.1085102896][-conn2-] Error: rp_sources_filter: file "/web/openacs/www/resources/acs-templating/htmlarea/dialog.js" does not exists trying to serve as a normal request
[06/Apr/2004:17:15:33][32318.1080175408][-conn1-] Error: rp_sources_filter: file "/web/openacs/www/resources/acs-templating/htmlarea/htmlarea.css" does not exists trying to serve as a normal request

Thanks Lars.

Are you on the latest 5.1 version? Which browser?

/Lars

In .ADP:
<master>
<property name="title">@page_title@</property>
<formtemplate id="html_area"></formtemplate>


In .TCL:
set page_title "Test HTMLarea"

template::form create html_area

template::element create html_area referer \
        -optional \
        -value "/" \
        -datatype text \
        -widget hidden

template::element create html_area content \
        -value "{Hello HTMLarea} text/html" \
        -datatype richtext \
        -widget richtext \
        -htmlarea_p "t"