On Friday, April 17, 2009, at 02:06PM, "Daniel Roßberg" <[email protected]> wrote:
>I know the GE from the brlcad.org wiki and the files in rt^3 only. >These are quite different from what I did in the core interface. But, >if you think that the core interface represents mainly your intention >for the GE let's "rename" coreInterface to GE and put all the >additional functionality (UUID etc.) into the GS. Per our talk on IRC a couple weeks ago, hopefully that misunderstanding is clarified. I think this suggestion sounds great. >However, everybody should know an important property of the Object >classes in the core interface: They represent copies of database >elements. I.e. changing an Object class does not change the database. > The Object has to be written back to do this (the call-back method >does this automatically). This behavior cannot be changed at >coreInterface level. But one could write object classes with >automatic write backs on a higher level (on top of the coreInterface). That's interesting to know, and I'm not sure I understood that from reading the sources but I gather that's why there are internal-only objects in use. Don't see that as a problem really as the notion of the application always being in a saved state certainly is something that should happen at the application level and not the library level (hence why librt writes are so explicit). Cheers! Sean ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
