| | [ Return to Bugs & Features | Post Text | Post File | Prev | Next ]
STR #3360
| Application: | FLTK Library |
|---|
| Status: | 5 - New |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Documentation |
|---|
| Summary: | fltk manpage improvements |
|---|
| Version: | 1.4-feature |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | greg.ercolano |
|---|
| Fix Version: | Unassigned |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
[ Post File ]No files
Trouble Report Comments:
[ Post Text ]
| |
| #1 | greg.ercolano
09:47 Dec 04, 2016 |
| Would like to suggest improvements to the 'man fltk' page,
which currently only shows the LGPL license and reference to
other pages and the main website link.
It should include extra info that library intro pages do,
e.g. ncurses(3X), libcurl(3), libpng(3), Xft(3X).
Things we should add:
o minimal reference on what files to #include
o example of how to build a simple program (fltk-config --compile)
o perhaps a simple Makefile example.
o short description of the lib files provided (fltk, fltk_images, etc)
o a url to the website docs
o a description of the fltk.general newsgroup (website link)
o a description of the license (LGPL + static link)
o short description of naming conventions (FL_* for macros, Fl_* for classes..)
Just that, nothing much more.. simple one or two pages with pointers
to everything else.
I imagine the audience to be people who have Fltk installed on their
machine as part of their OS install (or a yum/apt-get install) and found
a simple "hello world" example on an unrelated website (like http://kukuruku.co/hubs/)
and are trying to figure out enough about the library to build and run. | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |
FLTK Apps 
