On Nov 15, 2007, at 2:26 PM, Pierre Frisch wrote:
> Of course I am biased :)
>
> I think we should use the EOF and I am suggesting that syntax
> because it will be more familiar to WO developers.
That is a good point and one that I have been wrestling with. The
original EOGenerator had yet a different syntax, so regardless of
which one gets used, templates need to be re-written.
JavaEOGenerator has the advantage of a familiar syntax, Velocity has
the advantages of compactness and closeness to the original
EOGenerator syntax.
I looked at a couple of comparisons and decided that I (personally)
prefer reading the Velocity syntax. At least this week. But choice
is not a bad thing.
Chuck
> On Nov 15, 2007, at 13:42, Pierce T. Wetter III wrote:
>
>>
>> On Nov 15, 2007, at 2:00 PM, Chuck Hill wrote:
>>
>>> My vote would be for Mike's version. Though his uses Entity
>>> Modeler's "EOF" stack and JavaEOGenerator uses real EOF. I like
>>> the templates that Mike's uses better (Velocity) and the fact
>>> that you don't need to launch an entire WO App to generate some
>>> text files.
>>
>> Me too, I actually hadn't quite meant to send out that email yet
>> (I missed "close" and hit "Send") because I realized part way
>> through that what I really want is Mikes version but hopefully
>> with any subtle implementation details from the Apple version
>> included. That's why the last sentence just sort of trails off. If
>> Eclipse/Entity Modeler is now "The way" it seems that the
>> generation part should be built into Entity Modeler.
>>
>> Pierce
>>
>>
>>
>>
>
--Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 18:47:03 EST