|
|
|
| This is a tool for formatting ideas and concepts, as well as for sharing the resulting knowledge. It works with a structured textual content. The 2D-infoExplorer is a fully functional 2D-info browser, which can be used to create, view and edit 2D-information programs. |
![]() (see screenshot) |
|
In a nutshell, the 2D-infoExplorer is a container for information fragments. It works like the
Rubik's Cube. We can enter or paste data into any its "cell", and "play" with the information cube!
Main content types are plain text and graphics. Also, fragments of files in other formats (currently only HTML) can be used. For example, we can insert an HTML table into our content. However, making changes in the table requires knowledge of the underlying HTML format. The 2D-infoExplorer allows formatting your knowledge into special InfoPages, which describe knowledge as a set of objects within 2D-information space. Each InfoPage is a mini-program, a portable module, generated in cross-platform JavaTM syntax (see 2D-information file format). The textual content has a special built-in InfoProcessor, allowing navigation between the objects. The whole document is interactive, and can be easily edited. Unlike HTML, the InfoPages' content is made of hyper links only: text consists of fragments, all of which are hyper links. Clicking any fragment reveals its 2D-info structure. Resulting Java source files can be compiled from within 2D-infoExplorer. Knowledge of Java is not required! Design of the 2D-infoExplorer also has a module concept, which allows developing customized extensions. The InfoPages can be developed independently, and later assembled and disassembled into blocks, - InfoWorlds. In addition, recent version of the 2D-infoExplorer includes functionality of the Fragmentator to allow assembling specified fragments from files at different locations into one page.
|
|
This utility allows applying principles of fragmentation to textual data. Currently document items are represented by whole files. However, typically we need only a part (fragment) of used text. For example, only one cite from a huge document, or a specific paragraph on a specific page. Or, only that parts which we have highlighted by marker early, etc. Why create new files every time we want to operate with such small sub-parts? Other examples include content customization, when we need an efficient management for variety of different views to the same page. In more complex cases, we may be required to develop a collection of fragments from many different files in one place. |
|
A special code syntax is devised to describe position of required fragment in a textual content.
For example, having some Base text,
To manage processing of that code, we can use Data Compiler package. It helps Java programmers to integrate high volumes of similar textual information into their programs: Enter code, - get resulting text. Enter text, - get the code. Fragmentator is a user-friendly Java application that extends the Data Compiler. |
![]() (see screenshot) |
|
The idea behind Fragmentator is in presenting text as object-oriented structure (set of fragments), and applying principles of inheritance to information.
For example, in groupware context, each version of a document can be described as extension to some super information class (Base text). Instead of keeping multiple files on disk, we can save only the Base text file. Content of other versions can be calculated dynamically from a rather compact code, which describes a difference comparatively to the Base text.
Advantage is a reduced disk space and faster processing! Typical example is developing customized versions of text documents, e.g., compiling short and full versions of the same content. Other examples may include new types of content archivers, cyphering devices, etc.
The Fragmentator is able to save results (code or text) as a file. The file for code has
|
|
|