> Actually Vadim, for img::jpeg I ended up modifying tkkit.dll. > I included > the teapot path solution for the sake of completeness. Agree that > activating packages that are already in tkkit.dll is the > elegant solution.
yes. > However, what about a case where a package is not in the > current tkkit.dll > but in the teapot packages ? How would one go about adding > one such package Here is where I am not agreed. IMHO if you're using teapot you'll better use entire ActiveTCL. Teapot contains too much small files, config entries and even windows-registry entries - which is what I seriously dislike. When I tried to move teapot-enabled TCL to another directory - all broke - it is not moveable. I am not going to criticize teapot - it just works for many people - it just do not suffice me. BUT! Once you included teapot - you already paid the price - so just use entire ActiveTCL distro - at least you'll get many features! > to tkkit.dll ? Don't think packaging the whole tcl tk is a > solution for > most people as you said yourself. (that time I only said that ordinary user will not rebuild tcl, tk, blt, tix as I did - using MSVC compiler) Just my opinion. BR, Vadim.
