On Sep 1, 2006, at 10:23 AM, David LeBer wrote:
> Huh? EOModeler still (limpingly) works. But more importantly, I
> think you could argue that Apple felt free to deprecated the
> existing tool stack *because* Entity Modeler exists. No one has
> ever seriously suggested people create .eomodels manually.
Sorry, I was using an extreme case to illustrate my point that while
you *can* manage all the various pieces of WO by simply editing text
files, the tools make it so much easier and accessible. EOModeler/
Entity Modeler is the best example of this. I in no way intended to
imply that people actually needed to manually create or
edit .eomodeler packages.
I was responding to what I thought was a statement that WOBuilder
isn't important because seasoned users don't need it. Ken has since
clarified and I understand that this wasn't what he was saying at all.
I think that the WO community is in a VERY strong position in that
the Apple tools still work and will for the near-term and we have
time to devise replacements. Entity Modeler is an excellent example
of what can be done. I'd love to see the same class of tool to
replace WOBuilder. I only wish I had the ability to create it!
Dave
This archive was generated by hypermail 2.0.0 : Fri Sep 01 2006 - 10:52:08 EDT