[fltk.development] [RFE] STR #2936: fluid: needs mods to allow defining a 'namespace'

2013-03-21 Thread Greg Ercolano

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2936
Version: 1.3-feature


(Submitted on behalf of Gonzalo's request on fltk.general 03/20/13)

Fluid seems not to allow one to define a 'namespace' for functions/methods
defined in fluid.

For instance, New-Code-Declaration does not allow one to define
two entries:

namespace whatever {

..and

};

..due to bracket imbalance warnings.

One solution would be to allow the warnings to be ignored (ie. dialog to
have an 'ignore' button)

Another would be to modify Fl_Decl_Type::open() to allow namespace.. and
}; through without a code checks.

Perhaps there are other ways to support 'namespace', similar to
New-Code-Declaration Block.

Gonzalo mentions fltk2's fluid supports namespaces; I'm not familiar with
it, but perhaps it has features we can port to 1.3


Link: http://www.fltk.org/str.php?L2936
Version: 1.3-feature

___
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev


Re: [fltk.general] Fltk Preferences are noisy...

2013-03-21 Thread chris
I think there was alreay a STR for that (with a possible solution):

http://www.fltk.org/str.php?L2823+P0+S-2+C0+I0+E0+QFl_Preference

Cheers,
chris

 Widget handle() method upon first use calls Fl::visible_focus() which through 
 Fl::option() reads fltk standard preferences (that is (Fl_Preferences::SYSTEM,
 fltk.org, fltk) and (Fl_Preferences::USER, fltk.org, fltk)).
 Fl::option() function (Fl.cxx, line around 1944) just constructs these 
 preferences, uses only get() methods and then destructs these preferences. 
 However upon
 destruction the preferences are flushed/re-written on the disk.
 Is that necessary if only get() methods are used and preferences are not 
 changed?

 R.


___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk


Re: [fltk.general] Fltk Preferences are noisy...

2013-03-21 Thread MacArthur, Ian (Selex ES, UK)
Yes indeed; that looks like the same issue.

Does look like something that could be changed without harm, too.

Be handy if someone who is familiar with the preferences stuff had a view on 
this - Matthias' DSL is back on we hear; maybe he's still a little busy after 
the moves though!


 I think there was alreay a STR for that (with a possible solution):
 
 http://www.fltk.org/str.php?L2823+P0+S-2+C0+I0+E0+QFl_Preference
 
 Cheers,
 chris
 
  Widget handle() method upon first use calls Fl::visible_focus() which
 through Fl::option() reads fltk standard preferences (that is
 (Fl_Preferences::SYSTEM,
  fltk.org, fltk) and (Fl_Preferences::USER, fltk.org, fltk)).
  Fl::option() function (Fl.cxx, line around 1944) just constructs
 these preferences, uses only get() methods and then destructs these
 preferences. However upon
  destruction the preferences are flushed/re-written on the disk.
  Is that necessary if only get() methods are used and preferences are
 not changed?
 
  R.



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] docking windows

2013-03-21 Thread asif saeed
Hi,

I have turned to FLTK after a very long time. Almost a new user. I just
wanna know if you have support available for docking windows? Or do you
have to make do it in order to achieve it?

-Asif
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk


Re: [fltk.general] fltk1.3 namespace in fluid

2013-03-21 Thread Greg Ercolano
 I am trying to port my software from flkt2 to fltk1.3.
 However fluid1.3 complains due to lacking namespaces.
 Any chance of adding namespaces to fluid1.3 or a work-around?

Gonzalo, I've opened STR #2936 for this feature request,
so that it doesn't get lost.

___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk


Re: [fltk.general] fltk1.3 namespace in fluid

2013-03-21 Thread MacArthur, Ian (Selex ES, UK)

  I am trying to port my software from flkt2 to fltk1.3.
  However fluid1.3 complains due to lacking namespaces.
  Any chance of adding namespaces to fluid1.3 or a work-around?
 
 Gonzalo, I've opened STR #2936 for this feature request,
 so that it doesn't get lost.


Oh, was Gonzalo asking whether fluid could support namespaces? I had thought he 
was asking if fltk-1.3 itself would have namespaces (which for compatibility I 
guess it can't).

I suppose in fluid a namespace might be entered a bit like a grouping widget, 
such that other entities would be declared nested inside it? Is that the sort 
of thing?




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


Re: [fltk.general] fltk1.3 namespace in fluid

2013-03-21 Thread Roman Kantor
I am using namespaces in fluid, although with some tricks. Fluid complains (and 
does not accept) lines with open { brackets so first I have defined macros

#define NAMESPACE_START(name)  namespace name {
#define NAMESPACE_END}

and then use these macros as

1) either in declaration block and putting all your code in that declaration 
block and switch property of that declaration block to in header and source 
file

2) at the beginning and end of fluid files in simple declarations but  you 
need to do it twice, one for option include in header file and one for 
include
in source file as there is no option to include in both for simple 
declarations.


R.


___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk


Re: [fltk.general] fltk1.3 namespace in fluid

2013-03-21 Thread Greg Ercolano
On 03/21/13 11:24, MacArthur, Ian (Selex ES, UK) wrote:
 Oh, was Gonzalo asking whether fluid could support namespaces?
 
 I suppose in fluid a namespace might be entered a bit like a grouping widget,
 such that other entities would be declared nested inside it? Is that the sort 
 of thing?

Right, I think so; quoting the OP:
Any chance of adding namespaces to fluid1.3

..and I can certainly see the need for it, if one wanted to create
a widget or suite of tools in fluid attached to a namespace, or be able
to have multiple namespaces.

And yes, I think both the thing we use in fluid now for Declaration 
Block
could work for namespaces, as well as allowing a single declaration
to open and close should be possible too.

 I had thought he was asking if fltk-1.3 itself would have namespaces (which 
 for compatibility I guess it can't).

Right, I don't think he's asking for an API change.

___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk


Re: [fltk.general] docking windows

2013-03-21 Thread Ian MacArthur

On 21 Mar 2013, at 13:12, asif saeed wrote:

 Hi,
 
 I have turned to FLTK after a very long time. Almost a new user. I just
 wanna know if you have support available for docking windows? Or do you
 have to make do it in order to achieve it?


There's no built-in support, though there are a few worked examples in the 
links pages.

Mine is here, FWIW: http://www.fltk.org/links.php?V326+Q

Though I don't actually use that code much myself; I really wrote it in answer 
to a forum question. The code worked fine, but may be subject to bit rot as it 
is a few years old now (i.e. 5 or 6 I guess... It was a while ago!) though I 
don't think it did anything unusual, so probably works fine still!


Hmm, I just noticed that the links on that page link through to a ISP I no 
lnger have an account with: oh well, still seem to be working though!




___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk