Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

2.0 User Guide http://www.debugmode.com Wink™ © 2003-06 Satish Kumar. S. All ri

2.0 User Guide http://www.debugmode.com Wink™ © 2003-06 Satish Kumar. S. All rights reserved. User Guide © 2003-06 Bent Møller Madsen, Linda Worthington & Satish Kumar. S Wink™ 2.0 User Guide Copyright © 2003-06 Bent Møller Madsen, Linda Worthington & Satish Kumar. S. All rights reserved. The information in this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by the author. The author assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. The software described in this document is furnished under license and may only be used or copied in accordance with the terms of such license. Macromedia® and Macromedia® Flash® are trademarks of Macromedia, Inc. and may be registered in certain jurisdictions. Adobe® and Adobe® Reader® are trademarks of Adobe Systems Incorporated that may be registered in certain jurisdictions. Microsoft® and Microsoft® Windows® are trademarks of Microsoft Corporation that may be registered in certain jurisdictions. All other products or name brands are trademarks of their respective holders and are acknowledged. Table of Contents 1 Introduction 4 1.1 About Wink™ 4 1.2 Requirements 4 1.3 Installation 4 1.4 New features in version 2.0 5 1.5 Differences between Windows and Linux versions 5 1.6 Using this guide 5 2 Basics 6 2.1 How to use Wink 6 2.2 Your first Wink project step-by-step 7 3 User Interface 10 3.1 Basic UI 10 3.2 New Project Wizard and capturing screenshots 10 3.2.1 Step 1 - Setting up the project 10 3.2.2 Step 2 - Capturing screenshots 12 3.3 Project Settings 13 3.4 Palette 15 3.5 Editing frames in a project 16 3.5.1 Frame Titles 16 3.5.2 Stay in this frame for time 16 3.5.3 Add Audio 17 3.5.4 Add Image 17 3.5.5 Add Preset Shape 18 3.5.6 Shapes Editor 18 3.5.7 Add Textbox 18 3.5.8 Callout Editor 19 3.5.9 Cursor 22 3.5.10 Next/Previous Buttons 23 3.5.11 Goto Frame Button 23 3.5.12 Background Image/Colour 24 3.5.13 Shift All Elements 25 3.5.14 Crop All Frames 25 3.5.15 Resize All Frames 25 3.5.16 Insert and delete frames 25 3.5.17 Editing the sequence of frames 26 3.5.18 Thumbnails Only View 26 3.6 Rendering the flash presentation 26 3.7 Templates 27 3.8 Export/import text to and from file 27 3.9 Export to HTML, PDF, PostScript and image files 28 3.10 Preferences 28 3.10.1 Flash Preloader 29 3.10.2 Flash Control bar 30 3.11 Shortcut keys 31 3.12 Toolbar 32 4 Tips and Tweaks 33 4.1 Screen size of presentations 33 4.2 Optimal use of input-driven capture 33 4.3 Edit multiple frames 34 4.4 Editing screenshots in frames 34 4.5 How to create more than one textbox in a frame 34 4.6 Copy frames between projects 34 4.7 Optimize the size of presentations 34 4.8 Maximize the space for showing presentations in a browser 34 4.9 Saving compressed projects 35 4.10 URLs of interest 35 5 Known issues 36 5.1 Buttons in PDF files exported from Wink 36 5.2 Flash output sometimes looks garbled with palette 36 4 1 1.1 About Wink™ Wink is a software tool to make presentations and tutorials about using software programs. A Wink presentation will resemble a live walkthrough about how to use the software. Also the author of the presentation can add comments and explanations to parts of the presentation to better explain the concepts and usage to the end user. There are many purposes for these kinds of presentations: • Advertising of software. • Tutorials of software for classes. • Documentation of software to supplement written documentation. • Answer questions about the use of programs visually. The basic output format of Wink is Flash. Flash is viewed in a web browser using the free Macromedia Flash Player which is already installed on most computers or can easily be installed the first the time the end user tries to watch a flash file. Wink is actively in development and constantly improving. If you have a comment or suggestion to make or an idea to improve, please make it public by posting in the User Forums at " http://www.debugmode.com/userforums/". 1.2 Requirements When working inside Wink the minimum screen resolution to be used should be 800*600 although it is recommended to use a screen resolution of 1024*768 or better. This will make it easier to edit a presentation with a large area size because you will be able to see full or at least a large part of the current frame. The minimum and recommended screen resolution doesn't apply when you are capturing screenshots for a Wink presentation. Screenshots could very well be captured with a screen resolution of 640*480 depending on the needs. 1.3 Installation The installation package comes as a zip file with the install file. Unzip this file into any temporary folder and run the executable to start the installation. If you have an earlier version of Wink installed, this installation may overwrite the settings of the earlier install (similar to an upgrade). 1 I IN NT TR RO OD DU UC CT TI IO ON N 5 1.4 New features in version 2.0 Wink has been completely rewritten for version 2.0. Currently version 2.0 is available only for Windows; a Linux version will be available soon. The following is a list of the most important new features in Wink 2.0 among many improvements, changes and bug fixes. • Translated to more languages • Undo/Redo • Unlimited textboxes • Unlimited buttons • URL Buttons to open a webpage when clicked • Image objects • Shape objects, create and use shapes just like callouts with no text • Audio (can record while capturing, as well as add/edit later) • Improved and simpler properties panel • Improved flow of control in output swf file so no more flickering of title/callouts when no buttons are used • Ability to disable frames in a project so they won’t appear in output 1.5 Differences between Windows and Linux versions Most of the Wink user interface and features are the same in Windows and Linux, but there are a few differences. The key ones are listed below. • No input-driven capture mode in Linux • Text fonts in Windows and Linux will be different depending on what is available in the system • UI widgets will be different in both platforms so there will be minor differences in the functionalities • Wink system tray icon in Linux will be available only if the window manager supports the required extension Please note that the UI is very different between the latest Windows version (2.0) and the Linux version (1.5). The above points still apply to the Linux Wink version 1.5. 1.6 Using this guide This user guide is distributed as a PDF document so that it can be printed as a manual if necessary. It is recommended that you read this document completely before starting to use Wink so that you can work with ease. Also a printout of the shortcut keys will be helpful. Two tutorial projects are present in this distribution. Once installed, run Wink and choose menu "Help > View tutorial 1". Answer Yes to render the tutorial. You will see the tutorial right after the rendering is done. The sample projects are named "tutorial1.wnk" and "tutorial2.wnk". These files are present in the Wink\Samples folder. There is also a step-by-step tutorial later in this document. 6 2 2.1 How to use Wink To create a new presentation in Wink you run your target software and take screenshots with Wink (automatically and/or manually) of each action done in that software. These screenshots will afterwards be put together by Wink into a continuous movie in which each screenshot represents a frame. Frames can be moved, deleted and copied inside the project and between projects. The mouse cursor’s position is saved separately for each frame. This way Wink will take care of making the cursor move smoothly between frames. You can also change the position of the mouse cursor in any frame. There are several advantages to record presentations using screenshots and not recording the entire presentation as a single movie: • It is easier to capture screenshots because if you make mistakes (open the wrong file, do the wrong action, forget what to do and thereby making a long pause etc.) in the recording progress you just don't take screenshots of these errors. If you were recording a continuous file you would have to be very prepared in advance to avoid these kinds of recording mistakes. • When editing the file afterwards there are fewer frames to work with and most frames are important - that is to say that there are only few or none intermediate frames that for instance just show the mouse cursor moving from one place to another. • The resulting flash file will also be smaller because there are fewer frames in the presentation. But in some cases it can be useful and easier to just record everything that happens e.g. when drawing or uploads/Litterature/ wink-user-guide.pdf