Well, nobody else has answered this, so I'll take a stab at it.

I believe Palm(One/Source) could very easily accomplish a wrapper
library which wouldn't require code changes everywhere. A simple
implementation would be to add a function to the glue libraries which
would initialize the logical database system, taking as arguments the
number of logical records per physical record and the size per logical
record. The only thing a developer would need to do is call this glue
function once per database requiring logical operations, and the rest
of the Dm family of functions could stay the same.

Of course, I'm assuming that the logical records would be the same
size for the above implementation, but that would likely cover the
majority of developer cases already. Working under such an assumption,
I can't see something like this taking much time to implement and
provide the necessary glue library to developers.

If for some reason it's not practical to modify the original Dm family
of functions easily, a total wrapper around the DataMgr shouldn't be
too difficult. The biggest challenge would likely be the typing
element rather than any complexity in actually developing it.

Adrien.

Tuesday, May 3, 2005, 4:00:15 PM, you wrote:

CT> From: "Adrien Regimbald" <[EMAIL PROTECTED]>
>> Unfortunately, there is no way around this for now. Perhaps PalmOne
>> will issue a patch, but we don't have any news that one is coming as
>> of yet. The minimum record size on the T5 is actually 512 bytes, which
CT> (snip)
>> physicalIndex = logicalIndex / logicalRecordsPerPhysical;
>> physicalOffset = logicalRecordSize * (logicalIndex %
>> logicalRecordsPerPhysical);
>> 
>> Of course, it would be a good idea to put this functionality in a
>> wrapper class of some sort, so that you have a new "logical family" of
>> database functions to perform all of your physical <-> logical
>> translation for you.

CT> Which is exactly what Palm(One or Source) could do and release 
CT> open-source if they were serious about helping developers
CT> overcome this problem.  For many apps I suspect that a simple
CT> wrapper for the Dm functions would do the job, although I haven't
CT> investigated.

CT> Has anyone that's taken this step got an opinion on whether it 
CT> can be implemented as a wrapper lib without code changes?

CT> Chris Tutty




-- 
For information on using the Palm Developer Forums, or to unsubscribe, please 
see http://www.palmos.com/dev/support/forums/

Reply via email to