Hi,

our company is currently evaluting PhpEd and so far it looks pretty good and helpfull.

We have just one small problem. The workspace and project files created by PhpEd don't seem to be SVN compatible like for example in a Visual Studio project. As there are normaly working many people at one project, the absolute path storage within these files is a problem, because it causes conflicts with the project files of other users.

So, before we license PhpEd we need to know if there is some way to make the projects SVN capable, or if someone encoutered something like this and knows a solution.

Thanks in advance!

Regards,
Matthias Gabel
Game Programmer,
3d-io games & video production GmbH

Hi there! Does this help:
tip-svn-subversion-and-phped-v4-t1888.html

Thanks!

It would be nice to have a customizable commit/update in the projects context menu and the possibility for a key shortcut

Thanks for the reply, but this isn't the solution we were looking for. We already know how to use an svn with PhpEd

To be more precise about the problem with a simple example:
Lets say, we have a project where there is a file located like c:\svn\myScript.php.
This path will be stored absolute in the project file. Now someone else created his svn folder at p:\php_projects\svn\.
Everytime me or an other one is commiting the project, the file pathes get switched in the project file, more or less breaking it for everyone else.

So my question was, if it is possible to make the project/workspace files svn compatible at all (like for example Visual Studio project files), as they aren't compatible right now.
Without these files we have for example also a problem if someone is adding files to the project, and so on...

Regards,
Matthias Gabel
Game Programmer,
3d-io games & video production GmbH

I'm not sure what compatibility you mean.
As far as I know, in no way "absolute path" may cause any problem.
For example you have an SVN repository say running on the server and it means that user A may check it out into p:\userA
while user B may check it out c:\somedir\someotherdir
Where is the problem?
If you mean absolute path stored in the ppj file, it may cause some propblems if ppj files stored in the repository. But why would you need to store them there?

Yes, that is what i was talking about.
Everytime someone does a fresh checkout, he would be forced to create a new workspace/project, as there are people switching teams or help out with a project for some time, or just want to implement some functions.
Creating new projects everytime is kinda lame.

And we also prefer to have our project settings in sync.

So, there is no way to make these .ppj .ppw files svn "friendly"?

Regards,
Matthias Gabel
Game Programmer,
3d-io games & video production GmbH

you may try to edit ppj files and put relative path in RelativeRootDir=

At our company, we use SVN, and we only commit the .ppj file to the repository as an assist for people working on different projects.

There is one fixed path in there, that might be a problem for you. Our resolution was to just have everyone put there checkouts at the same place on the computers.

For example:

Create "C:\Repository\" or something like that on each computer, and then just checkout to that location. After that the .ppj files will work for anyone with that path.

As for the workspace files (.ppw) you probably don't want to commit those, as they contain the user-specific file layout that the person was using.

The idea here is:
- checkout repository
- open the .ppj file, and do some work
- when you exit, save the .ppw file in the same place as the .ppj file, with a similar name, but DO NOT add it to your repository
- next time you want to edit, just open the .ppw file