I just updated to the head of 1.3, and my app failed to compile,
complaining that Fl_X was undefined. Looking at FL/mac.H, it looks
like it's intentionally hidden when compiling against an application.
Hiding system specific stuff seems like a good idea, but it looks like
this is
I don't see the Fl_X class documented in Doxygen. Am I wrong ?
I think you're right, I don't see it either. I'm not sure where I got
the idea to use it. It seems less likely to make portability if it's
consistently not exported for all OSes, but if it's not documented
then I suppose you can
I just updated to the head of 1.3, and my app failed to compile,
complaining that Fl_X was undefined. Looking at FL/mac.H, it looks
like it's intentionally hidden when compiling against an application.
Hiding system specific stuff seems like a good idea, but it looks like
this is
On 11.01.2011 10:21, MacArthur, Ian (SELEX GALILEO, UK) wrote:
One for Manolo I guess. Though... There is the bigger question of
whether Fl_X should be exposed or not.
What do folk think?
I'd say don't expose, because it's internal and can be changed.
If we really need to expose some of the
On 11.01.2011, at 10:21, MacArthur, Ian (SELEX GALILEO, UK) wrote:
One for Manolo I guess. Though... There is the bigger question of
whether Fl_X should be exposed or not.
What do folk think?
I don't know - I'd guess not, for safety reasons, but there are some
advantages, too...
This
On 11.01.2011, at 12:06, Albrecht Schlosser wrote:
I don't know what to do with fluid, but I think that fluid should
probably use an external browser for its docs as well.
I'd rather have a short intro to Fluid inside the fluid source files and an
explanation where to find the complete docs
On 11.01.2011, at 10:21, MacArthur, Ian (SELEX GALILEO, UK) wrote:
One for Manolo I guess. Though... There is the bigger question of
whether Fl_X should be exposed or not.
=20
What do folk think?=20
=20
I don't know - I'd guess not, for safety reasons, but there are some
advantages,
On 11.01.2011, at 14:58, Manolo Gouy wrote:
This is bad. The xid should be available to the user.
Isn't the fl_xid(const Fl_Window*) function (documented
in the OS issues section) enough ?
first_window, btw., is a static member of Fl_Window in FLTK2 (or
rather fltk::Window). I find
What do folk think?
I'd say don't expose, because it's internal and can be changed.
If we really need to expose some of the internals that are not
available now, then we should write accessor methods that do it
in a defined way.
Except that we used to expose it on all hosts, and now
This is bad. The xid should be available to the user.
Isn't the fl_xid(const Fl_Window*) function (documented
in the OS issues section) enough ?
I tend to agree, and that's what I've used in my code (where I have
needed this functionality) but it may still be a change that has side
On Jan 10, 2011, at 1:14 PM, imacart...@gmail.com wrote:
On 10/01/11 20:42, Greg Ercolano wrote:
I haven't tried this myself, but can the FLTK html viewer
even show our doxygen docs correctly?
Short answer: Not it can not.
Neither the frames or the non-frames versions of the
On Jan 11, 2011, at 1:21 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I just updated to the head of 1.3, and my app failed to compile,
complaining that Fl_X was undefined. Looking at FL/mac.H, it looks
like it's intentionally hidden when compiling against an application.
Hiding system
Michael Sweet wrote:
Would it make sense to provide a separate help file for FLUID, and then use
that as the test file for the help_viewer demo?
That sounds good, as I don't think the FLTK doxygen docs
cover fluid anyway.
___
fltk-dev
Albrecht Schlosser wrote:
Thus, we shouldn't bother to provide a main.html file, but rather
add a sample html page for the html viewer test (as Greg volunteered
to do already) and add appropriate browser links where needed.
Mike might have a point about making separate simple fluid
Greg Ercolano wrote:
Michael Sweet wrote:
Would it make sense to provide a separate help file for FLUID, and then use
that as the test file for the help_viewer demo?
That sounds good, as I don't think the FLTK doxygen docs
cover fluid anyway.
..or I guess I never read them!
On 11.01.2011, at 18:15, Greg Ercolano wrote:
Albrecht Schlosser wrote:
Thus, we shouldn't bother to provide a main.html file, but rather
add a sample html page for the html viewer test (as Greg volunteered
to do already) and add appropriate browser links where needed.
Mike might have
I'm thinking of making the online docs version-specific, i.e.
instead of having
http://www.fltk.org/doc-1.3/index.html
we should probably have
http://www.fltk.org/doc-1.3.0/index.html
http://www.fltk.org/doc-1.3.1/index.html
...
Reasoning: The doxygen'erated HTML docs change their
On Jan 11, 2011, at 10:09 AM, Albrecht Schlosser wrote:
...
Mike, what about server space and... ?
Server space isn't an issue - about 500GB free on our RAID at the moment.
I would probably limit what is shown/linked to on the documentation page to the
most recent version - that will make
Mike:
Would it make sense to provide a separate help file for FLUID,
and then use that as the test file for the help_viewer demo?
Greg:
That sounds good, as I don't think the FLTK doxygen docs
cover fluid anyway.
Greg:
..or I guess I never read them! Well bite my tongue,
On 10.01.2011 19:35, Boris Mayer-St-Onge wrote:
I did some test on Fedora 10 and 14 with current svn(8241). No major
problem.
Thanks.
Here are some suggestions:
1- When compiling fltk, at the end one have
=== making documentation ===
This making ... specifies the directory that is
On 11.01.2011 18:48, Greg Ercolano wrote:
Greg Ercolano wrote:
Michael Sweet wrote:
Would it make sense to provide a separate help file for FLUID, and then use
that as the test file for the help_viewer demo?
That sounds good, as I don't think the FLTK doxygen docs
cover fluid
On 11.01.2011 21:05, Albrecht Schlosser wrote:
On 10.01.2011 19:35, Boris Mayer-St-Onge wrote:
Also, there is 2 copyright in this page
with year 2010. Maybe change it to 2011?
Sigh. We just changed all copyright dates to 2010, but now it's already
2011. Time goes by... I'll see what I can
Duncan Gibson wrote:
Greg:
..or I guess I never read them! Well bite my tongue, apparently
there /are/ doxygen fluid docs: http://fltk.org/doc-1.3/fluid.html
The problem with this page is that it's too complicated for new users
learning fluid. If someone is going to write a fluid
Albrecht Schlosser wrote:
In that doc it could link to the local and/or website docs,
eg:
FLTK Docs:A
HREF=file://path/to/localdocs/html/index.html(local)/A
The above would be an autoconfigured path, or optional an expanded
environment variable?
Good
24 matches
Mail list logo
