thanks cybero thats what i was thinking. one could make there own sort custom picker or just hard code some filters or something into an app i suppose. i mean its easy enough to make a package installer that could place comps into the system repository for use, but i'm trying to keep my projects app store friendly if possible and i think writing to the system folder is against the rules.
however being able to utilize the picker in a custom repository i think would greatly improve the object. just a thought i was coming across while messing with a custom app last night.
i am also wondering what cool changes there are in lion. i took the xcode 4 plunge last night. i'm getting to like it. at first some of my older apps where gripping about things, but once you get the subtle difference down, it seems like it might improve the work flow.
i have been looking at that lion seed for a few weeks now, i'm thinking this weekend i will put it on a machine and or make a partition.
well, having read through all the above, I think I've pretty much totally misunderstood what you were asking after and pretty much why you were asking about setting your picker view to load up compositions from your bundled repository instead of from the systems repository, dust.
I guess what you were working at was creating a lot of the program logic in Cocoa to load the .qtz 's ?
@cybero no you didn't miss understand. i want to use the custom picker to load up my own repo, which does seem to not be possible. i was just rambling on about how i could make my own picker or hard code the comps or something, sorry for the confusion.
@gt. now thats actually another solution i didn't really think about, making a picker inside qc with a directory scanner for comps. i suppose its worth a try to hit /Applications/myAppe.app/Contents/Resources/ with the directory scanner ?
If you use relative path, the directory scanner keeps working regardless of location of your app, and gives you whatever other options are built into it. Vade's suggestion of hardcoding is a simple one as well, if you know what the file names will be ahead of time. Hardcoding will likely perform the best.
@gt yeah passing the string of the path from the app is probably best in the off chance someone doesn't use the applications folder. got to think about an interesting way to make picker in qc. as of now i'm leaning towards just leaning towards having a drop down menu instead a thumbnail preview of the effect, that way i can still use the parameters view to show the different parameters for each effect etc...
You can make the path short and relative to the resource(or other) folder in your app, and the scanner still works. You don't have to reference the Applications folder.
So, it would be something like ~/Resources I think...If the folder was named Resources, depending on the location of your executable. I maybe wrong on the exact syntax of that, I mix it up sometimes. It works wherever you move your app.
SAFIK :-)
Short answer, no.
Reason why, that's how & where the program is coded to pick up such items.
Perhaps with 10.7 ?
Just downloading the delta seed.
Perhaps if we could compile our own version of QC - hardly likely to happen though is it ?
thanks cybero thats what i was thinking. one could make there own sort custom picker or just hard code some filters or something into an app i suppose. i mean its easy enough to make a package installer that could place comps into the system repository for use, but i'm trying to keep my projects app store friendly if possible and i think writing to the system folder is against the rules.
however being able to utilize the picker in a custom repository i think would greatly improve the object. just a thought i was coming across while messing with a custom app last night.
i am also wondering what cool changes there are in lion. i took the xcode 4 plunge last night. i'm getting to like it. at first some of my older apps where gripping about things, but once you get the subtle difference down, it seems like it might improve the work flow.
i have been looking at that lion seed for a few weeks now, i'm thinking this weekend i will put it on a machine and or make a partition.
Directory scanner?
well, having read through all the above, I think I've pretty much totally misunderstood what you were asking after and pretty much why you were asking about setting your picker view to load up compositions from your bundled repository instead of from the systems repository, dust.
I guess what you were working at was creating a lot of the program logic in Cocoa to load the .qtz 's ?
@cybero no you didn't miss understand. i want to use the custom picker to load up my own repo, which does seem to not be possible. i was just rambling on about how i could make my own picker or hard code the comps or something, sorry for the confusion.
@gt. now thats actually another solution i didn't really think about, making a picker inside qc with a directory scanner for comps. i suppose its worth a try to hit /Applications/myAppe.app/Contents/Resources/ with the directory scanner ?
Use Cocoa to pass the string from your applications main bundle, so it works regardless of location of the app.
Hard coding. Its not 1990 :)
actually, I did misunderstand :-)
clearer now.
If you use relative path, the directory scanner keeps working regardless of location of your app, and gives you whatever other options are built into it. Vade's suggestion of hardcoding is a simple one as well, if you know what the file names will be ahead of time. Hardcoding will likely perform the best.
@gt yeah passing the string of the path from the app is probably best in the off chance someone doesn't use the applications folder. got to think about an interesting way to make picker in qc. as of now i'm leaning towards just leaning towards having a drop down menu instead a thumbnail preview of the effect, that way i can still use the parameters view to show the different parameters for each effect etc...
You can make the path short and relative to the resource(or other) folder in your app, and the scanner still works. You don't have to reference the Applications folder.
So, it would be something like ~/Resources I think...If the folder was named Resources, depending on the location of your executable. I maybe wrong on the exact syntax of that, I mix it up sometimes. It works wherever you move your app.