Jean-Claude Wippler wrote in
>- dqkit is like tclkit, but with more extensions built in, such as BLT
>- starkits are script/data/extension hybrids
>- BLT cannot be used as starkit because it does not support stubs
Aha. This explains why dqkit was able to read my starkit (that included
ref's to BLT procs) only if the original VFS files were in place. (Though
it was not really reading the starkit - instead it sought out and found the
VFS files.) So dqkit has BLT, but requires presence of the tcl scripts at
runtime if BLT is included.
I have an application that relies fairly heavily on BLT and I wish to
distribute this without the tcl script code.
Am I simply out of options? (I tried freewrap but got "tk dll" error
messages from windows xp. I haven't given up on that route, but am at a
loss as what to try next. I've already put in about 10 hours on freewrap
and about half that on sdx/starpack just trying different combinations being
teased the whole way that success was just around the again next corner!)
Is it overly complicated to convert the BLT C source code so that it is
stub enabled? Would this allow BLT to work in a starkit? I've not found
alternatives to BLT's graphing capabilities.