Status: New Owner: ---- CC: anquetil...@gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Currently, VerveineJ exports the FileAnchors with full path. It should export it with the path relative to the input folder.
Not sure about this one. On my computer, it does output relative path. Only they are not really relative to the input folder, but relative to the argument you gave to verveinej:
so if you say: verveinej.sh ../some/path/to/java/project
all path in the file anchors will start with "../some/path/to/java/project" I think it is more conveniant because you can still have relative path if you want, you only need to give them relative when you call verveinej and you can also get absolute paths if needed by giving absolute paths as argument ...
Did you give fullpaths as arguments?
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Jeudi 28 Avril 2011 23:40:37 Objet: [Moose-dev] Issue 603 in moose-technology: VerveineJ should export relative paths Status: New Owner: ---- CC: anquetil...@gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Currently, VerveineJ exports the FileAnchors with full path. It should export it with the path relative to the input folder.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Nicolas,
I gave full path as argument, but even if I give relative path I do not want to see it in the MSE file.
In Moose, we always relate the file anchor path to a root folder.
For example: verveinej.sh -- Annotations/
results in a path like: "Annotations/src/layout/SpringUtilities.java"
but, I only want "src/layout/SpringUtilities.java" (without the trailing "/")
Like that, the model is movable in other locations without a problem without having to think about how to invoke the parser. It only depends on the root folder, and this folder can be renamed after the fact.
We have the same convention in inFusion and it works well. From what it sounds, you already add this information explicitly in VerveineJ, so it would not be difficult to take out.
Cheers, Doru
On 28 Apr 2011, at 23:50, Nicolas Anquetil wrote:
Not sure about this one. On my computer, it does output relative path. Only they are not really relative to the input folder, but relative to the argument you gave to verveinej:
so if you say: verveinej.sh ../some/path/to/java/project
all path in the file anchors will start with "../some/path/to/java/project" I think it is more conveniant because you can still have relative path if you want, you only need to give them relative when you call verveinej and you can also get absolute paths if needed by giving absolute paths as argument ...
Did you give fullpaths as arguments?
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Jeudi 28 Avril 2011 23:40:37 Objet: [Moose-dev] Issue 603 in moose-technology: VerveineJ should export relative paths Status: New Owner: ---- CC: anquetil...@gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Currently, VerveineJ exports the FileAnchors with full path. It should export it with the path relative to the input folder.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Value is always contextual."
Hummmm, I am not convinced yet :-(
The argument of preservation of behaviour as some strength, but still verveinej is not infusion.
And above all, I believe the proposed behaviour is more flexible and powerful.
You can very simply have the old behaviour just by doing "cd project-root ; verveinej ." And you can have full paths, or paths relative to some other place than the project root.
nicolas
----- Mail original -----
De: "Tudor Girba" tudor.girba@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Cc: codesite-noreply@google.com Envoyé: Vendredi 29 Avril 2011 00:03:22 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Hi Nicolas,
I gave full path as argument, but even if I give relative path I do not want to see it in the MSE file.
In Moose, we always relate the file anchor path to a root folder.
For example: verveinej.sh -- Annotations/
results in a path like: "Annotations/src/layout/SpringUtilities.java"
but, I only want "src/layout/SpringUtilities.java" (without the trailing "/")
Like that, the model is movable in other locations without a problem without having to think about how to invoke the parser. It only depends on the root folder, and this folder can be renamed after the fact.
We have the same convention in inFusion and it works well. From what it sounds, you already add this information explicitly in VerveineJ, so it would not be difficult to take out.
Cheers, Doru
On 28 Apr 2011, at 23:50, Nicolas Anquetil wrote:
Not sure about this one. On my computer, it does output relative path. Only they are not really relative to the input folder, but relative to the argument you gave to verveinej:
so if you say: verveinej.sh ../some/path/to/java/project
all path in the file anchors will start with "../some/path/to/java/project" I think it is more conveniant because you can still have relative path if you want, you only need to give them relative when you call verveinej and you can also get absolute paths if needed by giving absolute paths as argument ...
Did you give fullpaths as arguments?
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Jeudi 28 Avril 2011 23:40:37 Objet: [Moose-dev] Issue 603 in moose-technology: VerveineJ should export relative paths Status: New Owner: ---- CC: anquetil...@gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Currently, VerveineJ exports the FileAnchors with full path. It should export it with the path relative to the input folder.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Value is always contextual."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
On 29 Apr 2011, at 01:06, Nicolas Anquetil wrote:
Hummmm, I am not convinced yet :-(
The argument of preservation of behaviour as some strength, but still verveinej is not infusion.
I was talking about the behavior that Moose relies on. inFusion merely complies to it, and I would expect other exporters to comply to it as well.
And above all, I believe the proposed behaviour is more flexible and powerful.
It is not more flexible. I never had the need for this behavior, but I always wanted to have it nicely portable. As a consequence, I would always have to cd first. This is less flexible :).
It only constraints us and adds more variables to a situation that is already complex: explaining people that they have to set the root folder is already problematic without the extra possibilities.
If you really insist on it, you could provide it as an optional setting (but the default should be no prefix)?
Cheers, Doru
You can very simply have the old behaviour just by doing "cd project-root ; verveinej ." And you can have full paths, or paths relative to some other place than the project root.
nicolas
----- Mail original -----
De: "Tudor Girba" tudor.girba@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Cc: codesite-noreply@google.com Envoyé: Vendredi 29 Avril 2011 00:03:22 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Hi Nicolas,
I gave full path as argument, but even if I give relative path I do not want to see it in the MSE file.
In Moose, we always relate the file anchor path to a root folder.
For example: verveinej.sh -- Annotations/
results in a path like: "Annotations/src/layout/SpringUtilities.java"
but, I only want "src/layout/SpringUtilities.java" (without the trailing "/")
Like that, the model is movable in other locations without a problem without having to think about how to invoke the parser. It only depends on the root folder, and this folder can be renamed after the fact.
We have the same convention in inFusion and it works well. From what it sounds, you already add this information explicitly in VerveineJ, so it would not be difficult to take out.
Cheers, Doru
On 28 Apr 2011, at 23:50, Nicolas Anquetil wrote:
Not sure about this one. On my computer, it does output relative path. Only they are not really relative to the input folder, but relative to the argument you gave to verveinej:
so if you say: verveinej.sh ../some/path/to/java/project
all path in the file anchors will start with "../some/path/to/java/project" I think it is more conveniant because you can still have relative path if you want, you only need to give them relative when you call verveinej and you can also get absolute paths if needed by giving absolute paths as argument ...
Did you give fullpaths as arguments?
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Jeudi 28 Avril 2011 23:40:37 Objet: [Moose-dev] Issue 603 in moose-technology: VerveineJ should export relative paths Status: New Owner: ---- CC: anquetil...@gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Currently, VerveineJ exports the FileAnchors with full path. It should export it with the path relative to the input folder.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Value is always contextual."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow."
Comment #1 on issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Do we agree to have the sources without the trailing folder?
I have been busy working on the other bugs. I am still pondering it. I must admit I fail to see how "cd <some-directory> ; verveinej ." is that much complex or annoying that "verveinej <some-directory>" In all cases, you need to know where the root of your project is (if I understand correctly your argument).
I could add an option, but this does not appear yet as a pressing emergency ...
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Dimanche 1 Mai 2011 10:28:38 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Comment #1 on issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Do we agree to have the sources without the trailing folder?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Nicolas,
The complexity comes for the following reason.
There is no use case that could make use of the path that includes the initial folder. However, if you would call verveinej.sh from outside the current folder, you will have troubles getting the sources in Moose. So, basically you will always have to do the cd <some-directory> first. I just tested it on Mac, and that works, but I do not know if having a ./ would work on Windows.
Anyway, having to cd first is not intuitive, because people would expect to be able to run a shell script from anywhere. Failing to comply to this would produce errors that would be too subtle for newcomers to debug.
Cheers, Doru
On 1 May 2011, at 21:23, Nicolas Anquetil wrote:
I have been busy working on the other bugs. I am still pondering it. I must admit I fail to see how "cd <some-directory> ; verveinej ." is that much complex or annoying that "verveinej <some-directory>" In all cases, you need to know where the root of your project is (if I understand correctly your argument).
I could add an option, but this does not appear yet as a pressing emergency ...
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Dimanche 1 Mai 2011 10:28:38 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Comment #1 on issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Do we agree to have the sources without the trailing folder?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Being happy is a matter of choice."
----- Mail original -----
De: "Tudor Girba" tudor.girba@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Cc: codesite-noreply@google.com Envoyé: Dimanche 1 Mai 2011 21:35:41 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Hi Nicolas,
The complexity comes for the following reason.
There is no use case that could make use of the path that includes the initial folder.
Maybe the case with appear with the possibility
However, if you would call verveinej.sh from outside the current folder, you will have troubles getting the sources in Moose. So, basically you will always have to do the cd <some-directory> first. I just tested it on Mac, and that works, but I do not know if having a ./ would work on Windows.
Anyway, having to cd first is not intuitive, because people would expect to be able to run a shell script from anywhere. Failing to comply to this would produce errors that would be too subtle for newcomers to debug.
OK, I could also change the shell script so that it does the cd itself and then calls the java program with . as parameter ... Talking about that, there is currently no windows script ...
Cheers, Doru
On 1 May 2011, at 21:23, Nicolas Anquetil wrote:
I have been busy working on the other bugs. I am still pondering it. I must admit I fail to see how "cd <some-directory> ; verveinej ." is that much complex or annoying that "verveinej <some-directory>" In all cases, you need to know where the root of your project is (if I understand correctly your argument).
I could add an option, but this does not appear yet as a pressing emergency ...
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Dimanche 1 Mai 2011 10:28:38 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Comment #1 on issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Do we agree to have the sources without the trailing folder?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Being happy is a matter of choice."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Nicolas,
On 2 May 2011, at 10:38, Nicolas Anquetil wrote:
----- Mail original -----
De: "Tudor Girba" tudor.girba@gmail.com À: "Moose-related development" moose-dev@iam.unibe.ch Cc: codesite-noreply@google.com Envoyé: Dimanche 1 Mai 2011 21:35:41 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Hi Nicolas,
The complexity comes for the following reason.
There is no use case that could make use of the path that includes the initial folder.
Maybe the case with appear with the possibility
We had several functionalities before, and there was no use for them. The current solution came out of needs, not out of lack of options.
However, if you would call verveinej.sh from outside the current folder, you will have troubles getting the sources in Moose. So, basically you will always have to do the cd <some-directory> first. I just tested it on Mac, and that works, but I do not know if having a ./ would work on Windows.
Anyway, having to cd first is not intuitive, because people would expect to be able to run a shell script from anywhere. Failing to comply to this would produce errors that would be too subtle for newcomers to debug.
OK, I could also change the shell script so that it does the cd itself and then calls the java program with . as parameter ... Talking about that, there is currently no windows script ...
I know, but it happens that an MSE is produced on one system and then used on another later on.
Cheers, Doru
Cheers, Doru
On 1 May 2011, at 21:23, Nicolas Anquetil wrote:
I have been busy working on the other bugs. I am still pondering it. I must admit I fail to see how "cd <some-directory> ; verveinej ." is that much complex or annoying that "verveinej <some-directory>" In all cases, you need to know where the root of your project is (if I understand correctly your argument).
I could add an option, but this does not appear yet as a pressing emergency ...
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Dimanche 1 Mai 2011 10:28:38 Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative paths Comment #1 on issue 603 by tudor.gi...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
Do we agree to have the sources without the trailing folder?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Being happy is a matter of choice."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."
Updates: Status: Fixed
Comment #2 on issue 603 by anquetil...@gmail.com: VerveineJ should export relative paths http://code.google.com/p/moose-technology/issues/detail?id=603
I believe this one is solved. At least in the way it is expressed here. There is still the issue of computing the "root" folder of all sources which was not settled
-
moose-technology＠googlecode.com -
Nicolas Anquetil -
Tudor Girba