QUOTE
I tried the 800x600 resize screen wink and it worked out nicely. Since the new Wink has audio, I'll try that and see how it works out. This tutorial stuff is getting interesting. As soon as I remake the tutorial, I'll post it here. It will cover the basics of modeling a hand or foot and the problems that come up and can be solved along the way. Hope I don't make it too long.
Thats the size I was finding worked best for me.
There are some tutorials that will benefit from larger resolution screens. While I haven't tested it out entirely in those cases it might work well to resize those particular frames and then reduce them again when the detail is not longer required. I know Raf Anzovin used a magnifying glass in some of his tutorials to show the detail close to the mouse clicks.
If your tutorial allows for it you might break up the lesson into separate parts.
One way you could do it is:
Capture the entire tutorial
Save the Wink file
Open the Wink file and delete those parts you don't want in that part of the tutorial.
Save a new Wink file as Part 1 (or whatever name you need).
Do the same for each section (reopening the original Wink file each time) until you've saved out each part.
Then edit each and render out your SWF files.
Note: Save your Wink files because you can alway go back in and add new information, provide links, correct errors etc.
Once all parts of the tutorials are completed link the tutorials together:
Wink 2.0 can now link to external files/webpages. With that capability you could create a menu to acts as user interface for the various parts of a tutorial.
Another method would be to embed the links in the HTML that (most) people will click on to access the tutorial. The downside here would be that if they open the SWF file directly they've bypassed your menu.
This is powerful stuff. We just haven't investigated and shared what we've learned enough yet.
It would be nice to trade templates to leverage Wink's ability to exported to PDF, HTML, Postscript too.