From: Jim I. <ji...@ap...> - 2001-12-12 17:53:27
|
On 12/12/01 9:22 AM, "Franc Brglez" <br...@cb...> wrote: > Jim, > > Last month you kindly instructed us how to install latest version of tk > under OSX. It turned out that our tcltk application (already crossplatform, > including under macOS9.2) is too complex for a quick fix under OSX -- it > requires augmenting the "standard mac OS9.x" distribution with packages > such as latest tcllib, tclxml, BWidget, TclSOAP, TclDOM. Some missing > features are also listed under our "widget test" below. > > Soon afterwards, I left for Europe with the Titanium, resigned to demo > under OS9.2 -- only to find out in the last moment that Titanimum would > synchronize with the projector under OSX only -- so while I could still > project PowerPoint under OSX, I could not do the same for the tcltk > application. > > We are trying to figure out what chances we have for a "quick" > cross-plaform tcltk port to OSX. We have a number of concerns: > > (1) the structure of current tcltk-installed directory has no resemblance > to 9.2 and earlier generation. Even the nominal "widget test" directory > appears to be missing. The 9.2 structure makes the "nominal mac > distribution" easier to augment with missing parts from a standard linux > distribution. How are we to proceed with augmenting the "standard OSX > distribution". The widget test is still there. For instance, just start up the Wish Shell.app, and do: source [file join $tk_library demos widget] What used to be in the Tool Command Language folder on Classic MacOS is now in the Resources/Scripts folder in each of the frameworks. > > (2) can we hope for a quick fix to the current version of wish-OSX, so that > the entire widget directory works as in the earlier versions .... I have > results from my tests below -- it appears that fixing the "stdout" channel > problem would fix a number of related problems ..... this is my entire > problem list: > > labels #8 > no images are displayed > This is probably just because you aren't setting up the paths for the widget demo correctly. If you use the one that is part of the Tk framework, as shown above, I bet this will work fine. > menus #2 (menu buttons) > bgerror failed to handle background error. > Original error: can not find channel named "stdout" > Error in bgerror: invalid command name "sting" > > misc #2, #3 (both grab commands) > bgerror failed to handle background error. > Original error: can not find channel named "stdout" > Error in bgerror: invalid command name "sting" > This was a bug that is fixed in the current sources in the macosx-8-4-branch version of Tk. It is pretty easy to build this, there are instructions in the announcement I sent with the first binary. > Any comments and suggestions on these experiences would be most appreciated. > For other packages, you have two problems, building the ones that need building, and getting Tcl to find them... Building the Tcl only ones that you mentioned is not too hard, it is easier if you build Tcl, and then point the new packages at the tclConfig.sh in the framework. Most of the extension configury prefers the build version of Tcl to the installed, and will find all the things they need. On getting Tcl to find them. I need to work out how I want to seed the tcl_pkgPath, and the auto_path, for Tcl on MacOS X. I was struggling just to get it to find the Framework versions of packages at first. This works now, and so the next step is to seed the pkg path both with the typical Unix'y places to find stuff, and somewhere in ~/Library, /Library, and /System/Library. For now, you can just seed it yourself with wherever you are putting stuff. One thing that would work for a stand-alone app is to put tcllib, etc in the Resources/Scripts folder of your App package. This gets added to the auto_path by default, so packages here should get found automatically... Hope this helps, Jim > MANY THANKS -- Franc Brglez > > _______________________________________________ > Tcl-mac mailing list > Tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac > -- ++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++= Jim Ingham ji...@ap... Developer Tools - gdb |