Difference between revisions of "Glom"

From Glom
Jump to: navigation, search
(List features more explicitly.)
Line 1: Line 1:
 
===What you need, without the nonsense.===
 
===What you need, without the nonsense.===
  
With Glom you can design table definitions and the relationships between them, plus arrange the fields on the screen. You can edit and search the data in those tables, and specify field values in terms of other fields. It's as easy as it should be.
+
With Glom you can design database systems - the database and the user interface. Glom has high-level features such as relationships, lookups, related fields, related records, calculated fields, drop-down choices, searching, reports, users and groups, so you don't have to implement it all yourself.
  
The design is loosely based on [http://www.filemaker.com/ FileMaker Pro], with the added advantage of separation between interface and data. Its simple framework should be enough to implement most database applications. Without Glom these systems normally consist of lots of repetitive, unmaintainable code.
+
Glom keeps things simple. It has Numeric, Text, Date, Time, Boolean, and Image field types, and displays them appropriately.
  
Glom-specific data such as the relationship definitions is saved in the Glom document. Glom re-connects to the database server when it loads a previous Glom document. The document is in XML format.
+
Most Glom systems require almost no programming code, though you can use Python for calculated fields or add buttons that runs python code.
 +
 
 +
The design is loosely based on [http://www.filemaker.com/ FileMaker Pro], with the added advantage of separation between interface and data. Its simple framework should be enough to implement most database applications. Without Glom these systems normally consist of lots of repetitive, unmaintainable code.
  
 
Glom uses the [http://www.postgres.org/ PostgreSQL] database backend but it can not edit databases that it did not create, because it uses only a simple subset of Postgres functionality.
 
Glom uses the [http://www.postgres.org/ PostgreSQL] database backend but it can not edit databases that it did not create, because it uses only a simple subset of Postgres functionality.
Line 11: Line 13:
 
Here are some [[Screenshots|screenshots]] with explanations, and [[News|news]] about recent changes.
 
Here are some [[Screenshots|screenshots]] with explanations, and [[News|news]] about recent changes.
  
[[Development]] is at an early stage, so it's not a complete database solution yet. See the [[Development/Plans|Development Plans]].
+
[[Development]] is ongoing. See the [[Development/Plans|Development Plans]].
  
 
http://www.glom.org/screenshots/small_glom_data_details.png
 
http://www.glom.org/screenshots/small_glom_data_details.png

Revision as of 05:37, 23 February 2006

What you need, without the nonsense.

With Glom you can design database systems - the database and the user interface. Glom has high-level features such as relationships, lookups, related fields, related records, calculated fields, drop-down choices, searching, reports, users and groups, so you don't have to implement it all yourself.

Glom keeps things simple. It has Numeric, Text, Date, Time, Boolean, and Image field types, and displays them appropriately.

Most Glom systems require almost no programming code, though you can use Python for calculated fields or add buttons that runs python code.

The design is loosely based on FileMaker Pro, with the added advantage of separation between interface and data. Its simple framework should be enough to implement most database applications. Without Glom these systems normally consist of lots of repetitive, unmaintainable code.

Glom uses the PostgreSQL database backend but it can not edit databases that it did not create, because it uses only a simple subset of Postgres functionality.

Here are some screenshots with explanations, and news about recent changes.

Development is ongoing. See the Development Plans.

small_glom_data_details.png