>  I'm having trouble grokking TclApp and wrapping apps from the GUI. How
>  do I specify what packages to include? Is it necessary for me to use the
>  package editor application? Using the "scan" button results in
>  complaints about missing packages in TclApp, and nothing gets wrapped.
>  I'm a bit lost--all the tutorials are a bit too simple for the app I'm
>  trying to wrap.

I should prefix this with the note that the new package management panel in
the beta 1 is way overengineered, and it will be simpler in the beta-2. My
fault, I got carried away into overcomplexity-land.

The 'package editor' application is needed only if you have internal
packages you wish to wrap into your application. These packages need .tap
files which list the files which belong to the package, in essence. The
package editor helps in the creation of the .tap file (*), and TclApp will
then pick the definition up, allowing you to add the package to the wrap
project.


>  What I'm envisioning is specifying my main script in one entry field,
>  and specifying additional packages in a listbox or something, and then

Yeah, this is what the beta-2 will look like in essence. None of all the
status blinking and diddling stuff.
It is a complete rewrite in that area.

>  they get wrapped. That's more or less what I do in a script with sdx and
>  starkits.

>  Can anyone point me to some online tutorials (outside of the
>  documentation)

I do not think that such exist. At least not from AS.

>  or otherwise provide a simple set of steps to help me get
>  going? Sorry for the terminal cluelessness.

Ok, let me seee if I can describe the beta-1 ...

- You select the files of your app, file panel
- You scan for packages in the package mgmt panel (PMP).
- In the PMP you have two tables. The top table is the list of packages you
want to wrap.
  The bottom table shows which are available. If you have stuff marked as
missing in the top
  table ... Yes, it tried to find them in the bottom table, but was unable
to.
  You can remove these entries and then wrap, however your app may be
incomplete.

- An alternative to the scan is, if you know which packages you need, to
select
  them in the bottom table and then add them to the top.

  If the packages you want are not in the bottom table then tclapp did not
find them
  in the repositories it has access to (configured in the preferences).

  At that point the package editor may have to come in, if the missing
packages are yours.


(*) In the beta-2 it will have very rough abilities to deal with the new
teapot meta data and such packages too.

--
	Andreas Kupries <andreask@[...].com> 
	Developer @ http://www.ActiveState.com
	Tel: +1 778-786-1122


_______________________________________________
Tdk-beta mailing list
Tdk-beta@[...].com
http://listserv.ActiveState.com/mailman/listinfo/tdk-beta