htmlArea

A directory of browser-based WYSIWYG editors

  MAIN
INDEX
SEARCH
POSTS
WHO'S
ONLINE
LOG
IN

Home: htmlArea 3 (beta): htmlArea 2 & 3 archive (read only): htmlArea v3.0 - Discussion:
Newest release canidate: @ area's wont work at all in FF and IE


The htmlArea 2 & 3 editors have been discontinued.

We've made these forums available as a read-only reference and knowledge-base for people using or developing editors based on htmlArea 2 or 3.

Anyone who is interested in taking over version 2 or 3 is free to do so. All we ask is that you choose a new name that doesn't have "htmlarea" in it to avoid confusion with this site. We'll even give you a link in the directory to make it easier for people to find you. If you are developing or hosting an htmlArea based-editor under a new name, please submit it to our directory.

 


Gerben
Novice

Jan 27, 2005, 8:17 AM

Post #1 of 9 (3244 views)
Shortcut
Newest release canidate: @ area's wont work at all in FF and IE Can't Post

Hi is use Firefox and IE. To display one textarea with htmlarea3 support it will work, but if i want two it won't work. I use the same code as from the exsample page.

Doies anybody has a solution?

grtzz

Gerben van Erkelens


reg
Novice

Jan 27, 2005, 3:47 PM

Post #2 of 9 (3217 views)
Shortcut
Re: [Gerben] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

Works for me, I run about 5 on a page with no problem. What does your code look like?

Reg


Gerben
Novice

Jan 28, 2005, 2:14 AM

Post #3 of 9 (3190 views)
Shortcut
Re: [reg] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

my code looks like:
<script type="text/javascript">
// the _editor_url is REQUIRED! don't forget to set it.
_editor_url = "../htmlarea_3/";
// implicit language will be "en", but let's set it for brevity
_editor_lang = "en";
</script>
<script type="text/javascript" src="../htmlarea_3/htmlarea.js"></script>
<script type="text/javascript">
HTMLArea.loadPlugin("TableOperations");
HTMLArea.loadPlugin("SpellChecker");
HTMLArea.loadPlugin("CSS");
HTMLArea.loadPlugin("FullPage");

// this function will get called at body.onload
function initDocument() {
// cache these values as we need to pass it for both editors
var css_plugin_args = {
combos : [
{ label: "Syntax",
// menu text // CSS class
options: { "None" : "",
"Code" : "code",
"String" : "string",
"Comment" : "comment",
"Variable name" : "variable-name",
"Type" : "type",
"Reference" : "reference",
"Preprocessor" : "preprocessor",
"Keyword" : "keyword",
"Function name" : "function-name",
"Html tag" : "html-tag",
"Html italic" : "html-helper-italic",
"Warning" : "warning",
"Html bold" : "html-helper-bold"
},
context: "pre"
},
{ label: "Info",
options: { "None" : "",
"Quote" : "quote",
"Highlight" : "highlight",
"Deprecated" : "deprecated"
}
}
]
};

//---------------------------------------------------------------------
// CREATE FIRST EDITOR
//
var editor1 = new HTMLArea("intro");

// plugins must be registered _per editor_. Therefore, we register
// plugins for the first editor here, and we will also do this for the
// second editor.
editor1.registerPlugin(TableOperations);
editor1.registerPlugin(SpellChecker);
editor1.registerPlugin(CSS, css_plugin_args);
editor1.registerPlugin(FullPage);

// custom config must be done per editor. Here we're importing the
// stylesheet used by the CSS plugin.
editor1.config.pageStyle = "@import url(custom.css);";

// generate first editor
editor1.generate();
//---------------------------------------------------------------------


//---------------------------------------------------------------------
// CREATE SECOND EDITOR
//
var editor2 = new HTMLArea("bericht");

editor2.registerPlugin(TableOperations);
editor2.registerPlugin(SpellChecker);
editor2.registerPlugin(CSS, css_plugin_args);
editor2.registerPlugin(FullPage);

editor2.config.pageStyle = "@import url(custom.css);";

setTimeout(function() {
editor2.generate();
}, 500);
//---------------------------------------------------------------------
};
</script>


reg
Novice

Jan 28, 2005, 7:28 AM

Post #4 of 9 (3150 views)
Shortcut
Re: [Gerben] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

Well, your code looks far more complex than mine, but I haven't started using any plugins yet, and perhaps that is the difference. The script to apply htmlarea to one of the fields needing editing on my page is as follows:

522: </script>
523: <script type="text/javascript" >
524: var config = new HTMLArea.Config();
525: config.toolbar= [
526: ['copy','cut','paste','separator','undo','redo', 'separator','bold','italic','underline', 'separator','superscript','subscript', 'separator','removeformat','killword', 'separator','htmlmode','showhelp']
527: ];
528: config.statusbar='false';
529: config.width='600';
530: config.pageStyle='body { background-color: whitesmoke; color: black; font-family: verdana; font-size: 1em;' ;
531: HTMLArea.replace('fullpage_itemlongtext7',config);
532: </script>


hope this helps,

Reg


Gerben
Novice

Jan 28, 2005, 9:33 AM

Post #5 of 9 (3121 views)
Shortcut
Re: [reg] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

aha, but that is only for one area isnt it?
Anyway the code of mine is 90% like the example ("2_areas.html") i thought that code should work.


reg
Novice

Jan 28, 2005, 9:47 AM

Post #6 of 9 (3118 views)
Shortcut
Re: [Gerben] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

Yes, it is just for one area, but there are 5 other scripts just like it, referencing other textarea objects

Reg


Gerben
Novice

Jan 28, 2005, 9:52 AM

Post #7 of 9 (3115 views)
Shortcut
Re: [reg] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

aha and whats the id of your textarea?


reg
Novice

Jan 28, 2005, 9:59 AM

Post #8 of 9 (3113 views)
Shortcut
Re: [Gerben] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

variations on

531: HTMLArea.replace('fullpage_itemlongtext7',config);

so fullpage_itemlongtext1 to fullpage_itemlongtext6


Gerben
Novice

Jan 29, 2005, 7:22 AM

Post #9 of 9 (3058 views)
Shortcut
Re: [reg] Newest release canidate: @ area's wont work at all in FF and IE [In reply to] Can't Post

aha so if my fields are called content or so, i need to fill in there: content1 to 3 or so :d

 
 
 


Search for (options)