Components of vishia-Java
From Java4c
(first) |
m (Dependencies of ZBNF) |
||
Line 23: | Line 23: | ||
* The ZBNF is used in almost all applications of the author. It is because the applications translates some texts (for example Java2C), it needs config-files (GUI) etc. | * The ZBNF is used in almost all applications of the author. It is because the applications translates some texts (for example Java2C), it needs config-files (GUI) etc. | ||
- | + | Includes: | |
* A commandline calling argument preparer is included in the srcJava_ZBNF-package between it is the core-package of all applications. | * A commandline calling argument preparer is included in the srcJava_ZBNF-package between it is the core-package of all applications. | ||
* Some util-components are included. | * Some util-components are included. | ||
* A MessageDispatcher which separates output messages (logs, able to use for embedded applications too) is contained there. | * A MessageDispatcher which separates output messages (logs, able to use for embedded applications too) is contained there. | ||
+ | |||
+ | Dependencies: | ||
+ | * This component has not any dependencies to any foreign component. Only standard-Java-classes are used. | ||
==vishiaJava_Util== | ==vishiaJava_Util== |
Revision as of 20:17, 25 February 2011
Contents |
Overview
vishia-Java is a tree of Java-files in the package-structure org/vishia/stuff. All files are written by Hartmut Schorrig, www.vishia.org. They are used in some applications in profession too (with second license model). It is a conglomeration of different things, of course.
The usage of all files as jar-library if only a few files are needed - it isn't optimal:
- The usage as library will be proper, if an extrinsic application will use them as it is.
- If one of developers uses a component in another self-programmed application, it is self-evident to improve the used component with the challenges of the application. In that case the source should be present to check, change and improve.
- But on the other hand, if an extrinsic application should use that components proper, it should be well tested in a defined environment. A conglomeration can't be tested well enough.
Therefore that Java-sources are separated in some components. Any of the named component is available as a bazaar archive to work with sources. Any of this components are available as a download-file with some test environments as a application - or some test-Java-files exist.
This components are presented in the next chapters:
srcJava_ZBNF
- distribution on [sf.net/projects/zbnf]
- bazaar-archive on [launchpad.net/zbnf/srcjava.zbnf]
- description, home-site on [www.vishia.org/ZBNF]
Content of the distribution:
- The ZBNF-Parser with this Java-soruce is able to use discrete to convert plain-text but well-syntactical files into XML.
- The Java-sources includes a tool Header2Reflection which translates C/C++-headerfiles to C-files, which represents reflection-information about the data structures. It is used in a ReflectPro-suite.
- A Zmake-Tool is assiciated there. It converts simple make-prescripts to [ANT]-make-files.
Further usage:
- The ZBNF is used in almost all applications of the author. It is because the applications translates some texts (for example Java2C), it needs config-files (GUI) etc.
Includes:
- A commandline calling argument preparer is included in the srcJava_ZBNF-package between it is the core-package of all applications.
- Some util-components are included.
- A MessageDispatcher which separates output messages (logs, able to use for embedded applications too) is contained there.
Dependencies:
- This component has not any dependencies to any foreign component. Only standard-Java-classes are used.
vishiaJava_Util
TODO
vishiaJava_Java2C
TODO
vishiaJava_GUI
TODO