What ?  You expect me to take a look at what we put up on the web for download ?
I tried downloading it last night (after I read your email) but  after 10 mins I
got fed up and stopped the download - its just that I am at home on a 56K modem
:=)

 What can I say about using the IntlGlue.lib...for the time being, I guess, its
okay. But only for the time being!  You will be shot if you are found using it
afterwards... :-)
PalmOSGlue.lib is something that will be released (very) soon...its the
repackaged version of IntlGlue.lib.

Okay now to the tricky  'Right? ' or 'Wrong? ' part :
One of the differences that will be coming in with PalmOSGlue.lib is that the
fucntions have the word 'Glue' in them.
By using 'Glue' in the name we hope to make it clear that this is a compatabilty
fucntion call   -  e.g. the glue version of Txt* is now TxtGlue*
TxtGlue provides compatibility for applications that wish to make calls to Text
Manager, but which might actually be running on devices with roms that do not
have this
support available, in which case the glue code executes the standard (Latin
only) routines instead.


--vivek








Scott Johnson <[EMAIL PROTECTED]> on 09/08/99 09:02:58 AM

Please respond to [EMAIL PROTECTED]

Sent by:  Scott Johnson <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:    (Vivek Magotra/HQ/3Com)
Subject:  Re: IntlGlue.h missing from SDK 3.1?




[EMAIL PROTECTED] wrote:
> I am not sure what's in the zip bundle that you downloaded...

Which is <http://www.palm.com/devzone/tools/sdk31a1.zip>...

> but you may want to take a look and see if PalmOSGlue.lib exists.

Negative.  The only file with "glue" in the name is this one:

    Palm OS 3.1 Support\Libraries\IntlGlue\IntlGlue.lib

> And along with that you need to use the glue headers : TxtGlue.h,
> FntGlue.h,WinGlue.h.

Negative, none of those files exist in this alpha 3.1 SDK.

> Let me know if you have problems.

Well, these are problems.  :-)

Back to my original question: is it safe for me to proceed to use the
IntlGlue.lib that does come with the SDK (since whipping up a header for
it isn't hard) -or- has it been changed greatly for next SDK release
that you have apparently not released yet?  Those file names you mention
suggest some amount of rearranging at minimum, but hopefully not any
major functional or naming changes.  Right?  Wrong?

-slj-






Reply via email to