* EOAccess/EOModel.h: Forward declare NSMutableArray class.

* GDL2Palette/README: Document some pitfalls due to lack
        of project management app support.



git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/gdl2/trunk@24419 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
ratmice 2007-01-25 22:57:24 +00:00
parent 8e26c418d7
commit 79f10f22d0
3 changed files with 18 additions and 3 deletions

View file

@ -1,3 +1,9 @@
2007-01-25 Matt Rice <ratmice@gmail.com>
* EOAccess/EOModel.h: Forward declare NSMutableArray class.
* GDL2Palette/README: Document some pitfalls due to lack
of project management app support.
2007-01-11 Matt Rice <ratmice@gmail.com>
* GDL2Palette/README: New file.

View file

@ -37,7 +37,7 @@
#include <EOAccess/EODefines.h>
#include <EOAccess/EOPropertyListEncoding.h>
@class NSMutableArray;
@class NSArray;
@class NSDictionary;
@class NSNotification;

View file

@ -1,7 +1,16 @@
The GDL2 Palette uses runtime introspection to know which Associations/Aspects
are available. EOInterface has skeleton classes (ready to be implemented)
for all the associations, some of which are incomplete. So not everything
creatable with gorm will actually work.
for all the associations, some of which are incomplete. So not all
associations creatable with gorm will actually work.
Please see the EOInterface TODO file for a list of implemented association
classes and aspects.
Currently the palette looks for .eomodel or .eomodeld files, in the
same directory as the .gorm file. Ideally it would get the list of models from
a project management tool such as Project Manager or Project Center.
Inability to locate a model file would manifest itself as a lack of keys
to bind aspects to.
This tool should also be able to notify Gorm when a model file is changed.
Currently you must quit Gorm and reload the .gorm file when the model changes.