Book a Demo

Author Topic: Relative File Paths still not properly supported?  (Read 3541 times)

Philipp

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Relative File Paths still not properly supported?
« on: July 31, 2007, 01:06:47 am »
Hi there

Just downloaded EA 7.0 and notified a fellow developer via Skype. His first question was the same as mine: Are relative file paths now supported out of the box?

And it appears they aren't! IMO, this "Local Path" solution really is a hack that makes life harder for 99% of your customers. I really can't think of a real-live situation where model and source code aren't stored below a common root directory (may it be below "C:\projects\projectX" or "X:\dev\customerX\theirproject". Especially with dev teams, it can be expected that EA files are part of the same source code repository, so this makes absolutely no sense. The docs on "Local Paths" treat this very situation like something special, but I'd say this is just the regular situation.

I'm still hoping I overlooked something, but if not - please add this really basic feature. I think it's not too much to ask. Anyway: congrats to the new release :)

Cheers
Philipp
« Last Edit: July 31, 2007, 05:30:19 am by philipp »

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Relative File Paths still not properly support
« Reply #1 on: July 31, 2007, 11:49:58 am »
The support for local paths hasn't changed in the new version.

You're obviously familiar with how local paths are supported.  How does this feature not meet your needs?

Philipp

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Relative File Paths still not properly support
« Reply #2 on: July 31, 2007, 01:49:50 pm »
I think absolute file path's are something I shouldn't have to configure at all, as they - unlike relative paths - tend to change. If I check out a project folder to any location (VS2005 solutions/projects, test and localization projects etc.), everything works out of the box - except the model file which requires me to update variables according to the EAP's current location.

I often work with other developers (of which quite a few now use EA, too :)), and this is one of the first things (probably *the* first thing) people are complaining once they start using the tool in a productive environment. I'm honestly surprised that this isn't something you guys are annoyed with yourself  ;D

I've been using EA for years now and never felt it was an advantage to have the "Local Paths" feature. And besides: Why not make it configurable how EA stores file paths (absolute or relative)? Wouldn't that be a reasonable improvement?

Cheers
Philipp

thomaskilian

  • Guest
Re: Relative File Paths still not properly support
« Reply #3 on: July 31, 2007, 08:06:44 pm »
Totally agree with that! Relative paths should simply be the standard for each and everything in EA. I ususally change them manually and tedious. Can't Sparx simply introduce a switch that tells: Store paths as relative/absolute? That would really be an improvement!

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Relative File Paths still not properly support
« Reply #4 on: August 01, 2007, 02:42:30 am »
Yes, desperately, please!
No, you can't have it!

Martin Terreni

  • EA User
  • **
  • Posts: 672
  • Karma: +0/-0
  • Sorry, I can't write
    • View Profile
Re: Relative File Paths still not properly support
« Reply #5 on: August 01, 2007, 06:32:16 am »
well, at least using SQL server and TFS I haven't had that problem. I configured it once the same as workspace and that's it. works for all of our team.
I though remember the times when we worked on EAPs (god forbid!) I use to have tom prolbems with the paths (I can't remember what...)
Recursion definition:
If you don’t understand the definition read "Recursion definition".