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 called e.g. "HtmlEditor" which uses the HtmlArea component and builds upon the core component the toolbars and all the whistles and bells one can expect of an editor component. This way we can keep the core component light and clean for all those you only need the editing component and create a ready-to-use out-of-the-box editor component for all those who just want to drop in the whole component into their application. I really like to see such an editor component with toolbars and dialogs in the contrib. This would also help us in pointing out the differences between the core component (HtmlArea) and the editor component (let's call it "HtmlEditor"). How does this proposal sound to you? cheers, Alex > > > -----Original Message----- > From: Alexander Back [mailto:[EMAIL PROTECTED] > Sent: 31 October 2008 09:15 > To: qooxdoo Development > Subject: Re: [qooxdoo-devel] 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 <[EMAIL PROTECTED]>: >>> 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 <[EMAIL PROTECTED]>: >>>> 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:[EMAIL PROTECTED] >>>> 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----- >>>> From: Petr Kobalíček [mailto:[EMAIL PROTECTED] >>>> 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 >>>> 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() >>>> { >>>> // [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] >>>> this._tabView = new qx.ui.tabview.TabView(); >>>> this._container.add(this._tabView, {flex: 1}); >>>> >>>> for (var i = 0; i < 3; i++) >>>> { >>>> var page = new qx.ui.tabview.Page("Page " + i); >>>> var area = new htmlarea.HtmlArea(); >>>> >>>> page.setLayout(new qx.ui.layout.Canvas); >>>> page.add(area, {edge: 0}); >>>> >>>> this._tabView.add(page); >>>> } >>>> } >>>> } >>>> }); >>>> >>>> When you use TABs, you can't focus to previously hidden HtmlAreas in >>>> Firefox. >>>> >>>> c) And for John, >>>> >>>> John, I'm doing something very similar to your work. I called it >>>> RichEditor and it's HtmlArea with toolbars with some customizing way. >>>> My code depends to our system, but I try to make it generic. We can >>>> colaborate on this if you want. >>>> >>>> Cheers >>>> - Petr >>>> >>>> 2008/10/9 Fabian Jakobs <[EMAIL PROTECTED]>: >>>>> 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 >>>>>> 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 >>>>>> itself should stay a plain html editing widget without custom chrome >>>>>> (toolbars, etc.). Well, we'll figure out the details, also when Alex is >>>>>> back. >>>>>> >>>>> I absolutely agree that the core HtmlArea widget should only focus on >>>>> plain Html editing but why not include it into the current HtmlArea as >>>>> an example application. It is not required to have just one example >>>>> application in a contrib project. This way example editor is always in >>>>> sync with the editing component and serves as a good example. >>>>>> What do you think? In the meantime you could have a look at >>>>>> http://contrib.qooxdoo.org for the contribution details and then email >>>>>> me directly to answer all your questions and getting you started, >>>>>> >>>>>> >>>>> Best Fabian ------------------------------------------------------------------------- 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=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
