Smarty

[johannes]

Hi list

Im thinking of using SPAW html-editor (see http://sourceforge.net/projects/spaw) and Smarty thogether.

Is it anybody on this forum that has done this before? Please let me know about problems and think-abouts, if there are any.... How did you solve this? and so on, tips and tricks.

...or is there a better html-editor too use?

/JohannesF

[Justin]

well, I'm using htmlArea ( http://www.interactivetools.com/products/htmlarea/ ) with my own image manager. and SPAW.. He's free for non-commercial use - see http://www.solmetra.com/en/disp.php/en_products/en_spaw/en_spaw_purchase
Yes, SPAW is cool, but htmlArea community is bigger.
_________________
http://www.baubas.net

[AZTEK]

Well the new htmlArea works with Mozilla 1.3 browsers so its not IE only anymore
_________________
"Imagine a school with children that can read and write, but with teachers who cannot, and you have a metaphor of the Information Age in which we live." -Peter Cochrane

[Justin]

[boots]

I've been toying with the SPAW control (thanks for pointing it out johannes -- SPAW is pretty cool) and have implemented a Smarty custom plugin function to wrap it. It works -- in degrees -- but I am having a little bit of a problem with paths.

In particular, I am trying to keep all of the server-side Spaw code base out of my web root and then I want to put the client libraries and resources (js, css, img files) in directories of my choosing in the web root. Has anyone already done something like that?

In the meantime, I have the entire Spaw package located in a subdirectory off the webroot and it still isn't completely happy with that. The demos work okay, even with that setup, but I think only because they are in a subdir of the spaw directory. What doesn't work are the dialogs -- I'm not getting syntax errors anymore, but they aren't working as they are in the demo and I'm sure its because of the darn paths. I think SPAW wants to be at the document root.

I have to take another look at htmlArea--its been awhile and I got caught up by SPAW's flashy look Still, SPAW sure beats using <textarea> !

Okay, it is so simplistic, I'm embarassed to post it, but perhaps it will save a lazy soul a few keystrokes; here is the current state of the my custom {editor} function plugin. You'll obviously have to modify it a bit to match your website and spaw installation, but apparently I'm not the one to look for advice on that
[php:1:4319925d68]<?php
// this part determines the physical root of your website
define('DR', MY_ROOT_DIR.'www/');
// include the control file
include_once DR.'spaw/config/'.'spaw_control.config.php';
include_once DR.'spaw/'.'spaw_control.class.php';

/**
* Smarty function plugin
* -------------------------------------------------------------
* Type: function
* Name: editor
* Version: 1.0
* Author: boots
* Purpose: create a spaw editor control
* -------------------------------------------------------------
* @param name required form name for control
* @param data optional data that control will start with
* @param lang optional country code for language, default: en
* @param toolbar optional toolbar style, default: SPAW default
* @param width optional control width (css units), default: 200
* @param height optional control height (css units), default: 400
* @param stylesheet optional stylesheet to use for styling SPAW, default: SPAW default
* @param theme optional theme to use for styling SPAW, default: SPAW default
* @param styles optional array of drop down style options, default set in function
*/
function smarty_function_editor( $params, &$this )
{
extract ( $params );
if ( empty( $name ) ) {
$this->trigger_error('editor: required parameter "name" missing');
} else {
$_styles['style']['default'] = 'Default';
$_styles['style']['crazystyle1'] = 'Crazy style no. 1';
$_styles['style']['crazystyle2'] = 'Crazy style no. 2';
$_styles['style']['crazystyle3'] = 'Crazy style no. 3';
if (!isset($data) || empty($data)) $data = '';
if (!isset($lang) || empty($lang)) $lang = 'en';
if (!isset($toolbar) || empty($toolbar)) $toolbar = '';
if (!isset($width) || empty($width)) $width = 200;
if (!isset($height) || empty($height)) $height = 90;
if (!isset($stylesheet) || empty($stylesheet)) $stylesheet = '';
if (!isset($theme) || empty($theme)) $theme = '';
if (!isset($styles) || empty($styles) || !is_array($styles)) $styles = $_styles;
$sw = new SPAW_Wysiwyg( $name, stripslashes($data),
$lang, $toolbar, $theme,
$width, $height, $stylesheet, $styles );
return $sw->getHtml();
}
}
?>[/php:1:4319925d68]

Good Luck!

[Hpatoio]

[Hpatoio]

[boots]

@Hpatoio: That sounds great! I started to dig into the path problems and saw that I would have to be messing with the source files, so I put it aside again to ponder. Would you be willing to post a patch or diff so that I can see where the affected areas are?

It would be nice to have the ability to simply drop-in new versions of spaw, but it sounds like that is less likely to happen .

[Hpatoio]

Hej ... ok, sorry if I've been away 4 a while ...
I wanted to test my works before to spread it ... and now I think to have a stable and multi-domain version of SPAW

I'm going to write to the SPAW developers to see if they want to integrate my changes in the official release ...

But anyway, if you want I can send you a ZIP file with all the files !
It's your job to understand how it works ...
documentation is not provided !!!

So if you want these files let me know how to give them to U !

Ciao ciao

Simone

[blue]

do you still have the zip package???

[Hpatoio]

[blue]

well i'm trying too..... i was just wondering how you did it.

[boots]

I tried both a few months ago and I heartily suggest htmlArea over SPAW. It is easier to integrate and appears to have a better licence and larger dev community. I've been very happy with htmlArea but pulled a lot of hairs out with SPAW, even after using Hpatio's customizations (thanks Hpatio). htmlArea v3 (currently beta) is also a big improvement over the v2.

[blue]

did you release it as a plugin??

[boots]

@blue: if you mean htmlArea -- check it out -- there is no need to release it as a plugin