On Tue, Dec 29, 2009 at 12:00 PM, Lola Lee Beno wrote:
> On 12/29/09 1:25 PM, Chuck Savage wrote:
>> I've seen several of Ray's projects, from Galleon, to BlogCFC, to his
>> Wiki for RIAForge, each one apparently uses different editors,
>> wouldn't it be handy to have one great editor that anyone could link
>> to their project? In my opinion, that would be a great use of action
>> packs/modules. It would need to allow as I think I've seen Ray post,
>> a separate API that would parse text. Hope he's reading this and can
>> pipe in, but it was something like the name's of the functions were
>> the markup, or something like that.
>
> Are you talking about WYSIWYM editors? I would like to have the ability
> to replace with editors like MarkEdit
> (http://github.com/tstone/jquery-markedit/). I really dislike TinyMCE
> and I'm not in love with CKEditor, either.
Sounds like what we need is a custom tag. :)
The obviously messy parts (JS location, for instance) could be
configured in MG somewhere I guess...
Ok, let us imagine we have a custom tag that works with {x} WYS*
editors-- the place where MG comes in is where?
A controller & a view I reckon? Maybe with stuff that lets us easily
add buttons (everybody needs custom buttons)... maybe has a variable
for plugging in file management... ?
Maybe what we need is a "widget" extension to the framework? For
configuring things like nifty editors or grids or bad-ass gauges?
Bah. However I roll this stuff around in my head, it leads me to
extending MG views to do more (like handle widgets).
Which tends to go against the idea of MG, sorta. ('course, I guess we
could just pin the widgets to the event, like we do with linkTo()?
Bottom line is that MG views won't work for other stuff anyways--
maybe it doesn't matter)
Anyways, for the moment, 'magine that we already have the "magic"
component that lets us use whatever editor (forget the widgets for a
second) the coder wants to use-- now what? How would we use this
component MG-style?
How are you imagining leveraging this editor in your MG application?
*that* is where things get interesting.
I think I'm leaning toward a widget/helper type deal, with default
implementations of editors and grids and whatnot.
Hrm. Whatever it is, it should fit in with scaffolding all slick-like, too.
:den
--
Happiness resides not in possessions, and not in gold, happiness
dwells in the soul.
Democritus
--
Model-Glue Sites:
Home Page: http://www.model-glue.com
Documentation: http://docs.model-glue.com
Bug Tracker: http://bugs.model-glue.com
Blog: http://www.model-glue.com/blog
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en
