because I have not contributed anything in such a long time, I wanted to ask first before making changes.
Short term, I would love to update Fluid (fix all STRs,
make it use Fl_Tree,
add Fl_Grid,
etc.), so I want to add the header files to be visible in the IDE.
Should I commit directly to fltk/fltk for major milestones, or would you prefer Pull Requests?
For example, I would like to add set (CMAKE_XCODE_GENERATE_SCHEME 1) to line 72 in CMake/setup.cmake. This keeps Xcode form asking to rebuild all schemes after every CMake change and simply rebuilds them. The disadvantage is, that it overwrites custom schemes, which only Core developers would use. Is anyone carefully crafting schemes, or can I commit this change?
If the Fluid upgrade works out, I may feel confident enough to get Nano/Pico up to date and implement SDL/Framebuffer/Android rendering correctly.
Hi devs,
because I have not contributed anything in such a long time, I wanted to ask first before making changes.
Short term, I would love to update Fluid (fix all STRs, make it use Fl_Tree, add Fl_Grid, etc.), so I want to add the header files to be visible in the IDE. Should I commit directly to fltk/fltk for major milestones, or would you prefer Pull Requests?
If the Fluid upgrade works out, I may feel confident enough to get Nano/Pico up to date and implement SDL/Framebuffer/Android rendering correctly.
Hi devs,…
For example, I would like to add set (CMAKE_XCODE_GENERATE_SCHEME 1) to line 72 in CMake/setup.cmake. This keeps Xcode form asking to rebuild all schemes after every CMake change and simply rebuilds them. The disadvantage is, that it overwrites custom schemes, which only Core developers would use. Is anyone carefully crafting schemes, or can I commit this change?
Thanks guys. I just tried the first commit and for reasons that I don't understand, it also pushed "Merge branch 'fltk:master' into master". Albrecht, could you please check if this reversed Manolo's changes (I don't think so) and reverse if I ruined anything. Bad start :-( .
Yes, Xcode, and yes, I read you mai and did the git config --global pull.ff only , but I I am afraid it doesn't fix Xcode, and I don't really want to try it either. Xcode does the typical Mac thing: it looks simple and easy on the outside, but gives the user no clue on what is happening inside. Sorry about the noise.
Again, maybe Manolo can help. Manolo, can you tell us how you are working now? Are you still using Xcode?
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/d25ced2f-e56b-9326-e2f0-b5b369e8614f%40online.de.