Guillaume Evrard

i was thinking about how to have clean searchpaths for my abstractions.

i currently have one folder containing all my abstractions and 3rd party

it would be great if max handles "projects", which could have a specific

a bit like eclipse or netbeans does with java projects.

then you could be sure about the place where max is going to reach for your

abstractions... and building apps would be easier i think. (even if it's not

i was thinking about how to have clean searchpaths for my abstractions.
i currently have one folder containing all my abstractions and 3rd party
objects/abstractions (in subfolders).
this is not very handy i think.
it would be great if max handles "projects", which could have a specific
directory for its own libs/abstractions.
a bit like eclipse or netbeans does with java projects.
then you could be sure about the place where max is going to reach for your
abstractions... and building apps would be easier i think. (even if it's not
so hard)

handling-projects-libs

Honestly I would love this. Or some version of it. You define a project file or folder, and whenever you add an abstraction or an external, it gets copied to the project folder. I'd still prefer to keep my externals all in the cycling 74 folder (so that I can use them easily in multiple projects) but this would add a great deal to portability - just copy your project folder to another computer and add it's own 'externals' folder to the search path on that computer. Or have the project file know to search for that folder automagically.

Building apps could be done simply, as the project folder would already contain all the things necessary, no need to search through your C74 folder for all the externals you used, just include the folders in your project.

Honestly I would love this.  Or some version of it.  You define a project file or folder, and whenever you add an abstraction or an external, it gets copied to the project folder.  I'd still prefer to keep my externals all in the cycling 74 folder (so that I can use them easily in multiple projects) but this would add a great deal to portability - just copy your project folder to another computer and add it's own 'externals' folder to the search path on that computer.  Or have the project file know to search for that folder automagically.

Building apps could be done simply, as the project folder would already contain all the things necessary, no need to search through your C74 folder for all the externals you used, just include the folders in your project.


in my opinion, projects specific filepaths could be a great feature...

more than filepaths... meta-filepaths :)
in my opinion, projects specific filepaths could be a great feature...

throw a filepath object in your root patch. make changes to it with loadbang, and revert those changes with closebang.

project specific filepaths. or am i missing something?

throw a filepath object in your root patch.  make changes to it with loadbang, and revert those changes with closebang.

project specific filepaths.  or am i missing something?


On Dec 13, 2008, at 12:31 PM, Robert Ramirez wrote:

> project specific filepaths. or am i missing something?

I haven't tried it in Max 5, but in Max 4, subdirectories weren't 

searched in path that were added in this way.

On Dec 13, 2008, at 12:31 PM, Robert Ramirez wrote:
> project specific filepaths.  or am i missing something?

I haven't tried it in Max 5, but in Max 4, subdirectories weren't  
searched in path that were added in this way.

Chris Muir
cbm@well.com	
http://www.xfade.com

Handling "projects" & libs