FLUID

FLUID (Fast Light User Interface Designer) is a graphical editor and GUI builder that is used to produce FLTK source code. FLUID edits and saves its state in text .fl files, which can be edited in a text editor for finer control over display and behavior.[2]

For other uses, see Fluid (disambiguation).
FLUID
FLUID's code view window shows how the C++ output would look like if written on the disk.
Stable release1.3.5 (March 3, 2019 (2019-03-03)[1]) [±]
Preview releaserelease-1.3.4-2 (December 22, 2019 (2019-12-22)) [±]
Type
LicenseGNU Lesser General Public Licence
Websitewww.fltk.org
FLUID widget list window

After designing the application, FLUID compiles the .fl file into a .cxx file, which defines all the objects from the .fl file, and an .h file, which declares all the global ones.[3] FLUID also supports localization of label strings using message files and the GNU gettext or POSIX catgets interfaces.[4]

A flowchart showing the steps needed to compile FLUID-generated code

A simple program can be made by putting all non-interface code (including a main function) into the .fl file, thus making the .cxx file a single source file to compile. Most programs are more complex than this, so other .cxx files can be written that call the FLUID functions. These .cxx files must #include the .h file, or they can #include the .cxx file so it still appears to be a single source file.

Normally the FLUID file defines one or more functions or classes, which output C++ code. Each function defines one or more FLTK windows, and all the widgets that go inside those windows.

Widgets created by FLUID are "named", "complex named", or "unnamed". A named widget has a legal C++ variable identifier as its name (i.e. only alphanumeric and underscore), and is defined by a global variable or class member that will point at the widget after the function defining it is called. A complex named object has punctuation such as '.' or '->' or any other symbols in its name. In this case, FLUID assigns a pointer to the widget to the name, but does not attempt to declare it. This can be used to get the widgets into structures. An unnamed widget has a blank name and no pointer is stored.

Widgets may either call a named callback function that one writes in another source file, or one can supply a small piece of C++ source and FLUID will write a private callback function into the .cxx file.

Code View window

While editing the program FLUID the user can look at the Code View window which shows exactly how the C++ output of the program would look. The Code View window supports auto refreshing (when something in the program is changed, Code View will automatically change the source code being shown) which can be disabled by the user. It won't let the user change the code being shown through it. Code View is part of FLUID and is not automatically shown on startup. It can be enabled through FLUID's menu.

Widget bin window
FLUID's widget bin window
gollark: Vowels are ignored when comparing symbol names. The float type is replaced with a ratio of two decimals. Macros but they require you to rewrite the block of code they're used in as lisp syntax. JSON literals.
gollark: Maybe… even weaker types? Integer types with crazier names and also u24s and stuff for some reason? Do operator overloading to a stupid degree in the stdlib?
gollark: Idea: C-flat language, like C but stupider somehow.
gollark: Clearly what we need is C with better macros, so that "extensions" are no longer necessary.
gollark: What's the issue with `{}`?

See also

References
  1. https://www.fltk.org/articles.php?L1635
  2. Reference, from the FLTK documentation
  3. FLTK 1.3.3: Programming with FLUID, from the FLTK manual.
  4. fltk.org/doc-1.3/fluid.html#fluid_i18n FLTK 1.3.3: Programming with FLUID, FLTK manual
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.