PToolBox & IrPrintLib

[SyPDA]

Hi Joe!

Any thoughts about merging these two libraries? I think the IrPrintLib would be a great enhancement to the PToolboxLib.

[jstadolnik]

I've debated about doing this.

The problem in my mind is that there are 3 major competing IR print engines out there: PalmPrint, PrintBoy, and TealPrint.

I enventually envision the IRPrintLib supporting all three engines, including any others which come down the road.

Each of them has it's own interface and feature set. This leads to a lot potential feature creep. I don't have a feel for large the library will get.

I currently have only 14k of space left in the PToolboxLib. Library resources (libr0000.bin) max out at 65k in the PalmOS and they cannot be made multi-segmented. I still have quite a number of features planned (resource form support, regular expressions, string manipulation functions, datebook/alarm support, IRcomm?, database interfaces? (DB,Jfile,HandDBase,etc), hashes/dictionaries?, TCP/IP?), but it's getting down to the wire.

So in short, my answer is: "not right now, I have to see how much space I have left".

I do plan to make the IRPrintLib functions available in "customized" versions of the PToolboxLib.

Joe



Edited by - jstadolnik on 09/04/2001 09:20:44

[SyPDA]

> I do plan to make the IRPrintLib functions available in "customized" versions of the PToolboxLib.

Excellent!

That is exactly what I needed.

I hope you will be able to ship customized versions soon...

[Claw]

Joe,

I would love to see a ThinkDB interface for PocketC.

I can see why you don't want to add interfaces to PToolboxLib. Your Running out of room and you have many other ideas for more stuff.

Maybe you can combine Database & Printing interfaces to another library. PInterfaceLib or something like that.

Keep up the hard work joe !

[jstadolnik]

Unfortunately ThinkingBytes Technologies has a rather restrictive legal agreement for thier ThinkDB development kit. There's a number of nasties in the agreement, but the clincher is that the SDK is proprietary and cannot be released by a 3rd party. A PocketC native library supporting it would fall under this umbrella because someone could then develop applications which use their database technology without having to sign their SDK legal agreement. You also have to have them review any softare you create using thier technology, and your application cannot interface with any competing database formats (Handbase, DB, Jfile, Julia, mobileDB, etc).

Here is one of the more rediculous paragraphs from thier legal agreement:

1.5 Developer Applications. Upon completion of each Developer Application, Developer will deliver a copy of the Developer Application to TBT. TBT will examine the Developer Application, and if it determines that the Developer Application performs in accordance with the specifications required for use with the thinkDB Software, TBT will acknowledge its acceptance of the Developer Application and such Developer Application shall be deemed ?¢‚Ǩ?ìCertified?¢‚Ǩ

[Claw]

Holy smokes,

It reads like some lawyer barfed up his breakfast.

Oh well, I guess we don?¢‚Ǩ‚Ñ¢t even want to directly or indirectly imply about any opinion whatsoever on regarding the probable use or examine the potential use of a third party interface even if it is in accordance with its acceptance as a developer certified application on its functionality pertaining to the use during this examination period and for a period of six months after this posting.
<img src=icon_smile_angry.gif border=0 align=middle>

[Craig Park]

Wow! yeah, that is some clause. Does it even allow said developer the right to go to the bathroom on their own? (Doesn't sound like it!)

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Unfortunately ThinkingBytes Technologies has a rather restrictive legal agreement for thier ThinkDB development kit. There's a number of nasties in the agreement, but the clincher is that the SDK is proprietary and cannot be released by a 3rd party. A PocketC native library supporting it would fall under this umbrella because someone could then develop applications which use their database technology without having to sign their SDK legal agreement. You also have to have them review any softare you create using thier technology, and your application cannot interface with any competing database formats (Handbase, DB, Jfile, Julia, mobileDB, etc).

Here is one of the more rediculous paragraphs from thier legal agreement:

1.5 Developer Applications. Upon completion of each Developer Application, Developer will deliver a copy of the Developer Application to TBT. TBT will examine the Developer Application, and if it determines that the Developer Application performs in accordance with the specifications required for use with the thinkDB Software, TBT will acknowledge its acceptance of the Developer Application and such Developer Application shall be deemed ?¢‚Ǩ?ìCertified?¢‚Ǩ