24 May
2011
24 May
'11
9:31 p.m.
Because we did it for
http://www.themoosebook.org/book/externals/import-export/root-folder
kind of ....
I suggested to cyrille to spend 1 hours and add some settings.
Which ones do you want to have.
Me
- Project main folder location
- VerveineJ code location
- Import statements to be used
I do not see why I have to type
PATH_TO_verveine.extractor.java/verveine.sh -Xmx 2000m -- .
Each time I import a model I do not want to have to dive into this fucking file system to
find my way (with a soon) resizeable interface.
Stef
24 May
24 May
9:38 p.m.
Hi,
Because nobody did anything for it.
On 24 May 2011, at 21:31, Stéphane Ducasse wrote:
Because we did it for
http://www.themoosebook.org/book/externals/import-export/root-folder
kind of ....
I suggested to cyrille to spend 1 hours and add some settings.
Which ones do you want to have.
Me
- Project main folder location
In Moose you can have multiple models, so this has to be per model.
- VerveineJ code location
- Import statements to be used
I do not see why I have to type
PATH_TO_verveine.extractor.java/verveine.sh -Xmx 2000m -- .
There used to be a wizard for this, but now it does not seem to work anymore.
Each time I import a model I do not want to have to
dive into this fucking file system to find my way (with a soon) resizeable interface.
I do not understand.
Doru
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
10:53 p.m.
On May 24, 2011, at 9:38 PM, Tudor Girba wrote:
I should select where the verveineJ.sh is and then I should check the folder of the source
files and starting from / is not optimal.
Stef
Hi,
Because nobody did anything for it.
On 24 May 2011, at 21:31, Stéphane Ducasse wrote:
we could have a folder for the root of the projects, this could make sense and if
disabled
you specify all the paths by hand.
Imagine having a folder for each of your mc packages....
Because we did it for
http://www.themoosebook.org/book/externals/import-export/root-folder
kind of ....
I suggested to cyrille to spend 1 hours and add some settings.
Which ones do you want to have.
Me
- Project main folder location
In Moose you can have multiple models, so this has to be per model. - VerveineJ
code location
- Import statements to be used
I do not see why I have to type
PATH_TO_verveine.extractor.java/verveine.sh -Xmx 2000m -- .
There used to be a wizard for this, but now it does not seem to work anymore.
> Each time I import a model I do not want to have to dive into this fucking file
system to find my way (with a soon) resizeable interface.
I do not understand.
Doru
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:57 p.m.
Hi,
On 24 May 2011, at 22:53, Stéphane Ducasse wrote:
I should select where the verveineJ.sh is and then I should check the folder of the
source files and starting from / is not optimal.
Sure. But someone needs to do it :)
Doru
On May 24, 2011, at 9:38 PM, Tudor Girba wrote:
Ok, sounds good. Who is doing that?
Until then, like I told you before: the current default folder is the folder of the image
+ src/.
Hi,
Because nobody did anything for it.
On 24 May 2011, at 21:31, Stéphane Ducasse wrote:
we could have a folder for the root of the projects, this could make sense and if
disabled
you specify all the paths by hand.
Imagine having a folder for each of your mc packages.... Because we did it for
http://www.themoosebook.org/book/externals/import-export/root-folder
kind of ....
I suggested to cyrille to spend 1 hours and add some settings.
Which ones do you want to have.
Me
- Project main folder location
In Moose you can have multiple models, so this has to be per model. - VerveineJ code location
- Import statements to be used
I do not see why I have to type
PATH_TO_verveine.extractor.java/verveine.sh -Xmx 2000m -- .
There used to be a wizard for this, but now it does not seem to work anymore.
> Each time I import a model I do not want to have to dive into this fucking file
system to find my way (with a soon) resizeable interface. Stef
--
www.tudorgirba.com
"Beauty is where we see it."
I do not understand.
Doru
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
4960
days inactive
4961
days old
4 comments
2 participants
participants (2)
-
Stéphane Ducasse -
Tudor Girba