From parker at azimuthinc.com Mon Feb 14 08:33:02 2005 From: parker at azimuthinc.com (James Parker) Date: Mon Feb 14 06:53:08 2005 Subject: [missing-sync-palmos-dev-talk] Missing headers Message-ID: I can't get the Cocoa sample conduit to compile in Xcode. It can't find MissingSyncConduit.h and SyncManagerObjectiveC.h. As far as I can tell those files weren't with the sample conduit source. How do I obtain these files? Am I missing something simple? Thanks. From sgruby at markspace.com Mon Feb 14 07:36:54 2005 From: sgruby at markspace.com (Scott Gruby) Date: Mon Feb 14 07:37:23 2005 Subject: [missing-sync-palmos-dev-talk] Missing headers In-Reply-To: References: Message-ID: <237c3ab91eb7394965fea1a9ce6aecc8@markspace.com> On Feb 14, 2005, at 5:33 AM, James Parker wrote: > > I can't get the Cocoa sample conduit to compile in Xcode. It can't > find > MissingSyncConduit.h and SyncManagerObjectiveC.h. > > As far as I can tell those files weren't with the sample conduit > source. > How do I obtain these files? Am I missing something simple? > > These are located in the MissingSync.framework which is installed in /Library/Frameworks when you install Missing Sync. -- Scott Gruby Lead Engineer, Missing Sync for Palm OS Mark/Space, Inc. Please contact support@markspace.com for assistance with Mark/Space products. From parker at azimuthinc.com Mon Feb 14 15:15:17 2005 From: parker at azimuthinc.com (James Parker) Date: Mon Feb 14 12:16:12 2005 Subject: [missing-sync-palmos-dev-talk] Missing headers In-Reply-To: <237c3ab91eb7394965fea1a9ce6aecc8@markspace.com> Message-ID: On 2/14/05 10:36 AM, "Scott Gruby" wrote: >> >> I can't get the Cocoa sample conduit to compile in Xcode. It can't >> find >> MissingSyncConduit.h and SyncManagerObjectiveC.h. >> >> As far as I can tell those files weren't with the sample conduit >> source. >> How do I obtain these files? Am I missing something simple? >> >> > > These are located in the MissingSync.framework which is installed in > /Library/Frameworks when you install Missing Sync. Thanks. Knew it was something simple, ;-) Works much better now. From lists at mostrom.pp.se Fri Feb 18 06:18:12 2005 From: lists at mostrom.pp.se (Jan Erik =?iso-8859-1?Q?Mostr=F6m?=) Date: Thu Feb 17 21:18:15 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice Message-ID: Hi I would like to learn how to write conduits but I'm a bit unsure how do to it. I've downloaded the conduit info from MarkSpace but it looks like I need more info ... but what info, that's the question. I'm only interested in using this conduit under OS X but I have no experience from Objecive-C. As a newbie in this area I would appriciate a few pointers. jem -- Jan Erik Mostr?m www.mostrom.pp.se From brian_hall at markspace.com Fri Feb 18 00:42:16 2005 From: brian_hall at markspace.com (Brian Hall) Date: Thu Feb 17 21:44:17 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: References: Message-ID: At 6:18 AM +0100 2/18/05, Jan Erik Mostr?m wrote: >I would like to learn how to write conduits but I'm a bit unsure how do to >it. I've downloaded the conduit info from MarkSpace but it looks like I need >more info ... but what info, that's the question. I'd recommend you download and/or follow every link in the "Missing Sync for Palm OS v4" section of http://www.markspace.com/developers.html In addition to all of the resources we provide, you'll want to also get all teh resources that PalmSource, in particular the CDK (Conduit Development Kit). Our own resources are a *superset* to this kit. >I'm only interested in using this conduit under OS X but I have no experience >from Objecive-C. You'll want to check out the self-help resources that Apple provides for X-Code and Objective-C in that case. We have some sample code that shows how to do a conduit in that environment. >As a newbie in this area I would appriciate a few pointers. If you attend WWDC or Machack, and are still looking for help, we usually have engineers at attendance at both of those conferences. If you can share what sort of conduit you are working on, would be nice to hear. If you can't, that is fine too. Just curious! Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 654 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030-4360 From lists at mostrom.pp.se Fri Feb 18 07:01:46 2005 From: lists at mostrom.pp.se (Jan Erik =?iso-8859-1?Q?Mostr=F6m?=) Date: Thu Feb 17 22:01:48 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: Message-ID: On 2005-02-18 06:42, Brian Hall wrote: Thanks for the info, I'll look into it > If you can share what sort of conduit you are working on, would be nice to > hear. If you can't, that is fine too. Just curious! :-) I've actually been planning to write some conduits for several years now but have always waited "until I get some free time". Well, I never seem to get any free time so I might as well go ahead and learn it anyway. What caused me to look into this right now was that started to look at the Mark/Space memopad file, I thought that if could write my own memo program that was able to read/write directly to memopad file I wouldn't have to write a conduit ... well I opened the file in an hexeditor and it looked liked serialized objects (I'm not sure since I don't know Objective-C, is it even possible to serialize data in Objective-C?). So then I downloaded the conduit SDK to see if I could find some clues there ... but since I'm Objective-C illitrerate (yes, I should learn it) I started to think: I might as well write my own conduit based on the examples. So: at first a Memo conduit just to see if I can learn how to do it (and since the example seems to have everything I should be able to do that ;-). Then I have two commercial apps from two other companies that I would like to see both a Mac desktop and Mac conduit for. I could write the desktop right now but it wouldn't be useful without the conduit ... so I'll see how much time it takes to understand how to make a simple conduit (time is the critical sector for me). ke, -- Jan Erik Mostr?m www.mostrom.pp.se From brian_hall at markspace.com Fri Feb 18 01:12:47 2005 From: brian_hall at markspace.com (Brian Hall) Date: Thu Feb 17 22:13:19 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: References: Message-ID: >On 2005-02-18 06:42, Brian Hall wrote: > >Thanks for the info, I'll look into it > >> If you can share what sort of conduit you are working on, would be nice to >> hear. If you can't, that is fine too. Just curious! > >:-) I've actually been planning to write some conduits for several years now >but have always waited "until I get some free time". Well, I never seem to >get any free time so I might as well go ahead and learn it anyway. It is a good skill to have. There aren't nearly enough skilled Mac OS conduit developers, and we get asked from time to time to recommend consultants. Additionally we have need for conduit developers ourselves here at Mark/Space. >So: at first a Memo conduit just to see if I can learn how to do it (and >since the example seems to have everything I should be able to do that ;-). >Then I have two commercial apps from two other companies that I would like to >see both a Mac desktop and Mac conduit for. I could write the desktop right >now but it wouldn't be useful without the conduit ... so I'll see how much >time it takes to understand how to make a simple conduit (time is the >critical sector for me). If it helps any, we are more than happy to talk with the "other companies" to help convince them that is a good idea. We can provide various forms of co-marketing, cross-marketing, distribution, technical and other assistance to developers to help make the choice easier. Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 654 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030-4360 From eshapiro at markspace.com Fri Feb 18 09:24:43 2005 From: eshapiro at markspace.com (Eric Shapiro) Date: Fri Feb 18 06:24:59 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: References: Message-ID: On Feb 18, 2005, at 12:18 AM, Jan Erik Mostr?m wrote: > I'm only interested in using this conduit under OS X but I have no > experience > from Objecive-C. Note that you can develop conduits in C/C++/Carbon too. There's no specific need for Objective-C, although many people find it easier than C++, especially if your conduit is going to have dialogs, windows, and settings. -Eric Shapiro ----------------------------------------------- Eric Shapiro eshapiro at markspace.com ----------------------------------------------- From lists at mostrom.pp.se Fri Feb 18 17:18:13 2005 From: lists at mostrom.pp.se (Jan Erik =?iso-8859-1?Q?Mostr=F6m?=) Date: Fri Feb 18 08:18:16 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: Message-ID: On 2005-02-18 15:24, Eric Shapiro wrote: > > I'm only interested in using this conduit under OS X but I have no > > experience > > from Objecive-C. > > Note that you can develop conduits in C/C++/Carbon too. There's no > specific need for Objective-C, although many people find it easier than > C++, especially if your conduit is going to have dialogs, windows, and > settings. Yep, that's one thing I'm looking at. I know C/C++ and too many (?) other languages so my I'm currently considering if I should learn Cocoa/Objective-C and do both the conduit and the application using them (as a learning experience). Well, I've printed Palms documentation for making conduits so I'm going to browse them during the weekend and then I'll probably have to make some decision. jem -- Jan Erik Mostr?m www.mostrom.pp.se From dustindoan at gmail.com Mon Feb 21 11:15:52 2005 From: dustindoan at gmail.com (Dustin Doan) Date: Mon Feb 21 08:15:57 2005 Subject: [missing-sync-palmos-dev-talk] Problems with Carbon compilation Message-ID: When I build the sample carbon conduit everything seems to go fine, but the resulting SampleMachOConduit.plugin is recognized by the OS as a folder, not a Missing Sync Document. I thought this problem might have something to do with incorrect type and creator, but so far I've had no luck. Any help would be greatly appreciated, Thanks, Dustin From sgruby at markspace.com Mon Feb 21 08:27:14 2005 From: sgruby at markspace.com (Scott Gruby) Date: Mon Feb 21 08:27:42 2005 Subject: [missing-sync-palmos-dev-talk] Problems with Carbon compilation In-Reply-To: References: Message-ID: On Feb 21, 2005, at 8:15 AM, Dustin Doan wrote: > When I build the sample carbon conduit everything seems to go fine, > but the resulting SampleMachOConduit.plugin is recognized by the OS as > a folder, not a Missing Sync Document. I thought this problem might > have something to do with incorrect type and creator, but so far I've > had no luck. Any help would be greatly appreciated, Thanks, > You might try moving it to another location as sometimes the Finder doesn't quite know what is going on. By using the .plugin (or .bundle) extension, the Finder should identify it as a bundle and not a folder. Here's the Info.plist from the Mark/Space MemoPad Conduit. Important pieces are the package type and bundle signature. What does yours look like? The info below is much newer than the sample conduit. CFBundleDevelopmentRegion English CFBundleExecutable MarkSpaceMemoPadConduit CFBundleGetInfoString MemoPad Conduit version 1.0, Copyright ? 2004-2005 Mark/Space, Inc. CFBundleIconFile CFBundleIdentifier com.markspace.missingsync.memopadconduit CFBundleInfoDictionaryVersion 6.0 CFBundlePackageType BNDL CFBundleSignature MSyc CFBundleVersion 1.0 NSHumanReadableCopyright Copyright ? 2004-2005 Mark/Space, Inc. NSPrincipalClass MemoPadConduit -- Scott Gruby Lead Engineer, Missing Sync for Palm OS Mark/Space, Inc. Please contact support@markspace.com for assistance with Mark/Space products. From dustindoan at gmail.com Mon Feb 21 13:22:32 2005 From: dustindoan at gmail.com (Dustin Doan) Date: Mon Feb 21 10:22:42 2005 Subject: [missing-sync-palmos-dev-talk] Problems with Carbon compilation In-Reply-To: References: Message-ID: Hi Scott, Thanks for getting back to me so quickly. I looked at my Info.plist, it was nearly identical to the one you sent, including the entries for package type and signature. I tried renaming the file to a .bundle file and all of a sudden the OS recognized it as a file which i could then import into the missing sync conduit list. What confuses me at this point is why my compiled .plugin file is thought of as a folder while the current MarkSpaceMemoPad conduit, which also has a .plugin extension, is not. Also, when I get info on the SampleMachOConduit.bundle file it's entry in the "Kind:" field reads "Bundle" and it's icon is empty, while the entry for any other conduit in my list reads "SampleMachOConduit.bundle Document" and has a Missing Sync icon. The only exception to this is the MarkSpaceMemoPadConduit.plugin file which reads "Missing Sync for Palm OS document", the entry i would expect. What am i missing here? Dustin On Mon, 21 Feb 2005 08:27:14 -0800, Scott Gruby wrote: > > On Feb 21, 2005, at 8:15 AM, Dustin Doan wrote: > > > When I build the sample carbon conduit everything seems to go fine, > > but the resulting SampleMachOConduit.plugin is recognized by the OS as > > a folder, not a Missing Sync Document. I thought this problem might > > have something to do with incorrect type and creator, but so far I've > > had no luck. Any help would be greatly appreciated, Thanks, > > > > You might try moving it to another location as sometimes the Finder > doesn't quite know what is going on. By using the .plugin (or .bundle) > extension, the Finder should identify it as a bundle and not a folder. > Here's the Info.plist from the Mark/Space MemoPad Conduit. Important > pieces are the package type and bundle signature. What does yours look > like? The info below is much newer than the sample conduit. > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> > > > CFBundleDevelopmentRegion > English > CFBundleExecutable > MarkSpaceMemoPadConduit > CFBundleGetInfoString > MemoPad Conduit version 1.0, Copyright ? 2004-2005 Mark/Space, > Inc. > CFBundleIconFile > > CFBundleIdentifier > com.markspace.missingsync.memopadconduit > CFBundleInfoDictionaryVersion > 6.0 > CFBundlePackageType > BNDL > CFBundleSignature > MSyc > CFBundleVersion > 1.0 > NSHumanReadableCopyright > Copyright ? 2004-2005 Mark/Space, Inc. > NSPrincipalClass > MemoPadConduit > > > > -- > Scott Gruby > Lead Engineer, Missing Sync for Palm OS > Mark/Space, Inc. > > > Please contact support@markspace.com for assistance with Mark/Space > products. > > _______________________________________________ > missing-sync-palmos-dev-talk mailing list > missing-sync-palmos-dev-talk@lists.markspace.com > http://lists.markspace.com/mailman/listinfo/missing-sync-palmos-dev-talk > From parker at azimuthinc.com Mon Feb 14 08:33:02 2005 From: parker at azimuthinc.com (James Parker) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Missing headers Message-ID: I can't get the Cocoa sample conduit to compile in Xcode. It can't find MissingSyncConduit.h and SyncManagerObjectiveC.h. As far as I can tell those files weren't with the sample conduit source. How do I obtain these files? Am I missing something simple? Thanks. From sgruby at markspace.com Mon Feb 14 07:36:54 2005 From: sgruby at markspace.com (Scott Gruby) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Missing headers In-Reply-To: References: Message-ID: <237c3ab91eb7394965fea1a9ce6aecc8@markspace.com> On Feb 14, 2005, at 5:33 AM, James Parker wrote: > > I can't get the Cocoa sample conduit to compile in Xcode. It can't > find > MissingSyncConduit.h and SyncManagerObjectiveC.h. > > As far as I can tell those files weren't with the sample conduit > source. > How do I obtain these files? Am I missing something simple? > > These are located in the MissingSync.framework which is installed in /Library/Frameworks when you install Missing Sync. -- Scott Gruby Lead Engineer, Missing Sync for Palm OS Mark/Space, Inc. Please contact support@markspace.com for assistance with Mark/Space products. From parker at azimuthinc.com Mon Feb 14 15:15:17 2005 From: parker at azimuthinc.com (James Parker) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Missing headers In-Reply-To: <237c3ab91eb7394965fea1a9ce6aecc8@markspace.com> Message-ID: On 2/14/05 10:36 AM, "Scott Gruby" wrote: >> >> I can't get the Cocoa sample conduit to compile in Xcode. It can't >> find >> MissingSyncConduit.h and SyncManagerObjectiveC.h. >> >> As far as I can tell those files weren't with the sample conduit >> source. >> How do I obtain these files? Am I missing something simple? >> >> > > These are located in the MissingSync.framework which is installed in > /Library/Frameworks when you install Missing Sync. Thanks. Knew it was something simple, ;-) Works much better now. From lists at mostrom.pp.se Fri Feb 18 06:18:12 2005 From: lists at mostrom.pp.se (Jan Erik =?iso-8859-1?Q?Mostr=F6m?=) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice Message-ID: Hi I would like to learn how to write conduits but I'm a bit unsure how do to it. I've downloaded the conduit info from MarkSpace but it looks like I need more info ... but what info, that's the question. I'm only interested in using this conduit under OS X but I have no experience from Objecive-C. As a newbie in this area I would appriciate a few pointers. jem -- Jan Erik Mostr?m www.mostrom.pp.se From brian_hall at markspace.com Fri Feb 18 00:42:16 2005 From: brian_hall at markspace.com (Brian Hall) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: References: Message-ID: At 6:18 AM +0100 2/18/05, Jan Erik Mostr?m wrote: >I would like to learn how to write conduits but I'm a bit unsure how do to >it. I've downloaded the conduit info from MarkSpace but it looks like I need >more info ... but what info, that's the question. I'd recommend you download and/or follow every link in the "Missing Sync for Palm OS v4" section of http://www.markspace.com/developers.html In addition to all of the resources we provide, you'll want to also get all teh resources that PalmSource, in particular the CDK (Conduit Development Kit). Our own resources are a *superset* to this kit. >I'm only interested in using this conduit under OS X but I have no experience >from Objecive-C. You'll want to check out the self-help resources that Apple provides for X-Code and Objective-C in that case. We have some sample code that shows how to do a conduit in that environment. >As a newbie in this area I would appriciate a few pointers. If you attend WWDC or Machack, and are still looking for help, we usually have engineers at attendance at both of those conferences. If you can share what sort of conduit you are working on, would be nice to hear. If you can't, that is fine too. Just curious! Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 654 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030-4360 From lists at mostrom.pp.se Fri Feb 18 07:01:46 2005 From: lists at mostrom.pp.se (Jan Erik =?iso-8859-1?Q?Mostr=F6m?=) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: Message-ID: On 2005-02-18 06:42, Brian Hall wrote: Thanks for the info, I'll look into it > If you can share what sort of conduit you are working on, would be nice to > hear. If you can't, that is fine too. Just curious! :-) I've actually been planning to write some conduits for several years now but have always waited "until I get some free time". Well, I never seem to get any free time so I might as well go ahead and learn it anyway. What caused me to look into this right now was that started to look at the Mark/Space memopad file, I thought that if could write my own memo program that was able to read/write directly to memopad file I wouldn't have to write a conduit ... well I opened the file in an hexeditor and it looked liked serialized objects (I'm not sure since I don't know Objective-C, is it even possible to serialize data in Objective-C?). So then I downloaded the conduit SDK to see if I could find some clues there ... but since I'm Objective-C illitrerate (yes, I should learn it) I started to think: I might as well write my own conduit based on the examples. So: at first a Memo conduit just to see if I can learn how to do it (and since the example seems to have everything I should be able to do that ;-). Then I have two commercial apps from two other companies that I would like to see both a Mac desktop and Mac conduit for. I could write the desktop right now but it wouldn't be useful without the conduit ... so I'll see how much time it takes to understand how to make a simple conduit (time is the critical sector for me). ke, -- Jan Erik Mostr?m www.mostrom.pp.se From brian_hall at markspace.com Fri Feb 18 01:12:47 2005 From: brian_hall at markspace.com (Brian Hall) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: References: Message-ID: >On 2005-02-18 06:42, Brian Hall wrote: > >Thanks for the info, I'll look into it > >> If you can share what sort of conduit you are working on, would be nice to >> hear. If you can't, that is fine too. Just curious! > >:-) I've actually been planning to write some conduits for several years now >but have always waited "until I get some free time". Well, I never seem to >get any free time so I might as well go ahead and learn it anyway. It is a good skill to have. There aren't nearly enough skilled Mac OS conduit developers, and we get asked from time to time to recommend consultants. Additionally we have need for conduit developers ourselves here at Mark/Space. >So: at first a Memo conduit just to see if I can learn how to do it (and >since the example seems to have everything I should be able to do that ;-). >Then I have two commercial apps from two other companies that I would like to >see both a Mac desktop and Mac conduit for. I could write the desktop right >now but it wouldn't be useful without the conduit ... so I'll see how much >time it takes to understand how to make a simple conduit (time is the >critical sector for me). If it helps any, we are more than happy to talk with the "other companies" to help convince them that is a good idea. We can provide various forms of co-marketing, cross-marketing, distribution, technical and other assistance to developers to help make the choice easier. Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 654 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030-4360 From eshapiroatmarkspace.com Fri Feb 18 09:24:43 2005 From: eshapiroatmarkspace.com (Eric Shapiro) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: References: Message-ID: On Feb 18, 2005, at 12:18 AM, Jan Erik Mostr?m wrote: > I'm only interested in using this conduit under OS X but I have no > experience > from Objecive-C. Note that you can develop conduits in C/C++/Carbon too. There's no specific need for Objective-C, although many people find it easier than C++, especially if your conduit is going to have dialogs, windows, and settings. -Eric Shapiro ----------------------------------------------- Eric Shapiro eshapiro at markspace.com ----------------------------------------------- From lists at mostrom.pp.se Fri Feb 18 17:18:13 2005 From: lists at mostrom.pp.se (Jan Erik =?iso-8859-1?Q?Mostr=F6m?=) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Looking for advice In-Reply-To: Message-ID: On 2005-02-18 15:24, Eric Shapiro wrote: > > I'm only interested in using this conduit under OS X but I have no > > experience > > from Objecive-C. > > Note that you can develop conduits in C/C++/Carbon too. There's no > specific need for Objective-C, although many people find it easier than > C++, especially if your conduit is going to have dialogs, windows, and > settings. Yep, that's one thing I'm looking at. I know C/C++ and too many (?) other languages so my I'm currently considering if I should learn Cocoa/Objective-C and do both the conduit and the application using them (as a learning experience). Well, I've printed Palms documentation for making conduits so I'm going to browse them during the weekend and then I'll probably have to make some decision. jem -- Jan Erik Mostr?m www.mostrom.pp.se From dustindoan at gmail.com Mon Feb 21 11:15:52 2005 From: dustindoan at gmail.com (Dustin Doan) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Problems with Carbon compilation Message-ID: When I build the sample carbon conduit everything seems to go fine, but the resulting SampleMachOConduit.plugin is recognized by the OS as a folder, not a Missing Sync Document. I thought this problem might have something to do with incorrect type and creator, but so far I've had no luck. Any help would be greatly appreciated, Thanks, Dustin From sgruby at markspace.com Mon Feb 21 08:27:14 2005 From: sgruby at markspace.com (Scott Gruby) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Problems with Carbon compilation In-Reply-To: References: Message-ID: On Feb 21, 2005, at 8:15 AM, Dustin Doan wrote: > When I build the sample carbon conduit everything seems to go fine, > but the resulting SampleMachOConduit.plugin is recognized by the OS as > a folder, not a Missing Sync Document. I thought this problem might > have something to do with incorrect type and creator, but so far I've > had no luck. Any help would be greatly appreciated, Thanks, > You might try moving it to another location as sometimes the Finder doesn't quite know what is going on. By using the .plugin (or .bundle) extension, the Finder should identify it as a bundle and not a folder. Here's the Info.plist from the Mark/Space MemoPad Conduit. Important pieces are the package type and bundle signature. What does yours look like? The info below is much newer than the sample conduit. CFBundleDevelopmentRegion English CFBundleExecutable MarkSpaceMemoPadConduit CFBundleGetInfoString MemoPad Conduit version 1.0, Copyright ? 2004-2005 Mark/Space, Inc. CFBundleIconFile CFBundleIdentifier com.markspace.missingsync.memopadconduit CFBundleInfoDictionaryVersion 6.0 CFBundlePackageType BNDL CFBundleSignature MSyc CFBundleVersion 1.0 NSHumanReadableCopyright Copyright ? 2004-2005 Mark/Space, Inc. NSPrincipalClass MemoPadConduit -- Scott Gruby Lead Engineer, Missing Sync for Palm OS Mark/Space, Inc. Please contact support@markspace.com for assistance with Mark/Space products. From dustindoan at gmail.com Mon Feb 21 13:22:32 2005 From: dustindoan at gmail.com (Dustin Doan) Date: Fri May 6 12:02:41 2005 Subject: [missing-sync-palmos-dev-talk] Problems with Carbon compilation In-Reply-To: References: Message-ID: Hi Scott, Thanks for getting back to me so quickly. I looked at my Info.plist, it was nearly identical to the one you sent, including the entries for package type and signature. I tried renaming the file to a .bundle file and all of a sudden the OS recognized it as a file which i could then import into the missing sync conduit list. What confuses me at this point is why my compiled .plugin file is thought of as a folder while the current MarkSpaceMemoPad conduit, which also has a .plugin extension, is not. Also, when I get info on the SampleMachOConduit.bundle file it's entry in the "Kind:" field reads "Bundle" and it's icon is empty, while the entry for any other conduit in my list reads "SampleMachOConduit.bundle Document" and has a Missing Sync icon. The only exception to this is the MarkSpaceMemoPadConduit.plugin file which reads "Missing Sync for Palm OS document", the entry i would expect. What am i missing here? Dustin On Mon, 21 Feb 2005 08:27:14 -0800, Scott Gruby wrote: > > On Feb 21, 2005, at 8:15 AM, Dustin Doan wrote: > > > When I build the sample carbon conduit everything seems to go fine, > > but the resulting SampleMachOConduit.plugin is recognized by the OS as > > a folder, not a Missing Sync Document. I thought this problem might > > have something to do with incorrect type and creator, but so far I've > > had no luck. Any help would be greatly appreciated, Thanks, > > > > You might try moving it to another location as sometimes the Finder > doesn't quite know what is going on. By using the .plugin (or .bundle) > extension, the Finder should identify it as a bundle and not a folder. > Here's the Info.plist from the Mark/Space MemoPad Conduit. Important > pieces are the package type and bundle signature. What does yours look > like? The info below is much newer than the sample conduit. > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> > > > CFBundleDevelopmentRegion > English > CFBundleExecutable > MarkSpaceMemoPadConduit > CFBundleGetInfoString > MemoPad Conduit version 1.0, Copyright ? 2004-2005 Mark/Space, > Inc. > CFBundleIconFile > > CFBundleIdentifier > com.markspace.missingsync.memopadconduit > CFBundleInfoDictionaryVersion > 6.0 > CFBundlePackageType > BNDL > CFBundleSignature > MSyc > CFBundleVersion > 1.0 > NSHumanReadableCopyright > Copyright ? 2004-2005 Mark/Space, Inc. > NSPrincipalClass > MemoPadConduit > > > > -- > Scott Gruby > Lead Engineer, Missing Sync for Palm OS > Mark/Space, Inc. > > > Please contact support@markspace.com for assistance with Mark/Space > products. > > _______________________________________________ > missing-sync-palmos-dev-talk mailing list > missing-sync-palmos-dev-talk@lists.markspace.com > http://lists.markspace.com/mailman/listinfo/missing-sync-palmos-dev-talk >