On Fri, Jun 20, 2008 at 12:11 PM, Hans-Christoph Steiner <[EMAIL PROTECTED]> wrote: > > On Jun 20, 2008, at 2:34 PM, Luke Iannini wrote: > >> On Fri, Jun 20, 2008 at 5:15 AM, Hans-Christoph Steiner >> <[EMAIL PROTECTED]> wrote: >>> >>> On Jun 20, 2008, at 1:55 PM, Luke Iannini wrote: >>> >>>> On Fri, Jun 20, 2008 at 4:02 AM, Hans-Christoph Steiner >>>> <[EMAIL PROTECTED]> wrote: >>>>> >>>>> Does this work at all on 10.4/Tiger? >>>>> >>>> Yes, it's configured by default to work with both 10.4 and 10.5. >>> >>> Any idea whether it would cause problems on 10.3? That's not a make- >>> or-break thing, but it would be nice if it could still work on 10.3. >>> As for including the Info.plist changes in v0-40, it would need to be >>> throughly tested before including it. Currently, there are only a >>> couple outstanding bugs that need to be fixed for this release >>> (AFAIK), so I am really hesitant to include something totally new. >>> >> According to this http://developer.apple.com/qa/qa2005/qa1406.html the >> public.plain-text UTI we're using existed in 10.3. Also, this seems >> to be a transitional document for 10.3>10.4, and doesn't include any >> callouts except: "Note: UTIs are available in Mac OS X v10.3 Panther >> and later. Mac OS X v10.4 Tiger added many new types and integrated >> support throughout the operating system." >> >> So I think it won't be a problem for the keys in the plist, and in the >> future, 10.3 should just ignore the >> Library/Spotlight/PureData.mdimporter file just as it would ignore any >> other file it didn't recognize in the bundle. > > > Ok, sounds like it is worth trying to add the Info.plist UTI stuff to > this release. Feel free to add it now to branches/pd-extended/v0-40, > but please test it. > > .hc > Yo, sorry I didn't read that closely and thought you were comfortable with adding the whole kit n' kaboodle, sorry about that.
> >>>>> >>>>> As for building it, how do you build it yourself? That's usually a >>>>> good starting point for adding it to the auto-build. If it is an >>>>> xcode project, you can use the command line tool xcodebuild. >>>>> >>>> Yo, >>>> I just built in with the build button : ). I like buttons... >>>> So yea, I have the project. Looks like it builds aok with >>>> xcodebuild, >>>> thanks for the tip. Where should I put the project folder? >>> >>> Good question. The first place I thought of is packages/darwin_app >>> since it is only for things related to the Pd.app for Mac OS X. >>> Maybe: >>> >>> packages/darwin_app/spotlight_importer >>> >>> Then it probalby makes sense to make a separate 'spotlight_importer:' >>> target in packages/darwin_app/Makefile to build and install it. >>> >>> .hc >> >> Will do. >> Cheers >> Luke > > > > ------------------------------------------------------------------------ > ---- > > All information should be free. - the hacker ethic > > > > > > _______________________________________________ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list