NicEdit - Micro Inline WYSIWYG

While, I haven't used a WYSIWYG editor with Bricolage in the
past, I may
in the future. Thus, I'm wondering if this will have any
applications
for Bricolage once it is developed further:

http://nicedit.com/index
.php

Chris

-------------------

Chris Schults
Web Developer
PCC Natural Markets
206-547-1222 x104
chris.schultspccsea.com
http://www.pccnatura
lmarkets.com 

That's certainly a nice one. I'm also fooling around with
integrating  
the Javascript Quicktags editor:
http://alex
king.org/projects/js-quicktags

Phillip.

On 21-Dec-07, at 4:44 PM, Schults, Chris wrote:

> While, I haven't used a WYSIWYG editor with Bricolage
in the past,  
> I may
> in the future. Thus, I'm wondering if this will have
any applications
> for Bricolage once it is developed further:
>
> http://nicedit.com/index
.php
>
> Chris
>
> -------------------
>
> Chris Schults
> Web Developer
> PCC Natural Markets
> 206-547-1222 x104
> chris.schultspccsea.com
> http://www.pccnatura
lmarkets.com

--
Phillip Smith,
Simplifier of Technology
Community Bandwidth
http://www.community
bandwidth.ca

So, this got me to thinking about something that came up
again today:  
how difficult would it be to configure multiple WYSIWYG
editors in a  
single bricolage instance?  I'm thinking either two
different editors,  
or just two different configurations of Xinha.

We're using a pretty standard Xinha config, but we have a
new project  
coming up where we'd rather have a very restricted toolbar
for one  
site (maybe just two or three options), but the other sites
would  
still use the larger feature set.

NicEdit looks sweet, btw.  I wonder, if two Xinha configs
wouldn't  
work, could we enable NicEdit just on certain elements? 
I've nosed  
around the source of the story editing workflow, and it
doesn't look  
like there are any field/element-based identifiers in the
markup.  It  
would be sweet if the textarea element id or class names
were somehow  
linked to the element names.  That way I could create a
textarea field  
called NicEdit, and any instances of it would be output to
the story  
editing interface with
'id="NicEdit_someuniquestuff"' or  
'class="NicEdit"'.  That might make it easier to
do custom javascript  
widget replacement, instead of creating whole new field
types.

-Aaron

---------------------------------
Aaron Fuleki
Web Services Manager
Denison University
740.587.5752
---------------------------------