Hi All,

It has been mentioned a couple of times now that having multiple APIs 
for use with fltk3 means multiple times the test load.

I suggest what is required is an automated test system, not as a 
replacement to manual testing but as a way to confirm that each test 
application renders as per the reference render.
The test applications already exist, what seems to be needed is the 
method to run them, obtain UI capures, send events to the program and 
obtain more captures, compare the captures to the renders and log the 
results.
This would boost confidence in the integrity of the various APIs and in 
the core of fltk while the developer was busy doing something equally 
important - like getting enough sleep at night :  )

I still feel that over the longer term, bringing development energy back 
together instead of continuing down divergent paths is better for the users.
If the price of that is we have to support the 1.3.x API then we need to 
make the method used to support it nice, slim and standardised so it 
doesn't take much work to include it.
To state it from my point of view, the goals of F3 are:
- To provide a stable, clean, and ready for expansion core FLTK
- To provide a 100% code compatible wrapper set around the core so F1 
(and F2) users can move to F3.
- To unify development effort going forward so that everyone benefits 
faster from everything.
- To allow the retirement of F1 and F2 branches from support as F3 
allows the old code to build while allowing the use of the new core API 
as well.
- To prevent the "Help! which version should I be using?!?!" panic which 
scares off new users.

I feel that, whatever decision is made for the API, F3 can only be good 
for the community as a whole.
Most of the bloat of the other frameworks comes from architectural 
decisions. I don't see FLTK ever weighing in at the same sort of mass as 
QT, GTK or wx.
It would probably be very useful if users of the 1.3 API would build 
against both 1.3 and 3(1.3 compatability API) and provide feedback as to 
performance differences and what breaks.

-- 
-Edward Hull
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to