Re: [fltk.development] RFC: decision on license to useforfltk/examplessource code
On 01.03.2013 04:16, Michael Sweet wrote: On 2013-02-28, at 8:24 PM, Albrecht Schlosser ... wrote: IIRC I haven't seen a real freeware (public domain) proposal. Wouldn't this be appropriate for the example code? Unfortunately, public domain isn't a universally-recognized status for copyrightable works. What you ultimately have to do is say I hold the copyright on this code and I say you can do whatever you want with it. Thanks for clarification. I'll take a look at the other licenses during the weekend, if I can find the time... Albrecht ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] FLTK version number update and release process [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packaged properly]
1) For large commercial software, I have a VERSION file in the main directory with a single line in it: VERSION=#.# This can be include'ed from Makefiles to define macros used on everything from compile lines to Makefile construction to documentation builds and tar filenames. In some way, the value in Enumerations.H is what we'd want to pick up - but that is not perhaps the most accessible format for it? Oh, and another question: WHEN do we upgrade the version number(s)? (a) immediately after one release, for the next release, or What Mike said: As soon as *anything* in SVN changes after a release, we need to bump the version numbers in some way. Ideally, I suppose, we might bump it to a temporary number, then change that to the formal number for the next release, so that folks can determine if the build they have is a formal release or some svn checkout or something...? (I sort of have this in some of my own builds, where the Makefile calls a script, which calls svnversion -n . at build time to get the rev number from the rep,o and writes that into a version.h header that the code pulls in. For formal releases I can override that behaviour to put in an actual number... The downside is that I can only build this on hosts that use Makefiles and have svn installed, which can be a pain on some Windows machines...) Selex ES Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] RFC: decision on license to use forfltk/examplessource code
IIRC I haven't seen a real freeware (public domain) proposal. Wouldn't this be appropriate for the example code? I see Mike's already said this, but thought I'd re-iterate: way back when, in my naivety, I went looking for a Public Domain license, and was told that such a thing really doesn't work well, as the whole concept of public domain doesn't even exist in a lot of legal systems... As ever, IANAL... Selex ES Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England Wales. Company no. 02426132 This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] FLTK version number update and release process [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packaged properly]
On Fri, 1 Mar 2013, MacArthur, Ian (Selex ES, UK) wrote: Oh, and another question: WHEN do we upgrade the version number(s)? (a) immediately after one release, for the next release, or What Mike said: As soon as *anything* in SVN changes after a release, we need to bump the version numbers in some way. Ideally, I suppose, we might bump it to a temporary number, then change that to the formal number for the next release, so that folks can determine if the build they have is a formal release or some svn checkout or something...? (I sort of have this in some of my own builds, Suggestion: After the release is done, append post to the version number. Rgds, --- Peter Åstrand ThinLinc Chief Developer Cendio AB http://cendio.com Teknikringen 8 http://twitter.com/ThinLinc 583 30 Linköpinghttp://facebook.com/ThinLinc Phone: +46-13-214600http://plus.google.com/112509906846170010689___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] FLTK version number update and releaseprocess [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packagedproperly]
On 01.03.2013 11:55, Peter Åstrand wrote: Suggestion: After the release is done, append post to the version number. The version number must be numeric, three parts only, see: http://www.fltk.org/doc-1.3/enumerations.html The FLTK version number is stored in a number of compile-time constants: FL_MAJOR_VERSION - The major release number, currently 1. FL_MINOR_VERSION - The minor release number, currently 3. FL_PATCH_VERSION - The patch release number, currently 2. FL_VERSION - A combined floating-point version number for the major, minor, and patch release numbers, currently 1.0302. We can't change this, but *maybe* we could _add_ some string to be used in another variable/macro for those who want to get that additional info. FL_VERSION_SUFFIX or something like that, maybe. Albrecht ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] FLTK version number update and releaseprocess [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packagedproperly]
On 03/01/13 01:33, MacArthur, Ian (Selex ES, UK) wrote: What Mike said: As soon as *anything* in SVN changes after a release, we need to bump the version numbers in some way. Or, just change it immediately after release. Changing the version number is itself a change, and would therefore bump the svn version#. If we do a release of 4.5.6 and its svn# is , then we immediately change the version# to 4.5.7 and check it in (svn#6667) and from there we tweak away. Ideally, I suppose, we might bump it to a temporary number, Right, I think linux (or something) used even release numbers for dev (.0, .2, etc), and odd numbers for release versions (eg. .1, .3, etc). This way if you built an app against a dev version, one could tell from the FLTK version number. Or, we could work the SVN version number into Enumerations.H (eg. FL_SCCS_VERSION?) which might be nice to have anyway so that someone with an app can see the FLTK version /and/ SCCS #. I think svn allows for hook scripts to be triggered whenever there's a checkin for this kind of thing. Pretty sure cvs had this too. Not sure what that number becomes if we ever move to git, though.. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] FLTK version number update and releaseprocess [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packagedproperly]
On 1 Mar 2013, at 15:39, Greg Ercolano wrote: On 03/01/13 01:33, MacArthur, Ian (Selex ES, UK) wrote: What Mike said: As soon as *anything* in SVN changes after a release, we need to bump the version numbers in some way. Or, just change it immediately after release. Changing the version number is itself a change, and would therefore bump the svn version#. Ah, fair point. Though in a sort of self-fulfilling prophecy kinda way... Right, I think linux (or something) used even release numbers for dev (.0, .2, etc), and odd numbers for release versions (eg. .1, .3, etc). Yes - I always quite liked that, but they stopped doing it that way... Or, we could work the SVN version number into Enumerations.H (eg. FL_SCCS_VERSION?) which might be nice to have anyway so that someone with an app can see the FLTK version /and/ SCCS #. I think svn allows for hook scripts to be triggered whenever there's a checkin for this kind of thing. Pretty sure cvs had this too. I use svnversion for this in my own build script, but you are right, the svn hooks can probably do this in a neater way. Not sure what that number becomes if we ever move to git, though.. What it becomes, as you know, is a human-opaque string of gibberish... (Technically I understand why it is like that, but I really can't believe we couldn't figure out some way to hide that behind some human-friendly index...) ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] FLTK version number update andreleaseprocess [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2tarball not packagedproperly]
Not sure what that number becomes if we ever move to git, though.. What it becomes, as you know, is a human-opaque string of gibberish... (Technically I understand why it is like that, but I really can't believe we couldn't figure out some way to hide that behind some human-friendly index...) Yes, I think there are some hacks recommended on the net. I don't think any of the devs have seen a reason to move the core to git, but perhaps we could continue to use svn for core dev, but have svn commits get cc'ed to git, so that people could develop against it. I think the main benefit of git is that non-devs can easily provide solutions against git, instead of having to maintain separate snapshots on websites that often go stale if enough time passes. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
[fltk.general] Question about Fl_Input
Hello, Is it possible to send text typed into an Fl_Input box to another box without using a callback via an enter button? The examples I have seen use a button to trigger a callback. I would like to have the user type an answer into an Input box and then hit the enter key on the keyboard. I would then like to send the user input to another box without any buttons in the window. Can this be done? I am guessing the when(ENTER_PRESSED...) function might do the trick, but I am not sure how to go about this. If this can work, what functions would be used and could you provide a short statement for syntax? Also, if I am wanting to loop this series of events, how would I go about this if the Input box and the other text box are dynamically allocated? Should they be destroyed and recreated with each iteration to avoid memory leaks? I can send my code if that would be helpful. Please pardon my ignorance and thanks for any suggestions. Edgar Crockett ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
Re: [fltk.general] Question about Fl_Input
Is it possible to send text typed into an Fl_Input box to another box
without using a callback via an enter button?
Sure; pretty much any fltk widget (including the windows themselves) can be
associated with a callback.
So for a Fl_Input you can set the when() as FL_WHEN_ENTER_KEY, then if you hit
the enter key, the callback for the input widget should run.
If this can work, what functions would be used and could you provide a
short statement for syntax?
Also, if I am wanting to loop this series of events, how would I go
about this if the Input box and the other text box are dynamically
allocated? Should they be destroyed and recreated with each iteration
to avoid memory leaks?
Can you clarify; I'm not clear what you are asking here, can you outline what
you are trying to achieve, then we can suggest some ways you might implement
that.
Anyway, here's a little fluid file that might show how the enter key stuff
works...
--
# data file for the Fltk User Interface Designer (fluid)
version 1.0302
header_name {.h}
code_name {.cxx}
decl {\#include stdio.h} {selected private local
}
Function {} {open
} {
Fl_Window main_win {open
private xywh {856 299 543 337} type Double visible
} {
Fl_Button quit_bt {
label Quit
callback {main_win-hide();}
private xywh {455 280 80 45} box THIN_UP_BOX
}
Fl_Browser brws {
private xywh {40 80 405 245} box THIN_DOWN_BOX
}
Fl_Input input_widget {
label {input:}
callback {printf(Enter key hit: value is %s\\n, input_widget-value());
fflush(stdout);
brws-add( input_widget-value());}
private xywh {65 31 190 28} box THIN_DOWN_BOX when 10
}
}
}
--
Ian
Selex ES Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England Wales. Company no. 02426132
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
[fltk.general] Which Fl_Menu_Bar submenu is current?
Hello, How can I find out which dropdown menu of an Fl_Menu_Bar is currently dropped down (if any)? I need to know this in an add_timeout()/repeat_timeout() timer. Thanks for any suggestions, Howard Rubin ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
