data model
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5450
Yukatan data model 1.0
Yukatan data model project is the schema definition of the Yukatan webmail database. more>>
Yukatan data model project is the schema definition of the Yukatan webmail database.
The PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented
<<lessThe PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented
Download (0.035MB)
Added: 2007-02-19 License: GPL (GNU General Public License) Price:
983 downloads
desktop-data-model 1.2.5
desktop-data-model is a GNOME wrapper library. more>> desktop-data-model 1.2.5 is a versatile software which functions as a GNOME wrapper library.
Installation: The simplest way to compile this package is:
- `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
- Running `configure might take a while. While running, it prints some messages telling which features it is checking for.
- Type `make to compile the package.
- Optionally, type `make check to run any self-tests that come with the package.
- Type `make install to install the programs and any data files and
- documentation.
- You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make disclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Added: 2008-10-29 License: LGPL Price: FREE
16 downloads
Datamixer 0.1.88
Datamixer generates mock data, mixes it with data from other sources such as files, and can write the results back to files or t more>>
How do you build a web application without data? Suppose it has many pages, including forms and pages for display. Until theyre developed, users cant enter information. Mock data has to be provided to the application, to test the interaction between screens, business logic, and database.
It may take a good amount of effort to create a mock dataset large and complex enough to mimic real world situations. For example, it is not unusual for an application to be supported by a database schema with hundreds of tables, each with many columns and many foreign key relationships. The database may have millions of rows of data. Datatypes include integer, floating precision, datetime, and string. There are a wide range of values, and they are dependent on each other in ways that must satisfy the business requirements.
Mock data is useful at various points in development. It can be used with an HTTP test client, to simulate the responses a user makes at the front end. It can be inserted directly into the database, to test the database access layer. It can replace the database layer, and be provided directly to the business logic implementation.
It might be nice if the datasets at these different stages come from the same pool, so that their values represent the same underlying model. It would be nice if this model could be constructed once, and then the presentation of the data tailored for the stage at which its used.
Often a great deal of effort is spent reducing the worlds objects into a compact object model. Datamixer goes the other way: it takes a conceptual object model, and explodes it back into a diversity of objects. It tries to make this diversity easy to manage, through configuration and customization. It interacts with data repositories, and is able to mix and merge mock values with real ones. The aim is to make it easy to create the data, so that time can be spent on the data model.
Datamixer does not attempt to analyze a problem domain, in order to generate data that does a better job at testing the domain. It could be driven by a tool that does that kind of analysis.
Installation:
To install, simply unzip or unjar the distribution package to a directory of your choice. A distribution has these directories:
- The data directory has files with samples of commonly used data, such as names. It is intended to grow.
- The doc directory has documentation.
- The examples directory has example Java source and XML configuration scripts. Apache Ant is used to run these examples: type ant build
- The lib directory has all jars required by the application.
Enhancements:
- license changed to BSD.
<<lessIt may take a good amount of effort to create a mock dataset large and complex enough to mimic real world situations. For example, it is not unusual for an application to be supported by a database schema with hundreds of tables, each with many columns and many foreign key relationships. The database may have millions of rows of data. Datatypes include integer, floating precision, datetime, and string. There are a wide range of values, and they are dependent on each other in ways that must satisfy the business requirements.
Mock data is useful at various points in development. It can be used with an HTTP test client, to simulate the responses a user makes at the front end. It can be inserted directly into the database, to test the database access layer. It can replace the database layer, and be provided directly to the business logic implementation.
It might be nice if the datasets at these different stages come from the same pool, so that their values represent the same underlying model. It would be nice if this model could be constructed once, and then the presentation of the data tailored for the stage at which its used.
Often a great deal of effort is spent reducing the worlds objects into a compact object model. Datamixer goes the other way: it takes a conceptual object model, and explodes it back into a diversity of objects. It tries to make this diversity easy to manage, through configuration and customization. It interacts with data repositories, and is able to mix and merge mock values with real ones. The aim is to make it easy to create the data, so that time can be spent on the data model.
Datamixer does not attempt to analyze a problem domain, in order to generate data that does a better job at testing the domain. It could be driven by a tool that does that kind of analysis.
Installation:
To install, simply unzip or unjar the distribution package to a directory of your choice. A distribution has these directories:
- The data directory has files with samples of commonly used data, such as names. It is intended to grow.
- The doc directory has documentation.
- The examples directory has example Java source and XML configuration scripts. Apache Ant is used to run these examples: type ant build
- The lib directory has all jars required by the application.
Enhancements:
- license changed to BSD.
Download (2.6MB)
Added: 2006-04-21 License: BSD License Price:
1282 downloads
Misfit Model 3D 1.3.5
Misfit Model 3D is an OpenGL-based 3D model editor. more>>
Misfit Model 3D is an OpenGL-based 3D model editor that works with triangle-based models. Misfit Model 3D supports multi-level undo, skeletal animations, simple texturing, scripting, command-line batch processing, and a plugin system for adding new model and image filters.
Complete online help is included. It is designed to be easy to use and easy to extend with plugins and scripts.
Misfit Model 3D was written and tested on Linux (2.4 and 2.6 kernels) and has been compiled and tested on most major Linux distributions.
It is not endian-safe so it is unlikely to run on non-x86 hardware platforms--this will probably not change soon unless I get requests for a version thats usable on big-endian archs.
Enhancements:
- The menus have been re-organized. There is a new command to make normals face outward. The texture coordinate window now has a rotate tool. Material support for COB has been improved. Many animation bugs have been fixed. A "File | Export" command has been added to indicate which formats have less reliable write support.
<<lessComplete online help is included. It is designed to be easy to use and easy to extend with plugins and scripts.
Misfit Model 3D was written and tested on Linux (2.4 and 2.6 kernels) and has been compiled and tested on most major Linux distributions.
It is not endian-safe so it is unlikely to run on non-x86 hardware platforms--this will probably not change soon unless I get requests for a version thats usable on big-endian archs.
Enhancements:
- The menus have been re-organized. There is a new command to make normals face outward. The texture coordinate window now has a rotate tool. Material support for COB has been improved. Many animation bugs have been fixed. A "File | Export" command has been added to indicate which formats have less reliable write support.
Download (0.71MB)
Added: 2007-07-16 License: GPL (GNU General Public License) Price:
832 downloads
Yukatan Webmail 0.1
Yukatan Webmail provides an advanced email management system. more>>
Yukatan Webmail provides an advanced email management system.
The goal of the project is to create an advanced webmail system, that uses a relational database backend to provide efficient search and classification capabilities.
The project is currently in pre-alpha state. The underlying data model has just reached 1.0 status, and a couple of utility tools are under active development.
Yukatan components
The Yukatan webmail system is developed as a collection of independent components based on a central data model.
Enhancements:
- Yukatan data model 1.0
- Java importer sources
- Initial webapp code for the webmail part
<<lessThe goal of the project is to create an advanced webmail system, that uses a relational database backend to provide efficient search and classification capabilities.
The project is currently in pre-alpha state. The underlying data model has just reached 1.0 status, and a couple of utility tools are under active development.
Yukatan components
The Yukatan webmail system is developed as a collection of independent components based on a central data model.
Enhancements:
- Yukatan data model 1.0
- Java importer sources
- Initial webapp code for the webmail part
Download (0.018MB)
Added: 2007-02-19 License: GPL (GNU General Public License) Price:
990 downloads
Quantity Modeling Language 0.1
QML (Quantity Modeling Language) is a thing-based language for scientific and mathematical data modeling. more>>
QML (Quantity Modeling Language) is a "thing"-based language for scientific and mathematical data modeling.
Each "thing" is a quantity which may be associated with either a structure or physical phenomena.
Quantities, in turn, may hold other Quantities or values (numbers or strings). Higher-level data models, which associate or define meanings to various quantities (such as velocity or position), can be built from QML quantities.
The higher-level data model (XML) schema that inherits from QML may be understood, and its instance documents may be parsed into QML documents and objects by the QMLReader.
Enhancements:
- This release adds partial Xerces2 DOM support, and works with Java 1.4 and Java 1.5 (no JAXP DocumentBuilder/Factory support currently).
- The test procedure is a little less chatty.
- Support has been added for testing either/both Crimson/Xerces DOM support.
- (Note: Crimson support only works with Java 1.4, as Java 1.5 interfaces have DOM lvl 2 and 3, which crimson doesnt support).
- This release adds compilerargs, and better build support for different configurations to build.xml.
<<lessEach "thing" is a quantity which may be associated with either a structure or physical phenomena.
Quantities, in turn, may hold other Quantities or values (numbers or strings). Higher-level data models, which associate or define meanings to various quantities (such as velocity or position), can be built from QML quantities.
The higher-level data model (XML) schema that inherits from QML may be understood, and its instance documents may be parsed into QML documents and objects by the QMLReader.
Enhancements:
- This release adds partial Xerces2 DOM support, and works with Java 1.4 and Java 1.5 (no JAXP DocumentBuilder/Factory support currently).
- The test procedure is a little less chatty.
- Support has been added for testing either/both Crimson/Xerces DOM support.
- (Note: Crimson support only works with Java 1.4, as Java 1.5 interfaces have DOM lvl 2 and 3, which crimson doesnt support).
- This release adds compilerargs, and better build support for different configurations to build.xml.
Download (0.16MB)
Added: 2005-11-10 License: Public Domain Price:
1443 downloads
Atocha 1.0
Atocha is a Python package for parsing and rendering data from Web forms. more>>
Atocha is a Python package for parsing and rendering data from web forms.
Atocha is framework-agnostic, generic, and it should be possible to use it with CGI scripts or to incorporate it in your favourite web application framework.
Just before I decided to write this software (2005-09-30), I had the following problems:
- There was no library that could parse input from widgets and perform automatic types conversions reliably, that was both decent and simple, or that was not tied to a specific web application framework. (A few options were starting to sprout and mature around that time, such as FormEncode);
- I was having lots of trouble in the various data paths of my handlers with type conversions, often having unicode encoding problems;
- I felt that the problem of handling and rendering web forms were really tied closely, and that it could be solved in a generic manner.
At the time, I had written my own web application framework, and a small form library I had copied from somewhere had grown into a messy monster. So I decided to attack the problem directly and rewrite my forms handling generically, with the following goals in mind:
- Reuse the form definition for parsing submitted arguments as well as rendering and displaying data (leverage the knowledge stored in the form definition as much as possible);
- Robustness: an emphasis on strict type checking and robustness via tests;
- Fields automatically perform appropriate type conversion when returning the parsed value to the user; Like desktop UI toolkit widgets, fields may return all sorts of data types. Also, fields can use multiple HTML input widgets, the notion of input and its mechanism are separate.
Essentially, I wanted functionality closer to what desktop UI toolkits provide, which is often not present in web form parsing toolkits.
Main features:
- Generic library that is possible to reused in many frameworks and applications. It is not tied to any storage model or domain model, this library provides the data, and you must then store the data yourself. This makes sense, as user-interfaces may change but the underlying data model remain the same;
- Extensible: it is easy to create and add new field types without having to modify the framework. It is also possible to create renderers for your favourite output library (e.g. Stan)
- Fields may render to multiple input widgets and are consolidated in a single value automatically;
- Internationalization (I18n) of all messages is supported (all messages generated by the library are grouped in a s single place and can be easily customized);
- Supports hidden, disabled, and read-only widgets that can be used for implementing multiple-page forms;
- Supports per-field errors, to be rendered next to the erroneous widgets;
- Supports a UI message and status for the re-rendering a form with errors;
- Could easily be extended to support widgets with JavaScript/AJAX code.
<<lessAtocha is framework-agnostic, generic, and it should be possible to use it with CGI scripts or to incorporate it in your favourite web application framework.
Just before I decided to write this software (2005-09-30), I had the following problems:
- There was no library that could parse input from widgets and perform automatic types conversions reliably, that was both decent and simple, or that was not tied to a specific web application framework. (A few options were starting to sprout and mature around that time, such as FormEncode);
- I was having lots of trouble in the various data paths of my handlers with type conversions, often having unicode encoding problems;
- I felt that the problem of handling and rendering web forms were really tied closely, and that it could be solved in a generic manner.
At the time, I had written my own web application framework, and a small form library I had copied from somewhere had grown into a messy monster. So I decided to attack the problem directly and rewrite my forms handling generically, with the following goals in mind:
- Reuse the form definition for parsing submitted arguments as well as rendering and displaying data (leverage the knowledge stored in the form definition as much as possible);
- Robustness: an emphasis on strict type checking and robustness via tests;
- Fields automatically perform appropriate type conversion when returning the parsed value to the user; Like desktop UI toolkit widgets, fields may return all sorts of data types. Also, fields can use multiple HTML input widgets, the notion of input and its mechanism are separate.
Essentially, I wanted functionality closer to what desktop UI toolkits provide, which is often not present in web form parsing toolkits.
Main features:
- Generic library that is possible to reused in many frameworks and applications. It is not tied to any storage model or domain model, this library provides the data, and you must then store the data yourself. This makes sense, as user-interfaces may change but the underlying data model remain the same;
- Extensible: it is easy to create and add new field types without having to modify the framework. It is also possible to create renderers for your favourite output library (e.g. Stan)
- Fields may render to multiple input widgets and are consolidated in a single value automatically;
- Internationalization (I18n) of all messages is supported (all messages generated by the library are grouped in a s single place and can be easily customized);
- Supports hidden, disabled, and read-only widgets that can be used for implementing multiple-page forms;
- Supports per-field errors, to be rendered next to the erroneous widgets;
- Supports a UI message and status for the re-rendering a form with errors;
- Could easily be extended to support widgets with JavaScript/AJAX code.
Download (0.25MB)
Added: 2006-04-07 License: GPL (GNU General Public License) Price:
1295 downloads
Hydrate 2.0
Hydrate is a tool that provides fast, efficient, and error-free transformation of data. more>>
Hydrate is a Java tool that provides for fast efficient and error-free transformation of data between three different representations: relational databases, objects in an object-oriented programming language and extended markup language (XML).
Each of these representations has its strengths and weaknesses as shown in the diagram below; but which should you use as a basis for your application design?
Hydrate relaxes some of the pressure on this decision by providing tools for moving data from one representation to another, guided by a master UML class representation of that data.
- You want to lay a domain object model view over an existing database or set of databases. Hydrate gives you the tools to design that model in UML and map your existing data to that model. Once in the object space, you can perform complex manipulations on the objects, calculate results and save information back to a relational cache for searching or reloading, as well as converting the results to XML for sending to downstream systems or transforming to a readable format for display.
- Your project involves taking various data files fed from external systems that you want to pull into an object model on your server before writing the results down to a fully relational database. You can now respond to requests from external systems by rehydrating the data from its relational form and sending it out as XML documents or transforming those documents to a readable format for display.
- You are building a data warehouse in which you have the broad specifications for the model, but want to provide for flexibility and adaptability for future unpredicted requests. Based on a core data model, Hydrate gives you the tools to create you database schema, and write information to it, but more significantly to subsequently lay a completely different object model perhaps aggregating some of the data over the top of that schema to process it in unforeseen ways.
- You need to integrate data from many different data sources in a highly performant manner. SQL permits you to read a huge data set a row at a time and perform running calculations and filtering on that data. But the performance pressures can lead to code that is highly coupled with the database and what do you do if you need to integrate data from elsewhere in order to complete your calculations? Hydrate permits you to operate in the object space and integrate information from other sources on-the-fly.
Main features:
- To integrate legacy and other data schemas over which you have little control. Map data from many different data sources into a single self-consistent in-memory model. Different parts of the same object, as well as different sub-populations of the same object type can be drawn from different data sources, different schemas and even different database architectures.
- Load, populate and connect up multiple object types from a single query. There is no limit to the number of object types that can be loaded from a single query, or to the complexity of the relationships that can be resolved between them. Objects read from a query are automatically merged into objects already in memory.
- Full control over the SQL that runs against the database (if you need it). Any SQL queries simultaneously from multiple JDBC drivers, even using database specific optimizations, as long as they returns a result set.
- Access and manipulate the same data through the rich and powerful XML toolset. Use the same meta data that describes your objects to easily read from, write to and validate any consistent XML schema. Use XML for display, data transmission or XSLT transformation. Load XML data back into objects.
- Highly optimized performance for reading and writing SQL and XML. Since native types are used and SQL chatter is non-existent, database performance is comparable with doing the mapping by hand. XML reading and writing uses SAX exclusively.
<<lessEach of these representations has its strengths and weaknesses as shown in the diagram below; but which should you use as a basis for your application design?
Hydrate relaxes some of the pressure on this decision by providing tools for moving data from one representation to another, guided by a master UML class representation of that data.
- You want to lay a domain object model view over an existing database or set of databases. Hydrate gives you the tools to design that model in UML and map your existing data to that model. Once in the object space, you can perform complex manipulations on the objects, calculate results and save information back to a relational cache for searching or reloading, as well as converting the results to XML for sending to downstream systems or transforming to a readable format for display.
- Your project involves taking various data files fed from external systems that you want to pull into an object model on your server before writing the results down to a fully relational database. You can now respond to requests from external systems by rehydrating the data from its relational form and sending it out as XML documents or transforming those documents to a readable format for display.
- You are building a data warehouse in which you have the broad specifications for the model, but want to provide for flexibility and adaptability for future unpredicted requests. Based on a core data model, Hydrate gives you the tools to create you database schema, and write information to it, but more significantly to subsequently lay a completely different object model perhaps aggregating some of the data over the top of that schema to process it in unforeseen ways.
- You need to integrate data from many different data sources in a highly performant manner. SQL permits you to read a huge data set a row at a time and perform running calculations and filtering on that data. But the performance pressures can lead to code that is highly coupled with the database and what do you do if you need to integrate data from elsewhere in order to complete your calculations? Hydrate permits you to operate in the object space and integrate information from other sources on-the-fly.
Main features:
- To integrate legacy and other data schemas over which you have little control. Map data from many different data sources into a single self-consistent in-memory model. Different parts of the same object, as well as different sub-populations of the same object type can be drawn from different data sources, different schemas and even different database architectures.
- Load, populate and connect up multiple object types from a single query. There is no limit to the number of object types that can be loaded from a single query, or to the complexity of the relationships that can be resolved between them. Objects read from a query are automatically merged into objects already in memory.
- Full control over the SQL that runs against the database (if you need it). Any SQL queries simultaneously from multiple JDBC drivers, even using database specific optimizations, as long as they returns a result set.
- Access and manipulate the same data through the rich and powerful XML toolset. Use the same meta data that describes your objects to easily read from, write to and validate any consistent XML schema. Use XML for display, data transmission or XSLT transformation. Load XML data back into objects.
- Highly optimized performance for reading and writing SQL and XML. Since native types are used and SQL chatter is non-existent, database performance is comparable with doing the mapping by hand. XML reading and writing uses SAX exclusively.
Download (7.0MB)
Added: 2006-06-04 License: LGPL (GNU Lesser General Public License) Price:
1240 downloads
Gtk::CListModel 0.7009
Gtk::CListModel is a simple data model with Gtk::Clist views. more>>
Gtk::CListModel is a simple data model with Gtk::Clist views.
SINOPSYS
my $model = tie @data, Gtk::CListModel,
titles => ["Fruit", "Price", "Quantity"];
# all data manipulation is done on @data now
push @data, ["Oranges", 5, 16];
# Create a view (a Gtk::Clist widget) to represent the data
# Include only some of the data in the view (fruit type and price)
# Also, do not include fruits that cost more than 6 price units.
my $clist = $model->create_view(main,
titles => [Fruit, Price],
filter => sub {$_[1] > 6? () : @_});
Gtk::CListModel lets you keep your data in a perl array and easily create a numer of different views on that data using Gtk::CList widgets. The views can show only some of the columns, or a subset of the data or even munge the data with user-defined filters.
All the data manipulations will be performed on a tied array and the changes will be propagated to the views created for that data.
To create the model use tie:
my $model = tie @data, Gtk::CListModel,
titles => ["head1", "head2",...];
The titles attribute should be an array reference with the titles of the columns of data. They will be used also for the default titles in the views.
You can also provide the initial data using the data attribute. Remember that the data elements you insert and retreive from the @data array are array references with as many items as the columns in the model. The order is the one defined by the titles attribute.
Later you can manipulate the @data array with the usual perl array operators, push, splice and so on.
METHODS
create_view ($name[, %options])
Create a Gtk::Clist widget that represents the data in the model. The name can be used later to disconnect the view from the data.
Options can be one of the following:
titles
An array reference of the titles of the columns to display in the list in the order they should appear in the view. The default is the titles specified at the model creation.
filter
A function that can manipulate the data just before it is inserted in the Gtk::CList. The function will receive the data and can either make a copy and modify the data or return an empty list. In the latter case the data will not be added to the view or, if the corresponding row was already present, it will be removed from the view.
postfilter
A function that receives the view, the row and the data that was just inserted/modified in the view. By default all the data is inserted in the views as text. This filter can be used to display pixmaps, for example or do any other kind of manipulations on the Gtk::CList row.
remove_view ($name)
Disconnect the named view from the data. The current data displayed in the view will not be affected, but changes in the model will not propagate to this view anymore.
map_row ($clist, $row)
Get the index in the data array cooresponding to the row displayed in the Gtk::CList widget.
<<lessSINOPSYS
my $model = tie @data, Gtk::CListModel,
titles => ["Fruit", "Price", "Quantity"];
# all data manipulation is done on @data now
push @data, ["Oranges", 5, 16];
# Create a view (a Gtk::Clist widget) to represent the data
# Include only some of the data in the view (fruit type and price)
# Also, do not include fruits that cost more than 6 price units.
my $clist = $model->create_view(main,
titles => [Fruit, Price],
filter => sub {$_[1] > 6? () : @_});
Gtk::CListModel lets you keep your data in a perl array and easily create a numer of different views on that data using Gtk::CList widgets. The views can show only some of the columns, or a subset of the data or even munge the data with user-defined filters.
All the data manipulations will be performed on a tied array and the changes will be propagated to the views created for that data.
To create the model use tie:
my $model = tie @data, Gtk::CListModel,
titles => ["head1", "head2",...];
The titles attribute should be an array reference with the titles of the columns of data. They will be used also for the default titles in the views.
You can also provide the initial data using the data attribute. Remember that the data elements you insert and retreive from the @data array are array references with as many items as the columns in the model. The order is the one defined by the titles attribute.
Later you can manipulate the @data array with the usual perl array operators, push, splice and so on.
METHODS
create_view ($name[, %options])
Create a Gtk::Clist widget that represents the data in the model. The name can be used later to disconnect the view from the data.
Options can be one of the following:
titles
An array reference of the titles of the columns to display in the list in the order they should appear in the view. The default is the titles specified at the model creation.
filter
A function that can manipulate the data just before it is inserted in the Gtk::CList. The function will receive the data and can either make a copy and modify the data or return an empty list. In the latter case the data will not be added to the view or, if the corresponding row was already present, it will be removed from the view.
postfilter
A function that receives the view, the row and the data that was just inserted/modified in the view. By default all the data is inserted in the views as text. This filter can be used to display pixmaps, for example or do any other kind of manipulations on the Gtk::CList row.
remove_view ($name)
Disconnect the named view from the data. The current data displayed in the view will not be affected, but changes in the model will not propagate to this view anymore.
map_row ($clist, $row)
Get the index in the data array cooresponding to the row displayed in the Gtk::CList widget.
Download (0.43MB)
Added: 2006-07-11 License: Perl Artistic License Price:
1201 downloads
JavaPK for Desktop 2.5
JavaPK for Desktop (JPKD) is a Clinical Pharmacokinetic (CPK) Services (or Therapeutic Drug Monitoring, TDM). more>>
JavaPK for Desktop (JPKD) is a Clinical Pharmacokinetic (CPK) Services (or Therapeutic Drug Monitoring, TDM).
It not only inherits all functionalities of JavaPK for Mobile Devices, but also has a built- in algorithm of users defined Bayesian model for individualized pharmacokinetic parameter estimation (UDBM) for batch input data.
Users can define their own pharmacokinetic prediction models with population PK parameters and then use the defined model to solve batch prediction data or applied the defined model to therapeutic drug monitoring (TDM).
JPKD is created for your own personal uses and testing purposes. JPKD shall be used as a guide or a decision support tool only. Medical decisions should NOT be solely based on the results of this program. Although this program has been tested thoroughly, the accuracy of the information cannot be guaranteed. Once you use JPKD, you have automatically agreed with this disclaimer.
Main features:
- Sawchuk-Zaske (aminoglycosides & vancomycin) and Bayesian method for PK parameter estimation
- 15 built-in drugs for TDM (see the below drug lists)
- functions for users defined Bayesian estimation drug models
- portable function for users defined models
- a built-in spread sheet for batch PK parameter estimation & input data manipulation
- application user-defined Bayesian model to TDM
- multiple desktop platforms (WinXP/NT, Mac OS X, Linux PC) supported
Built-in drug lists
- Amikacin
- Carbamazepine
- Cyclosporin
- Digoxin
- Enfuvirtide
- Everolimus
- Gentamicin
- Indinavir
- Lithium
- Phenytoin
- Ritonavir
- Tacrolimus
- Theophylline
- Tobramycin
- Vancomycin
<<lessIt not only inherits all functionalities of JavaPK for Mobile Devices, but also has a built- in algorithm of users defined Bayesian model for individualized pharmacokinetic parameter estimation (UDBM) for batch input data.
Users can define their own pharmacokinetic prediction models with population PK parameters and then use the defined model to solve batch prediction data or applied the defined model to therapeutic drug monitoring (TDM).
JPKD is created for your own personal uses and testing purposes. JPKD shall be used as a guide or a decision support tool only. Medical decisions should NOT be solely based on the results of this program. Although this program has been tested thoroughly, the accuracy of the information cannot be guaranteed. Once you use JPKD, you have automatically agreed with this disclaimer.
Main features:
- Sawchuk-Zaske (aminoglycosides & vancomycin) and Bayesian method for PK parameter estimation
- 15 built-in drugs for TDM (see the below drug lists)
- functions for users defined Bayesian estimation drug models
- portable function for users defined models
- a built-in spread sheet for batch PK parameter estimation & input data manipulation
- application user-defined Bayesian model to TDM
- multiple desktop platforms (WinXP/NT, Mac OS X, Linux PC) supported
Built-in drug lists
- Amikacin
- Carbamazepine
- Cyclosporin
- Digoxin
- Enfuvirtide
- Everolimus
- Gentamicin
- Indinavir
- Lithium
- Phenytoin
- Ritonavir
- Tacrolimus
- Theophylline
- Tobramycin
- Vancomycin
Download (51.6MB)
Added: 2006-10-09 License: Freeware Price:
1112 downloads
dtoGen 0.5.2
dtoGe project is a java source generation tool. more>>
dtoGe project is a java source generation tool that can ease the development of multi-tier systems by offering a reliable solution to obtain the data transfer objects out of the domain model objects without hand-writting additional code.
Using a simple set of javadoc tags, dtoGen™ provides the possibility to define the whole set of data transfer objects used by your system.
<<lessUsing a simple set of javadoc tags, dtoGen™ provides the possibility to define the whole set of data transfer objects used by your system.
Download (0.63MB)
Added: 2006-09-01 License: GPL (GNU General Public License) Price:
1149 downloads
MODELbuilder 0.7.5
MODELbuilder is a scientific application that provides a graphical way to derive models from empirical and simulation data. more>>
MODELbuilder is a scientific application that provides a graphical way to derive models from empirical and simulation data. MODELbuilder is fit to do regression and regression analysis.
Enhancements:
- This release has a new project file format, data editor, and data import class.
- An external solver has been added.
<<lessEnhancements:
- This release has a new project file format, data editor, and data import class.
- An external solver has been added.
Download (MB)
Added: 2007-01-01 License: GPL (GNU General Public License) Price:
1027 downloads
JSBSim Flight Dynamics Model 0.9.13
JSBSim is an open source flight dynamics model. more>>
JSBSim Flight Dynamics Model is an open source flight dynamics model (FDM) that compiles and runs under many operating systems, including Linux, Apple Macintosh, Microsoft Windows, Linux, IRIX, Cygwin (Unix on Windows), etc.
The FDM is essentially the physics/math model that defines the movement of an aircraft under the forces and moments applied to it using the various control mechanisms and from the forces of nature.
JSBSim has no native graphics. It can be run by itself as a standalone program, taking input from a script file and various aircraft configuration files; or, it can be run as an integrated part of a larger flight simulator implementation that includes a visual system.
The most notable example of the use of JSBSim is currently seen in the open source FlightGear simulator. JSBSim models the aerodynamic forces and moments by the classic coefficient buildup method.
JSBSim has seen the growth of a fairly large user base, with some of the more notable projects (of which I am aware) described on the Users page.
Main features:
- Fully configurable flight control system, aerodynamics, propulsion, landing gear arrangement, etc. through XML-based text file format.
- Rotational earth effects on the equations of motion (coriolis and centrifugal acceleration modeled).
- Configurable data output formats to screen, file, socket, or any combination of those.
Enhancements:
- This release includes new options for the standalone JSBSim executable, including improved real-time capability.
- This release also includes experimental (but tested) logic to reduce ground reactions jitter while on the ground.
<<lessThe FDM is essentially the physics/math model that defines the movement of an aircraft under the forces and moments applied to it using the various control mechanisms and from the forces of nature.
JSBSim has no native graphics. It can be run by itself as a standalone program, taking input from a script file and various aircraft configuration files; or, it can be run as an integrated part of a larger flight simulator implementation that includes a visual system.
The most notable example of the use of JSBSim is currently seen in the open source FlightGear simulator. JSBSim models the aerodynamic forces and moments by the classic coefficient buildup method.
JSBSim has seen the growth of a fairly large user base, with some of the more notable projects (of which I am aware) described on the Users page.
Main features:
- Fully configurable flight control system, aerodynamics, propulsion, landing gear arrangement, etc. through XML-based text file format.
- Rotational earth effects on the equations of motion (coriolis and centrifugal acceleration modeled).
- Configurable data output formats to screen, file, socket, or any combination of those.
Enhancements:
- This release includes new options for the standalone JSBSim executable, including improved real-time capability.
- This release also includes experimental (but tested) logic to reduce ground reactions jitter while on the ground.
Download (0.95MB)
Added: 2007-01-21 License: GPL (GNU General Public License) Price:
604 downloads
WildCAT 1.0.0
WildCAT project is a Java toolkit/framework which can be used to build context-aware applications. more>>
WildCAT project is a Java toolkit/framework which can be used to build context-aware applications, of which self-adaptive applications are a special case.
From the client applications point of view, it provides a simple and dynamic data-model to represent the execution context of the application, and offers a simple API for the programmers to access this information both synchronously and synchronously (pull and push).
Internally, it is a framework designed to facilitate the acquisition and aggregation of contextual data and to create reusable ontologies to represent aspects of the execution context relevant to many applications.
<<lessFrom the client applications point of view, it provides a simple and dynamic data-model to represent the execution context of the application, and offers a simple API for the programmers to access this information both synchronously and synchronously (pull and push).
Internally, it is a framework designed to facilitate the acquisition and aggregation of contextual data and to create reusable ontologies to represent aspects of the execution context relevant to many applications.
Download (0.75MB)
Added: 2007-01-04 License: LGPL (GNU Lesser General Public License) Price:
1025 downloads
Model Builder 0.4.0
Model Builder is a graphical tool for designing, simulating, and analyzing mathematical models. more>>
Model Builder is a graphical tool for designing, simulating, and analyzing mathematical models consisting of a system of ordinary differential equations (ODEs).
Main features:
- Equation-based model definition. No need to learn to program to define and run your models. Just type-in you differential equations
- Graphic output of simulation. You can save the graphics in the most common formats: png, svg, pdf, etc.
- Spreadsheet view of the results. From the spreadsheet you can make customized plots from your variables. You can also export your data to a .csv text file
- Latex rendering of your system of equations.
- Intuitive graphical interface.
- Uncertainty analysis module (coming soon!)
<<lessMain features:
- Equation-based model definition. No need to learn to program to define and run your models. Just type-in you differential equations
- Graphic output of simulation. You can save the graphics in the most common formats: png, svg, pdf, etc.
- Spreadsheet view of the results. From the spreadsheet you can make customized plots from your variables. You can also export your data to a .csv text file
- Latex rendering of your system of equations.
- Intuitive graphical interface.
- Uncertainty analysis module (coming soon!)
Download (0.21MB)
Added: 2007-03-27 License: GPL (GNU General Public License) Price:
558 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above data model search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed