Federico Giménez Nieto wrote: > I had commented the move_resources call related to GDL2 in preinst, > now it is removed completeley.
Just delete the file, it is not needed. > Builds fine, nothing breaks but the palette is empty, see the attached > screenshot. AFAICS it doesn't have any draggable items so that is expected. The GDL2 palette hooks eomodel objects into Gorm so that they are available in the GUI that Gorm creates. It is only usable with DBModeler. To test, open a eomodel file in DBModeler and try to drag and drop some objects from there to Gorm's object window. During the drag operation, the cursor should change to something very similar to DBModeler's logo and become an object in Gorm, after you drop it. Then, you can add a NSTableView and start editing attributes, making connections, instantiate a EOEditingContext class, etc. Basically, the usual Gorm stuff but with a GDL2-aware application. There were a few videos by Matt Rice, the DBModeler/EOModel author; I'm not sure if they're still available. The eomodel(d) file must be in the same directory as the gorm file, as the palette README says. P.S. I'd suggest you to talk with upstream about a new release, and more importantly, what is their recommended route for the future. In SVN trunk, there's now an incompatible fork of the EOModel library under Apps/ and a new app, EOModelEditor, designed for the same job as DBModeler. I don't know if it is usable (either independently or in conjunction with the palette). Both libraries+apps are built by default, but only one can run since the libraries are with the same soname and the two versions are not ABI-compatible. A bit messy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
