I don't want to delay the release of fltk 1.3, as I told I applied this  
patch over a original fltk-svn and it compile and run all tests on win32  
as well I'm using it for my own applications.

Some of the modifications I think will improve fltk and benefit other  
users and will leverage my task of update my working fltk with the daily  
changes.

I propose for apply then on a fresh trunk and play a bit with it and try  
compile other apps with it to see if could have any incompatibiliy, in the  
later case I'll be pleased to try correct then.


En 12/12/2010 15:48:06, Matthias Melcher <[email protected]> escribió:

>
> On 12.12.2010, at 15:05, Domingo Alvarez Duarte wrote:
>
>> Here there is most of my diffs to fltk 1.3 trunk hoping they can be  
>> incorporated on the official distribution.
>> It was tested and seems to work fine with fltk 1.3 trunk as of today,  
>> I'm using it on my applications too.
>
> Holy cow, Domingo!
>
> This is great work with lots of additions, some of them very useful,  
> some a little less useful for the general public. You really put a lot  
> of work into your customized FLTK.
>
> But here is my problem: you have packed 16 issues into three patches. If  
> I go ahead and just apply them we will have big troubles if anything  
> breaks. It would have been nice to see them isolated. Also, I need much  
> more of a description for the larger segments, like the Fl_Help_View  
> patch.
>
>
> I am really stunned just by the amount of code. So what's the best way  
> to proceed?
>
> 1: release 1.3.0 and apply your patches later. This way, everyone could  
> have a working 1.3 before the end of the year as planned
>
> or
>
> 2: apply some of your patches now, so they make it into 1.3.0, but that  
> would put us back a month or so until everything is tested and  
> documented.
>
>
> - Matthias
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to