From mmieczkowski at mac.com Tue Apr 6 14:44:56 2004 From: mmieczkowski at mac.com (Mark Mieczkowski) Date: Tue Apr 6 10:45:01 2004 Subject: [missing-sync-palmos-dev-talk] features? Message-ID: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> Any updated info on the Missing Sync CDK? 1. What are the licensing details for the missing sync for palm 6? 2. Is this subsidized by Palmsource, will mac users have to purchase "The Missing Sync"? What will be the price? 3. As a developer how do I distribute conduits which rely on it? Do I bundle the missing sync with the conduit? If I do that what is the cost to me? is it a flat fee or a price per unit? 4. is the missing sync cdk going to have any additional classes and utilities above and beyond the palmsource cdk?Are you still taking feature requests? -Mark From sgruby at markspace.com Tue Apr 6 14:08:45 2004 From: sgruby at markspace.com (Scott Gruby) Date: Tue Apr 6 13:13:11 2004 Subject: [missing-sync-palmos-dev-talk] features? In-Reply-To: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> References: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> Message-ID: <356B6D98-8806-11D8-BE66-000393A57B52@markspace.com> On Apr 6, 2004, at 10:44 AM, Mark Mieczkowski wrote: > 4. is the missing sync cdk going to have any additional classes and > utilities above and beyond the palmsource cdk?Are you still taking > feature requests? > At this time, our primary goal is to provide compatibility with the current CDK (4.0.3). We hope to provide the ability to develop Cocoa/Mach-O conduits down the line. If there are any specific classes/features you want, please post them here and we'll consider them. -- Scott Gruby Lead Engineer Mark/Space, Inc. From brian_hall at markspace.com Tue Apr 6 14:38:40 2004 From: brian_hall at markspace.com (Brian Hall) Date: Tue Apr 6 13:38:43 2004 Subject: [missing-sync-palmos-dev-talk] features? In-Reply-To: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> References: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> Message-ID: At 1:44 PM -0400 4/6/04, Mark Mieczkowski wrote: >Any updated info on the Missing Sync CDK? The most recent information posted to the public is at http://www.markspace.com/cobalt.html >1. What are the licensing details for the missing sync for palm 6? >2. Is this subsidized by Palmsource, will mac users have to purchase >"The Missing Sync"? What will be the price? I *think* you are asking pretty much the same thing in 1 and 2, if I don't cover what you are asking, let me know and I can clarify. There will be various models for Missing Sync getting to an end user. - OEM (ie, hardware vendor) could choose to bundle a full, reduced, or trial version of the product - Conduit developer could choose to do same - Customer could purchase product - direct from Mark/Space - via US distributor for resale (Navarre, Inc) - via international distributor for resale (Hamiro - France, JTT - Japan) - via one of our online resellers in the US, France, Germany, Japan, UK (www.markspace.com/distributors.html) - via one of our retail resellers (Comp USA currently, Apple Retail, Frys, etc in the timeframe of this product). (Note that this product will be available localized to French, German and Japanese, same as we currently do for our Sony and Pocket PC versions of Missing Sync). We started talking with all of the Palm OS licensees (ie, hardware vendors) last November, and continue to keep them abreast of our progress and plans. Much as it is now, we expect that some licensees will choose to include a Mac solution "in the box" (for example PalmOne does that currently) and others will not (for example, Sony,Garmin, Kyocera, etc.) Either way, a customer will still be covered because they can always purchase a copy direct from us if it has not already been provided for them. There are several current devices that right now fall between the cracks - nobody "supports" them (Kyocera 7135 for example). Our upcoming product will (in general) support *all* devices that meet the basic criteria (native USB on device, Palm OS 4, 5 or 6). >3. As a developer how do I distribute conduits which rely on it? You can continue to do as you do now. In fact, current conduits will work with our solution w/o any changes so long as they don't "break the rules". If you are concerned about this, and need to get a general idea now (vs when we start seeding outside developers) you can ask that we test your conduit against our internal builds to see if there are any issues. Your installer can also remain the same as we provide the "User Manager" API in a transparent form. So, short term, just continue to write conduits to the current CDK, and you are all set for a "classic" style experience with our upcomiing product, and remain backwards compat with the current Palm Desktop as well. If you are willing to do a recompile, you will get additional benefits, which will be explained at a later date. > Do I >bundle the missing sync with the conduit? If I do that what is the cost >to me? is it a flat fee or a price per unit? We are very flexible. You could bundle Missing Sync with your own product. You could direct your customers to purchase direct from us. We could provide you with a referral code and/or special web "landing page" at markspace.com where you earn a referral fee for sales generated by visits you generate (ie, we write you a check, instead of the other way around!) We also will soon (later this month) have the ability to sell 3rd party products at our own store, giving you great access to those with Macs and handhelds. You don't have to wait for this new Missing Sync to participate in that - as long as it compliments one of our products (and any Mac OS X conduit qualifies for that), you should talk to us. Again, this is similar to how it is now - you write a conduit, and if someone wants to use that conduit with a Sony CLIE (for example), they purchase Missing Sync and your conduit and off they go. >4. is the missing sync cdk going to have any additional classes and >utilities above and beyond the palmsource cdk? Scott (lead engineer) will take this and the other technical questions. For now, it is best to tell us what it is you'd like to see, as we may or may not be able to discuss technical details in public in advance of those details being made officially public. >Are you still taking >feature requests? Absolutely. Now is a great time to make your wishes known. You can do that via this list, or via private email. For technical issues, please contact Scott Gruby (lead engineer), for business issues, please contact myself (President/CEO) or Ken Freeman (Product Manager). Other Mark/Space engineers and support staff also monitor this list. Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 540 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030 From mmieczkowski at mac.com Thu Apr 22 17:10:21 2004 From: mmieczkowski at mac.com (Mark Mieczkowski) Date: Thu Apr 22 13:10:31 2004 Subject: [missing-sync-palmos-dev-talk] WWDC BOF anyone? Message-ID: <1509CA35-9499-11D8-90E0-000393548674@mac.com> I assume Mark/Space is going to WWDC this year. Any chance of setting up a BOF (Birds of a feather) session so that all the mac / palm / conduit folks can get the in-depth skinny? -Mark From brian_hall at markspace.com Thu Apr 22 14:49:10 2004 From: brian_hall at markspace.com (Brian Hall) Date: Thu Apr 22 13:49:14 2004 Subject: [missing-sync-palmos-dev-talk] WWDC BOF anyone? In-Reply-To: <1509CA35-9499-11D8-90E0-000393548674@mac.com> References: <1509CA35-9499-11D8-90E0-000393548674@mac.com> Message-ID: >I assume Mark/Space is going to WWDC this year. >Any chance of setting >up a BOF (Birds of a feather) session so that all the mac / palm / >conduit folks can get the in-depth skinny? We are currently in the planning stages for WWDC (San Francisco) and Machack (Michigan). We should be able to post more on WWDC by the end of this month, and info on Machack sometime next month. Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 540 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030 From sgruby at markspace.com Thu Apr 22 20:37:27 2004 From: sgruby at markspace.com (Scott Gruby) Date: Thu Apr 22 19:42:24 2004 Subject: [missing-sync-palmos-dev-talk] Re: Requests In-Reply-To: <13C18B18-94CD-11D8-8974-000393548674@mac.com> References: <13C18B18-94CD-11D8-8974-000393548674@mac.com> Message-ID: <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> [Mark, I'm replying to the list as I'm sure others are quite interested.] On Apr 22, 2004, at 7:22 PM, Mark Mieczkowski wrote: > Scott, > > my feature request list. I might as well ask for the moon but if you > don't ask.... > > 1. POSE hotsync support for debugging and testing This is a POSE issue and one we have no plans on addressing. > 2. Stationary that works. > 3. project stationary that gives more than the bare C API entry > points. how about one for the Generic conduit framework and one for a > as yet to be determined mac based framework. see item 6. I'm not sure we're going to do a stationery that has some sort of wizard for creating conduits; we don't have the resources to do this. We do plan on providing sample MachO conduits compiled in XCode. > 4. I'd like to use xCode. Codewarrior for mac looks just about dead. > The writing is on the wall. I believe that we will have this pretty early on. > 5. I don't think I need to tell you this, but I'll say it anyway, > support codewarrior, 8.3 +. There is simply no reason to set minimum > requirement to 9.x > We will support the current CDK which runs fine on CodeWarrior 8.3. > 6. A working, robust Conduit Framework. Notice that I did not say > Generic conduit framework. The CDK 4.0.3 Generic conduit framework is > quite buggy, overly complicated, and not very cleanly written. You > have to understand too much about the guts of it to work with it. I > think it is more marketing than substance. Windows has the MFC based > framework, could we have a cocoa conduit Framework Framework :)? > We do plan on having an Objective C Framework so that you can develop using Objective C. As for a replacement of the Generic conduit framework or a conduit framework, we encourage other developers to develop to our APIs. There is nothing stopping you from developing a conduit framework; unfortunately we don't have the resources to do this ourselves. (If anyone is interested in doing this, please contact me off the list and maybe we can arrange to license it.) > 7. Backward compatibility with this mac cocoa framework so it can be > used with the the Palm Hotsync Manager. I've toyed around with this > bridge idea myself so I'm pretty sure it can be done. The Mac OS will > hide the implementation details so as long as the dlls are bundles. > This would require a Shared Lib bundle from palm for the API (as > opposed to a static library) and some glue to load and manage the > entry points to this shared library. A pass through CFM conduit to > explicitly load the Mach 0 dll and provide CFM entry points. I guess > you would also need an abstraction layer to hide who is making the > connection to the palm (Missing Sync or Conduit Manager/Hotsync > Manager) > We have no plans on doing this (no incentive). Our application will handle CFM conduits as well as MachO conduits. However, the MachO conduits will not be compatible with HotSync as HotSync doesn't support it. > The only difficulty I can see with this scheme is that the PROGRESSFN > callback could be tricky and CSyncProperties::m_UserDirFSSpec will > have to be handled. I guess the pass through CFM conduit would have to > mediate those as well. Well, since I'm starting to ramble, I'll leave > my wish list at that. > > I realize that all of this isn't clear, yet, but we're still developing and one of our most important goals is compatibility with existing conduits, so that's where we're been spending our time. -- Scott Gruby Lead Engineer Mark/Space, Inc. From sgruby at markspace.com Thu Apr 22 20:55:39 2004 From: sgruby at markspace.com (Scott Gruby) Date: Thu Apr 22 20:00:35 2004 Subject: [missing-sync-palmos-dev-talk] Re: Requests In-Reply-To: <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> References: <13C18B18-94CD-11D8-8974-000393548674@mac.com> <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> Message-ID: On Apr 22, 2004, at 7:37 PM, Scott Gruby wrote: > [Mark, I'm replying to the list as I'm sure others are quite > interested.] > > On Apr 22, 2004, at 7:22 PM, Mark Mieczkowski wrote: > >> Scott, >> >> my feature request list. I might as well ask for the moon but if you >> don't ask.... >> >> 1. POSE hotsync support for debugging and testing > > This is a POSE issue and one we have no plans on addressing. > Replying to my own message; my answer was not correct. We plan on supporting Network HotSync, so you'll be able to do a Network HotSync from POSE and have it connect back to your Mac. I hope that solves the issue for testing/debugging conduits with POSE. -- Scott Gruby Lead Engineer Mark/Space, Inc. From florent.pillet at wanadoo.fr Fri Apr 23 11:42:23 2004 From: florent.pillet at wanadoo.fr (Florent Pillet) Date: Fri Apr 23 01:43:09 2004 Subject: [missing-sync-palmos-dev-talk] Re: Requests In-Reply-To: <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> References: <13C18B18-94CD-11D8-8974-000393548674@mac.com> <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> Message-ID: <2455D7BC-9502-11D8-83E8-000393A143CC@wanadoo.fr> Actually I got a Mach-O conduit working. It took some bridging (a lot actually) and wrapping into a CFM bundle, but it's absolutely feasible. I think that as long as you support the existing CFM conduits, that'll be fine with me. Florent On 23 avr. 04, at 04:37, Scott Gruby wrote: >> 7. Backward compatibility with this mac cocoa framework so it can be >> used with the the Palm Hotsync Manager. I've toyed around with this >> bridge idea myself so I'm pretty sure it can be done. The Mac OS will >> hide the implementation details so as long as the dlls are bundles. >> This would require a Shared Lib bundle from palm for the API (as >> opposed to a static library) and some glue to load and manage the >> entry points to this shared library. A pass through CFM conduit to >> explicitly load the Mach 0 dll and provide CFM entry points. I guess >> you would also need an abstraction layer to hide who is making the >> connection to the palm (Missing Sync or Conduit Manager/Hotsync >> Manager) >> > > We have no plans on doing this (no incentive). Our application will > handle CFM conduits as well as MachO conduits. However, the MachO > conduits will not be compatible with HotSync as HotSync doesn't > support it. > -- Florent Pillet, Code Segment florent.pillet@wanadoo.fr Developer tools and end-user products for Palm OS & Mac OS X ICQ: 117292463 http://perso.wanadoo.fr/fpillet From mmieczkowski at mac.com Tue Apr 6 14:44:56 2004 From: mmieczkowski at mac.com (Mark Mieczkowski) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] features? Message-ID: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> Any updated info on the Missing Sync CDK? 1. What are the licensing details for the missing sync for palm 6? 2. Is this subsidized by Palmsource, will mac users have to purchase "The Missing Sync"? What will be the price? 3. As a developer how do I distribute conduits which rely on it? Do I bundle the missing sync with the conduit? If I do that what is the cost to me? is it a flat fee or a price per unit? 4. is the missing sync cdk going to have any additional classes and utilities above and beyond the palmsource cdk?Are you still taking feature requests? -Mark From sgruby at markspace.com Tue Apr 6 14:08:45 2004 From: sgruby at markspace.com (Scott Gruby) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] features? In-Reply-To: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> References: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> Message-ID: <356B6D98-8806-11D8-BE66-000393A57B52@markspace.com> On Apr 6, 2004, at 10:44 AM, Mark Mieczkowski wrote: > 4. is the missing sync cdk going to have any additional classes and > utilities above and beyond the palmsource cdk?Are you still taking > feature requests? > At this time, our primary goal is to provide compatibility with the current CDK (4.0.3). We hope to provide the ability to develop Cocoa/Mach-O conduits down the line. If there are any specific classes/features you want, please post them here and we'll consider them. -- Scott Gruby Lead Engineer Mark/Space, Inc. From brian_hall at markspace.com Tue Apr 6 14:38:40 2004 From: brian_hall at markspace.com (Brian Hall) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] features? In-Reply-To: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> References: <1E4B7F2B-87F2-11D8-9539-000A95BAD036@mac.com> Message-ID: At 1:44 PM -0400 4/6/04, Mark Mieczkowski wrote: >Any updated info on the Missing Sync CDK? The most recent information posted to the public is at http://www.markspace.com/cobalt.html >1. What are the licensing details for the missing sync for palm 6? >2. Is this subsidized by Palmsource, will mac users have to purchase >"The Missing Sync"? What will be the price? I *think* you are asking pretty much the same thing in 1 and 2, if I don't cover what you are asking, let me know and I can clarify. There will be various models for Missing Sync getting to an end user. - OEM (ie, hardware vendor) could choose to bundle a full, reduced, or trial version of the product - Conduit developer could choose to do same - Customer could purchase product - direct from Mark/Space - via US distributor for resale (Navarre, Inc) - via international distributor for resale (Hamiro - France, JTT - Japan) - via one of our online resellers in the US, France, Germany, Japan, UK (www.markspace.com/distributors.html) - via one of our retail resellers (Comp USA currently, Apple Retail, Frys, etc in the timeframe of this product). (Note that this product will be available localized to French, German and Japanese, same as we currently do for our Sony and Pocket PC versions of Missing Sync). We started talking with all of the Palm OS licensees (ie, hardware vendors) last November, and continue to keep them abreast of our progress and plans. Much as it is now, we expect that some licensees will choose to include a Mac solution "in the box" (for example PalmOne does that currently) and others will not (for example, Sony,Garmin, Kyocera, etc.) Either way, a customer will still be covered because they can always purchase a copy direct from us if it has not already been provided for them. There are several current devices that right now fall between the cracks - nobody "supports" them (Kyocera 7135 for example). Our upcoming product will (in general) support *all* devices that meet the basic criteria (native USB on device, Palm OS 4, 5 or 6). >3. As a developer how do I distribute conduits which rely on it? You can continue to do as you do now. In fact, current conduits will work with our solution w/o any changes so long as they don't "break the rules". If you are concerned about this, and need to get a general idea now (vs when we start seeding outside developers) you can ask that we test your conduit against our internal builds to see if there are any issues. Your installer can also remain the same as we provide the "User Manager" API in a transparent form. So, short term, just continue to write conduits to the current CDK, and you are all set for a "classic" style experience with our upcomiing product, and remain backwards compat with the current Palm Desktop as well. If you are willing to do a recompile, you will get additional benefits, which will be explained at a later date. > Do I >bundle the missing sync with the conduit? If I do that what is the cost >to me? is it a flat fee or a price per unit? We are very flexible. You could bundle Missing Sync with your own product. You could direct your customers to purchase direct from us. We could provide you with a referral code and/or special web "landing page" at markspace.com where you earn a referral fee for sales generated by visits you generate (ie, we write you a check, instead of the other way around!) We also will soon (later this month) have the ability to sell 3rd party products at our own store, giving you great access to those with Macs and handhelds. You don't have to wait for this new Missing Sync to participate in that - as long as it compliments one of our products (and any Mac OS X conduit qualifies for that), you should talk to us. Again, this is similar to how it is now - you write a conduit, and if someone wants to use that conduit with a Sony CLIE (for example), they purchase Missing Sync and your conduit and off they go. >4. is the missing sync cdk going to have any additional classes and >utilities above and beyond the palmsource cdk? Scott (lead engineer) will take this and the other technical questions. For now, it is best to tell us what it is you'd like to see, as we may or may not be able to discuss technical details in public in advance of those details being made officially public. >Are you still taking >feature requests? Absolutely. Now is a great time to make your wishes known. You can do that via this list, or via private email. For technical issues, please contact Scott Gruby (lead engineer), for business issues, please contact myself (President/CEO) or Ken Freeman (Product Manager). Other Mark/Space engineers and support staff also monitor this list. Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 540 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030 From mmieczkowski at mac.com Thu Apr 22 17:10:21 2004 From: mmieczkowski at mac.com (Mark Mieczkowski) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] WWDC BOF anyone? Message-ID: <1509CA35-9499-11D8-90E0-000393548674@mac.com> I assume Mark/Space is going to WWDC this year. Any chance of setting up a BOF (Birds of a feather) session so that all the mac / palm / conduit folks can get the in-depth skinny? -Mark From brian_hall at markspace.com Thu Apr 22 14:49:10 2004 From: brian_hall at markspace.com (Brian Hall) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] WWDC BOF anyone? In-Reply-To: <1509CA35-9499-11D8-90E0-000393548674@mac.com> References: <1509CA35-9499-11D8-90E0-000393548674@mac.com> Message-ID: >I assume Mark/Space is going to WWDC this year. >Any chance of setting >up a BOF (Birds of a feather) session so that all the mac / palm / >conduit folks can get the in-depth skinny? We are currently in the planning stages for WWDC (San Francisco) and Machack (Michigan). We should be able to post more on WWDC by the end of this month, and info on Machack sometime next month. Brian -- _____________________________________________________________________ Mark/Space, Inc. voice 408-293-7299 540 N. Santa Cruz Ave. #300 fax 408-293-7298 Los Gatos, CA 95030 From sgruby at markspace.com Thu Apr 22 20:37:27 2004 From: sgruby at markspace.com (Scott Gruby) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] Re: Requests In-Reply-To: <13C18B18-94CD-11D8-8974-000393548674@mac.com> References: <13C18B18-94CD-11D8-8974-000393548674@mac.com> Message-ID: <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> [Mark, I'm replying to the list as I'm sure others are quite interested.] On Apr 22, 2004, at 7:22 PM, Mark Mieczkowski wrote: > Scott, > > my feature request list. I might as well ask for the moon but if you > don't ask.... > > 1. POSE hotsync support for debugging and testing This is a POSE issue and one we have no plans on addressing. > 2. Stationary that works. > 3. project stationary that gives more than the bare C API entry > points. how about one for the Generic conduit framework and one for a > as yet to be determined mac based framework. see item 6. I'm not sure we're going to do a stationery that has some sort of wizard for creating conduits; we don't have the resources to do this. We do plan on providing sample MachO conduits compiled in XCode. > 4. I'd like to use xCode. Codewarrior for mac looks just about dead. > The writing is on the wall. I believe that we will have this pretty early on. > 5. I don't think I need to tell you this, but I'll say it anyway, > support codewarrior, 8.3 +. There is simply no reason to set minimum > requirement to 9.x > We will support the current CDK which runs fine on CodeWarrior 8.3. > 6. A working, robust Conduit Framework. Notice that I did not say > Generic conduit framework. The CDK 4.0.3 Generic conduit framework is > quite buggy, overly complicated, and not very cleanly written. You > have to understand too much about the guts of it to work with it. I > think it is more marketing than substance. Windows has the MFC based > framework, could we have a cocoa conduit Framework Framework :)? > We do plan on having an Objective C Framework so that you can develop using Objective C. As for a replacement of the Generic conduit framework or a conduit framework, we encourage other developers to develop to our APIs. There is nothing stopping you from developing a conduit framework; unfortunately we don't have the resources to do this ourselves. (If anyone is interested in doing this, please contact me off the list and maybe we can arrange to license it.) > 7. Backward compatibility with this mac cocoa framework so it can be > used with the the Palm Hotsync Manager. I've toyed around with this > bridge idea myself so I'm pretty sure it can be done. The Mac OS will > hide the implementation details so as long as the dlls are bundles. > This would require a Shared Lib bundle from palm for the API (as > opposed to a static library) and some glue to load and manage the > entry points to this shared library. A pass through CFM conduit to > explicitly load the Mach 0 dll and provide CFM entry points. I guess > you would also need an abstraction layer to hide who is making the > connection to the palm (Missing Sync or Conduit Manager/Hotsync > Manager) > We have no plans on doing this (no incentive). Our application will handle CFM conduits as well as MachO conduits. However, the MachO conduits will not be compatible with HotSync as HotSync doesn't support it. > The only difficulty I can see with this scheme is that the PROGRESSFN > callback could be tricky and CSyncProperties::m_UserDirFSSpec will > have to be handled. I guess the pass through CFM conduit would have to > mediate those as well. Well, since I'm starting to ramble, I'll leave > my wish list at that. > > I realize that all of this isn't clear, yet, but we're still developing and one of our most important goals is compatibility with existing conduits, so that's where we're been spending our time. -- Scott Gruby Lead Engineer Mark/Space, Inc. From sgruby at markspace.com Thu Apr 22 20:55:39 2004 From: sgruby at markspace.com (Scott Gruby) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] Re: Requests In-Reply-To: <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> References: <13C18B18-94CD-11D8-8974-000393548674@mac.com> <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> Message-ID: On Apr 22, 2004, at 7:37 PM, Scott Gruby wrote: > [Mark, I'm replying to the list as I'm sure others are quite > interested.] > > On Apr 22, 2004, at 7:22 PM, Mark Mieczkowski wrote: > >> Scott, >> >> my feature request list. I might as well ask for the moon but if you >> don't ask.... >> >> 1. POSE hotsync support for debugging and testing > > This is a POSE issue and one we have no plans on addressing. > Replying to my own message; my answer was not correct. We plan on supporting Network HotSync, so you'll be able to do a Network HotSync from POSE and have it connect back to your Mac. I hope that solves the issue for testing/debugging conduits with POSE. -- Scott Gruby Lead Engineer Mark/Space, Inc. From florent.pillet at wanadoo.fr Fri Apr 23 11:42:23 2004 From: florent.pillet at wanadoo.fr (Florent Pillet) Date: Fri May 6 12:02:40 2005 Subject: [missing-sync-palmos-dev-talk] Re: Requests In-Reply-To: <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> References: <13C18B18-94CD-11D8-8974-000393548674@mac.com> <28D4F9D6-94CF-11D8-8284-000393A57B52@markspace.com> Message-ID: <2455D7BC-9502-11D8-83E8-000393A143CC@wanadoo.fr> Actually I got a Mach-O conduit working. It took some bridging (a lot actually) and wrapping into a CFM bundle, but it's absolutely feasible. I think that as long as you support the existing CFM conduits, that'll be fine with me. Florent On 23 avr. 04, at 04:37, Scott Gruby wrote: >> 7. Backward compatibility with this mac cocoa framework so it can be >> used with the the Palm Hotsync Manager. I've toyed around with this >> bridge idea myself so I'm pretty sure it can be done. The Mac OS will >> hide the implementation details so as long as the dlls are bundles. >> This would require a Shared Lib bundle from palm for the API (as >> opposed to a static library) and some glue to load and manage the >> entry points to this shared library. A pass through CFM conduit to >> explicitly load the Mach 0 dll and provide CFM entry points. I guess >> you would also need an abstraction layer to hide who is making the >> connection to the palm (Missing Sync or Conduit Manager/Hotsync >> Manager) >> > > We have no plans on doing this (no incentive). Our application will > handle CFM conduits as well as MachO conduits. However, the MachO > conduits will not be compatible with HotSync as HotSync doesn't > support it. > -- Florent Pillet, Code Segment florent.pillet@wanadoo.fr Developer tools and end-user products for Palm OS & Mac OS X ICQ: 117292463 http://perso.wanadoo.fr/fpillet