On Dec 16, 2012, at 10:18 AM, Ivan Stankovic wrote: > So far I only implemented EdaObject, EdaPage, EdaNet and EdaPin and I'm > able to load very simple schematics. Attributes willl be perhaps the most > work, but even that should be relatively straightforward. Every object emits > an event when something interesting happens, such as adding or removing an > object to/from a page, rotating an object etc. > > In any case, I think this is the way we should move forward, but I don't > see it as too realistic since it would imply e.g. rewriting most of gschem, > or writing a new schematic editor from scratch (honestly, I'm not sure > what would be easier).
I did the same thing in the component manager. In the git repository for the component manager, there are the following sources: geom-* : Boxed types representing all the primitives. sch-* : GObject types representing all the GOBJECTs in gEDA. These portions of the code are decoupled well, and anyone is welcome to use them. I discover that it is quite easy to burnout with the large amounts of boilerplate code required by GObject. (I also discovered that Vala takes the pain out of implementing GObjects.) Cheers, Ed -- Mailing list: https://launchpad.net/~geda-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~geda-developers More help : https://help.launchpad.net/ListHelp
