Welcome to Geeklog, Anonymous Thursday, November 28 2024 @ 12:52 am EST
Geeklog Forums
HTMLArea fork - xinha
Status: offline
ldfoo
Forum User
Junior
Registered: 05/10/04
Posts: 34
It seems HTMLArea development has stalled a little. There is an active fork called xinha (the warrior princess) http://xinha.python-hosting.com/
I have it working in the story editor for geeklog. The image upload plugin has been reworked but I am still having a little difficulty in getting it to work - hopefully just a matter of time.
Why bother with this rather tham fckeditor or tinymce? - Mainly because HTMLArea/Xinha has a zoom to full screen editor feature and the installation and setup for different configurations seems much easier
I have a one difficulty
- I can't get it to work with static pages - editor_advanced.thtml - only thing I can think is I have path problem with my header.thtml entry
_editor_url = "/xinha/";
_editor_lang = "en";
</script>
<script type="text/javascript" src="/xinha/htmlarea.js"></script>
<script type="text/javascript" src="/xinha/geeklog.js"></script>
Does anybody have HTMLArea (or Xinha) working with static pages?
Thanks
Laurie
I have it working in the story editor for geeklog. The image upload plugin has been reworked but I am still having a little difficulty in getting it to work - hopefully just a matter of time.
Why bother with this rather tham fckeditor or tinymce? - Mainly because HTMLArea/Xinha has a zoom to full screen editor feature and the installation and setup for different configurations seems much easier
I have a one difficulty
- I can't get it to work with static pages - editor_advanced.thtml - only thing I can think is I have path problem with my header.thtml entry
Text Formatted Code
<script type="text/javascript">_editor_url = "/xinha/";
_editor_lang = "en";
</script>
<script type="text/javascript" src="/xinha/htmlarea.js"></script>
<script type="text/javascript" src="/xinha/geeklog.js"></script>
Does anybody have HTMLArea (or Xinha) working with static pages?
Thanks
Laurie
15
9
Quote
Status: offline
drshakagee
Forum User
Full Member
Registered: 10/01/03
Posts: 231
I don't have HTMLArea or anything installed but I think you should make your paths in header.thtml to be:
<script type="text/javascript" src="{site_url}/xinha/htmlarea.js"></script>
<script type="text/javascript" src="{site_url}/xinha/geeklog.js"></script>
Yes I am mental.
Text Formatted Code
<script type="text/javascript" src="{site_url}/xinha/htmlarea.js"></script>
<script type="text/javascript" src="{site_url}/xinha/geeklog.js"></script>
Yes I am mental.
15
12
Quote
Ldfoo
Anonymous
Thanks - I have tried several variations - tried both path and URL
BTW - Have the image plugin working - temporarily commented the debug in config.inc - will fix when put on live site.
BTW - Have the image plugin working - temporarily commented the debug in config.inc - will fix when put on live site.
16
12
Quote
ted
Anonymous
you might consider that static pages are being called from a different dir than your story editor. That maybe why DrS. suggestes complete URL. I have to use "../dir/script" when doing this type of thing with staticpages.
13
18
Quote
ldfoo
Anonymous
Thanks again - This is running on xampp server under winxp
I have tried these
http://127.0.0.1/xinha/
c:/xampp/htdocs/xinha/
../xinha/
/xinha/
../../xinha/
Maybe I'll try straight HTMLArea - xinha has the configuration in the header and identifies the textareas using the ID (the id needed to be added as Geeklog only uses the name)
I thought there may be something about the way ststic pages works apart from the template being above the webroot
Thanks
Laurie
I have tried these
http://127.0.0.1/xinha/
c:/xampp/htdocs/xinha/
../xinha/
/xinha/
../../xinha/
Maybe I'll try straight HTMLArea - xinha has the configuration in the header and identifies the textareas using the ID (the id needed to be added as Geeklog only uses the name)
I thought there may be something about the way ststic pages works apart from the template being above the webroot
Thanks
Laurie
10
15
Quote
Status: offline
1000ideen
Forum User
Full Member
Registered: 08/04/03
Posts: 1298
Sorry I can`t help you with the problem but I`d like to point out to the developers, that the ease of editing in Geeklog is essential to sell a site to customers.
Up to now I sold 2 sites with Mambo on because the normal user who is used to MSWord wants to alter text online too. Mambo includes a version of HTMLArea. This is an essential feature.
Up to now I sold 2 sites with Mambo on because the normal user who is used to MSWord wants to alter text online too. Mambo includes a version of HTMLArea. This is an essential feature.
15
16
Quote
Status: offline
1000ideen
Forum User
Full Member
Registered: 08/04/03
Posts: 1298
If you look at this:
http://www.opensourcecms.com/index.php?option=content&task=view&id=134
you will see that a few comments are negative because people are missing a working HTMLArea with Geeklog. I`d also love one.
http://www.opensourcecms.com/index.php?option=content&task=view&id=134
you will see that a few comments are negative because people are missing a working HTMLArea with Geeklog. I`d also love one.
11
9
Quote
Status: offline
DTrumbower
Forum User
Moderator
Registered: 01/08/03
Posts: 507
The cvs version has a wysiwyg editor, FCKEditor.
14
11
Quote
Status: offline
jetshack
Forum User
Full Member
Registered: 06/29/04
Posts: 122
Location:Texas
try looking through this tread
http://www.geeklog.net/forum/viewtopic.php?forum=8&showtopic=49211&highlight=HTMLarea
however with that said,
one of the beautiful things about GL is that is it's ability to display straight HTML exactly like it should be displayed. This works in both posts and static pages...
http://www.geeklog.net/forum/viewtopic.php?forum=8&showtopic=49211&highlight=HTMLarea
however with that said,
one of the beautiful things about GL is that is it's ability to display straight HTML exactly like it should be displayed. This works in both posts and static pages...
12
12
Quote
Status: offline
ravage
Forum User
Newbie
Registered: 05/26/04
Posts: 2
Thank you very much for this lead to using Xinha. I just love it and got it working right out of the install and following the Xinha newbies guide. I installed it for stories and static pages and got it working right away. Added the following code in the top of storyeditor_advanced.thtml and editor_advanced.thtml
<script type="text/javascript">
_editor_url = "/xinha/" // (preferably absolute) URL (including trailing slash) where Xinha is installed
_editor_lang = "en"; // And the language we need to use in the editor.
</script>
<script type="text/javascript" src="/xinha/htmlarea.js"></script>
Difference in what i did was that I did not install the javascript code into header.thtml, i find that rather kind of lazy and that it might load unnecessary code into all the other pages that are not story editors. I also took the 2nd approach prescribed by the newbies guide and did not make the "geeklog.js" file that you made. I put the additional code into the end of storyeditor_advanced.thtml and editor_advanced.thtml.
All that was left was to edit "Step 2" and "Step 5" of the additional code.
Here's my additional code for editor_advanced.html
xinha_editors = null;
xinha_init = null;
xinha_config = null;
xinha_plugins = null;
// This contains the names of textareas we will make into Xinha editors
xinha_init = xinha_init ? xinha_init : function()
{
/** STEP 1 ***************************************************************
* First, what are the plugins you will be using in the editors on this
* page. List all the plugins you will need, even if not all the editors
* will use all the plugins.
************************************************************************/
xinha_plugins = xinha_plugins ? xinha_plugins :
[ 'CharacterMap', 'ContextMenu', 'FullScreen', 'ListType', 'SpellChecker', 'Stylist', 'SuperClean', 'TableOperations', 'Template' ];
// THIS BIT OF JAVASCRIPT LOADS THE PLUGINS, NO TOUCHING :)
if(!HTMLArea.loadPlugins(xinha_plugins, xinha_init)) return;
/** STEP 2 ***************************************************************
* Now, what are the names of the textareas you will be turning into
* editors?
************************************************************************/
xinha_editors = xinha_editors ? xinha_editors :
[ 'sp_content' ];
/** STEP 3 ***************************************************************
* We create a default configuration to be used by all the editors.
* If you wish to configure some of the editors differently this will be
* done in step 5.
*
* If you want to modify the default config you might do something like this.
*
* xinha_config = new HTMLArea.Config();
* xinha_config.width = '640px';
* xinha_config.height = '420px';
*
*************************************************************************/
xinha_config = xinha_config ? xinha_config() : new HTMLArea.Config();
/** STEP 4 ***************************************************************
* We first create editors for the textareas.
*
* You can do this in two ways, either
*
* xinha_editors = HTMLArea.makeEditors(xinha_editors, xinha_config, xinha_plugins);
*
* if you want all the editor objects to use the same set of plugins, OR;
*
* xinha_editors = HTMLArea.makeEditors(xinha_editors, xinha_config);
* xinha_editors['myTextArea'].registerPlugins(['Stylist','FullScreen']);
* xinha_editors['anotherOne'].registerPlugins(['CSS','SuperClean']);
*
* if you want to use a different set of plugins for one or more of the
* editors.
************************************************************************/
xinha_editors = HTMLArea.makeEditors(xinha_editors, xinha_config, xinha_plugins);
/** STEP 5 ***************************************************************
* If you want to change the configuration variables of any of the
* editors, this is the place to do that, for example you might want to
* change the width and height of one of the editors, like this...
*
* xinha_editors.myTextArea.config.width = '640px';
* xinha_editors.myTextArea.config.height = '480px';
*
************************************************************************/
xinha_editors.sp_content.config.width = '640px';
xinha_editors.sp_content.config.height = '640px';
/** STEP 6 ***************************************************************
* Finally we "start" the editors, this turns the textareas into
* Xinha editors.
************************************************************************/
HTMLArea.startEditors(xinha_editors);
}
window.onload = xinha_init;
</script>
I've now tried three WYSIWYG editors namely this, HTMLArea, and FCKEditor. This one looks great and I will try it. I could not get HTMLArea3 to function properly on both firefox and IE, and FCKEditor installs quick, but loads so slowly. Will have comments for xinha soon, but looking good so far.
Text Formatted Code
<script type="text/javascript">
_editor_url = "/xinha/" // (preferably absolute) URL (including trailing slash) where Xinha is installed
_editor_lang = "en"; // And the language we need to use in the editor.
</script>
<script type="text/javascript" src="/xinha/htmlarea.js"></script>
Difference in what i did was that I did not install the javascript code into header.thtml, i find that rather kind of lazy and that it might load unnecessary code into all the other pages that are not story editors. I also took the 2nd approach prescribed by the newbies guide and did not make the "geeklog.js" file that you made. I put the additional code into the end of storyeditor_advanced.thtml and editor_advanced.thtml.
All that was left was to edit "Step 2" and "Step 5" of the additional code.
Here's my additional code for editor_advanced.html
Text Formatted Code
<script type="text/javascript">xinha_editors = null;
xinha_init = null;
xinha_config = null;
xinha_plugins = null;
// This contains the names of textareas we will make into Xinha editors
xinha_init = xinha_init ? xinha_init : function()
{
/** STEP 1 ***************************************************************
* First, what are the plugins you will be using in the editors on this
* page. List all the plugins you will need, even if not all the editors
* will use all the plugins.
************************************************************************/
xinha_plugins = xinha_plugins ? xinha_plugins :
[ 'CharacterMap', 'ContextMenu', 'FullScreen', 'ListType', 'SpellChecker', 'Stylist', 'SuperClean', 'TableOperations', 'Template' ];
// THIS BIT OF JAVASCRIPT LOADS THE PLUGINS, NO TOUCHING :)
if(!HTMLArea.loadPlugins(xinha_plugins, xinha_init)) return;
/** STEP 2 ***************************************************************
* Now, what are the names of the textareas you will be turning into
* editors?
************************************************************************/
xinha_editors = xinha_editors ? xinha_editors :
[ 'sp_content' ];
/** STEP 3 ***************************************************************
* We create a default configuration to be used by all the editors.
* If you wish to configure some of the editors differently this will be
* done in step 5.
*
* If you want to modify the default config you might do something like this.
*
* xinha_config = new HTMLArea.Config();
* xinha_config.width = '640px';
* xinha_config.height = '420px';
*
*************************************************************************/
xinha_config = xinha_config ? xinha_config() : new HTMLArea.Config();
/** STEP 4 ***************************************************************
* We first create editors for the textareas.
*
* You can do this in two ways, either
*
* xinha_editors = HTMLArea.makeEditors(xinha_editors, xinha_config, xinha_plugins);
*
* if you want all the editor objects to use the same set of plugins, OR;
*
* xinha_editors = HTMLArea.makeEditors(xinha_editors, xinha_config);
* xinha_editors['myTextArea'].registerPlugins(['Stylist','FullScreen']);
* xinha_editors['anotherOne'].registerPlugins(['CSS','SuperClean']);
*
* if you want to use a different set of plugins for one or more of the
* editors.
************************************************************************/
xinha_editors = HTMLArea.makeEditors(xinha_editors, xinha_config, xinha_plugins);
/** STEP 5 ***************************************************************
* If you want to change the configuration variables of any of the
* editors, this is the place to do that, for example you might want to
* change the width and height of one of the editors, like this...
*
* xinha_editors.myTextArea.config.width = '640px';
* xinha_editors.myTextArea.config.height = '480px';
*
************************************************************************/
xinha_editors.sp_content.config.width = '640px';
xinha_editors.sp_content.config.height = '640px';
/** STEP 6 ***************************************************************
* Finally we "start" the editors, this turns the textareas into
* Xinha editors.
************************************************************************/
HTMLArea.startEditors(xinha_editors);
}
window.onload = xinha_init;
</script>
I've now tried three WYSIWYG editors namely this, HTMLArea, and FCKEditor. This one looks great and I will try it. I could not get HTMLArea3 to function properly on both firefox and IE, and FCKEditor installs quick, but loads so slowly. Will have comments for xinha soon, but looking good so far.
29
12
Quote
Status: offline
Blaine
Forum User
Moderator
Registered: 07/16/02
Posts: 1232
Location:Canada
The FCKeditor that is now integrated into GL-CVS and wil be part of GL 1.3.12 has the imageEditor with image/file upload and Thumbnail generator all buildin and integrated.
It's available for users to check-out.
Geeklog components by PortalParts -- www.portalparts.com
It's available for users to check-out.
Geeklog components by PortalParts -- www.portalparts.com
14
9
Quote
All times are EST. The time is now 12:52 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content