mmcdtools-discuss

[Mmcdtools-discuss] MMCd Tools update

[Shawn P. <spo...@ex...>]

Hi all,

I'm putting together some code for a minor update to MMCd Tools.  So far
I've only made minor internal updates to Palm Conduit code and how the
DLLs work together.  i.e. Upgraded to from CDK 4.03 to 6.01.  Using COM
instead of standard DLL, fixes some unsightly confusion in the code as
to where the MMCdHelp.dll is located.  COM allows me to make function
calls while knowing only the ClassID.  If you cared to know. :)

So while I'm at it, I'm up for some additional ideas as to what I could
incorporate this time around.

I've done some brainstorming.  So far I'd really like to replace the
Excel export code with pure C code and not use the OLE automation
object, which is slower than molassas.  There's a Perl module
Spreadsheet::WriteExcel does such in pure perl, so I plan to learn from
it.  However, I'd like to incorporate this feature in the next major
version.

So. any thoughts?

---
Shawn Poulson
spo...@ex...

Re: [Mmcdtools-discuss] MMCd Tools update

[Clinton B. <cba...@la...>]

MMCd Tools updateEnhanced Excel export performance would be great. When the
logger project gets back on the front burner, I will need to update the code
to support a new log format with variable number of sensors, 8/16 bit data,
and scaling info embedded in the header. (Not really a candidate for a minor
release.)


Clint

  ----- Original Message -----
  From: Shawn Poulson
  To: mmc...@li...
  Sent: Sunday, October 03, 2004 1:11 AM
  Subject: [Mmcdtools-discuss] MMCd Tools update


  Hi all,

  I'm putting together some code for a minor update to MMCd Tools.  So far
I've only made minor internal updates to Palm Conduit code and how the DLLs
work together.  i.e. Upgraded to from CDK 4.03 to 6.01.  Using COM instead
of standard DLL, fixes some unsightly confusion in the code as to where the
MMCdHelp.dll is located.  COM allows me to make function calls while knowing
only the ClassID.  If you cared to know. :)

  So while I'm at it, I'm up for some additional ideas as to what I could
incorporate this time around.

  I've done some brainstorming.  So far I'd really like to replace the Excel
export code with pure C code and not use the OLE automation object, which is
slower than molassas.  There's a Perl module Spreadsheet::WriteExcel does
such in pure perl, so I plan to learn from it.  However, I'd like to
incorporate this feature in the next major version.

  So. any thoughts?

  ---
  Shawn Poulson
  spo...@ex...