On Sun, Dec 16, 2007 at 04:58:38PM +0000, Jeremy Henty wrote:
On Sun, Dec 16, 2007 at 09:53:06AM -0300, Jorge Arellano Cid wrote:
BTW, I decided to bind it to the html parser ...
Hey, *I* wanted to do that! Why are you spoiling my fun? :-) Guess I'll have to look at selections instead.
There was a small chance of you still hesitant to dig in the parser... I'll happily expect the full patch for the SELECT element! :-)
The next time you visit a form with a TEXTAREA, it will show! :-)
Which means I can use Dillo to post flamebait to blogs. Clearly a great milestone has been passed! :-)
I'm afraid that's not yet the case.
Please test and polish to full functionality.
Text is not yet submitted, the enter key doesn't work as enter key when the textarea is selected, no word wrapping, rows&columns...
OK, I'm looking at adding the rows and columns parameters. It should be easy, except that I'm not sure which class to add the extra members to. Options are:
1) dw::core::ui::MultiLineTextResource 2) dw::fltk::ui::FltkMultiLineTextResource
I'm inclined to say 2), since I don't like the idea of hardwiring this API into the base class. Do you agree?
From a distance, to me, it looks like the idea is to have MultiLineTextResource as an abstraction that can have different potential implementations (as FLTK2, GTK2, etc). If this is correct, FltkMultiLineTextResource is the implementation of that API in FLTK2. Now, I see no problem in implementing it in FltkMultiLineTextResource to test and then to decide what general API should go (or not) in the base class. -- Cheers Jorge.-