HtmlArea for 0.8 still not usable

Hi devs,

I have one idea to the development team. I remember the "table bug
hunting day" and I will be happy if some day in future can be focused
on the HtmlArea. Qooxdoo is very good framework, but it totally fails
in html editing. It's not usable for any kind of cms systems (also for
ecommerce systems, because here should be html content too).

So my question is. Need anyone html editing in qooxdoo ?

I have contributed some code to it, but there two critical bugs thats
making HtmlArea totally unusable (bugs are already reported):
- Firefox problem with hiding HtmlArea (once you hide it, you can't edit)
- In some case when I press enter, I have this text in new line
"[object HTMLSpanElement]"
  this can be reproduced by hitting enter when you focus in HtmlArea

So my idea is simple: I have some time to contribute to HtmlArea, but
I need that others will fix these two bugs, because I don't know how
to fix them (for HtmlArea authors this should be for few minutes :-) )

Note: I'm talking about qooxdoo 0.8 from SVN and HtmlArea for 0.8.

I will provide simple application where others can look at the bugs
I'm talking about.

Cheers
- Petr

-------------------------------------------------------------------------
(Continue reading)

Fabian Jakobs | 6 Oct 11:22
Favicon

Re: HtmlArea for 0.8 still not usable

Petr Kobalíček schrieb:
> Hi devs,
>
> I have one idea to the development team. I remember the "table bug
> hunting day" and I will be happy if some day in future can be focused
> on the HtmlArea. Qooxdoo is very good framework, but it totally fails
> in html editing. It's not usable for any kind of cms systems (also for
> ecommerce systems, because here should be html content too).
>
> So my question is. Need anyone html editing in qooxdoo ?
>
> I have contributed some code to it, but there two critical bugs thats
> making HtmlArea totally unusable (bugs are already reported):
> - Firefox problem with hiding HtmlArea (once you hide it, you can't edit)
> - In some case when I press enter, I have this text in new line
> "[object HTMLSpanElement]"
>   this can be reproduced by hitting enter when you focus in HtmlArea
>
> So my idea is simple: I have some time to contribute to HtmlArea, but
> I need that others will fix these two bugs, because I don't know how
> to fix them (for HtmlArea authors this should be for few minutes :-) )
>
> Note: I'm talking about qooxdoo 0.8 from SVN and HtmlArea for 0.8.
>
> I will provide simple application where others can look at the bugs
> I'm talking about.
>
> Cheers
> - Petr
>
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi Fabian,

I didn't know about his vacation, so it's ok for now :)

Cheers
- Petr

2008/10/6 Fabian Jakobs <fabian.jakobs <at> 1und1.de>:
> Petr Kobalíček schrieb:
>> Hi devs,
>>
>> I have one idea to the development team. I remember the "table bug
>> hunting day" and I will be happy if some day in future can be focused
>> on the HtmlArea. Qooxdoo is very good framework, but it totally fails
>> in html editing. It's not usable for any kind of cms systems (also for
>> ecommerce systems, because here should be html content too).
>>
>> So my question is. Need anyone html editing in qooxdoo ?
>>
>> I have contributed some code to it, but there two critical bugs thats
>> making HtmlArea totally unusable (bugs are already reported):
>> - Firefox problem with hiding HtmlArea (once you hide it, you can't edit)
>> - In some case when I press enter, I have this text in new line
>> "[object HTMLSpanElement]"
>>   this can be reproduced by hitting enter when you focus in HtmlArea
>>
>> So my idea is simple: I have some time to contribute to HtmlArea, but
>> I need that others will fix these two bugs, because I don't know how
>> to fix them (for HtmlArea authors this should be for few minutes :-) )
>>
(Continue reading)

John Spackman | 8 Oct 19:21

Re: HtmlArea for 0.8 still not usable

I realise Alexander is on holiday right now so I'm leaving this as a note
for when he returns as much as anything.

I'd like to add my vote to this - a rich text editor is important and we've
abandoned the FCKeditor integration because it's too slow.

Petr - have you tried the latest SVN version of HtmlArea?  I'm not getting
the "[object HTMLSpanElement]" bug with that version, even though the demo
of 0.3-pre does.

I've nearly finished a wrapper around HtmlArea which adds toolbars for
styling, formatting, images, links, etc in one Widget; I'd like to
contribute it as part of the HtmlArea package but obviously don't want to go
steaming in until Alexander is back.  I'll post it here if anyone wants to
take a look in the mean time.

John

-----Original Message-----
From: Petr Kobalíček [mailto:kobalicek.petr <at> gmail.com] 
Sent: 07 October 2008 08:22
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] HtmlArea for 0.8 still not usable

Hi Fabian,

I didn't know about his vacation, so it's ok for now :)

Cheers
- Petr
(Continue reading)

Andreas Ecker | 9 Oct 09:42

Re: HtmlArea for 0.8 still not usable

Hi John!

> I realise Alexander is on holiday right now so I'm leaving this as a note
> for when he returns as much as anything.
> 
> I'd like to add my vote to this - a rich text editor is important and we've
> abandoned the FCKeditor integration because it's too slow.

Would be great we could collaborate on improving HtmlArea. Such a widget
requires quite some community effort to iron out immanent cross-browser
issues.

> I've nearly finished a wrapper around HtmlArea which adds toolbars for
> styling, formatting, images, links, etc in one Widget; I'd like to
> contribute it as part of the HtmlArea package but obviously don't want to go
> steaming in until Alexander is back.  I'll post it here if anyone wants to
> take a look in the mean time.

Yes, that could become a fine contribution to qooxdoo-contrib for people
interested in an out-of-the-box solution for an HTML editor. Actually,
we never wanted to package up such a combined solution (other than the
sample included with HtmlArea), as one would need to support so many
variants that it easily becomes (again) a heavy-weight configuration
thingy. Attaching toolbars and other elements to HtmlArea should be
fairly easy in qooxdoo to satisfy individual requirements. But if you
think you've come up with a solution that could be widely used, that's
great.

Anyway, as I suggested it should rather be a separate contribution
(maybe called "HtmlEditor") next to the existing HtmlArea. The area
(Continue reading)

Fabian Jakobs | 9 Oct 10:48
Favicon

Re: HtmlArea for 0.8 still not usable

Andreas Ecker schrieb:
> Hi John!
>
>   
>> I realise Alexander is on holiday right now so I'm leaving this as a note
>> for when he returns as much as anything.
>>
>> I'd like to add my vote to this - a rich text editor is important and we've
>> abandoned the FCKeditor integration because it's too slow.
>>     
>
> Would be great we could collaborate on improving HtmlArea. Such a widget
> requires quite some community effort to iron out immanent cross-browser
> issues.
>
>   
>> I've nearly finished a wrapper around HtmlArea which adds toolbars for
>> styling, formatting, images, links, etc in one Widget; I'd like to
>> contribute it as part of the HtmlArea package but obviously don't want to go
>> steaming in until Alexander is back.  I'll post it here if anyone wants to
>> take a look in the mean time.
>>     
>
> Yes, that could become a fine contribution to qooxdoo-contrib for people
> interested in an out-of-the-box solution for an HTML editor. Actually,
> we never wanted to package up such a combined solution (other than the
> sample included with HtmlArea), as one would need to support so many
> variants that it easily becomes (again) a heavy-weight configuration
> thingy. Attaching toolbars and other elements to HtmlArea should be
> fairly easy in qooxdoo to satisfy individual requirements. But if you
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi Guys,

I'm happy for too much comments here :-)

First

a) about [HTMLSpanElement] bug:

I'm corrected it, but unfortunally there is something wrong with my
code (see latest commit), because it not behaves good (I don't know
how to document it, there are growing number if <p> tags and I don't
know).

b) about anything else :)

I have sometimes time to contribute to HtmlArea, I have read early all
code, but I have sometimes problems to understand it at all (it's not
badly written, but there seems be too much bugs in browsers and Html
editing is COMPLEX to implement).

Problem for me is that the "firefox focus bug" is still there, try this code:

qx.Class.define("bfly.admin.Application",
{
  extend : qx.application.Standalone,

  members :
  {
    // [Entry point]
    main: function()
(Continue reading)

John Spackman | 9 Oct 13:32

Re: HtmlArea for 0.8 still not usable

Hi Petr,

I'm very happy to collaborate on this - although I suspect I'll be more a
user of HtmlArea itself than a major contributor to it.  I think that there
is a reasonable amount of work to add rich controls to the editor and make
it a very accessible and easy to use component, especially for the smarter
features like image pickers and other dialogs etc so it would be great to
work together on this.  Is it possible for you to put your RichEditor on the
web somewhere?  I need to finish some things off today but upload it later
on for you to look at.

Regards,
John

-----Original Message-----
From: Petr Kobalíček [mailto:kobalicek.petr <at> gmail.com] 
Sent: 09 October 2008 11:57
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] HtmlArea for 0.8 still not usable

Hi Guys,

I'm happy for too much comments here :-)

First

a) about [HTMLSpanElement] bug:

I'm corrected it, but unfortunally there is something wrong with my
code (see latest commit), because it not behaves good (I don't know
(Continue reading)

John Spackman | 10 Oct 14:07

Re: HtmlArea for 0.8 still not usable

Hi guys,

I've uploaded my sample and the code to
http://www.zenesis.com/qx/dev/myapp/source/ - there's a readme at
http://www.zenesis.com/qx/dev/README.txt and if you want to take a look at
the code it's http://www.zenesis.com/qx/dev.zip. 

John

-----Original Message-----
From: John Spackman [mailto:john.spackman <at> zenesis.com] 
Sent: 09 October 2008 12:32
To: 'qooxdoo Development'
Subject: Re: [qooxdoo-devel] HtmlArea for 0.8 still not usable

Hi Petr,

I'm very happy to collaborate on this - although I suspect I'll be more a
user of HtmlArea itself than a major contributor to it.  I think that there
is a reasonable amount of work to add rich controls to the editor and make
it a very accessible and easy to use component, especially for the smarter
features like image pickers and other dialogs etc so it would be great to
work together on this.  Is it possible for you to put your RichEditor on the
web somewhere?  I need to finish some things off today but upload it later
on for you to look at.

Regards,
John

-----Original Message-----
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi John,

Thanks for you sample, I'm trying to split my implementation but some
things are very dependent to our file browser. I hope that tonight it
will be ready, but without file browser.

You implementation is good:)

Cheers
- Petr

2008/10/10 John Spackman <john.spackman <at> zenesis.com>:
> Hi guys,
>
> I've uploaded my sample and the code to
> http://www.zenesis.com/qx/dev/myapp/source/ - there's a readme at
> http://www.zenesis.com/qx/dev/README.txt and if you want to take a look at
> the code it's http://www.zenesis.com/qx/dev.zip.
>
> John
>
> -----Original Message-----
> From: John Spackman [mailto:john.spackman <at> zenesis.com]
> Sent: 09 October 2008 12:32
> To: 'qooxdoo Development'
> Subject: Re: [qooxdoo-devel] HtmlArea for 0.8 still not usable
>
> Hi Petr,
>
> I'm very happy to collaborate on this - although I suspect I'll be more a
(Continue reading)

Re: HtmlArea for 0.8 still not usable

After some time I'm posting here my code, that's only stripped from
our application. I don't have time to make it functional without our
components.

Currently we are not using this RichText and we will probably never use.

Cheers
- Petr

/**
 * Html area widget width toolbar.
 */
qx.Class.define("bfly.ui.RichText",
{
  extend: qx.ui.container.Composite,

  construct: function()
  {
    // [Super Class]
    this.base(arguments);

    // [UI]
    this.setLayout(new qx.ui.layout.VBox());

    this._tools = {};
    this._syncing = false;

    this._toolBar = new qx.ui.toolbar.ToolBar().set({show: "icon"});
    this._htmlArea = new htmlarea.HtmlArea();
    this._htmlArea.setPostprocess(this.self(arguments)._postprocess);
(Continue reading)

Alexander Back | 31 Oct 10:15
Favicon

Re: HtmlArea for 0.8 still not usable

Hi Petr,

Petr Kobalíček wrote:
> After some time I'm posting here my code, that's only stripped from
> our application. I don't have time to make it functional without our
> components.
> 
> Currently we are not using this RichText and we will probably never use.
I'm curious about your reason not to choose the HtmlArea ever again. 
Which bugs are open in 0.3-pre version which prevents you from using 
this widget?
As a side note: I've fixed this annoying focus bug in Firefox ( 
http://bugzilla.qooxdoo.org/show_bug.cgi?id=1366 ) this week.

As far as I know the current 0.3-pre version is usable and there are no 
major bugs open. So if you encountered some major bugs I'm currently not 
aware of let us know by filing bug reports.

thanks,
   Alex

> 
> Cheers
> - Petr
> 2008/10/11 Petr Kobalíček <kobalicek.petr <at> gmail.com>:
>> Hi John,
>>
>> Thanks for you sample, I'm trying to split my implementation but some
>> things are very dependent to our file browser. I hope that tonight it
>> will be ready, but without file browser.
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi Alex,

Fixed focus bug is great:-)

Problem is that I have currently too little time to try HtmlArea
again. When I will have some time I will try to get our RichText
component from our application and I will be happy to share it (and to
improve it in community base).

There are some problems, but I can't describe them without live
demonstration. For example B, I, U and S checkboxes are sometimes not
updated correctly.

Meybe I can try it now:)

Cheers
Petr

2008/10/31 Alexander Back <alexander.back <at> 1und1.de>:
> Hi Petr,
>
> Petr Kobalíček wrote:
>> After some time I'm posting here my code, that's only stripped from
>> our application. I don't have time to make it functional without our
>> components.
>>
>> Currently we are not using this RichText and we will probably never use.
> I'm curious about your reason not to choose the HtmlArea ever again.
> Which bugs are open in 0.3-pre version which prevents you from using
> this widget?
(Continue reading)

John Spackman | 31 Oct 16:15

Re: HtmlArea for 0.8 still not usable

Hi Alex,

IMHO it's not that HtmlArea itself is unusable, it's that it is often not usable on its own; in order to
integrate it into an application there needs to be simple toolbars for bold/italic/etc but also more
complex issues like:

+. support for styles (H1, H2, etc as well as custom styles in SPAN tags) - this requires some fairly involved
code manipulating the DOM
+. An image picker where the server can be browsed in some way
+. Other dialogs for inputing and editing URLs etc

The current demo makes HtmlArea look like a poor cousin to FCKEditor/TinyMCE/etc and it's only when you
look further that you realise that HtmlArea is something _good_ but that is intended to be built upon.  I
only realised it when I got fed up with FCKEditor being so slow, and I'm not the only one to make that mistake.

Petr & I briefly raised these issues while you were on holiday (my [slightly buggy] version is available
here http://www.zenesis.com/qx/dev/) and we discussed working on a contrib.  

I'd like to suggest that it becomes part of the HtmlArea contrib - anyone who wants a drop-in user friendly
editor uses the HtmlEditor class but internally there's a clear separation between the toolbars etc and
the HtmlArea.  At the very least, it would be a great demo for the HtmlArea control.

What do you think?

John

-----Original Message-----
From: Alexander Back [mailto:alexander.back <at> 1und1.de] 
Sent: 31 October 2008 09:15
To: qooxdoo Development
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi John,

I have some simple image chooser and I can release it under BSD
licence. If you are interested I can send it to you, but as all my
code, it depends to some our code that I cannot release.

But it's only image chooser with NO thinks like image width,height,
alt text and others. Also main problem is that it can show only file
names, not thumbnails, because flow layout not works well :(

I'm sending screenshot to imagine how it's look like (nothing pretty)

2008/10/31 John Spackman <john.spackman <at> zenesis.com>:
> Hi Alex,
>
> IMHO it's not that HtmlArea itself is unusable, it's that it is often not usable on its own; in order to
integrate it into an application there needs to be simple toolbars for bold/italic/etc but also more
complex issues like:
>
> +. support for styles (H1, H2, etc as well as custom styles in SPAN tags) - this requires some fairly
involved code manipulating the DOM
> +. An image picker where the server can be browsed in some way
> +. Other dialogs for inputing and editing URLs etc
>
> The current demo makes HtmlArea look like a poor cousin to FCKEditor/TinyMCE/etc and it's only when you
look further that you realise that HtmlArea is something _good_ but that is intended to be built upon.  I
only realised it when I got fed up with FCKEditor being so slow, and I'm not the only one to make that mistake.
>
> Petr & I briefly raised these issues while you were on holiday (my [slightly buggy] version is available
here http://www.zenesis.com/qx/dev/) and we discussed working on a contrib.
(Continue reading)

John Spackman | 31 Oct 20:35

Re: HtmlArea for 0.8 still not usable

Hi Petr,

Yes please, that looks very cool but I'm worried that the licensing might
conflict with the Qooxdoo and that might prevent it from being a contrib?  I
am literally just off on holiday (I popped back into the office to get the
hotel info and my g/f is not amused!) but I'll take this up again in a few
weeks

John

-----Original Message-----
From: Petr Kobalíček [mailto:kobalicek.petr <at> gmail.com] 
Sent: 31 October 2008 18:37
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] HtmlArea for 0.8 still not usable

Hi John,

I have some simple image chooser and I can release it under BSD licence. If
you are interested I can send it to you, but as all my code, it depends to
some our code that I cannot release.

But it's only image chooser with NO thinks like image width,height, alt text
and others. Also main problem is that it can show only file names, not
thumbnails, because flow layout not works well :(

I'm sending screenshot to imagine how it's look like (nothing pretty)

2008/10/31 John Spackman <john.spackman <at> zenesis.com>:
> Hi Alex,
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi John,

BSD (Modified) licence is most liberal licence for software. I think
that it should never be in conflict with anything. Personally I'm not
using GPL or LGPL licences, only BSD, MIT, Public Domain and similar
ones.

Just send me PM when you will be ready to colaborate on image chooser.
I have too little time now but for this I will make it:)

Cheers
- Petr

2008/10/31 John Spackman <john.spackman <at> zenesis.com>:
> Hi Petr,
>
> Yes please, that looks very cool but I'm worried that the licensing might
> conflict with the Qooxdoo and that might prevent it from being a contrib?  I
> am literally just off on holiday (I popped back into the office to get the
> hotel info and my g/f is not amused!) but I'll take this up again in a few
> weeks
>
> John
>
> -----Original Message-----
> From: Petr Kobalíček [mailto:kobalicek.petr <at> gmail.com]
> Sent: 31 October 2008 18:37
> To: qooxdoo Development
> Subject: Re: [qooxdoo-devel] HtmlArea for 0.8 still not usable
>
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi Alex,

Have you some time o improve HtmlArea ?

I tried it, the focus bug is really out, but there are still few bugs
that making html area not so usable for me.

I try to describe them:

1. There is something wrong with first paragraph. When you try on
first focus to remove everything (use Ctrl+A and Delete) and then type
some text, there will not be paragraph.

For example I tried to set alignment and instead paragraph it will
create DIV. Here is some text output:
  <div style="text-align:center;">dsfsdf</div><p>sdf</p><p
style="text-align:left;">sdf</p><p>sf</p><p>sdfs</p><p>f</p>

2. There is no full control over bold, italic, etc. I can toggle them,
but I can't set them for example to true or false that's bad.

3. I don't know how to control styles and allow styles.

4. I don't know how to use CSS style in HtmlArea, because documents
are usually edited like web preview.

Only 4 points now, I can continue when these wil be solved (there are
critical for me)

What do you thing ?
(Continue reading)

Alexander Back | 3 Nov 10:38
Favicon

Re: HtmlArea for 0.8 still not usable

Hi Petr,

Petr Kobalíček wrote:
> Hi Alex,
> 
> Have you some time o improve HtmlArea ?
I try to work on the HtmlArea and improve it, but there are also a lot 
of other work to do, especially for the upcoming 0.8.1 release. So I 
don't want to promise anything that I can not keep.

> I tried it, the focus bug is really out, but there are still few bugs
> that making html area not so usable for me.
> 
> I try to describe them:
> 
> 1. There is something wrong with first paragraph. When you try on
> first focus to remove everything (use Ctrl+A and Delete) and then type
> some text, there will not be paragraph.
> 
> For example I tried to set alignment and instead paragraph it will
> create DIV. Here is some text output:
>   <div style="text-align:center;">dsfsdf</div><p>sdf</p><p
> style="text-align:left;">sdf</p><p>sf</p><p>sdfs</p><p>f</p>
> 
> 2. There is no full control over bold, italic, etc. I can toggle them,
> but I can't set them for example to true or false that's bad.
> 
> 3. I don't know how to control styles and allow styles.
> 
> 4. I don't know how to use CSS style in HtmlArea, because documents
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi Alex,

1. bug (Paragraph) submitted as #1538.
2. bug (Full control over B, I, U, S) submitted as #1539
3. bug (There is no API for controlling styles and current path)
submitted as #1540
4. bug merged with #1540.

Alex, and I noticed one issue about firefox focus bug. It will focus
now, but cursor is not blinking (but I can type). Also report this ?

Cheers
- Petr

2008/11/3 Alexander Back <alexander.back <at> 1und1.de>:
> Hi Petr,
>
> Petr Kobalíček wrote:
>> Hi Alex,
>>
>> Have you some time o improve HtmlArea ?
> I try to work on the HtmlArea and improve it, but there are also a lot
> of other work to do, especially for the upcoming 0.8.1 release. So I
> don't want to promise anything that I can not keep.
>
>> I tried it, the focus bug is really out, but there are still few bugs
>> that making html area not so usable for me.
>>
>> I try to describe them:
>>
(Continue reading)

Alexander Back | 6 Nov 09:48
Favicon

Re: HtmlArea for 0.8 still not usable

Hi Petr,

Petr Kobalíček wrote:
> Hi Alex,
> 
> 1. bug (Paragraph) submitted as #1538.
> 2. bug (Full control over B, I, U, S) submitted as #1539
> 3. bug (There is no API for controlling styles and current path)
> submitted as #1540
> 4. bug merged with #1540.
Many thanks for filing all those bugs.

> Alex, and I noticed one issue about firefox focus bug. It will focus
> now, but cursor is not blinking (but I can type). Also report this ?
You can report it, however I've just re-tested it with Firefox 2 and 3 
and I can't reproduce the behaviour you described. My test code was 
minimalistic using the "setVisibility" method. How is your setup where 
you encounter this behaviour?

cheers,
   Alex

P.S. if in doubt, report it as a bug :)

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
(Continue reading)

Re: HtmlArea for 0.8 still not usable

Hi Alex,

I checked that bug again and it is interesting :-D

When I click to first row, cursor is displayed and blinking, when I
click somewhere else, cursor will hide, but I can type.

I think that this my old snip should demonstrate the behavior:

qx.Class.define("bfly.main.Application",
{
  extend : qx.application.Standalone,

  members :
  {
    // [Entry point]
    main: function()
    {
      // [SuperClass]
      this.base(arguments);

      // [Main Container]
      this._container = new qx.ui.container.Composite(
        new qx.ui.layout.VBox().set({
          spacing: 1
        })
      );
      this.getRoot().add(this._container, {edge:0});

      // [MenuBar]
(Continue reading)

Alexander Back | 3 Nov 10:25
Favicon

Re: [SPAM] RE: HtmlArea for 0.8 still not usable

Hi John,

John Spackman wrote:
> Hi Alex,
> 
> IMHO it's not that HtmlArea itself is unusable, it's that it is often not usable on its own; in order to
integrate it into an application there needs to be simple toolbars for bold/italic/etc but also more
complex issues like:
> 
> +. support for styles (H1, H2, etc as well as custom styles in SPAN tags) - this requires some fairly
involved code manipulating the DOM
> +. An image picker where the server can be browsed in some way
> +. Other dialogs for inputing and editing URLs etc
> 
> The current demo makes HtmlArea look like a poor cousin to FCKEditor/TinyMCE/etc and it's only when you
look further that you realise that HtmlArea is something _good_ but that is intended to be built upon.  I
only realised it when I got fed up with FCKEditor being so slow, and I'm not the only one to make that mistake.
Yes the current demo is not that impressive, but it is intented to 
demonstrate the core HtmlArea component and act as reference 
implementation for the component. You're right, that is should become 
more clear, that the HtmlArea is a component to build upon. The 
documentation should point out this clearer.

> Petr & I briefly raised these issues while you were on holiday (my [slightly buggy] version is available
here http://www.zenesis.com/qx/dev/) and we discussed working on a contrib.  
> I'd like to suggest that it becomes part of the HtmlArea contrib - anyone who wants a drop-in user friendly
editor uses the HtmlEditor class but internally there's a clear separation between the toolbars etc and
the HtmlArea.  At the very least, it would be a great demo for the HtmlArea control.
That sounds great and your demo is really nice.
However I would suggest another approach: create a new contrib-project 
(Continue reading)

benco | 6 Nov 11:28

Re: HtmlArea for 0.8 still not usable


In fact, I you need a WYSIWYG editor fast, it's really easy to integrate
TinyMCE in Qooxdoo. I've tested it in Qx 0.7 and the speed was really
raisonnable compared to FCKEditor. 

You can use this kind of code :

v Qx 0.7:

var initValue; // set the tinyMCE content
var uniqid; // pseudo-random id to set to allow several tinyMCE instance

var widget = new qx.ui.embed.HtmlEmbed();
var textarea = '<textarea id="tinymce_'+uniqid+'"
name="tinymce_'+uniqid+'">'+initValue+'</textarea>';
widget.setHtml(textarea);

// the event is registered to avoid loading to many instances (ex: if you
use a tabbed system) 
widget.addEventListener("appear",function(e)
{
	if (tinyMCE && !this.tinyEnabled) 
	{ 
		tinyMCE.execCommand("mceAddControl", false, "tinymce_"+uniqid); 
		this.tinyEnabled=true;
	}
}
				
widget.getValue = function()
{
(Continue reading)

Alexander Back | 6 Nov 13:59
Favicon

Re: HtmlArea for 0.8 still not usable

Hi benco,

benco wrote:
> In fact, I you need a WYSIWYG editor fast, it's really easy to integrate
> TinyMCE in Qooxdoo. I've tested it in Qx 0.7 and the speed was really
> raisonnable compared to FCKEditor. 
Just for completion: the HtmlArea component is also available for 
qooxdoo 0.7.x releases if you need a WYSIWYG widget which seamlessly 
integrates into qooxdoo applications :)

cheers,
   Alex

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Andreas Ecker | 9 Oct 09:25

Re: HtmlArea for 0.8 still not usable

Hi Petr!

> Qooxdoo is very good framework, but it totally fails
> in html editing. It's not usable for any kind of cms systems (also for
> ecommerce systems, because here should be html content too).

That statement seems to be too negative. At least the 0.7 version of
HtmlArea is successfully being used in production by large-scale apps.

While the HtmlArea may not be "perfect" just yet, it should already be a
solid foundation for a cross-browser html editing widget. Goal is not to
have another feature "monster" (there are way too many on the web
already). 

Thanks for your recent collaboration with Alex for a preliminary 0.8
version :-), so lets continue to make HtmlArea one of the best
components of that kind (as has been pointed out Alex is to return to
work next week). Your input is much appreciated,

Andreas

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Chris Banford | 9 Oct 10:24
Favicon
Gravatar

Re: HtmlArea for 0.8 still not usable

Andreas Ecker wrote:
> While the HtmlArea may not be "perfect" just yet, it should already be a
> solid foundation for a cross-browser html editing widget. Goal is not to
> have another feature "monster" (there are way too many on the web
> already)
>   

I completely agree with Andreas on this one -- the HtmlArea code should 
be kept as lean and clean as possible!

Adding pre-built Toolbars and such will just make it a pig, and most 
developers will want it to do something that it doesn't/can't out of the 
box. Much better would be a very solid core html editing backdrop, that 
we can easily hook into with our own code (am sure this is the direction 
you've taken already).

I haven't looked into it in detail yet, but it should give us a range of 
events that will let us act on changes occurring while the user is doing 
edits, so we can do things like filter the generated html code 
efficiently, as well as being able to set properties that will 
enable/disable various editing abilities...

+1 for a lean, fast html editor 'core' :-)

-Chris

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
(Continue reading)


Gmane