Just started using 3.0… I especially like the extended shape
Can I ask a favor… now that Go 3.0 is open for surgery, can GoUserFlags and GoUserObject be made part of all visual base classes (especially goShape) or is this a critical strategy in the design of base classes?
It will make the writing of custom “home brew” serialization routines and property editors easier and more efficient…
PS What is the status of 3.0 and anything more coming in its release.
PPS… Is this possible?.. (Rainy day in New Jersey and nothing else to do:)
Any chance of a Visual Object Builder where mostly static objects can be built very much by draging and dropping shapes, nodes, ect onto base object layers… and where properties and events set on a canvas or using a property editor?
I know that this is not easy but is it something feasible or am I not understanding GoDiagram fully.
For example, my app requires complex interactive part templates… very much like those found in Visio, very time consuming to build using execution code… If I could only “paint” them on a canvas first… maybe my dog (who said I am spending too much time with “GoDiagram” and not him) will stop telling me he’s thinking about moving in with the neighbors…