Re: EOGenerator reference

From: Pierre Frisch (pierre.frisc..pearway.com)
Date: Tue Jul 11 2006 - 10:24:20 EDT

  • Next message: Mike Schrag: "Re: EOModeler editor file association"

    Yes please Thank you. I usually store my templates in a separate
    framework with common custom types that way they are part of the
    source control and I can use different sets of templates for
    different customers.

    Pierre

    On 11-Jul-06, at 7:16 AM, Mike Schrag wrote:

    > Actually, I didn't even consider doing this for template folders
    > (mainly because are never project-relative -- just didn't occur to
    > me). So what you're saying is you want the same auto-relative-path
    > conversion on template path so you can have project-relative
    > templates, correct?
    >
    > ms
    >
    > On Jul 11, 2006, at 9:56 AM, Pierre Frisch wrote:
    >
    >> Hi Mike,
    >>
    >> I think you miss one. It works for the model reference, but not
    >> for the template reference (template folder). At least it does not
    >> appears to change in the UI.
    >>
    >> Pierre
    >>
    >> On 9-Jul-06, at 1:27 PM, Mike Schrag wrote:
    >>
    >>> For the moment, I've made it so that when it makes sense to use a
    >>> relative path, it will do so (i.e. if there is overlap between
    >>> the model path and your workspace path, it will become a relative
    >>> path). If you have an absolute path that has no overlap (i.e. /
    >>> Library/Frameworks/etc) then it will remain an absolute path.
    >>> This is not optimal, but it should be a little smarter than
    >>> before. Longer term we can add variable support.
    >>>
    >>> If you have absolute paths in your model now, you can open them
    >>> and resave them and they'll turn into the new style (you should
    >>> actually see the new style in the editor itself when you open it).
    >>>
    >>> ms
    >>>
    >>> On Jul 3, 2006, at 2:43 PM, Pierre Frisch wrote:
    >>>
    >>>> Is there some global eclipse variable that refer to the
    >>>> workspace? I am not proficient enough in eclipse internal but it
    >>>> should be possible to recognize that the start of the path is
    >>>> equal to the workspace path and switch to relative path or
    >>>> replace the workspace part of the path by a substitution variable.
    >>>>
    >>>> I think that the best would be to have something like $
    >>>> {workspace}/DatabaseTypes/Resources/Prototypes.eomodeld if this
    >>>> is possible within the eclipse framework. Relative path are good
    >>>> too but they are a little less expressive.
    >>>>
    >>>> The relative path does not work with the current version of wolips.
    >>>>
    >>>> Thanks
    >>>>
    >>>> Pierre
    >>>>
    >>>> On 3-Jul-06, at 9:54 AM, Mike Schrag wrote:
    >>>>
    >>>>> Yeah, I know .. This is a weird problem, actually. I'm open
    >>>>> for suggestions. Technically, yes, you can edit the text file
    >>>>> underneath and make it a relative path -- I think it evaluates
    >>>>> relative to the project path? You might have to test that one.
    >>>>>
    >>>>> We need to be able to support paths to /Library/Frameworks/
    >>>>> whatever as well as project paths. I'm thinking if the path
    >>>>> you choose is beneath your workspace folder, then it should
    >>>>> switch over to relative paths.
    >>>>>
    >>>>> ms
    >>>>>
    >>>>> On Jul 3, 2006, at 12:02 PM, Pierre Frisch wrote:
    >>>>>
    >>>>>> Is there a way to reference a Prototype model without
    >>>>>> embedding the workspace path in the eogen file? Can I use
    >>>>>> relative path?
    >>>>>>
    >>>>>> I would rather not have in my project:
    >>>>>> /Users/pierre/Projects/workspace/DatabaseTypes/Resources/
    >>>>>> Prototypes.eomodeld
    >>>>>>
    >>>>>> Thanks
    >>>>>>
    >>>>>> Pierre
    >>>>>
    >>>>
    >>>
    >>
    >



    This archive was generated by hypermail 2.0.0 : Tue Jul 11 2006 - 10:24:25 EDT