html editor component

[Matthias Wessendorf <mw...@gmail.com>]

Werner,

there are some tickets in jira regarding the html editor component.
Will it be better to used dojo for this? And REMOVE the old component
?

Thoughts?

--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com

Re: html editor component

[Werner Punz <we...@gmx.at>]

Mike Kienenberger schrieb:
> If I get some free time (hah!), I'll take a look at creating a sandbox
> component for it since I'm using it.   There's nothing much to it
> other than outputing the example code we came up with, is there?   And
> probably calling AddResource to inline the javascript.   If I have
> time, I can at least get something out there to start the process.
> 
> If someone else provides a patch before I get to it, I can at least
> make time to commit the patch and make sure it's working.
> 
No need for direct calling of addresource, I added a DojoUtils utils 
class which does all the dojo preinitialisation for you, have a look
at the effects or dojoInitialiser code.

The problem is, I had to add another layer instead of just using add 
resource because dojo does so much more like the require stuff.

Basically all you have to do is to call dojoutils for the main include
call dojo utils for the require

and then hack away as usual

Re: html editor component

[Mike Kienenberger <mk...@gmail.com>]

If I get some free time (hah!), I'll take a look at creating a sandbox
component for it since I'm using it.   There's nothing much to it
other than outputing the example code we came up with, is there?   And
probably calling AddResource to inline the javascript.   If I have
time, I can at least get something out there to start the process.

If someone else provides a patch before I get to it, I can at least
make time to commit the patch and make sure it's working.

On 2/22/06, Werner Punz <we...@gmx.at> wrote:
> Matthias Wessendorf schrieb:
> > On 2/22/06, Werner Punz <we...@gmx.at> wrote:
> >> Yes, but we have to add it as a htmledit2 or so, I would not
> >> remove the old component for now (the dojo one also has bugs but
> >> not as many as the other one)
> >> but would set it to deprecated use htmledit2 instead or so.
> >
> > +1 since *old* html edit seems to have lot's of bugs :-)
> >
> >> But for now we need a tag for the component the status quo is not
> >> acceptible for end users ;-)
> >
> > so, the foundations is already in there, right ?
> >
> Yes some one has to componentize the dreaded thing, since I am stuffed
> with work here, I can only hope someone else does it ;-)
> there are a few people who work on components, soneonce who has a
> dojoized tag for the html edit running could push a jira patch down ;-)
> so that one of the committers can push it into the codebase ;-)
>
> Otherwise you guys will have to wait at least another two weeks for me
> doing it ;-)
>
>

Re: html editor component

[Werner Punz <we...@gmx.at>]

Matthias Wessendorf schrieb:
> On 2/22/06, Werner Punz <we...@gmx.at> wrote:
>> Yes, but we have to add it as a htmledit2 or so, I would not
>> remove the old component for now (the dojo one also has bugs but
>> not as many as the other one)
>> but would set it to deprecated use htmledit2 instead or so.
> 
> +1 since *old* html edit seems to have lot's of bugs :-)
> 
>> But for now we need a tag for the component the status quo is not
>> acceptible for end users ;-)
> 
> so, the foundations is already in there, right ?
> 
Yes some one has to componentize the dreaded thing, since I am stuffed 
with work here, I can only hope someone else does it ;-)
there are a few people who work on components, soneonce who has a 
dojoized tag for the html edit running could push a jira patch down ;-)
so that one of the committers can push it into the codebase ;-)

Otherwise you guys will have to wait at least another two weeks for me 
doing it ;-)

Re: html editor component

[Matthias Wessendorf <mw...@gmail.com>]

On 2/22/06, Werner Punz <we...@gmx.at> wrote:
> Yes, but we have to add it as a htmledit2 or so, I would not
> remove the old component for now (the dojo one also has bugs but
> not as many as the other one)
> but would set it to deprecated use htmledit2 instead or so.

+1 since *old* html edit seems to have lot's of bugs :-)

> But for now we need a tag for the component the status quo is not
> acceptible for end users ;-)

so, the foundations is already in there, right ?


>
> Werner
>
>
> Matthias Wessendorf schrieb:
> > Werner,
> >
> > there are some tickets in jira regarding the html editor component.
> > Will it be better to used dojo for this? And REMOVE the old component
> > ?
> >
> > Thoughts?
> >
> > --
> > Matthias Wessendorf
> > Zülpicher Wall 12, 239
> > 50674 Köln
> > http://www.wessendorf.net
> > mwessendorf-at-gmail-dot-com
> >
>
>


--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com

Re: html editor component

[Werner Punz <we...@gmx.at>]

Mike Kienenberger schrieb:

> Sorry, I guess my statement could be interpreted multiple ways.
> 
> Currently you have to use a dojo tag, an input, and a piece of inline
> javascript to make it work.   What I meant was that I'd prefer a
> component tag so you'd only have to use the component tag (which would
> generate the javascript for you).
> 
> See http://wiki.apache.org/myfaces/WYSIWYG_Editor at the bottom of the page.
> 

Exactly what I want to have in the end as well, the current
dojoInitializer is only a helper class which should help the component
developers to kickstart the system (dojo needs a little bit more than
just a plain javascript include, you have the djConfig block before the
include and the reqire blocks after the include)

Re: html editor component

[Mike Kienenberger <mk...@gmail.com>]

On 2/22/06, Sean Schofield <se...@gmail.com> wrote:
> Mike, can you explain how the current version does not require
> javascript?  Its hard to imagine a component like this working without
> it.  I'm new to this component so pardon my ignorance.

> On 2/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > I'd prefer htmlEditDojo rather than htmlEdit2.   Actually, the status
> > quo isn't all that horrible for end-users (of which I am now one).
> > I'd much rather see a component without the need for javascript, but
> > now that the current situation is documented on the wiki, it's
> > certainly usable.

Sorry, I guess my statement could be interpreted multiple ways.

Currently you have to use a dojo tag, an input, and a piece of inline
javascript to make it work.   What I meant was that I'd prefer a
component tag so you'd only have to use the component tag (which would
generate the javascript for you).

See http://wiki.apache.org/myfaces/WYSIWYG_Editor at the bottom of the page.

Re: html editor component

[Werner Punz <we...@gmx.at>]

Ok you are right, anyway, name it as you wish, just implement the tag ;-)


Mike Kienenberger schrieb:
> I think the "front-end" of the component name should state its functionality.
> The "back-end" would distinquish between different implementations.
> 
> That makes it easier for end-users to find what they need.
> 
> I'm unlikely to go looking for components just because they're
> dojo-based, but I'm likely to be interested in choosing between
> "htmlEditorDojo" and "htmlEditorPrototype" and "htmlEditorKapu" and
> having them show up near each other alphabetically will make it easier
> to realize there's choices.
> 
> On 2/22/06, Werner Punz <we...@gmx.at> wrote:
>> Even better whe should open a separate dojo component namespace
>> something like dojoHtmlEdit etc.. so that users can decide upfront if
>> they want to use it.
> 

Re: html editor component

[Mike Kienenberger <mk...@gmail.com>]

I think the "front-end" of the component name should state its functionality.
The "back-end" would distinquish between different implementations.

That makes it easier for end-users to find what they need.

I'm unlikely to go looking for components just because they're
dojo-based, but I'm likely to be interested in choosing between
"htmlEditorDojo" and "htmlEditorPrototype" and "htmlEditorKapu" and
having them show up near each other alphabetically will make it easier
to realize there's choices.

On 2/22/06, Werner Punz <we...@gmx.at> wrote:
> Even better whe should open a separate dojo component namespace
> something like dojoHtmlEdit etc.. so that users can decide upfront if
> they want to use it.

Re: html editor component

[Werner Punz <we...@gmx.at>]

Sean Schofield schrieb:
> Please no more '2' components.  Seriously.  We need to consider
> retiring old components and just replacing them.  If users want to
> keep using the old component that is their porogative.
> 
> Mike, can you explain how the current version does not require
> javascript?  Its hard to imagine a component like this working without
> it.  I'm new to this component so pardon my ignorance.
> 
> In any event, we need to stop slapping stuff into tomahawk propper
> with a '2' ending on it.  Put whatever you need in sandbox and call it
> whatever you want for now.  I agree you want to use a name that you
> have a chance of keeping so I would go with htmlEditDojo.
> 
Even better whe should open a separate dojo component namespace 
something like dojoHtmlEdit etc.. so that users can decide upfront if 
they want to use it.

Re: html editor component

[Matthias Wessendorf <mw...@gmail.com>]

On 2/22/06, Sean Schofield <se...@gmail.com> wrote:
> Please no more '2' components.  Seriously.  We need to consider
> retiring old components and just replacing them.  If users want to
> keep using the old component that is their porogative.

hehe

http://tinyurl.com/nutug

>
> Mike, can you explain how the current version does not require
> javascript?  Its hard to imagine a component like this working without
> it.  I'm new to this component so pardon my ignorance.
>
> In any event, we need to stop slapping stuff into tomahawk propper
> with a '2' ending on it.  Put whatever you need in sandbox and call it
> whatever you want for now.  I agree you want to use a name that you
> have a chance of keeping so I would go with htmlEditDojo.
>
> Sean
>
> On 2/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > I'd prefer htmlEditDojo rather than htmlEdit2.   Actually, the status
> > quo isn't all that horrible for end-users (of which I am now one).
> > I'd much rather see a component without the need for javascript, but
> > now that the current situation is documented on the wiki, it's
> > certainly usable.   When we make a component out of it, is the plan to
> > change items: ["textGroup", "blockGroup", "justifyGroup",
> > "colorGroup", "listGroup", "indentGroup", "linkGroup"] into a set of
> > boolean attributes?
> >
> > <htmlEditDojo textGroup="#{true}" blockGroup="#{true}"> and so on?
> >
> > On 2/22/06, Werner Punz <we...@gmx.at> wrote:
> > > Yes, but we have to add it as a htmledit2 or so, I would not
> > > remove the old component for now (the dojo one also has bugs but
> > > not as many as the other one)
> > > but would set it to deprecated use htmledit2 instead or so.
> > >
> > > But for now we need a tag for the component the status quo is not
> > > acceptible for end users ;-)
> > >
> > >
> > >
> > > Werner
> > >
> > >
> > > Matthias Wessendorf schrieb:
> > > > Werner,
> > > >
> > > > there are some tickets in jira regarding the html editor component.
> > > > Will it be better to used dojo for this? And REMOVE the old component
> > > > ?
> > > >
> > > > Thoughts?
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > > Zülpicher Wall 12, 239
> > > > 50674 Köln
> > > > http://www.wessendorf.net
> > > > mwessendorf-at-gmail-dot-com
> > > >
> > >
> > >
> >
>


--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com

Re: html editor component

[Sean Schofield <se...@gmail.com>]

Please no more '2' components.  Seriously.  We need to consider
retiring old components and just replacing them.  If users want to
keep using the old component that is their porogative.

Mike, can you explain how the current version does not require
javascript?  Its hard to imagine a component like this working without
it.  I'm new to this component so pardon my ignorance.

In any event, we need to stop slapping stuff into tomahawk propper
with a '2' ending on it.  Put whatever you need in sandbox and call it
whatever you want for now.  I agree you want to use a name that you
have a chance of keeping so I would go with htmlEditDojo.

Sean

On 2/22/06, Mike Kienenberger <mk...@gmail.com> wrote:
> I'd prefer htmlEditDojo rather than htmlEdit2.   Actually, the status
> quo isn't all that horrible for end-users (of which I am now one).
> I'd much rather see a component without the need for javascript, but
> now that the current situation is documented on the wiki, it's
> certainly usable.   When we make a component out of it, is the plan to
> change items: ["textGroup", "blockGroup", "justifyGroup",
> "colorGroup", "listGroup", "indentGroup", "linkGroup"] into a set of
> boolean attributes?
>
> <htmlEditDojo textGroup="#{true}" blockGroup="#{true}"> and so on?
>
> On 2/22/06, Werner Punz <we...@gmx.at> wrote:
> > Yes, but we have to add it as a htmledit2 or so, I would not
> > remove the old component for now (the dojo one also has bugs but
> > not as many as the other one)
> > but would set it to deprecated use htmledit2 instead or so.
> >
> > But for now we need a tag for the component the status quo is not
> > acceptible for end users ;-)
> >
> >
> >
> > Werner
> >
> >
> > Matthias Wessendorf schrieb:
> > > Werner,
> > >
> > > there are some tickets in jira regarding the html editor component.
> > > Will it be better to used dojo for this? And REMOVE the old component
> > > ?
> > >
> > > Thoughts?
> > >
> > > --
> > > Matthias Wessendorf
> > > Zülpicher Wall 12, 239
> > > 50674 Köln
> > > http://www.wessendorf.net
> > > mwessendorf-at-gmail-dot-com
> > >
> >
> >
>

Re: html editor component

[Mike Kienenberger <mk...@gmail.com>]

I'd prefer htmlEditDojo rather than htmlEdit2.   Actually, the status
quo isn't all that horrible for end-users (of which I am now one).  
I'd much rather see a component without the need for javascript, but
now that the current situation is documented on the wiki, it's
certainly usable.   When we make a component out of it, is the plan to
change items: ["textGroup", "blockGroup", "justifyGroup",
"colorGroup", "listGroup", "indentGroup", "linkGroup"] into a set of
boolean attributes?

<htmlEditDojo textGroup="#{true}" blockGroup="#{true}"> and so on?

On 2/22/06, Werner Punz <we...@gmx.at> wrote:
> Yes, but we have to add it as a htmledit2 or so, I would not
> remove the old component for now (the dojo one also has bugs but
> not as many as the other one)
> but would set it to deprecated use htmledit2 instead or so.
>
> But for now we need a tag for the component the status quo is not
> acceptible for end users ;-)
>
>
>
> Werner
>
>
> Matthias Wessendorf schrieb:
> > Werner,
> >
> > there are some tickets in jira regarding the html editor component.
> > Will it be better to used dojo for this? And REMOVE the old component
> > ?
> >
> > Thoughts?
> >
> > --
> > Matthias Wessendorf
> > Zülpicher Wall 12, 239
> > 50674 Köln
> > http://www.wessendorf.net
> > mwessendorf-at-gmail-dot-com
> >
>
>

Re: html editor component

[Werner Punz <we...@gmx.at>]

Yes, but we have to add it as a htmledit2 or so, I would not
remove the old component for now (the dojo one also has bugs but
not as many as the other one)
but would set it to deprecated use htmledit2 instead or so.

But for now we need a tag for the component the status quo is not 
acceptible for end users ;-)



Werner


Matthias Wessendorf schrieb:
> Werner,
> 
> there are some tickets in jira regarding the html editor component.
> Will it be better to used dojo for this? And REMOVE the old component
> ?
> 
> Thoughts?
> 
> --
> Matthias Wessendorf
> Zülpicher Wall 12, 239
> 50674 Köln
> http://www.wessendorf.net
> mwessendorf-at-gmail-dot-com
>