Bill Spitzak wrote:
I very much dislike all the fltk3 stuff everywhere in the code.
It sounds like the most popular solution is to call the namespace fl
(all lowercase). This avoids collisions with fltk2 and fltk1 names. The
assumption is that fltk3 will be so perfect that future collisions
On 24.02.2012 18:24, Greg Ercolano wrote:
Perhaps I wasn't clear; what I meant about setting up svn:
I didn't bother simulating FLTK's SVN master repository config,
so that my machine could simulate an SVN server.
Okay, that was { a | my } misunderstanding, then.
end to that this endless confusion with
users starting new development with FLTK 2 would have an end...
I think this could be solved by changing the php code
in software.php to highlight the FLTK2 and FLTK3 releases
*IN RED* with a header that says DEVELOPMENT USE
On 02/22/12 09:13, Albrecht Schlosser wrote:
I'd say its easier to do it locally once you've installed your own
test environment.
Thanks for the advice.
Yes, got it all working in about 45 mins.
Just defaults for everything.
Installed LAMP and downloaded the
On 21.02.2012 10:50, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I very much dislike all the fltk3 stuff everywhere in the code.
Hmm, I'm OK with it I think. I like it better than just fl.
It sounds like the most popular solution is to call the namespace fl
(all lowercase). This avoids
