Simple Time Saver for those about to build.

May 20, 2011 at 3:26pm

Simple Time Saver for those about to build.

I just realized that if I build a max application, and put all my patches and my eclipse project in a “source” folder, then I can directly edit the application without having to rebuild in max until it’s perfect.

#57228
May 20, 2011 at 8:35pm

i don’t know what any of that means, but that you ended with max and perfect CONGRATULATIONS!! =)

#204969
May 21, 2011 at 11:16am

I don’t know what it means either – edit the application how, exactly?

Eclipse is not very good at tracking file changes made outside Eclipse itself. While it can sometimes make sense to keep Max patcher files in an Eclipse project (to get coherent source control, for example), you end up hitting F5 rather a lot.

#204970
May 21, 2011 at 12:06pm

i think he means that you make an application with all the abstractions,
picture files, and stuff kept as single files on disk. (just like you would
do with java, drivers, or audio files.)

of course this works, but it somehow makes building an app senseless,
you could as well just leave the main patcher a patch as well and open it
with the runtime or maxmsp.

-110
 

#204971
May 21, 2011 at 12:38pm

Sorry to be so ambiguous.

Typically I waste a lot of time rebuilding standalones. I have to drag things into them for 10 minutes before it starts working. My maxinterface.json needs to get dragged in. My abstractions need to get dragged in, I have to export a new eclipse project as a .jar file. I have to go down the list and see what 3rd party objects I need. And then, after all of that, something is screwed up and I have to start all over again.

Instead, what I’ve been doing is editing all this stuff inside a source folder inside my application package including my entire eclipse project. Then, when it’s working perfectly, I’m rebuilding once.

I’m not claiming this will save your life or anything. But I find it helpful.

#204972
May 21, 2011 at 2:01pm

When I rebuild standalones, I generally build a new .app and replace the .mxf and MacOS folder of the previous version with the new ones. So I don’t need to copy all the “support” files into the package all the time.

p

#204973
May 21, 2011 at 2:06pm

This might be even quicker! The difference, it sounds like, is that my main patcher rarely gets changed so I can keep and edit everything inside package without rebuilding.

#204974
May 21, 2011 at 2:49pm

hm. when i builds apps or plug-in, i have one folder with all the project files and
my abstractions are in /externals anyway.

so i include these 2 folders when i build and everything required is there.

and if xou really spread stuff across multiple places, why not just include the
whole search path? or the whole max folder?

#204975
May 21, 2011 at 3:30pm

what is eclipse?

#204976
May 21, 2011 at 3:35pm

Java IDE. That’s a whole different level of “how to arrange files”

#204977
May 21, 2011 at 6:19pm

Ah. I think I see.

My approach is usually to bash together some Ant scripts to deploy Java into the Max world.

Ant is, also, a whole different level of “how to arrange files.” Don’t get me started on Maven.

#204978

You must be logged in to reply to this topic.