| |
| |
On 11/20/22 01:34, 'melcher....@googlemail.com' via fltk.coredev
wrote:
Hi Devs,
tl;dr : I would like to overhaul the menubar code, and I
would like to do it incrementally, so we can find regressions. I
want to use the master branch for that, but I would like to hear
you first, since that may add work.
Cool! Sounds a little scary though, lol. But maybe that's
needed.
We seem to keep holding back 1.4.0 release, so I'm thinking we'd
need
to keep the old code the default, but could maybe make your code
a
build option that can be turned on to test, and later it could
become
the default?
I know that old application code might be using perhaps
"unsavory"
ways of accessing the internals of Fl_Menu's data to work around
API limitations, which a code cleanup might break.
Or, should the rewrite have a new API, e.g. Fl_Menubar_V2,
Fl_Menu_V2
so you can go bananas on the API, without having to worry about
breaking
old code (since the old Fl_Menubar / Fl_Menu API would remain
"forever")
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/db552b35-3f6d-42ad-5d92-80b4241e6d9d%40seriss.com.
[ Direct Link to Message ] | |
|
| |
