tl;dr : yes, that sounds great
long answer and question:
Fluid: I have reorganised Fluid a little bit and fixed a few pressing issues, like i18n, dnd, insertion points, etc. . Fluid itself probably needs a separate post though.
Preferences: are 80% done and fix the most common issues: where is my file, locale, etc. . Still to do is the location of files on Linux.
Text Styles: background color should be relatively easy to implement
OTOH: there is some dead code that I started just before my long break.
- So, the Nano/Pico stuff, should we remove that before the big release? It's not working as intended, still some users ran with it and implemented half-working stuff. IMHO, if it isn't done, it has no place in a release (or better: I should have never checked that in to begin with. Sorry!)
- The Android stuff is also very half-assed. It pollutes some of the CMake files and it is just a proof of concept. Yet some users seem to have at least tried it. Same question: remove all traces, fix it, and put it in 1.5.0? Or leave it and drag it along?
I'll add more as things come to mind.
On 1/22/22 8:53 AM, Albrecht Schlosser wrote:
On 1/22/22 13:00 'melcher....@googlemail.com' via fltk.coredev wrote:
[..] Fluid itself probably needs a separate post though.
What "post" do you mean?
On 1/22/22 18:34 Gonzalo Garramuño wrote:
>
> Where can I find the new i18n code? I would like to test it when I
> have the time.
Fluid has an own chapter in the docs. Do you think that (some of) the new features should be mentioned?
> Preferences: are 80% done and fix the most common issues: where is my file, locale, etc. . Still to do is the location of files on Linux.
I'd like to have the XDG stuff (for others: location of preferences files) implemented in 1.4.0 though
> Text Styles: background color should be relatively easy to implement
You mean styles in Fl_Text_Display? Would be great to have, I think this has been a FAQ.
> OTOH: there is some dead code that I started just before my long break.
I'd love to remove all this for a clean release.
On 1/22/22 12:45 PM, 'melcher....@googlemail.com' via
fltk.coredev wrote:
I'd love to remove all this for a clean release.
Ok, I will put it into an experimental branch as soon as I get another +1.
A cleanup is a +1 from me, unless you think it'd in any way
delay the 1.4.0 release sched..
On 1/22/22 12:45 PM, 'melcher....@googlemail.com' via fltk.coredev wrote:
I'd love to remove all this for a clean release.
Ok, I will put it into an experimental branch as soon as I get another +1.
A cleanup is a +1 from me, unless you think it'd in any way
delay the 1.4.0 release sched..
On 1/22/22 23:03 Greg Ercolano wrote:
On 1/22/22 12:45 PM, 'matt' via fltk.coredev wrote:
I'd love to remove all this for a clean release.
Ok, I will put it into an experimental branch as soon as I get another +1.
... in your fork, please. (?)
A cleanup is a +1 from me, unless you think it'd in any way
delay the 1.4.0 release sched..
It's the opposite: removing the unused and unfinished test platforms would speed up the schedule - at least for me.
If would be really helpful if you could try it out too and point me at issues, so I can fix stuff before 1.4.0 . ;-)
I tried it with xgettext and all seems to work fine. I'll do more testing when I have more time.