I would feel dirty making properties files instead of GUI config, and
it did autoexecute after each change, which is why I don't actually
USE that feature anymore, which is why it hasn't had any more
development on it :) I think the easiest/best way is to be able to
right click on an EO and Generate ... (like you mentioned originally)
that has an optional config dialog that lets you specify params for
eogenerator.
http://www.mdimension.com/eogenerator/ for the Intel eogenerator ...
It refused to build universal for me, but then I'm not a big Makefile
kind of guy, so I just went ahead and built it straight x86. The
eogenerator guys did say they have a universal build for the next
release, but I'm not sure when that will be (they said "soon").
ms
On Mar 8, 2006, at 11:17 AM, Watkins, Garry wrote:
> The WOComponent Editor rocks! It is helping me strip out a bunch
> of garbage that is no longer needed, and helping me track down some
> errors in the .api files. I think that error that I was having was
> with caching issues. I had just brought the project in and it
> didn't have some of the frameworks pre-built.
>
> However, I have one minor suggestion. When the html validator
> complains about a missing webobject tag, can it give the opening
> webobject tag's name that is missing the close tag. It is very
> difficult for me to find the opening tag in some of these big html
> templates that I have.
>
> For the eogenerator stuff, why don't we have an eogen properties
> file for each of the models, and have the global settings in the
> preferences for wolips. For example, if I have models A, B and C.
> I would have an A.eogen.properties, B.eogen.properties. Then for C
> it would use the global properties set in the preferences panel.
>
> I can live with the automatic trigger for modified eomodels.
> However, some of the eomodels that I have can take up to a minute
> to save. Will it trigger automatically before it completely
> saves? If so this could be a problem. You might want to add a
> manual trigger by right clicking on it.
>
> Does anyone have a universal or intel binary for eogenerator?
>
> Thanks for the mojo on the eomodel stuff.
>
> Garry
>
> From: Mike Schrag [mailto:mschra..dimension.com]
> Sent: Wednesday, March 08, 2006 8:12 AM
> To: woproject-de..bjectstyle.org
> Subject: Re: Errors in the WOD editor and EOGenerator, and EOModels
>
>>> I am getting errors in the WO Component Editor, it is telling me
>>> that my custom component is either missing or does not extend
>>> WOElement. What search criteria is it using to find these
>>> errors? I am positive that it does, because it works when I run
>>> the app. My environment is: I am currently using the latest
>>> version of WOLips as of 3 or 4 days ago on a MBP and eclipse 3.2M5a.
>>
>> It happens when file is missing during the first build. You could
>> get rid of them with a clean build.
> The search criteria is basically what you would expect -- It
> searches everything in your classpath that has the same name as the
> element you declare looking for at least one that has a superclass
> in its type hierarchy of WOElement. There are a couple caching
> problems with errors in wod files, but making any change to the
> file should cause it to remove all errors for the wod and
> recompute. Make sure the class that implements the element type
> you declared is reachable by your project. I've never seen that be
> wrong (assuming you're using a relatively recent build) -- it's
> always been either me or an environmental problem.
>
>>> Next is anyone working on a right click on EOModel with an eogen
>>> option? Is that why WOLips has a EOGenerator executable path?
>>> Also you guys need to add a template path to that preference
>>> option. If not I will create a request for that one.
>>
>> I think Mike has an answer for that.
> So the eogen support is kind of tentative at the moment. What we
> really need is a per-model setting. At the moment, there's a per-
> project setting. You can set it in the WOLips tab of your project
> (basically fill in the rest of the commandline for EOGenerator).
> It will watch all the eomodels in your project and automatically
> run the eogen path + the project setting. The plan was to have per-
> model settings, but I just never got around to it.
>
>>>
>>> Finally, I am having issues with opening EOmodels from within
>>> eclipse. It keeps wanting to open it with XCode. I have already
>>> changed the file association options in XCode, and I have told
>>> the finder to use EOModeler to open .eomodel bundles.
>>
>> You could drag them on EOModeler.
> If you're telling finder by right-clicking and "Always Open With",
> Finder lies to you. It's evil. Instead, the mojo is Get Info on
> the eomodeld bundle and change "Open With" in that dialog to be old
> EOModeler and select Change All.
>
> ms
>
>
> Confidential & Privileged
>
> Unless otherwise indicated or obvious from its nature, the
> information contained in this communication is attorney-client
> privileged and confidential information/work product. This
> communication is intended for the use of the individual or entity
> named above. If the reader of this communication is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error or
> are not sure whether it is privileged, please immediately notify us
> by return e-mail and destroy any copies--electronic, paper or
> otherwise--which you may have of this communication.
This archive was generated by hypermail 2.0.0 : Wed Mar 08 2006 - 12:07:55 EST