MODULES
What are library modules
Modules are groupings of code which either get reused or which basically make up a tool.
Usually, modules will include all functions, object, data, values to accomplish one or more specific tasks.
Steel modules are extremely varied in scope. From a view layout engine to code linking.
quick tour of all modules | |
| |
SLIM
This is actually not a module per say but rather a library module specification, a run-time module loader and management tool.
Using slim you can forget about paths and store all your library modules in several places yet find them as if in a central location.
You can also take advantage of slim's module-relative file resource directories and internal console management which allow you
to nest and toggle print messages, using a library contextual verbose setting.
LIQUID
DATA-CENTRIC Dynamic and run-time allocated bi-directional signaling, notification, data flow and synchronisation.
Add/Delete signal channels as you wish, This is very usefull for any application size. Liquid allows you to design your application
in such a way that it is possible for you to add stuff and procedures without having to maintain previous code.
In some ways it resembles a neural network, where changes to data cause reactions elsewhere. Any function can be the initiator
of a chain reaction of events as your code updates values in data, which will in-turn cause reactions to others which are connected to it.
Internal validation mechanisms allow you to assign code which converts, fixes or even DENIES any data you send through a pipe. All
associated valves of a data pipe will be notified, so you can create ONE validation routine and apply it to ALL related parts of your app
which use a specific value.
GLAYOUT
VERY powerfull, completly window-size sensitive layout engine. Uses hierarchichal layout
which allows you to create rows and columns of
any kind of control. Layout is very simple to setup, yet the engine will give the proper controls the most space, while keeping ordered layout
look when there is enough space. Resizing window below minimum size will actually rescale window to minimum contents size and will squash
controls which do not benefit from space like buttons in favor of those who need as much space as possible, like text fields.
Built over REBOL technologie's VID dialect
for an easy learning curve. You keep easy stylesheet system, yet use a better layout engine.
Has its own requester engine and ANY window can be modal (event blocking) even resizable windows, by using the /modal refinement of view.
making floating menues becomes child's play.
Implements a new and more powerfull file browser
. Resisable window rename, delete, create files & directories right from the browser.
But you do not have the problem about having to commit to an open or save browser.
Includes an arbitrary and dynamically scaling scroll pane view, which adds and deletes scroll bars whenever contents is larger than
display size.
Allows soft edges to be done using nested panes.
SLIM-LINKER
A basic module linking tool, which spits out a stand-alone application which includes all libraries modules it normally loads at run-time.
It relies on slim specification and will eventually support nested library module linking.
Linking files together takes 2 lines of code!.
All features of slim are untouched as part of linking process, because slim is included in the resulting file. While this causes
file size to increase, it allows you to keep module-specific resource directories, module-specific print toggling, and other goodies.
last updated: 27-Jul-2004/1:34:27-4:00
|