From brian_hall at markspace.com Fri Jul 8 11:20:02 2005 From: brian_hall at markspace.com (Brian Hall) Date: Fri Jul 8 11:21:36 2005 Subject: [missing-sync-palmos-dev-talk] [PR] Mark/Space Announces Handheld Dev Sessions at ADHOC Message-ID: FOR IMMEDIATE RELEASE MARK/SPACE SOFTWARE ENGINEERS TO HOST HANDHELD DEVELOPER SESSIONS AT ADHOC Mac Developer Takes On Mentor Role in Handheld Connectivity Arena LOS GATOS, Calif.--July 8, 2005--Mark/Space, Inc. today announced upcoming developer sessions at the Advanced Developer Hands On Conference (ADHOC), also known as MacHack, later this month. Led by senior software engineers, these sessions will give Mac developers all the information and assistance they need to create conduits and plugins that allow their applications to communicate with Palm OS and Windows Mobile handhelds and smartphones. "We've come to a critical point in the development of handheld applications that integrate with Mac OS X," stated Brian Hall, Mark/Space president and CEO. "Now that Apple has articulated their future hardware plans, individuals and companies that build handheld applications need to know what is new, what has changed and how to go about planning their strategy for the Mac/Intel platform. Our engineers are going to be covering all of this and more at ADHOC later this month." The ADHOC conference takes place July 27-31 at the Holiday Inn Fairlane, in Dearborn, Michigan. Mark/Space engineers will present the following sessions. Writing Palm Conduits This session will cover the details of writing Palm OS conduits for Mac OS X. Topics will include HotSync Manager vs. The Missing Sync, Carbon vs. Cocoa, Xcode vs. CodeWarrior and PowerPC vs. Intel. Mark/Space will announce and describe an innovative method of writing universal plugins that will function properly today under HotSync Manager on PowerPCs, and under The Missing Sync for Palm OS on Intel-based Macs in the future. One attendee will be chosen at random to receive a new Palm OS device. Session speaker: Eric Shapiro. Writing Windows Mobile Plugins Never before has it been possible for Mac developers to write a plugin that allows communication between Mac OS X software and Windows Mobile Pocket PC and Smartphone devices. The forthcoming Missing Sync for Windows Mobile will provide this very capability. This session will describe how to write Missing Sync plugins that synchronize application data with a Windows Mobile device. Details will include cross-platform code sharing, Xcode build steps, and Intel-based Mac support. One attendee will be chosen at random to receive a new Pocket PC. Session speakers: Dave Koziol and Eric Shapiro. Missing Sync Kitchen Programmers interested in writing Palm OS conduits or Windows Mobile plugins for Mac OS X can attend this session to get hands-on instruction from Mark/Space senior engineers Dave Koziol and Eric Shapiro. Developers attending this session are encouraged to bring their laptop to receive help writing and debugging their code. For additional information about ADHOC, including registration details and session schedules, please visit www.adhocconference.com. ABOUT THE MISSING SYNC FOR PALM OS The Missing Sync for Palm OS provides Mac OS X users with an unparalleled synchronization manager for Palm Powered handhelds and smartphones. In addition to supporting existing Mac conduits and synchronization methods, The Missing Sync adds Wi-Fi sync, intuitive conduit management, Internet access over USB and Bluetooth, desktop mounting of memory cards and other features never before available to Mac users. Seamless integration with iPhoto and iTunes gives users mobile access to their digital media. Developers can leverage The Missing Sync for Palm OS's framework to create new Palm/Mac conduits using modern tools like Apple's Xcode and count on future support for Intel-powered Macs and Palm OS Cobalt. ABOUT THE MISSING SYNC FOR WINDOWS MOBILE Shipping in July, 2005, The Missing Sync for Windows Mobile connects Windows Mobile Pocket PC and Smartphone devices to a Mac, providing data synchronization with Mac OS X's Address Book and iCal applications, Microsoft Entourage and Mac-based personal information managers that support Apple's Sync Services. The Missing Sync for Windows Mobile also provides Desktop mounting of Windows Mobile devices' internal and card storage, Internet access via USB and Bluetooth, music and photo transfer capabilities and backup and restore of critical information on the device. Developers can use The Missing Sync for Windows Mobile's software development kit to create plugins that connect desktop applications with programs running on Pocket PC and smartphone devices. ABOUT MARK/SPACE, INC. Founded in 1990, Mark/Space, Inc., www.markspace.com, develops and markets mobile and wireless software, including the award-winning Missing Sync products that connect a Mac OS computer to handheld devices from Danger, Dell, Garmin, HP, palmOne, Samsung, Sony and others. # # # Mark/Space and The Missing Sync are trademarks of Mark/Space, Inc. All other product and brand names may be trademarks or registered trademarks of their respective owners. Mark/Space Contact: Eric Ullman Director of Sales and Marketing eullman@markspace.com +1 408.399.5300 x104 _______________________________________________ markspace-pr mailing list markspace-pr@lists.markspace.com http://lists.markspace.com/mailman/listinfo/markspace-pr -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 654 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030-4360 From dan at dogmelon.com.au Wed Jul 20 01:22:26 2005 From: dan at dogmelon.com.au (Dan Fletcher) Date: Wed Jul 20 01:23:17 2005 Subject: [missing-sync-palmos-dev-talk] Minimum required changes to the example conduit Message-ID: <2005720162226.611126@balants-champ> I have a conduit which works fine on my machine, and seems to work fine on some of our customers machines. To develop this conduit I started with the example conduit, and modified it. But, some users are reporting a clash with the MemoPad conduit. When the Memopad conduit is installed, our conduit doesn't show up in the Conduit dialog. If the Markspace memopad conduit is disabled though, then our conduit shows up! What are the minimum changes you need to make to the example MemoPad conduit to stop it clashing with the real MemoPad conduit? I'm not talking about the actual syncing logic here, just any init calls, the Info.plist file, etc. Dan From sgruby at markspace.com Wed Jul 20 07:13:45 2005 From: sgruby at markspace.com (Scott Gruby) Date: Wed Jul 20 07:13:51 2005 Subject: [missing-sync-palmos-dev-talk] Minimum required changes to the example conduit In-Reply-To: <2005720162226.611126@balants-champ> References: <2005720162226.611126@balants-champ> Message-ID: <16A45C74-7684-41C7-9877-302E6BE65B73@markspace.com> On Jul 20, 2005, at 1:22 AM, Dan Fletcher wrote: > I have a conduit which works fine on my machine, and seems to work > fine on > some of our customers machines. To develop this conduit I started > with the > example conduit, and modified it. > > But, some users are reporting a clash with the MemoPad conduit. > When the > Memopad conduit is installed, our conduit doesn't show up in the > Conduit > dialog. If the Markspace memopad conduit is disabled though, then our > conduit shows up! > > What are the minimum changes you need to make to the example MemoPad > conduit to stop it clashing with the real MemoPad conduit? I'm not > talking > about the actual syncing logic here, just any init calls, the > Info.plist > file, etc. 1) First off, if you can, get your customers to use Missing Sync for Palm OS 4.0.6 b3 (the final one is coming in a few weeks) as some changes were made to the handling of MachO conduits (I don't think this applies to you as the change was for MachO conduits that weren't Cocoa). 2) You MUST rename the class and all classes in the conduit. This is a limitation of Cocoa's handling of dynamically loaded objects. Yes, it isn't ideal, but rename everything otherwise the wrong code will be executed. Cocoa doesn't handle namespace collisions well. 3) In ConduitInfo.plist, change CreatorID and Conduit Name 4) In Info.plist, change CFBundleExecutable to be your executable name. 5) In Info.plist, change NSPrincipalClass to be whatever you renamed the class to be. If you still have problems after making these changes, please send me the conduit directly and we can work from there. We will have some updated sample code (not much has changed in the Cocoa sample) along with some whitepapers about conduit development and the transition to Intel next week in time for ADHOC. I'm personally very excited to see a Cocoa conduit developed, so if there is anything we can do to help you promote your conduit, please don't hesitate to contact me. Thanks. -- Scott Gruby Lead Engineer Mark/Space, Inc. Please visit for assistance with Mark/Space products. From dan at dogmelon.com.au Thu Jul 21 05:11:43 2005 From: dan at dogmelon.com.au (Dan Fletcher) Date: Thu Jul 21 05:12:30 2005 Subject: [missing-sync-palmos-dev-talk] Minimum required changes to the example conduit In-Reply-To: <16A45C74-7684-41C7-9877-302E6BE65B73@markspace.com> Message-ID: <2005721201143.938429@balants-champ> > 2) You MUST rename the class and all classes in the conduit. This > is a limitation of Cocoa's handling of dynamically loaded objects. > Yes, it isn't ideal, but rename everything otherwise the wrong code > will be executed. Cocoa doesn't handle namespace collisions well. This was the one causing the problem. It all looks good now... Thanks