> Ideally yes! That would be awesome!
OK ... Committed. There's a new construct called an
EOModelRenderContext that can be attached to the thread to control
what EOModels will hand you when you query their various formatting
methods for class names. entity.className will always be the raw
value, but any of the format-centric (classNameWithDefault,
classNameWithoutPackage, classNameWithOptionalPackage, etc) will hand
back context-specific class names. I think I tracked down all the
various calls to make sure they were going through the correct path
and not querying className() directly (which they should have been
doing anyway). Building now ... Check it in 15.
> The old EOGenerator didn't handle Fetch Spec parameters on the
> client-side either, so I was left with doing a search-and-replace on
> the client classes to replace ".server." anywhere in the classes
> with ".client.". It worked, but I had to do it EVERY TIME
> EOGenerator ran. A real PITA.
You may already be doing this, but I expect that you would have two
eogen files. One server.eogen and one client.eogen? You can then set
the flag in one and not in the other (if that's necessary). Both
should run on build.
> There is also some UI ugliness to the EOGen Editor in that the
> header for check-boxes is mislabeled as being for the templates,
> which is set in the section above. BUT I have just grabbed the
> WOLips source via SVN and was going to look into fixing that myself,
> as changing some text is a good place to start as a contributor (at
> least for THIS contributor). :) Race ya!
I was in there, so i went ahead and fixed this ... Sorry to ruin your
fun :)
ms
This archive was generated by hypermail 2.0.0 : Tue Mar 04 2008 - 14:24:18 EST