Thread: [Ktutorial-commits] SF.net SVN: ktutorial:[76] trunk/web-src
Status: Alpha
Brought to you by:
danxuliu
Menu
▾
▴
ktutorial-commits
|
From: <dan...@us...> - 2010-02-06 22:54:49
|
Revision: 76
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=76&view=rev
Author: danxuliu
Date: 2010-02-06 22:54:43 +0000 (Sat, 06 Feb 2010)
Log Message:
-----------
Release 0.2 new and download information
Modified Paths:
--------------
trunk/web-src/newsList.xml
trunk/web-src/pages/download.xml
trunk/web-src/pages/index.xml
trunk/web-src/pages/news.xml
Modified: trunk/web-src/newsList.xml
===================================================================
--- trunk/web-src/newsList.xml 2010-02-06 18:03:24 UTC (rev 75)
+++ trunk/web-src/newsList.xml 2010-02-06 22:54:43 UTC (rev 76)
@@ -12,4 +12,16 @@
<date>2010-01-30</date>
</fullDate>
</new>
+
+ <new>
+ <title>KTutorial 0.2 released!</title>
+ <summary>
+ <div xmlns="http://www.w3.org/1999/xhtml">
+ <p>Check <a href="download.html" title="Download page in KTutorial web">download page</a> for further information.</p>
+ </div>
+ </summary>
+ <fullDate>
+ <date>2010-02-06</date>
+ </fullDate>
+ </new>
</news>
\ No newline at end of file
Modified: trunk/web-src/pages/download.xml
===================================================================
--- trunk/web-src/pages/download.xml 2010-02-06 18:03:24 UTC (rev 75)
+++ trunk/web-src/pages/download.xml 2010-02-06 22:54:43 UTC (rev 76)
@@ -17,9 +17,8 @@
<div class="h2Rounded">
<h2><a id="releases" class="anchorLink">Releases</a></h2>
</div>
- <p><strong>Important:</strong> Note that the instructions in this page are outdated and refer to release 0.1, which is hosted in the forge previously used by KTutorial. Release 0.2, hosted at SourceForge.net, will be out soon.</p>
- <p>Current release is 0.1. You can download <a href="https://forja.rediris.es/frs/download.php/654/ktutorial-0.1.tar.gz" title="KTutorial 0.1 release in tar.gz">ktutorial-0.1.tar.gz</a> from <a href="https://forja.rediris.es/frs/?group_id=280" title="KTutorial project files">project's file list</a>.</p>
- <p>You can also see the <a href="https://forja.rediris.es/frs/shownotes.php?release_id=405" title="KTutorial 0.1 release notes">release notes</a> (although there isn't much to see ;) ).</p>
+ <p>Current release is 0.2. You can download <a href="https://sourceforge.net/projects/ktutorial/files/ktutorial-0.2/ktutorial-0.2.tar.gz/download" title="KTutorial 0.2 release in tar.gz">ktutorial-0.2.tar.gz</a> from <a href="https://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
+ <p>You can also see the <a href="https://sourceforge.net/projects/ktutorial/files/ktutorial-0.2/Release%20notes/view" title="KTutorial 0.2 release notes">release notes</a> (although there isn't much to see ;) ).</p>
<p>See below for build instructions, in <a href="#build" title="Build instructions">building section</a>.</p>
<p>If you do know what you are doing ;) , you can also checkout KTutorial sources from <acronym title="Subversion">SVN</acronym> repository. Go on reading to know how to do it.</p>
@@ -38,10 +37,10 @@
<h2><a id="build" class="anchorLink">Building</a></h2>
</div>
<p>In order to build KTutorial, it doesn't matter if you downloaded it from a release or from <acronym title="Subversion">SVN</acronym>.</p>
- <p>You will need <a href="http://www.cmake.org" title="CMake project web">CMake</a> and KDE 4 kdelibs development packages installed in your system. It can be built like any other KDE 4 library or application.</p>
+ <p>You will need <a href="http://www.cmake.org" title="CMake project web">CMake</a>, and Qt >= 4.5.3 and KDE 4 kdelibs development packages installed in your system. It can be built like any other KDE 4 library or application.</p>
<p>Create a <em>build</em> subdirectory in <em>ktutorial</em> directory, and change to it. Now, in a terminal, just run <strong>cmake ../ && make</strong> and it will configure and build KTutorial in the <em>build</em> directory. Once built, execute <strong>make install</strong> and you are done (you will likely need to change to root user, as default KDE installation is usually only root writable).</p>
<p>If you want to specify a prefix to install KTutorial to, instead of using KDE default installation directory, call CMake using the parameter <strong>-DCMAKE_INSTALL_PREFIX=/installation/prefix</strong>. For debugging purposes, use <strong>-DCMAKE_BUILD_TYPE=debugfull</strong>. To automatically build the unit tests when the library is built, use <strong>-DKDE4_BUILD_TESTS=ON</strong>.</p>
- <p class="lastUpdated">Last updated: 2010-01-30</p>
+ <p class="lastUpdated">Last updated: 2010-02-06</p>
</page:content>
</page>
Modified: trunk/web-src/pages/index.xml
===================================================================
--- trunk/web-src/pages/index.xml 2010-02-06 18:03:24 UTC (rev 75)
+++ trunk/web-src/pages/index.xml 2010-02-06 22:54:43 UTC (rev 76)
@@ -26,6 +26,19 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId2" class="anchorLink">KTutorial 0.2 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2010-02-06</p>
+ <div class="newContent">
+ <div>
+ <p>Check <a href="download.html" title="Download page in KTutorial web">download page</a> for further information.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId1" class="anchorLink">Moved to SourceForge.net</a>
</h2>
<div class="newBody">
Modified: trunk/web-src/pages/news.xml
===================================================================
--- trunk/web-src/pages/news.xml 2010-02-06 18:03:24 UTC (rev 75)
+++ trunk/web-src/pages/news.xml 2010-02-06 22:54:43 UTC (rev 76)
@@ -23,6 +23,19 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId2" class="anchorLink">KTutorial 0.2 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2010-02-06</p>
+ <div class="newContent">
+ <div>
+ <p>Check <a href="download.html" title="Download page in KTutorial web">download page</a> for further information.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId1" class="anchorLink">Moved to SourceForge.net</a>
</h2>
<div class="newBody">
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2010-02-06 22:57:05
|
Revision: 77
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=77&view=rev
Author: danxuliu
Date: 2010-02-06 22:56:59 +0000 (Sat, 06 Feb 2010)
Log Message:
-----------
Update base URL
Modified Paths:
--------------
trunk/web-src/cybertron.sh
trunk/web-src/news-toAtom.xsl
trunk/web-src/pages/index.xml
trunk/web-src/transformers/header.xsl
Modified: trunk/web-src/cybertron.sh
===================================================================
--- trunk/web-src/cybertron.sh 2010-02-06 22:54:43 UTC (rev 76)
+++ trunk/web-src/cybertron.sh 2010-02-06 22:56:59 UTC (rev 77)
@@ -169,7 +169,7 @@
encoding="utf-8";
outputDir=../build/;
-baseURL="http://csl2-ktutorial.forja.rediris.es/";
+baseURL="http://ktutorial.sourceforge.net/";
while getopts e:o:u: o
do
@@ -180,7 +180,7 @@
[?]) echo "Usage: $0 [-e encoding] [-o outputDir] [-u baseURL]";
echo " Default encoding: utf-8";
echo " Default output directory: ../build/";
- echo " Default baseURL: http://csl2-ktutorial.forja.rediris.es/";
+ echo " Default baseURL: http://ktutorial.sourceforge.net/";
exit 1;;
esac
done
Modified: trunk/web-src/news-toAtom.xsl
===================================================================
--- trunk/web-src/news-toAtom.xsl 2010-02-06 22:54:43 UTC (rev 76)
+++ trunk/web-src/news-toAtom.xsl 2010-02-06 22:56:59 UTC (rev 77)
@@ -39,7 +39,7 @@
<!--
The base URL of the feed site. Must include ending slash.
-->
- <xsl:param name="baseURL" select="'http://csl2-ktutorial.forja.rediris.es/'"/>
+ <xsl:param name="baseURL" select="'http://ktutorial.sourceforge.net/'"/>
<!--
The URL to the HTML news page from the base URL.
Modified: trunk/web-src/pages/index.xml
===================================================================
--- trunk/web-src/pages/index.xml 2010-02-06 22:54:43 UTC (rev 76)
+++ trunk/web-src/pages/index.xml 2010-02-06 22:56:59 UTC (rev 77)
@@ -7,7 +7,7 @@
</headElements>
<validationButtons>
<p xmlns="http://www.w3.org/1999/xhtml">
- <a href="http://feedvalidator.org/check.cgi?url=http%3A//csl2-ktutorial.forja.rediris.es/feed/atom/news.xml" title="Check Atom feed">
+ <a href="http://feedvalidator.org/check.cgi?url=http%3A//ktutorial.sourceforge.net/feed/atom/news.xml" title="Check Atom feed">
<img src="images/valid-atom.png" alt="Valid Atom 1.0!" height="15" width="80"/>
</a>
</p>
Modified: trunk/web-src/transformers/header.xsl
===================================================================
--- trunk/web-src/transformers/header.xsl 2010-02-06 22:54:43 UTC (rev 76)
+++ trunk/web-src/transformers/header.xsl 2010-02-06 22:56:59 UTC (rev 77)
@@ -17,7 +17,7 @@
<div id="header">
<div id="logo">
<div id="logoName">
- <a href="http://forja.rediris.es/projects/csl2-ktutorial/" title="KTutorial project page">KTutorial</a>
+ <a href="http://sourceforge.net/projects/ktutorial/" title="KTutorial project page">KTutorial</a>
</div>
<p id="logoCompleteName">Library for KDE interactive tutorials</p>
</div>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2010-03-24 21:08:56
|
Revision: 191
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=191&view=rev
Author: danxuliu
Date: 2010-03-24 21:08:50 +0000 (Wed, 24 Mar 2010)
Log Message:
-----------
Add release 0.3 new, and update development, documentation and download pages
Modified Paths:
--------------
trunk/web-src/newsList.xml
trunk/web-src/pages/development.xml
trunk/web-src/pages/documentation.xml
trunk/web-src/pages/download.xml
trunk/web-src/pages/index.xml
trunk/web-src/pages/news.xml
Modified: trunk/web-src/newsList.xml
===================================================================
--- trunk/web-src/newsList.xml 2010-03-24 21:03:40 UTC (rev 190)
+++ trunk/web-src/newsList.xml 2010-03-24 21:08:50 UTC (rev 191)
@@ -24,4 +24,18 @@
<date>2010-02-06</date>
</fullDate>
</new>
-</news>
\ No newline at end of file
+
+ <new>
+ <title>KTutorial 0.3 released!</title>
+ <summary>
+ <div xmlns="http://www.w3.org/1999/xhtml">
+ <p>The main feature introduced in this release is KTutorial editor, a graphical editor to ease tutorial authoring. It is still in an early stage of development (you can't even save and load a tutorial to continue working on it later), but it will be improved in the next releases.</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.3/Release notes/view" title="KTutorial 0.3 release notes">release notes</a> contain more information about the changes from 0.2 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </summary>
+ <fullDate>
+ <date>2010-03-24</date>
+ </fullDate>
+ </new>
+</news>
Modified: trunk/web-src/pages/development.xml
===================================================================
--- trunk/web-src/pages/development.xml 2010-03-24 21:03:40 UTC (rev 190)
+++ trunk/web-src/pages/development.xml 2010-03-24 21:08:50 UTC (rev 191)
@@ -34,6 +34,7 @@
<h2><a id="status" class="anchorLink">Status</a></h2>
</div>
<p>Right now, KTutorial is in a prototype state, but it is able to execute tutorials: it works!</p>
+ <p>As well as the library itself, KTutorial provides a graphical editor for tutorials, not surprisingly named Ktutorial editor.</p>
<p>In KTutorial SVN there is also a little test application, KTutorial test app, which shows the different features of KTutorial in a "real" environment.</p>
<p>Here it is the current features list:</p>
<ul>
@@ -55,6 +56,9 @@
<li>
<p><em>CMake build system:</em> KTutorial uses KDE 4 CMake build system, and also provides a CMake module to be used from applications using KTutorial to configure them as necessary.</p>
</li>
+ <li>
+ <p><em>Graphical editor:</em> KTutorial editor is a companion to KTutorial library to ease tutorial authoring. A tutorial can be defined using the editor and then exported to a scripted tutorial that can be understood by KTutorial library. However, the editor is still very basic at this time.</p>
+ </li>
</ul>
<div class="h2Rounded">
@@ -63,20 +67,20 @@
<p>Here you can see what (major) features I expect to include in the future.</p>
<ul class="foldableList">
<li>
- 0.3:
+ 0.4:
<ul>
- <li>A graphical editor to create tutorials</li>
+ <li>Emphasize widgets to help the user finding them (provided it is technically viable)</li>
+ <li>In KTutorial editor, get the name of the objects that send signals or receive events from the application the tutorial documents, just clicking on the desired widget (provided it is technically viable)</li>
</ul>
</li>
<li>
Someday? (these features need further investigation about their technical viability):
<ul>
- <li>Emphasize widgets to help the user finding them</li>
<li>Extended information in step texts (something like "What is this" help on specific words, for example)</li>
</ul>
</li>
</ul>
- <p class="lastUpdated">Last updated: 2010-01-30</p>
+ <p class="lastUpdated">Last updated: 2010-03-24</p>
</page:content>
</page>
Modified: trunk/web-src/pages/documentation.xml
===================================================================
--- trunk/web-src/pages/documentation.xml 2010-03-24 21:03:40 UTC (rev 190)
+++ trunk/web-src/pages/documentation.xml 2010-03-24 21:08:50 UTC (rev 191)
@@ -23,8 +23,8 @@
<div class="h2Rounded">
<h2><a id="finalUsers" class="anchorLink">For final users</a></h2>
</div>
- <p>There is no specific documentation for KTutorial final users right now.</p>
- <p>However, if you have an application that uses KTutorial, it is very easy to execute the tutorials. Just go to <em>Help->Tutorials...</em> and a dialog with all the available tutorials will appear. Select one, click on <em>Start</em> button and now just follow it!</p>
+ <p>KTutorial provides a tutorial named <em>Using tutorials</em> which purpose is, well, show how to use tutorials ;)</p>
+ <p>But, how you can start a tutorial? If you have an application that uses KTutorial, just go to <em>Help->Tutorials...</em> and a dialog with all the available tutorials will appear. Select one, click on <em>Start</em> button and now just follow it!</p>
<p>If your application doesn't have a <em>Help->Tutorials...</em> menu item, sorry, it doesn't use KTutorial ;)</p>
<p>Note, however, that right now only KTutorial test application uses KTutorial :P</p>
@@ -40,6 +40,6 @@
</div>
<p>Refer to <a href="development.html" title="Development information">development</a> section of the web.</p>
- <p class="lastUpdated">Last updated: 2010-01-30</p>
+ <p class="lastUpdated">Last updated: 2010-03-24</p>
</page:content>
</page>
Modified: trunk/web-src/pages/download.xml
===================================================================
--- trunk/web-src/pages/download.xml 2010-03-24 21:03:40 UTC (rev 190)
+++ trunk/web-src/pages/download.xml 2010-03-24 21:08:50 UTC (rev 191)
@@ -17,8 +17,8 @@
<div class="h2Rounded">
<h2><a id="releases" class="anchorLink">Releases</a></h2>
</div>
- <p>Current release is 0.2. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.2/ktutorial-0.2.tar.gz/download" title="KTutorial 0.2 release in tar.gz">ktutorial-0.2.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
- <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.2/Release%20notes/view" title="KTutorial 0.2 release notes">release notes</a> (although there isn't much to see ;) ).</p>
+ <p>Current release is 0.3. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.3/ktutorial-0.3.tar.gz/download" title="KTutorial 0.3 release in tar.gz">ktutorial-0.3.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
+ <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.3/Release%20notes/view" title="KTutorial 0.3 release notes">release notes</a> (although there isn't much to see ;) ).</p>
<p>See below for build instructions, in <a href="#build" title="Build instructions">building section</a>.</p>
<p>If you do know what you are doing ;) , you can also checkout KTutorial sources from <acronym title="Subversion">SVN</acronym> repository. Go on reading to know how to do it.</p>
@@ -41,6 +41,6 @@
<p>Create a <em>build</em> subdirectory in <em>ktutorial</em> directory, and change to it. Now, in a terminal, just run <strong>cmake ../ && make</strong> and it will configure and build KTutorial in the <em>build</em> directory. Once built, execute <strong>make install</strong> and you are done (you will likely need to change to root user, as default KDE installation is usually only root writable).</p>
<p>If you want to specify a prefix to install KTutorial to, instead of using KDE default installation directory, call CMake using the parameter <strong>-DCMAKE_INSTALL_PREFIX=/installation/prefix</strong>. For debugging purposes, use <strong>-DCMAKE_BUILD_TYPE=debugfull</strong>. To automatically build the unit tests when the library is built, use <strong>-DKDE4_BUILD_TESTS=ON</strong>.</p>
- <p class="lastUpdated">Last updated: 2010-02-06</p>
+ <p class="lastUpdated">Last updated: 2010-03-24</p>
</page:content>
</page>
Modified: trunk/web-src/pages/index.xml
===================================================================
--- trunk/web-src/pages/index.xml 2010-03-24 21:03:40 UTC (rev 190)
+++ trunk/web-src/pages/index.xml 2010-03-24 21:08:50 UTC (rev 191)
@@ -26,6 +26,21 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId3" class="anchorLink">KTutorial 0.3 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2010-03-24</p>
+ <div class="newContent">
+ <div>
+ <p>The main feature introduced in this release is KTutorial editor, a graphical editor to ease tutorial authoring. It is still in an early stage of development (you can't even save and load a tutorial to continue working on it later), but it will be improved in the next releases.</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.3/Release notes/view" title="KTutorial 0.3 release notes">release notes</a> contain more information about the changes from 0.2 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId2" class="anchorLink">KTutorial 0.2 released!</a>
</h2>
<div class="newBody">
Modified: trunk/web-src/pages/news.xml
===================================================================
--- trunk/web-src/pages/news.xml 2010-03-24 21:03:40 UTC (rev 190)
+++ trunk/web-src/pages/news.xml 2010-03-24 21:08:50 UTC (rev 191)
@@ -23,6 +23,21 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId3" class="anchorLink">KTutorial 0.3 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2010-03-24</p>
+ <div class="newContent">
+ <div>
+ <p>The main feature introduced in this release is KTutorial editor, a graphical editor to ease tutorial authoring. It is still in an early stage of development (you can't even save and load a tutorial to continue working on it later), but it will be improved in the next releases.</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.3/Release notes/view" title="KTutorial 0.3 release notes">release notes</a> contain more information about the changes from 0.2 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId2" class="anchorLink">KTutorial 0.2 released!</a>
</h2>
<div class="newBody">
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2010-03-24 21:03:47
|
Revision: 190
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=190&view=rev
Author: danxuliu
Date: 2010-03-24 21:03:40 +0000 (Wed, 24 Mar 2010)
Log Message:
-----------
Add KTutorial editor screenshots
Modified Paths:
--------------
trunk/web-src/pages/aboutWeb.xml
trunk/web-src/pages/screenshotsGallery.xml
trunk/web-src/screenshotsList.xml
Added Paths:
-----------
trunk/web-src/data/images/screenshots/MainWindow-192.png
trunk/web-src/data/images/screenshots/MainWindow.png
trunk/web-src/data/images/screenshots/NewCondition-192.png
trunk/web-src/data/images/screenshots/NewCondition.png
trunk/web-src/data/images/screenshots/SetReactionData-192.png
trunk/web-src/data/images/screenshots/SetReactionData.png
Added: trunk/web-src/data/images/screenshots/MainWindow-192.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/MainWindow-192.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Added: trunk/web-src/data/images/screenshots/MainWindow.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/MainWindow.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Added: trunk/web-src/data/images/screenshots/NewCondition-192.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/NewCondition-192.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Added: trunk/web-src/data/images/screenshots/NewCondition.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/NewCondition.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Added: trunk/web-src/data/images/screenshots/SetReactionData-192.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/SetReactionData-192.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Added: trunk/web-src/data/images/screenshots/SetReactionData.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/SetReactionData.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Modified: trunk/web-src/pages/aboutWeb.xml
===================================================================
--- trunk/web-src/pages/aboutWeb.xml 2010-03-24 19:49:06 UTC (rev 189)
+++ trunk/web-src/pages/aboutWeb.xml 2010-03-24 21:03:40 UTC (rev 190)
@@ -79,6 +79,7 @@
<p>The only known element used which isn't ECMAScript is <em>onresize</em> event handling for the window (used in the gallery generator to resize the screenshots when the window is resized, and also used to load the scripts on window load). As far as I know, it's Javascript, because the <a href="http://www.w3.org/TR/Window/" title="W3C Window Object 1.0 specification">Window Object specification</a> is still a Working draft and doesn't have <a href="http://www.w3.org/TR/Window/#ecmascript-binding" title="ECMAScript binding for Window Object">ECMAScript bindings</a> defined. I haven't found an equivalent way to do it with pure ECMAScript.</p>
<p>The four scripts are: <a href="src/data/script/roundedCorners.js" title="Script to round corners">script/roundedCorners.js</a>, <a href="src/data/script/galleryGenerator.js" title="Script to generate a screenshots gallery">script/galleryGenerator.js</a>, <a href="src/data/script/foldableList.js" title="Script to make nested lists foldable">script/foldableList.js</a> and <a href="src/data/script/videoEmbedder.js" title="Script to replace ogg video links with embedded players">script/videoEmbedder.js</a>. Further information about each script can be found in the documentation in their header and functions documentation.</p>
<p>Those scripts only adds some optional features. Their lack doesn't ruin the use of the website, and, as desirable, it's perfectly usable in not ECMAScript enabled browsers. Each script is guarded against not conformant browsers using the hasFeature(feature, version) method of the DOMImplementation interface.</p>
+ <p>In fact, <em>script/galleryGenerator.js</em> is currently disabled until I can get some time to fix it, as the screenshots are resized over their natural size when the page size is too large. Better no gallery than an ugly gallery :P</p>
<p>Sadly, the fifth script, the one that contains the true video player, wasn't developed by me and I don't know whether it conforms to ECMAScript or not. I hope that it does, anyway ;)</p>
<div class="h2Rounded">
<h2>
@@ -114,6 +115,6 @@
<li>Copy source dir: copy all the contents of the <em>src</em> directory to the <em>src</em> subdirectory of the output directory.</li>
</ol>
- <p class="lastUpdated">Last updated: 2010-01-30</p>
+ <p class="lastUpdated">Last updated: 2010-03-24</p>
</page:content>
</page>
Modified: trunk/web-src/pages/screenshotsGallery.xml
===================================================================
--- trunk/web-src/pages/screenshotsGallery.xml 2010-03-24 19:49:06 UTC (rev 189)
+++ trunk/web-src/pages/screenshotsGallery.xml 2010-03-24 21:03:40 UTC (rev 190)
@@ -5,10 +5,28 @@
<page:headElements xmlns:page="http://lusi.berlios.de/namespaces/page" xmlns="http://www.w3.org/1999/xhtml">
<script src="script/galleryGenerator.js" type="text/javascript">/*Empty*/</script>
</page:headElements>
- <scriptOnLoad>generateGallery();</scriptOnLoad>
</variables>
<page:content xmlns:page="http://lusi.berlios.de/namespaces/page" xmlns="http://www.w3.org/1999/xhtml">
<h1>Gallery</h1>
- <p>Nothing to see here. Move along.</p>
+ <ul id="screenshotsList">
+ <li>
+ <p>KTutorial editor: Main window</p>
+ <a href="images/screenshots/MainWindow.png" title="Click for full size">
+ <img src="images/screenshots/MainWindow-192.png" alt="KTutorial editor main window showing a tutorial being worked on" width="192" height="144"/>
+ </a>
+ </li>
+ <li>
+ <p>KTutorial editor: New condition to wait for</p>
+ <a href="images/screenshots/NewCondition.png" title="Click for full size">
+ <img src="images/screenshots/NewCondition-192.png" alt="KTutorial editor dialog to add a new condition to wait for" width="192" height="93"/>
+ </a>
+ </li>
+ <li>
+ <p>KTutorial editor: Set reaction data</p>
+ <a href="images/screenshots/SetReactionData.png" title="Click for full size">
+ <img src="images/screenshots/SetReactionData-192.png" alt="KTutorial editor dialog to set the trigger and response of a reaction" width="192" height="221"/>
+ </a>
+ </li>
+ </ul>
</page:content>
</page>
Modified: trunk/web-src/screenshotsList.xml
===================================================================
--- trunk/web-src/screenshotsList.xml 2010-03-24 19:49:06 UTC (rev 189)
+++ trunk/web-src/screenshotsList.xml 2010-03-24 21:03:40 UTC (rev 190)
@@ -4,6 +4,21 @@
<ul id="screenshotsList" xmlns="http://www.w3.org/1999/xhtml">
<li>
- <p>Nothing to see here. Move along.</p>
+ <p>KTutorial editor: Main window</p>
+ <a href="images/screenshots/MainWindow.png" title="Click for full size">
+ <img src="images/screenshots/MainWindow-192.png" alt="KTutorial editor main window showing a tutorial being worked on" width="192" height="144"/>
+ </a>
</li>
+ <li>
+ <p>KTutorial editor: New condition to wait for</p>
+ <a href="images/screenshots/NewCondition.png" title="Click for full size">
+ <img src="images/screenshots/NewCondition-192.png" alt="KTutorial editor dialog to add a new condition to wait for" width="192" height="93"/>
+ </a>
+ </li>
+ <li>
+ <p>KTutorial editor: Set reaction data</p>
+ <a href="images/screenshots/SetReactionData.png" title="Click for full size">
+ <img src="images/screenshots/SetReactionData-192.png" alt="KTutorial editor dialog to set the trigger and response of a reaction" width="192" height="221"/>
+ </a>
+ </li>
</ul>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2010-10-31 20:33:57
|
Revision: 286
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=286&view=rev
Author: danxuliu
Date: 2010-10-31 20:33:51 +0000 (Sun, 31 Oct 2010)
Log Message:
-----------
Add Creative Commons license button in page footer.
Modified Paths:
--------------
trunk/web-src/data/style/style.css
trunk/web-src/transformers/footer.xsl
Added Paths:
-----------
trunk/web-src/data/images/cc-by-sa-88x31.png
trunk/web-src/data/images/cc-by-sa.png
Added: trunk/web-src/data/images/cc-by-sa-88x31.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/cc-by-sa-88x31.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Added: trunk/web-src/data/images/cc-by-sa.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/cc-by-sa.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Modified: trunk/web-src/data/style/style.css
===================================================================
--- trunk/web-src/data/style/style.css 2010-10-30 15:02:44 UTC (rev 285)
+++ trunk/web-src/data/style/style.css 2010-10-31 20:33:51 UTC (rev 286)
@@ -220,7 +220,7 @@
display: inline;
}
-#validation {
+#buttons {
text-align: center;
}
Modified: trunk/web-src/transformers/footer.xsl
===================================================================
--- trunk/web-src/transformers/footer.xsl 2010-10-30 15:02:44 UTC (rev 285)
+++ trunk/web-src/transformers/footer.xsl 2010-10-31 20:33:51 UTC (rev 286)
@@ -21,8 +21,13 @@
<xsl:template name="footer">
<xsl:comment> Footer </xsl:comment>
<div id="footer">
- <div id="validation">
+ <div id="buttons">
<p>
+ <a href="http://creativecommons.org/licenses/by-sa/3.0/" title="Creative Commons Attribution-ShareAlike 3.0 Unported License">
+ <img src="images/cc-by-sa.png" alt="This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License" height="15" width="80"/>
+ </a>
+ </p>
+ <p>
<a href="http://validator.w3.org/check?uri=referer" title="Check XHTML">
<img src="images/valid-xhtml11.png" alt="Valid XHTML 1.1!" height="15" width="80"/>
</a>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2010-10-31 20:37:46
|
Revision: 287
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=287&view=rev
Author: danxuliu
Date: 2010-10-31 20:37:40 +0000 (Sun, 31 Oct 2010)
Log Message:
-----------
Update pages for release 0.4
Modified Paths:
--------------
trunk/web-src/data/images/screenshots/MainWindow-192.png
trunk/web-src/data/images/screenshots/MainWindow.png
trunk/web-src/data/images/screenshots/NewCondition-192.png
trunk/web-src/data/images/screenshots/NewCondition.png
trunk/web-src/newsList.xml
trunk/web-src/pages/development.xml
trunk/web-src/pages/documentation.xml
trunk/web-src/pages/download.xml
trunk/web-src/pages/faq.xml
trunk/web-src/pages/index.xml
trunk/web-src/pages/news.xml
trunk/web-src/pages/screenshotsGallery.xml
trunk/web-src/screenshotsList.xml
Added Paths:
-----------
trunk/web-src/data/images/screenshots/SignalNameCompletion-192.png
trunk/web-src/data/images/screenshots/SignalNameCompletion.png
Modified: trunk/web-src/data/images/screenshots/MainWindow-192.png
===================================================================
(Binary files differ)
Modified: trunk/web-src/data/images/screenshots/MainWindow.png
===================================================================
(Binary files differ)
Modified: trunk/web-src/data/images/screenshots/NewCondition-192.png
===================================================================
(Binary files differ)
Modified: trunk/web-src/data/images/screenshots/NewCondition.png
===================================================================
(Binary files differ)
Added: trunk/web-src/data/images/screenshots/SignalNameCompletion-192.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/SignalNameCompletion-192.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Added: trunk/web-src/data/images/screenshots/SignalNameCompletion.png
===================================================================
(Binary files differ)
Property changes on: trunk/web-src/data/images/screenshots/SignalNameCompletion.png
___________________________________________________________________
Added: svn:mime-type
+ image/png
Modified: trunk/web-src/newsList.xml
===================================================================
--- trunk/web-src/newsList.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/newsList.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -38,4 +38,18 @@
<date>2010-03-24</date>
</fullDate>
</new>
+
+ <new>
+ <title>KTutorial 0.4 released!</title>
+ <summary>
+ <div xmlns="http://www.w3.org/1999/xhtml">
+ <p>This release was geared mostly towards improving KTutorial editor (for example, tutorials can be saved and loaded now), although improvements were made also to KTutorial library (like being able to highlight widgets).</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.4/Release notes/view" title="KTutorial 0.4 release notes">release notes</a> contain more information about the changes from 0.3 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </summary>
+ <fullDate>
+ <date>2010-10-30</date>
+ </fullDate>
+ </new>
</news>
Modified: trunk/web-src/pages/development.xml
===================================================================
--- trunk/web-src/pages/development.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/pages/development.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -23,7 +23,8 @@
<h2><a id="documentation" class="anchorLink">Documentation</a></h2>
</div>
<p>This documentation is about KTutorial development. If you are a developer, but are looking for documentation about using KTutorial in your application, take a look in <a href="documentation.html#developers" title="Documentation for developers using KTutorial">developers section</a> in the documentation page.</p>
- <p>Instead, if you are curious about how KTutorial is developed (design, implementation...), take a look in <a href="doc/design.html" title="KTutorial design document">KTutorial design</a>. However, I still need to work on it, as it is more a draft than a final document.</p>
+ <p>Instead, if you are curious about how KTutorial is developed (design, implementation...), take a look in <a href="doc/design.html" title="KTutorial design document">KTutorial design</a>. However, I still need to work on it, as it is more a draft than a final document, and it is also painfully outdated...</p>
+ <p>The UML diagrams (mostly class diagrams), on the other hand, are up to date: <a href="doc/Editor.xmi" title="KTutorial Editor UML diagrams">editor</a> and <a href="doc/Library.xmi" title="KTutorial Library UML diagrams">library</a>. Both files can be opened using <a href="http://uml.sourceforge.net/" title="Umbrello UML Modeller home page">Umbrello UML Modeller</a>.</p>
<div class="h2Rounded">
<h2><a id="blog" class="anchorLink">Blog</a></h2>
@@ -35,7 +36,7 @@
</div>
<p>Right now, KTutorial is in a prototype state, but it is able to execute tutorials: it works!</p>
<p>As well as the library itself, KTutorial provides a graphical editor for tutorials, not surprisingly named Ktutorial editor.</p>
- <p>In KTutorial SVN there is also a little test application, KTutorial test app, which shows the different features of KTutorial in a "real" environment.</p>
+ <p>There is also a little test application, KTutorial test app, which shows several features of KTutorial in a "real" environment.</p>
<p>Here it is the current features list:</p>
<ul>
<li>
@@ -48,6 +49,9 @@
<p><em>Options in steps:</em> tutorials can show options to the user in the steps. It allows, for example, to make the user choose between one path or another when following a tutorial.</p>
</li>
<li>
+ <p><em>Widget highlighting:</em> tutorials can link to widgets in the text of their steps, and when the links are clicked the widgets are highlighted.</p>
+ </li>
+ <li>
<p><em>Easy integration:</em> KTutorial was designed to ease its use in applications, so the developer only has to worry about coding the tutorial. Setting KTutorial up, merging the menus, managing the tutorials and things like that are done almost automatically.</p>
</li>
<li>
@@ -57,8 +61,11 @@
<p><em>CMake build system:</em> KTutorial uses KDE 4 CMake build system, and also provides a CMake module to be used from applications using KTutorial to configure them as necessary.</p>
</li>
<li>
- <p><em>Graphical editor:</em> KTutorial editor is a companion to KTutorial library to ease tutorial authoring. A tutorial can be defined using the editor and then exported to a scripted tutorial that can be understood by KTutorial library. However, the editor is still very basic at this time.</p>
+ <p><em>Graphical editor:</em> KTutorial editor is a companion to KTutorial library to ease tutorial authoring. A tutorial can be defined using the editor and then exported to a scripted tutorial that can be understood by KTutorial library.</p>
</li>
+ <li>
+ <p><em>Application introspection:</em> KTutorial provides a system to introspect any application that uses KTutorial. Thanks to this, KTutorial editor can know, for example, the name of the objects accesible by KTutorial or the signals they can emit.</p>
+ </li>
</ul>
<div class="h2Rounded">
@@ -67,20 +74,20 @@
<p>Here you can see what (major) features I expect to include in the future.</p>
<ul class="foldableList">
<li>
- 0.4:
+ 0.5:
<ul>
- <li>Emphasize widgets to help the user finding them (provided it is technically viable)</li>
- <li>In KTutorial editor, get the name of the objects that send signals or receive events from the application the tutorial documents, just clicking on the desired widget (provided it is technically viable)</li>
+ <li>Add support for custom conditions in KTutorial editor.</li>
</ul>
</li>
<li>
Someday? (these features need further investigation about their technical viability):
<ul>
- <li>Extended information in step texts (something like "What is this" help on specific words, for example)</li>
+ <li>Extended information in step texts (something like "What is this" help on specific words, for example).</li>
+ <li>Add a <a href="http://martinfowler.com/bliki/FluentInterface.html" title="Fluent Interface article in Martin Fowler's Bliki">fluent interface</a> to the library.</li>
</ul>
</li>
</ul>
- <p class="lastUpdated">Last updated: 2010-03-24</p>
+ <p class="lastUpdated">Last updated: 2010-10-30</p>
</page:content>
</page>
Modified: trunk/web-src/pages/documentation.xml
===================================================================
--- trunk/web-src/pages/documentation.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/pages/documentation.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -26,7 +26,7 @@
<p>KTutorial provides a tutorial named <em>Using tutorials</em> which purpose is, well, show how to use tutorials ;)</p>
<p>But, how you can start a tutorial? If you have an application that uses KTutorial, just go to <em>Help->Tutorials...</em> and a dialog with all the available tutorials will appear. Select one, click on <em>Start</em> button and now just follow it!</p>
<p>If your application doesn't have a <em>Help->Tutorials...</em> menu item, sorry, it doesn't use KTutorial ;)</p>
- <p>Note, however, that right now only KTutorial test application uses KTutorial :P</p>
+ <p>Note, however, that right now only KTutorial editor and KTutorial test application use KTutorial :P</p>
<div class="h2Rounded">
<h2><a id="developers" class="anchorLink">For developers using KTutorial</a></h2>
@@ -40,6 +40,6 @@
</div>
<p>Refer to <a href="development.html" title="Development information">development</a> section of the web.</p>
- <p class="lastUpdated">Last updated: 2010-03-24</p>
+ <p class="lastUpdated">Last updated: 2010-10-30</p>
</page:content>
</page>
Modified: trunk/web-src/pages/download.xml
===================================================================
--- trunk/web-src/pages/download.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/pages/download.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -17,8 +17,8 @@
<div class="h2Rounded">
<h2><a id="releases" class="anchorLink">Releases</a></h2>
</div>
- <p>Current release is 0.3. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.3/ktutorial-0.3.tar.gz/download" title="KTutorial 0.3 release in tar.gz">ktutorial-0.3.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
- <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.3/Release%20notes/view" title="KTutorial 0.3 release notes">release notes</a> (although there isn't much to see ;) ).</p>
+ <p>Current release is 0.4. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.4/ktutorial-0.4.tar.gz/download" title="KTutorial 0.4 release in tar.gz">ktutorial-0.4.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
+ <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.4/Release%20notes/view" title="KTutorial 0.4 release notes">release notes</a> (although there isn't much to see ;) ).</p>
<p>See below for build instructions, in <a href="#build" title="Build instructions">building section</a>.</p>
<p>If you do know what you are doing ;) , you can also checkout KTutorial sources from <acronym title="Subversion">SVN</acronym> repository. Go on reading to know how to do it.</p>
@@ -37,10 +37,10 @@
<h2><a id="build" class="anchorLink">Building</a></h2>
</div>
<p>In order to build KTutorial, it doesn't matter if you downloaded it from a release or from <acronym title="Subversion">SVN</acronym>.</p>
- <p>You will need <a href="http://www.cmake.org" title="CMake project web">CMake</a>, and Qt >= 4.5.3 and KDE 4 kdelibs development packages installed in your system. It can be built like any other KDE 4 library or application.</p>
+ <p>You will need <a href="http://www.cmake.org" title="CMake project web">CMake</a>, and Qt >= 4.6 and KDE 4 kdelibs development packages installed in your system. It can be built like any other KDE 4 library or application.</p>
<p>Create a <em>build</em> subdirectory in <em>ktutorial</em> directory, and change to it. Now, in a terminal, just run <strong>cmake ../ && make</strong> and it will configure and build KTutorial in the <em>build</em> directory. Once built, execute <strong>make install</strong> and you are done (you will likely need to change to root user, as default KDE installation is usually only root writable).</p>
<p>If you want to specify a prefix to install KTutorial to, instead of using KDE default installation directory, call CMake using the parameter <strong>-DCMAKE_INSTALL_PREFIX=/installation/prefix</strong>. For debugging purposes, use <strong>-DCMAKE_BUILD_TYPE=debugfull</strong>. To automatically build the unit tests when the library is built, use <strong>-DKDE4_BUILD_TESTS=ON</strong>.</p>
- <p class="lastUpdated">Last updated: 2010-03-24</p>
+ <p class="lastUpdated">Last updated: 2010-10-30</p>
</page:content>
</page>
Modified: trunk/web-src/pages/faq.xml
===================================================================
--- trunk/web-src/pages/faq.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/pages/faq.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -24,7 +24,7 @@
<div class="QandAentry">
<h3 class="question"><a id="whenRelease" class="anchorLink">When will a working version be released?</a></h3>
<div class="answer">
- <p>Hopefully, a full working version will be out for May 2010, when the deadline to defend KTutorial as my final project in my Computer Engineering university course ends.</p>
+ <p>Version 0.4, released 2010-10-30, can be considered a working version. However, it still lacks several features, so it is a working version, but not a fully working version. I have no idea when, if ever, the fully working version will be ready.</p>
<p>Meanwhile, some prototypes will be released which will gain functionality over releases. I hope I'll be able to follow the <a href="http://www.free-soft.org/literature/papers/esr/cathedral-bazaar/cathedral-bazaar-4.html" title="The Cathedral and the Bazaar: Release early, release often">Release early, release often</a> model. I can't promise it, however ;)</p>
</div>
</div>
@@ -41,6 +41,6 @@
</div>
</div>
- <p class="lastUpdated">Last updated: 2010-01-30</p>
+ <p class="lastUpdated">Last updated: 2010-10-30</p>
</page:content>
</page>
Modified: trunk/web-src/pages/index.xml
===================================================================
--- trunk/web-src/pages/index.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/pages/index.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -26,6 +26,21 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId4" class="anchorLink">KTutorial 0.4 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2010-10-30</p>
+ <div class="newContent">
+ <div>
+ <p>This release was geared mostly towards improving KTutorial editor (for example, tutorials can be saved and loaded now), although improvements were made also to KTutorial library (like being able to highlight widgets).</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.4/Release notes/view" title="KTutorial 0.4 release notes">release notes</a> contain more information about the changes from 0.3 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId3" class="anchorLink">KTutorial 0.3 released!</a>
</h2>
<div class="newBody">
Modified: trunk/web-src/pages/news.xml
===================================================================
--- trunk/web-src/pages/news.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/pages/news.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -23,6 +23,21 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId4" class="anchorLink">KTutorial 0.4 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2010-10-30</p>
+ <div class="newContent">
+ <div>
+ <p>This release was geared mostly towards improving KTutorial editor (for example, tutorials can be saved and loaded now), although improvements were made also to KTutorial library (like being able to highlight widgets).</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.4/Release notes/view" title="KTutorial 0.4 release notes">release notes</a> contain more information about the changes from 0.3 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId3" class="anchorLink">KTutorial 0.3 released!</a>
</h2>
<div class="newBody">
Modified: trunk/web-src/pages/screenshotsGallery.xml
===================================================================
--- trunk/web-src/pages/screenshotsGallery.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/pages/screenshotsGallery.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -27,6 +27,12 @@
<img src="images/screenshots/SetReactionData-192.png" alt="KTutorial editor dialog to set the trigger and response of a reaction" width="192" height="221"/>
</a>
</li>
+ <li>
+ <p>KTutorial editor: Signal name completion</p>
+ <a href="images/screenshots/SignalNameCompletion.png" title="Click for full size">
+ <img src="images/screenshots/SignalNameCompletion-192.png" alt="KTutorial editor text completion of signal names emitted by an object in the target application" width="192" height="91"/>
+ </a>
+ </li>
</ul>
</page:content>
</page>
Modified: trunk/web-src/screenshotsList.xml
===================================================================
--- trunk/web-src/screenshotsList.xml 2010-10-31 20:33:51 UTC (rev 286)
+++ trunk/web-src/screenshotsList.xml 2010-10-31 20:37:40 UTC (rev 287)
@@ -21,4 +21,10 @@
<img src="images/screenshots/SetReactionData-192.png" alt="KTutorial editor dialog to set the trigger and response of a reaction" width="192" height="221"/>
</a>
</li>
+ <li>
+ <p>KTutorial editor: Signal name completion</p>
+ <a href="images/screenshots/SignalNameCompletion.png" title="Click for full size">
+ <img src="images/screenshots/SignalNameCompletion-192.png" alt="KTutorial editor text completion of signal names emitted by an object in the target application" width="192" height="91"/>
+ </a>
+ </li>
</ul>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2012-08-24 16:43:25
|
Revision: 382
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=382&view=rev
Author: danxuliu
Date: 2012-08-24 16:43:14 +0000 (Fri, 24 Aug 2012)
Log Message:
-----------
Update pages for 0.5 release.
Modified Paths:
--------------
trunk/web-src/newsList.xml
trunk/web-src/pages/about.xml
trunk/web-src/pages/development.xml
trunk/web-src/pages/download.xml
trunk/web-src/pages/faq.xml
trunk/web-src/pages/index.xml
trunk/web-src/pages/news.xml
Modified: trunk/web-src/newsList.xml
===================================================================
--- trunk/web-src/newsList.xml 2012-08-21 20:06:54 UTC (rev 381)
+++ trunk/web-src/newsList.xml 2012-08-24 16:43:14 UTC (rev 382)
@@ -52,4 +52,18 @@
<date>2010-10-30</date>
</fullDate>
</new>
+
+ <new>
+ <title>KTutorial 0.5 released!</title>
+ <summary>
+ <div xmlns="http://www.w3.org/1999/xhtml">
+ <p>The focus on this release was on getting KTutorial ready to be used by other applications besides the KTutorial editor itself.</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5/README/view" title="KTutorial 0.5 release notes">release notes</a> contain more information about the changes from 0.4 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </summary>
+ <fullDate>
+ <date>2012-08-21</date>
+ </fullDate>
+ </new>
</news>
Modified: trunk/web-src/pages/about.xml
===================================================================
--- trunk/web-src/pages/about.xml 2012-08-21 20:06:54 UTC (rev 381)
+++ trunk/web-src/pages/about.xml 2012-08-24 16:43:14 UTC (rev 382)
@@ -17,16 +17,16 @@
<div class="h2Rounded">
<h2><a id="project" class="anchorLink">Project overview</a></h2>
</div>
- <p>KTutorial is a library for interactive tutorials in KDE applications. Tutorials are embeded in the application itself, and reacts to user actions: waits for some task to be accomplished, warns if something wasn't done as it should, etcetera. As the tutorial is being followed, the system gives feedback to the user.</p>
+ <p>KTutorial is a library (and a graphical editor) for interactive tutorials in KDE applications. Tutorials are embeded in the application itself, and react to user actions: wait for some task to be accomplished, warn if something wasn't done as it should, etcetera. As the tutorial is being followed, the system gives feedback to the user.</p>
<p>It is licensed under the <a href="http://www.gnu.org/copyleft/gpl.html" title="GNU General Public License page">GNU GPL license</a>. It is also free as in "free beer".</p>
<div class="h2Rounded">
<h2><a id="author" class="anchorLink">Author</a></h2>
</div>
<p>KTutorial was initially developed by me, Daniel Calviño Sánchez, as my entry in the <a href="http://www.concursosoftwarelibre.org/" title="II Concurso Universitario de Software Libre web page">II Concurso Universitario de Software Libre</a> (second universitary free software contest). It didn't make its way to the final phase, although it received a <a href="http://www.concursosoftwarelibre.org/0708/node/157.html" title="Premios del II Concurso Universitario de Software Libre">Special Mention</a> :)</p>
- <p>Now it is being developed as my final project in Computer Engineering at <a href="http://www.epsig.uniovi.es" title="E.P.S.I.G. webpage">Escuela Politécnica Superior de Ingeniería de Gijón</a>.</p>
- <p>If you want, you can contact me using this e-mail address: danxuliu at gmail.com. Please, begin the subject with "KTutorial:" (without quotes) or something like that. It will help me to keep my inbox organized :) Thanks ;)</p>
- <p>Please note that I can understand only Spanish, Asturian and English, so if you send me a message in other language I won't be able to understand it ;)</p>
+ <p>Then I developed it further and defended it as my final project in Computer Engineering at Escuela Politécnica Superior de Ingeniería de Gijón.</p>
+ <p>If you want, you can contact me using this e-mail address: danxuliu at gmail.com.</p>
+ <p>And please note that I may not be able to understand your message if it is not written in Spanish, Asturian or English ;)</p>
<div class="h2Rounded">
<h2><a id="web" class="anchorLink">About this web</a></h2>
@@ -34,6 +34,6 @@
<p>The web is divided in several sections that can be accessed through the links in the menu in each page. I'm not going to explain its structure, as it seems very clear and I have better things to spend my time on :P</p>
<p>You can find information about how this web is built in its own page: <a href="aboutWeb.html" title="About KTutorial project web building">About web</a>.</p>
- <p class="lastUpdated">Last updated: 2010-01-30</p>
+ <p class="lastUpdated">Last updated: 2012-08-21</p>
</page:content>
</page>
Modified: trunk/web-src/pages/development.xml
===================================================================
--- trunk/web-src/pages/development.xml 2012-08-21 20:06:54 UTC (rev 381)
+++ trunk/web-src/pages/development.xml 2012-08-24 16:43:14 UTC (rev 382)
@@ -23,7 +23,7 @@
<h2><a id="documentation" class="anchorLink">Documentation</a></h2>
</div>
<p>This documentation is about KTutorial development. If you are a developer, but are looking for documentation about using KTutorial in your application, take a look in <a href="documentation.html#developers" title="Documentation for developers using KTutorial">developers section</a> in the documentation page.</p>
- <p>Instead, if you are curious about how KTutorial is developed (design, implementation...), take a look in <a href="doc/design.html" title="KTutorial design document">KTutorial design</a>. However, I still need to work on it, as it is more a draft than a final document, and it is also painfully outdated...</p>
+ <p>Instead, if you are curious about how KTutorial is designed, take a look in <a href="doc/design.html" title="KTutorial design document">KTutorial design</a>. Although it is painfully outdated, most is still valid. However, several components are missing from the explanation.</p>
<p>The UML diagrams (mostly class diagrams), on the other hand, are up to date: <a href="doc/Editor.xmi" title="KTutorial Editor UML diagrams">editor</a> and <a href="doc/Library.xmi" title="KTutorial Library UML diagrams">library</a>. Both files can be opened using <a href="http://uml.sourceforge.net/" title="Umbrello UML Modeller home page">Umbrello UML Modeller</a>.</p>
<div class="h2Rounded">
@@ -55,6 +55,9 @@
<p><em>Easy integration:</em> KTutorial was designed to ease its use in applications, so the developer only has to worry about coding the tutorial. Setting KTutorial up, merging the menus, managing the tutorials and things like that are done almost automatically.</p>
</li>
<li>
+ <p><em>Optional customization:</em> KTutorial also offers the possibility to developers to provide their own user interface instead of using the default one.</p>
+ </li>
+ <li>
<p><em>Internationalization:</em> KTutorial, as a good KDE library, uses KDE internationalization system, so it can be localized in several languages. Right now, only English and Spanish localizations are supported.</p>
</li>
<li>
@@ -74,9 +77,9 @@
<p>Here you can see what (major) features I expect to include in the future.</p>
<ul class="foldableList">
<li>
- 0.5:
+ 0.6:
<ul>
- <li>Add support for custom conditions in KTutorial editor.</li>
+ <li>Improve KTutorial editor for non-technical users.</li>
</ul>
</li>
<li>
@@ -88,6 +91,6 @@
</li>
</ul>
- <p class="lastUpdated">Last updated: 2010-10-30</p>
+ <p class="lastUpdated">Last updated: 2012-08-21</p>
</page:content>
</page>
Modified: trunk/web-src/pages/download.xml
===================================================================
--- trunk/web-src/pages/download.xml 2012-08-21 20:06:54 UTC (rev 381)
+++ trunk/web-src/pages/download.xml 2012-08-24 16:43:14 UTC (rev 382)
@@ -17,8 +17,8 @@
<div class="h2Rounded">
<h2><a id="releases" class="anchorLink">Releases</a></h2>
</div>
- <p>Current release is 0.4. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.4/ktutorial-0.4.tar.gz/download" title="KTutorial 0.4 release in tar.gz">ktutorial-0.4.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
- <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.4/Release%20notes/view" title="KTutorial 0.4 release notes">release notes</a> (although there isn't much to see ;) ).</p>
+ <p>Current release is 0.5. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5/ktutorial-0.5.tar.gz/download" title="KTutorial 0.5 release in tar.gz">ktutorial-0.5.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
+ <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5/README/view" title="KTutorial 0.5 release notes">release notes</a>, which list the changes from the previous release.</p>
<p>See below for build instructions, in <a href="#build" title="Build instructions">building section</a>.</p>
<p>If you do know what you are doing ;) , you can also checkout KTutorial sources from <acronym title="Subversion">SVN</acronym> repository. Go on reading to know how to do it.</p>
@@ -39,8 +39,8 @@
<p>In order to build KTutorial, it doesn't matter if you downloaded it from a release or from <acronym title="Subversion">SVN</acronym>.</p>
<p>You will need <a href="http://www.cmake.org" title="CMake project web">CMake</a>, and Qt >= 4.6 and KDE 4 kdelibs development packages installed in your system. It can be built like any other KDE 4 library or application.</p>
<p>Create a <em>build</em> subdirectory in <em>ktutorial</em> directory, and change to it. Now, in a terminal, just run <strong>cmake ../ && make</strong> and it will configure and build KTutorial in the <em>build</em> directory. Once built, execute <strong>make install</strong> and you are done (you will likely need to change to root user, as default KDE installation is usually only root writable).</p>
- <p>If you want to specify a prefix to install KTutorial to, instead of using KDE default installation directory, call CMake using the parameter <strong>-DCMAKE_INSTALL_PREFIX=/installation/prefix</strong>. For debugging purposes, use <strong>-DCMAKE_BUILD_TYPE=debugfull</strong>. To automatically build the unit tests when the library is built, use <strong>-DKDE4_BUILD_TESTS=ON</strong>.</p>
+ <p>If you want to specify a prefix to install KTutorial to, instead of using KDE default installation directory, call CMake using the parameter <strong>-DCMAKE_INSTALL_PREFIX=/installation/prefix</strong>. For debugging purposes, use <strong>-DCMAKE_BUILD_TYPE=debugfull</strong>. To automatically build the unit tests when the project is built, use <strong>-DKDE4_BUILD_TESTS=ON</strong>.</p>
- <p class="lastUpdated">Last updated: 2010-10-30</p>
+ <p class="lastUpdated">Last updated: 2012-08-21</p>
</page:content>
</page>
Modified: trunk/web-src/pages/faq.xml
===================================================================
--- trunk/web-src/pages/faq.xml 2012-08-21 20:06:54 UTC (rev 381)
+++ trunk/web-src/pages/faq.xml 2012-08-24 16:43:14 UTC (rev 382)
@@ -31,7 +31,7 @@
<div class="QandAentry">
<h3 class="question"><a id="whyGPL" class="anchorLink">Why did you choose <acronym title="GNU General Public License">GPL</acronym> license being a library?</a></h3>
<div class="answer">
- <p>Why not? Oh, wait, do you mean why I didn't choose the <a href="" title="GNU Lesser General Public License"><acronym title="Lesser General Public License">LGPL</acronym></a> instead? Well, because I prefer its "even if you're only linking against GPL code without modifying it the code where it's being used must be GPL" viral property. Anyway, if you need a special license for KTutorial, <a href="about.html#author" title="About the author">contact me</a>. Maybe you can convince me ;)</p>
+ <p>Why not? Oh, wait, do you mean why I didn't choose the <a href="http://www.gnu.org/copyleft/lgpl.html" title="GNU Lesser General Public License"><acronym title="Lesser General Public License">LGPL</acronym></a> instead? Well, because I prefer its "even if you're only linking against GPL code without modifying it the code where it's being used must be GPL" viral property. Anyway, if you need a special license for KTutorial, <a href="about.html#author" title="About the author">contact me</a>. Maybe you can convince me ;)</p>
</div>
</div>
<div class="QandAentry">
Modified: trunk/web-src/pages/index.xml
===================================================================
--- trunk/web-src/pages/index.xml 2012-08-21 20:06:54 UTC (rev 381)
+++ trunk/web-src/pages/index.xml 2012-08-24 16:43:14 UTC (rev 382)
@@ -26,6 +26,21 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId5" class="anchorLink">KTutorial 0.5 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2012-08-21</p>
+ <div class="newContent">
+ <div>
+ <p>The focus on this release was on getting KTutorial ready to be used by other applications besides the KTutorial editor itself.</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5/README/view" title="KTutorial 0.5 release notes">release notes</a> contain more information about the changes from 0.4 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId4" class="anchorLink">KTutorial 0.4 released!</a>
</h2>
<div class="newBody">
Modified: trunk/web-src/pages/news.xml
===================================================================
--- trunk/web-src/pages/news.xml 2012-08-21 20:06:54 UTC (rev 381)
+++ trunk/web-src/pages/news.xml 2012-08-24 16:43:14 UTC (rev 382)
@@ -23,6 +23,21 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId5" class="anchorLink">KTutorial 0.5 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2012-08-21</p>
+ <div class="newContent">
+ <div>
+ <p>The focus on this release was on getting KTutorial ready to be used by other applications besides the KTutorial editor itself.</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5/README/view" title="KTutorial 0.5 release notes">release notes</a> contain more information about the changes from 0.4 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId4" class="anchorLink">KTutorial 0.4 released!</a>
</h2>
<div class="newBody">
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2012-08-30 14:34:51
|
Revision: 383
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=383&view=rev
Author: danxuliu
Date: 2012-08-30 14:34:37 +0000 (Thu, 30 Aug 2012)
Log Message:
-----------
Add news, videos and sources for the "example of KTutorial for the real world" series of the blog.
Modified Paths:
--------------
trunk/web-src/newsList.xml
trunk/web-src/pages/index.xml
trunk/web-src/pages/news.xml
trunk/web-src/pages/screenshots.xml
Added Paths:
-----------
trunk/web-src/data/files/examples/
trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml
trunk/web-src/data/files/examples/gwenview.patch
trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml
trunk/web-src/data/files/examples/kdenlive.patch
trunk/web-src/data/files/examples/showfoto-levelsAdjust.xml
trunk/web-src/data/files/examples/showfoto.patch
trunk/web-src/data/files/gwenview-fullScreenInterface.ogv
trunk/web-src/data/files/gwenview-fullScreenInterface.png
trunk/web-src/data/files/kdenlive-simpleSlideTransitionBetweenTwoClips.ogv
trunk/web-src/data/files/kdenlive-simpleSlideTransitionBetweenTwoClips.png
trunk/web-src/data/files/showfoto-levelsAdjust.ogv
trunk/web-src/data/files/showfoto-levelsAdjust.png
Added: trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml
===================================================================
--- trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml (rev 0)
+++ trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml 2012-08-30 14:34:37 UTC (rev 383)
@@ -0,0 +1,129 @@
+<?xml version="1.0" encoding="utf-8"?>
+<tutorial name="Full screen interface">
+ <description>An overview of the full screen interface of Gwenview.</description>
+ <step id="start">
+ <text><para>Gwenview features two modes: browse and view. In versions prior to 2.9 only the view mode had also a full screen interface. In Gwenview 2.9 a full screen interface was added for the browse mode too.</para>
+
+<para>This tutorial will show you an overview of the full screen interface for browse and view modes. We will start by looking at the full screen browse mode, so browse to a folder with several images and, then, change to full screen.</para>
+
+<para>To change to full screen you can click on the <interface>Full screen</interface> button in the <link url="widget:mainToolBar">tool bar</link>, or click on the <interface>View|Full screen mode</interface> menu item in the menu bar.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForStepActivation/>
+ <waitForProperty objectName="StartMainPage" propertyName="visible" value="true"/>
+ </waitForComposed>
+ <nextStep id="start when start page is selected"/>
+ </reaction>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForStepActivation/>
+ <waitForProperty objectName="StartMainPage" propertyName="visible" value="false"/>
+ <waitForProperty objectName="BrowseMainPage" propertyName="visible" value="false"/>
+ </waitForComposed>
+ <nextStep id="start when view page is selected"/>
+ </reaction>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="fullscreen" signalName="triggered()"/>
+ <nextStep id="fullscreen browse mode"/>
+ </reaction>
+ </step>
+ <step id="start when start page is selected">
+ <text><para>Gwenview features two modes: browse and view. In versions prior to 2.9 only the view mode had also a full screen interface. In Gwenview 2.9 a full screen interface was added for the browse mode too.</para>
+
+<para>This tutorial will show you an overview of the full screen interface for browse and view modes. We will start by looking at the full screen browse mode so, first, change to browse mode.</para>
+
+<para>You can change to browse mode from the start page by double clicking on any of your <link url="widget:mHistoryWidget">recent folders</link> or by single clicking on any of your <link url="widget:mPlacesTagsWidget">places</link>.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="browse" signalName="triggered()"/>
+ <nextStep id="enter fullscreen in browser mode"/>
+ </reaction>
+ </step>
+ <step id="start when view page is selected">
+ <text><para>Gwenview features two modes: browse and view. In versions prior to 2.9 only the view mode had also a full screen interface. In Gwenview 2.9 a full screen interface was added for the browse mode too.</para>
+
+<para>This tutorial will show you an overview of the full screen interface for browse and view modes. We will start by looking at the full screen browse mode so, first, change to browse mode.</para>
+
+<para>You can change to browse mode from the view mode by clicking on the <interface>Browse</interface> button in the <link url="widget:mainToolBar">tool bar</link>, or by clicking on the <interface>View|Browse</interface> menu item in the menu bar.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="browse" signalName="triggered()"/>
+ <nextStep id="enter fullscreen in browser mode"/>
+ </reaction>
+ </step>
+ <step id="enter fullscreen in browser mode">
+ <text><para>Now browse to a folder with several images. Then, change to full screen.</para>
+
+<para>To change to full screen you can click on the <interface>Full screen</interface> button in the <link url="widget:mainToolBar">tool bar</link>, or click on the <interface>View|Full screen mode</interface> menu item in the menu bar.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="fullscreen" signalName="triggered()"/>
+ <nextStep id="fullscreen browse mode"/>
+ </reaction>
+ </step>
+ <step id="fullscreen browse mode">
+ <text><para>As you can see, the full screen interface for browse mode is pretty much the same as the normal interface. However, it does not have a menu bar, and neither a tool bar.</para>
+
+<para>It does have, though, a <link url="widget:mStatusBarContainer">status bar</link>, so you can use it to <link url="widget:mToggleSideBarButton">show or hide the side bar</link>, or <link url="widget:mThumbnailSlider">change the size of the thumbnails</link>. It also contains a top bar with a few buttons and the <link url="widget:mUrlNavigatorContainer">navigation bar</link> showing the current folder path.</para>
+
+<para>As the full screen interface for the browse mode is pretty much like its normal interface we will change now to the full screen view mode.</para>
+
+<para>To change to the view mode, select an image and then click on the view mode button in the top bar (its icon is a single picture).</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="view" signalName="triggered()"/>
+ <nextStep id="fullscreen view mode"/>
+ </reaction>
+ </step>
+ <step id="fullscreen view mode">
+ <text><para>The full screen interface for the view mode differs a lot more from its normal interface. The full screen interface only contains the selected image (or images) and an <link url="widget:fullScreenBar">auto-hiding top bar</link> (move the cursor to the top of the screen and the bar will appear, move the cursor outside the bar and the bar will dissapear).</para>
+
+<para>This full screen interface is designed to show a slideshow of your images. The slideshow (and other details of the full screen interface) can be configured clicking on the <interface>Configuration</interface> button in the top bar.</para>
+
+<para>Now start the slideshow. To do this, just click on the <interface>Start slideshow</interface> button (its icon is a <emphasis>Play</emphasis> icon) in the top bar.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="toggle_slideshow" signalName="triggered()"/>
+ <nextStep id="slideshow"/>
+ </reaction>
+ </step>
+ <step id="slideshow">
+ <text><para>The slideshow starts from the current image and shows all the images in the current folder, stopping at the last one (unless you check the <interface>Loop</interface> option in the configuration, in which case it will go back to the first image and continue the slideshow). Depending on the interval set in the configuration the images will change faster or slower.</para>
+
+<para>Stop the slideshow clicking on the same button in the top bar that you used to start it (this time its icon will have changed to a pause or stop icon).</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="toggle_slideshow" signalName="triggered()"/>
+ <nextStep id="change to browse mode from view mode"/>
+ </reaction>
+ </step>
+ <step id="change to browse mode from view mode">
+ <text><para>Besides the automatic image change performed by the slideshow you can change the current image using the <interface>Previous</interface> and <interface>Next</interface> buttons in the top bar, or clicking on a specific image in the thumbnail list (which can be shown or hidden in the <interface>Configuration</interface>).</para>
+
+<para>You can also change to full screen browse mode to select the image there. To do this, just click in the browse mode button in the top bar (its icon is a browser with several files).</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="browse" signalName="triggered()"/>
+ <nextStep id="change back to view mode"/>
+ </reaction>
+ </step>
+ <step id="change back to view mode">
+ <text><para>After selecting the desired image you can go back to the full screen view mode like the first time, that is, clicking on the view mode button in the top bar.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="view" signalName="triggered()"/>
+ <nextStep id="zoom in"/>
+ </reaction>
+ </step>
+ <step id="zoom in">
+ <text><para>Even if the full screen view mode shows the image fit to the screen size you can still zoom it in.</para>
+
+<para>Click with the right mouse button in the image. Then, in the menu that pop ups, click on <interface>Zoom in</interface>.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="view_zoom_in" signalName="triggered()"/>
+ <nextStep id="leave fullscreen mode"/>
+ </reaction>
+ </step>
+ <step id="leave fullscreen mode">
+ <text><para>Changing to the normal interface from the full screen interface is done in the same way in the view mode and in the browse mode. Just click in the <interface>Leave fullscreen</interface> button in the top bar.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="leave_fullscreen" signalName="triggered()"/>
+ <nextStep id="end"/>
+ </reaction>
+ </step>
+ <step id="end">
+ <text><para>And that is all. We have seen how to use the full screen interface for both the browse and view modes.</para></text>
+ </step>
+</tutorial>
Added: trunk/web-src/data/files/examples/gwenview.patch
===================================================================
--- trunk/web-src/data/files/examples/gwenview.patch (rev 0)
+++ trunk/web-src/data/files/examples/gwenview.patch 2012-08-30 14:34:37 UTC (rev 383)
@@ -0,0 +1,307 @@
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index d1a192d..d79dbf5 100644
+--- a/CMakeLists.txt
++++ b/CMakeLists.txt
+@@ -45,6 +45,9 @@ endif (NOT GWENVIEW_SEMANTICINFO_BACKEND_NONE)
+ find_package(LibKonq)
+ macro_log_feature(LIBKONQ_FOUND "libkonq" "Provides file management features" "http://www.kde.org" TRUE "" "")
+
++macro_optional_find_package(KTutorial "0.5")
++macro_log_feature(KTUTORIAL_FOUND "KTutorial" "Provides interactive tutorials support" "http://ktutorial.sourceforge.net" FALSE "0.5")
++
+ ## Global settings
+
+ # Avoid some build-time warnings in Nepomuk
+@@ -73,6 +76,7 @@ add_subdirectory(icons)
+ add_subdirectory(cursors)
+ add_subdirectory(color-schemes)
+ add_subdirectory(doc)
++add_subdirectory(tutorials)
+
+ configure_file(config-gwenview.h.cmake ${CMAKE_CURRENT_BINARY_DIR}/config-gwenview.h)
+
+diff --git a/Messages.sh b/Messages.sh
+index 6462d4e..078872d 100644
+--- a/Messages.sh
++++ b/Messages.sh
+@@ -1,3 +1,3 @@
+ #! /bin/sh
+ $EXTRACTRC `find . -name "*.ui" -o -name "*.rc" -o -name "*.kcfg" ` >> rc.cpp
+-$XGETTEXT `find . -name "*.cpp" -o -name "*.h"` -o $podir/gwenview.pot
++$XGETTEXT `find . -name "*.cpp" -o -name "*.h"` `find tutorials -name "*.js"` -o $podir/gwenview.pot
+diff --git a/app/CMakeLists.txt b/app/CMakeLists.txt
+index e039198..0478d5d 100644
+--- a/app/CMakeLists.txt
++++ b/app/CMakeLists.txt
+@@ -9,6 +9,11 @@ if (KIPI_FOUND)
+ include_directories(${KIPI_INCLUDE_DIR})
+ endif (KIPI_FOUND)
+
++if(KTUTORIAL_FOUND)
++ add_definitions(-DKTUTORIAL_FOUND)
++ include_directories(${KTUTORIAL_INCLUDE_DIRS})
++endif(KTUTORIAL_FOUND)
++
+ # For lib/gwenviewconfig.h and config-gwenview.h
+ include_directories(
+ ${CMAKE_CURRENT_BINARY_DIR}/..
+@@ -96,6 +101,10 @@ if (NOT GWENVIEW_SEMANTICINFO_BACKEND_NONE)
+ target_link_libraries(gwenview ${NEPOMUK_LIBRARIES})
+ endif (NOT GWENVIEW_SEMANTICINFO_BACKEND_NONE)
+
++if(KTUTORIAL_FOUND)
++ target_link_libraries(gwenview ${KTUTORIAL_LIBRARIES})
++endif(KTUTORIAL_FOUND)
++
+ install(TARGETS gwenview
+ ${INSTALL_TARGETS_DEFAULT_ARGS})
+
+diff --git a/app/gwenviewui.rc b/app/gwenviewui.rc
+index 0b1baad..da0e4a7 100644
+--- a/app/gwenviewui.rc
++++ b/app/gwenviewui.rc
+@@ -86,6 +86,9 @@
+ <Action name="options_configure_toolbars"/>
+ <Action name="options_configure"/>
+ </Menu>
++ <Menu name="help">
++ <DefineGroup name="ktutorial"/>
++ </Menu>
+ </MenuBar>
+
+ <ToolBar name="mainToolBar" noMerge="1">
+diff --git a/app/mainwindow.cpp b/app/mainwindow.cpp
+index 27d9584..682a8b8 100644
+--- a/app/mainwindow.cpp
++++ b/app/mainwindow.cpp
+@@ -60,6 +60,10 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+ #include <KXMLGUIFactory>
+ #include <KWindowSystem>
+
++#ifdef KTUTORIAL_FOUND
++#include <ktutorial/KTutorial.h>
++#endif
++
+ // Local
+ #include "configdialog.h"
+ #include "contextmanager.h"
+@@ -852,6 +856,15 @@ MainWindow::MainWindow()
+ updatePreviousNextActions();
+ d->mSaveBar->initActionDependentWidgets();
+
++#ifdef KTUTORIAL_FOUND
++ //Hack to make actions usable by KTutorial.
++ foreach (QAction* action, actionCollection()->actions()) {
++ action->setParent(this);
++ }
++
++ ktutorial::KTutorial::self()->setup(this);
++#endif
++
+ createGUI();
+ loadConfig();
+
+diff --git a/tutorials/CMakeLists.txt b/tutorials/CMakeLists.txt
+new file mode 100644
+index 0000000..f6f836a
+--- /dev/null
++++ b/tutorials/CMakeLists.txt
+@@ -0,0 +1 @@
++install(FILES fullScreenInterface.js DESTINATION ${DATA_INSTALL_DIR}/gwenview/tutorials/)
+diff --git a/tutorials/fullScreenInterface.js b/tutorials/fullScreenInterface.js
+new file mode 100644
+index 0000000..0c4153d
+--- /dev/null
++++ b/tutorials/fullScreenInterface.js
+@@ -0,0 +1,191 @@
++t = Kross.module("kdetranslation");
++
++tutorial.tutorialInformationAsObject().setName(t.i18n("Full screen interface"));
++tutorial.tutorialInformationAsObject().setDescription(t.i18n("An overview of the full screen interface of Gwenview."));
++
++//Step start
++startStep = ktutorial.newStep("start");
++startStep.setText(t.i18nc("@info", "<para>Gwenview features two modes: browse and view. In versions prior to 2.9 only the view mode had also a full screen interface. In Gwenview 2.9 a full screen interface was added for the browse mode too.</para>\n\n<para>This tutorial will show you an overview of the full screen interface for browse and view modes. We will start by looking at the full screen browse mode, so browse to a folder with several images and, then, change to full screen.</para>\n\n<para>To change to full screen you can click on the <interface>Full screen</interface> button in the <link url=\"widget:mainToolBar\">tool bar</link>, or click on the <interface>View|Full screen mode</interface> menu item in the menu bar.</para>"));
++
++function startStepSetup(step) {
++ waitForStepActivation = ktutorial.newWaitFor("WaitForStepActivation");
++ waitForStepActivation.setStep(tutorial, step);
++
++ waitForVisibleInStartMainPage = ktutorial.newWaitFor("WaitForProperty");
++ waitForVisibleInStartMainPage.setProperty(ktutorial.findObject("StartMainPage"), "visible", true);
++
++ waitForAnd = ktutorial.newWaitFor("WaitForAnd");
++ waitForAnd.add(waitForStepActivation);
++ waitForAnd.add(waitForVisibleInStartMainPage);
++ step.addWaitFor(waitForAnd, "start when start page is selected");
++
++ waitForStepActivation2 = ktutorial.newWaitFor("WaitForStepActivation");
++ waitForStepActivation2.setStep(tutorial, step);
++
++ waitForVisibleInStartMainPage2 = ktutorial.newWaitFor("WaitForProperty");
++ waitForVisibleInStartMainPage2.setProperty(ktutorial.findObject("StartMainPage"), "visible", false);
++
++ waitForVisibleInBrowseMainPage = ktutorial.newWaitFor("WaitForProperty");
++ waitForVisibleInBrowseMainPage.setProperty(ktutorial.findObject("BrowseMainPage"), "visible", false);
++
++ waitForAnd2 = ktutorial.newWaitFor("WaitForAnd");
++ waitForAnd2.add(waitForStepActivation2);
++ waitForAnd2.add(waitForVisibleInStartMainPage2);
++ waitForAnd2.add(waitForVisibleInBrowseMainPage);
++ step.addWaitFor(waitForAnd2, "start when view page is selected");
++
++ waitForTriggeredByFullscreen = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByFullscreen.setSignal(ktutorial.findObject("fullscreen"), "triggered()");
++ step.addWaitFor(waitForTriggeredByFullscreen, "fullscreen browse mode");
++}
++connect(startStep, "setup(QObject*)",
++ this, "startStepSetup(QObject*)");
++
++tutorial.addStep(startStep);
++
++//Step start when start page is selected
++startWhenStartPageIsSelectedStep = ktutorial.newStep("start when start page is selected");
++startWhenStartPageIsSelectedStep.setText(t.i18nc("@info", "<para>Gwenview features two modes: browse and view. In versions prior to 2.9 only the view mode had also a full screen interface. In Gwenview 2.9 a full screen interface was added for the browse mode too.</para>\n\n<para>This tutorial will show you an overview of the full screen interface for browse and view modes. We will start by looking at the full screen browse mode so, first, change to browse mode.</para>\n\n<para>You can change to browse mode from the start page by double clicking on any of your <link url=\"widget:mHistoryWidget\">recent folders</link> or by single clicking on any of your <link url=\"widget:mPlacesTagsWidget\">places</link>.</para>"));
++
++function startWhenStartPageIsSelectedStepSetup(step) {
++ waitForTriggeredByBrowse = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByBrowse.setSignal(ktutorial.findObject("browse"), "triggered()");
++ step.addWaitFor(waitForTriggeredByBrowse, "enter fullscreen in browser mode");
++}
++connect(startWhenStartPageIsSelectedStep, "setup(QObject*)",
++ this, "startWhenStartPageIsSelectedStepSetup(QObject*)");
++
++tutorial.addStep(startWhenStartPageIsSelectedStep);
++
++//Step start when view page is selected
++startWhenViewPageIsSelectedStep = ktutorial.newStep("start when view page is selected");
++startWhenViewPageIsSelectedStep.setText(t.i18nc("@info", "<para>Gwenview features two modes: browse and view. In versions prior to 2.9 only the view mode had also a full screen interface. In Gwenview 2.9 a full screen interface was added for the browse mode too.</para>\n\n<para>This tutorial will show you an overview of the full screen interface for browse and view modes. We will start by looking at the full screen browse mode so, first, change to browse mode.</para>\n\n<para>You can change to browse mode from the view mode by clicking on the <interface>Browse</interface> button in the <link url=\"widget:mainToolBar\">tool bar</link>, or by clicking on the <interface>View|Browse</interface> menu item in the menu bar.</para>"));
++
++function startWhenViewPageIsSelectedStepSetup(step) {
++ waitForTriggeredByBrowse = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByBrowse.setSignal(ktutorial.findObject("browse"), "triggered()");
++ step.addWaitFor(waitForTriggeredByBrowse, "enter fullscreen in browser mode");
++}
++connect(startWhenViewPageIsSelectedStep, "setup(QObject*)",
++ this, "startWhenViewPageIsSelectedStepSetup(QObject*)");
++
++tutorial.addStep(startWhenViewPageIsSelectedStep);
++
++//Step enter fullscreen in browser mode
++enterFullscreenInBrowserModeStep = ktutorial.newStep("enter fullscreen in browser mode");
++enterFullscreenInBrowserModeStep.setText(t.i18nc("@info", "<para>Now browse to a folder with several images. Then, change to full screen.</para>\n\n<para>To change to full screen you can click on the <interface>Full screen</interface> button in the <link url=\"widget:mainToolBar\">tool bar</link>, or click on the <interface>View|Full screen mode</interface> menu item in the menu bar.</para>"));
++
++function enterFullscreenInBrowserModeStepSetup(step) {
++ waitForTriggeredByFullscreen = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByFullscreen.setSignal(ktutorial.findObject("fullscreen"), "triggered()");
++ step.addWaitFor(waitForTriggeredByFullscreen, "fullscreen browse mode");
++}
++connect(enterFullscreenInBrowserModeStep, "setup(QObject*)",
++ this, "enterFullscreenInBrowserModeStepSetup(QObject*)");
++
++tutorial.addStep(enterFullscreenInBrowserModeStep);
++
++//Step fullscreen browse mode
++fullscreenBrowseModeStep = ktutorial.newStep("fullscreen browse mode");
++fullscreenBrowseModeStep.setText(t.i18nc("@info", "<para>As you can see, the full screen interface for browse mode is pretty much the same as the normal interface. However, it does not have a menu bar, and neither a tool bar.</para>\n\n<para>It does have, though, a <link url=\"widget:mStatusBarContainer\">status bar</link>, so you can use it to <link url=\"widget:mToggleSideBarButton\">show or hide the side bar</link>, or <link url=\"widget:mThumbnailSlider\">change the size of the thumbnails</link>. It also contains a top bar with a few buttons and the <link url=\"widget:mUrlNavigatorContainer\">navigation bar</link> showing the current folder path.</para>\n\n<para>As the full screen interface for the browse mode is pretty much like its normal interface we will change now to the full screen view mode.</para>\n\n<para>To change to the view mode, select an image and then click on the view mode button in the top bar (its icon is a single picture).</para>"));
++
++function fullscreenBrowseModeStepSetup(step) {
++ waitForTriggeredByView = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByView.setSignal(ktutorial.findObject("view"), "triggered()");
++ step.addWaitFor(waitForTriggeredByView, "fullscreen view mode");
++}
++connect(fullscreenBrowseModeStep, "setup(QObject*)",
++ this, "fullscreenBrowseModeStepSetup(QObject*)");
++
++tutorial.addStep(fullscreenBrowseModeStep);
++
++//Step fullscreen view mode
++fullscreenViewModeStep = ktutorial.newStep("fullscreen view mode");
++fullscreenViewModeStep.setText(t.i18nc("@info", "<para>The full screen interface for the view mode differs a lot more from its normal interface. The full screen interface only contains the selected image (or images) and an <link url=\"widget:fullScreenBar\">auto-hiding top bar</link> (move the cursor to the top of the screen and the bar will appear, move the cursor outside the bar and the bar will dissapear).</para>\n\n<para>This full screen interface is designed to show a slideshow of your images. The slideshow (and other details of the full screen interface) can be configured clicking on the <interface>Configuration</interface> button in the top bar.</para>\n\n<para>Now start the slideshow. To do this, just click on the <interface>Start slideshow</interface> button (its icon is a <emphasis>Play</emphasis> icon) in the top bar.</para>"));
++
++function fullscreenViewModeStepSetup(step) {
++ waitForTriggeredByToggle_slideshow = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByToggle_slideshow.setSignal(ktutorial.findObject("toggle_slideshow"), "triggered()");
++ step.addWaitFor(waitForTriggeredByToggle_slideshow, "slideshow");
++}
++connect(fullscreenViewModeStep, "setup(QObject*)",
++ this, "fullscreenViewModeStepSetup(QObject*)");
++
++tutorial.addStep(fullscreenViewModeStep);
++
++//Step slideshow
++slideshowStep = ktutorial.newStep("slideshow");
++slideshowStep.setText(t.i18nc("@info", "<para>The slideshow starts from the current image and shows all the images in the current folder, stopping at the last one (unless you check the <interface>Loop</interface> option in the configuration, in which case it will go back to the first image and continue the slideshow). Depending on the interval set in the configuration the images will change faster or slower.</para>\n\n<para>Stop the slideshow clicking on the same button in the top bar that you used to start it (this time its icon will have changed to a pause or stop icon).</para>"));
++
++function slideshowStepSetup(step) {
++ waitForTriggeredByToggle_slideshow = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByToggle_slideshow.setSignal(ktutorial.findObject("toggle_slideshow"), "triggered()");
++ step.addWaitFor(waitForTriggeredByToggle_slideshow, "change to browse mode from view mode");
++}
++connect(slideshowStep, "setup(QObject*)",
++ this, "slideshowStepSetup(QObject*)");
++
++tutorial.addStep(slideshowStep);
++
++//Step change to browse mode from view mode
++changeToBrowseModeFromViewModeStep = ktutorial.newStep("change to browse mode from view mode");
++changeToBrowseModeFromViewModeStep.setText(t.i18nc("@info", "<para>Besides the automatic image change performed by the slideshow you can change the current image using the <interface>Previous</interface> and <interface>Next</interface> buttons in the top bar, or clicking on a specific image in the thumbnail list (which can be shown or hidden in the <interface>Configuration</interface>).</para>\n\n<para>You can also change to full screen browse mode to select the image there. To do this, just click in the browse mode button in the top bar (its icon is a browser with several files).</para>"));
++
++function changeToBrowseModeFromViewModeStepSetup(step) {
++ waitForTriggeredByBrowse = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByBrowse.setSignal(ktutorial.findObject("browse"), "triggered()");
++ step.addWaitFor(waitForTriggeredByBrowse, "change back to view mode");
++}
++connect(changeToBrowseModeFromViewModeStep, "setup(QObject*)",
++ this, "changeToBrowseModeFromViewModeStepSetup(QObject*)");
++
++tutorial.addStep(changeToBrowseModeFromViewModeStep);
++
++//Step change back to view mode
++changeBackToViewModeStep = ktutorial.newStep("change back to view mode");
++changeBackToViewModeStep.setText(t.i18nc("@info", "<para>After selecting the desired image you can go back to the full screen view mode like the first time, that is, clicking on the view mode button in the top bar.</para>"));
++
++function changeBackToViewModeStepSetup(step) {
++ waitForTriggeredByView = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByView.setSignal(ktutorial.findObject("view"), "triggered()");
++ step.addWaitFor(waitForTriggeredByView, "zoom in");
++}
++connect(changeBackToViewModeStep, "setup(QObject*)",
++ this, "changeBackToViewModeStepSetup(QObject*)");
++
++tutorial.addStep(changeBackToViewModeStep);
++
++//Step zoom in
++zoomInStep = ktutorial.newStep("zoom in");
++zoomInStep.setText(t.i18nc("@info", "<para>Even if the full screen view mode shows the image fit to the screen size you can still zoom it in.</para>\n\n<para>Click with the right mouse button in the image. Then, in the menu that pop ups, click on <interface>Zoom in</interface>.</para>"));
++
++function zoomInStepSetup(step) {
++ waitForTriggeredByView_zoom_in = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByView_zoom_in.setSignal(ktutorial.findObject("view_zoom_in"), "triggered()");
++ step.addWaitFor(waitForTriggeredByView_zoom_in, "leave fullscreen mode");
++}
++connect(zoomInStep, "setup(QObject*)",
++ this, "zoomInStepSetup(QObject*)");
++
++tutorial.addStep(zoomInStep);
++
++//Step leave fullscreen mode
++leaveFullscreenModeStep = ktutorial.newStep("leave fullscreen mode");
++leaveFullscreenModeStep.setText(t.i18nc("@info", "<para>Changing to the normal interface from the full screen interface is done in the same way in the view mode and in the browse mode. Just click in the <interface>Leave fullscreen</interface> button in the top bar.</para>"));
++
++function leaveFullscreenModeStepSetup(step) {
++ waitForTriggeredByLeave_fullscreen = ktutorial.newWaitFor("WaitForSignal");
++ waitForTriggeredByLeave_fullscreen.setSignal(ktutorial.findObject("leave_fullscreen"), "triggered()");
++ step.addWaitFor(waitForTriggeredByLeave_fullscreen, "end");
++}
++connect(leaveFullscreenModeStep, "setup(QObject*)",
++ this, "leaveFullscreenModeStepSetup(QObject*)");
++
++tutorial.addStep(leaveFullscreenModeStep);
++
++//Step end
++endStep = ktutorial.newStep("end");
++endStep.setText(t.i18nc("@info", "<para>And that is all. We have seen how to use the full screen interface for both the browse and view modes.</para>"));
++
++tutorial.addStep(endStep);
++
Added: trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml
===================================================================
--- trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml (rev 0)
+++ trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml 2012-08-30 14:34:37 UTC (rev 383)
@@ -0,0 +1,202 @@
+<?xml version="1.0" encoding="utf-8"?>
+<tutorial name="Simple slide transition between two clips">
+ <description>Basic usage of "slide" transition.</description>
+ <license>Copyright (C) 2012 by Daniel Calviño Sánchez <dan...@gm...>
+
+This tutorial is licensed under the Creative Commons Attribution-ShareAlike License (http://creativecommons.org/licenses/by-sa/3.0/).</license>
+ <step id="start">
+ <text><para>In this tutorial you will learn how to add a <emphasis>slide</emphasis> transition between two clips and how to do some basic changes in the transition.</para>
+
+<para>For this tutorial you will need a project with at least two video tracks in the <link url="widget:TimeLine_UI">timeline</link>, and you will need too two clips.</para>
+
+<para>Do you want to use your own clips, or do you want to add two example clips just for this tutorial?</para></text>
+ <reaction triggerType="OptionSelected" responseType="NextStep">
+ <option name="I will use my own clips"/>
+ <nextStep id="add clips to timeline"/>
+ </reaction>
+ <reaction triggerType="OptionSelected" responseType="NextStep">
+ <option name="Let's add the example clips"/>
+ <nextStep id="add the first color clip"/>
+ </reaction>
+ </step>
+ <step id="add the first color clip">
+ <text><para>First, we will add a new color clip.</para>
+
+<para>To do this there are several options:
+<list>
+<item>In the menu bar, you can select <interface>Project|Add color clip</interface>.</item>
+
+<item>In the <link url="widget:project_tree">project tree</link>, you can click with the right mouse button on the clip list and then select <interface>Add color clip</interface>.</item>
+
+<item>In the project tree, you can click with the left mouse button on the arrow near to the <interface>Add clip</interface> button (its icon is a film with a <emphasis>+</emphasis> sign), and then select <interface>Add color clip</interface>.</item>
+</list>
+</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForWindow windowObjectName="ColorClip_UI"/>
+ <nextStep id="set name for first color clip"/>
+ </reaction>
+ </step>
+ <step id="set name for first color clip">
+ <text><para>In the dialog that has just been opened, change the <link url="widget:clip_name">clip name</link> to <emphasis>First clip</emphasis>.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForProperty objectName="clip_name" propertyName="text" value="t.i18n("First clip")"/>
+ <nextStep id="set color for first color clip"/>
+ </reaction>
+ </step>
+ <step id="set color for first color clip">
+ <text><para>Change the <link url="widget:clip_color">color</link> to black.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForStepActivation/>
+ <waitForProperty objectName="clip_color" propertyName="color" value=""#000000""/>
+ </waitForComposed>
+ <nextStep id="set duration for first color clip"/>
+ </reaction>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForProperty objectName="clip_color" propertyName="color" value=""#000000""/>
+ <nextStep id="set duration for first color clip"/>
+ </reaction>
+ </step>
+ <step id="set duration for first color clip">
+ <text>Set the clip duration to something around 4 or 5 seconds and then accept the dialog.</text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="ColorClip_UI" signalName="accepted()"/>
+ <nextStep id="add the second color clip"/>
+ </reaction>
+ </step>
+ <step id="add the second color clip">
+ <text><para>Now add another new color clip.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForWindow windowObjectName="ColorClip_UI"/>
+ <nextStep id="set name for second color clip"/>
+ </reaction>
+ </step>
+ <step id="set name for second color clip">
+ <text><para>Change the <link url="widget:clip_name">clip name</link> to <emphasis>Second clip</emphasis>.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForProperty objectName="clip_name" propertyName="text" value="t.i18n("Second clip")"/>
+ <nextStep id="set color for second color clip"/>
+ </reaction>
+ </step>
+ <step id="set color for second color clip">
+ <text><para>Change the <link url="widget:clip_color">color</link> to white.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForStepActivation/>
+ <waitForProperty objectName="clip_color" propertyName="color" value=""#FFFFFF""/>
+ </waitForComposed>
+ <nextStep id="set duration for second color clip"/>
+ </reaction>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForProperty objectName="clip_color" propertyName="color" value=""#FFFFFF""/>
+ <nextStep id="set duration for second color clip"/>
+ </reaction>
+ </step>
+ <step id="set duration for second color clip">
+ <text>Set the clip duration to something around 4 or 5 seconds and then accept the dialog.</text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="ColorClip_UI" signalName="accepted()"/>
+ <nextStep id="add clips to timeline"/>
+ </reaction>
+ </step>
+ <step id="add clips to timeline">
+ <text><para>Add the first clip to a video track in the <link url="widget:tracks_frame">timeline</link>. The track must have at least another video track below it.</para>
+
+<para>Then add the second clip to the track below the track of the first clip. Make sure that the two clips overlap by one or two seconds.</para>
+
+<para>Now it is time to add the <emphasis>slide</emphasis> transition. Look at the first clip in the timeline. One of its lower corners overlaps the second clip. Put the cursor on that corner, and an arrow will appear on it. Then, click with the right button of the mouse and, in the menu that pops up, select <interface>Add transition|Slide</interface>.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForSignal emitterName="transition_slide" signalName="activated()"/>
+ <nextStep id="select slide transition"/>
+ </reaction>
+ </step>
+ <step id="select slide transition">
+ <text><para>A <emphasis>slide</emphasis> transition has been added between the first and the second clip. You can see it by the yellow rectangle placed between the clips, in the area they overlap.</para>
+
+<para>Click with the left mouse button on that yellow rectangle to see the transition properties. Note that if you click in the upper part or in the lower part of the yellow rectangle you may select the clips instead; if that happens, just try again to select the yellow rectangle.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForStepActivation/>
+ <waitForProperty objectName="transition" propertyName="visible" value="false"/>
+ </waitForComposed>
+ <nextStep id="select slide transition when transition dock is hidden"/>
+ </reaction>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForEvent receiverName="transitionList" eventName="EnabledChange"/>
+ <waitForProperty objectName="transitionList" propertyName="enabled" value="true"/>
+ </waitForComposed>
+ <nextStep id="change slide transition length"/>
+ </reaction>
+ </step>
+ <step id="select slide transition when transition dock is hidden">
+ <text><para>A <emphasis>slide</emphasis> transition has been added between the first and the second clip. You can see it by the yellow rectangle placed between the clips, in the area they overlap.</para>
+
+<para>The transition panel is hidden. Before going any further, show that panel to be able to see the transition properties (<interface>View|Transition</interface>).</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForProperty objectName="TransitionSettings_UI" propertyName="visible" value="true"/>
+ <waitForEvent receiverName="TransitionSettings_UI" eventName="Show"/>
+ </waitForComposed>
+ <nextStep id="select slide transition after showing dock"/>
+ </reaction>
+ </step>
+ <step id="select slide transition after showing dock">
+ <text><para>Now, click with the left mouse button on the yellow rectangle to see the transition properties. Note that if you click in the upper part or in the lower part of the yellow rectangle you may select the clips instead; if that happens, just try again to select the yellow rectangle.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForEvent receiverName="transitionList" eventName="EnabledChange"/>
+ <waitForProperty objectName="transitionList" propertyName="enabled" value="true"/>
+ </waitForComposed>
+ <nextStep id="change slide transition length"/>
+ </reaction>
+ </step>
+ <step id="change slide transition length">
+ <text><para>By default, the second clip slides from the left to the center of the image. You can use the project monitor to see how it looks.</para>
+
+<para>Suppose that you have seen the transition and found that it was too slow. In that case, you have to reduce the transition length for it to become quicker.</para>
+
+<para>The easiest way to do this is just moving the second clip so its overlapping with the first clip is reduced. If you do it, as soon as you release the mouse button (not while you are dragging the clip), you will see how the transition is automatically resized to fit with the new position of the clips. You can check again the project monitor after moving the clip to see how it looks now.</para>
+
+<para>Once you are done changing the transition length we will see how to make changes in the transition itself.</para></text>
+ <reaction triggerType="OptionSelected" responseType="NextStep">
+ <option name="Continue"/>
+ <nextStep id="edit slide transition start"/>
+ </reaction>
+ </step>
+ <step id="edit slide transition start">
+ <text><para>Instead of sliding from left to center we will change the transition to slide from bottom to center.</para>
+
+<para>The start position of the slide is defined by the button toggled in the <link url="widget:Wipeval_UI/groupBox">start parameters</link> of the <emphasis>slide transition</emphasis>. So, to start from the bottom, just toggle the <link url="widget:start_down">bottom button</link>.</para>
+
+<para>If you check the project monitor after toggling the bottom button you will see how the transition has changed, sliding as expected from the bottom instead of from the left.</para>
+
+<para>And that is all. We have seen how to add a <emphasis>slide</emphasis> transition between two clips and how to make some basic changes on that transition.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForStepActivation/>
+ <waitForProperty objectName="transitionList" propertyName="enabled" value="false"/>
+ </waitForComposed>
+ <nextStep id="edit slide transition start when transition not selected"/>
+ </reaction>
+ </step>
+ <step id="edit slide transition start when transition not selected">
+ <text><para>Instead of sliding from left to center we will change the transition to slide from bottom to center.</para>
+
+<para>First you have to select the transition again, as it was deselected when moving the clip.</para></text>
+ <reaction triggerType="ConditionMet" responseType="NextStep">
+ <waitForComposed compositionType="And">
+ <waitForEvent receiverName="transitionList" eventName="EnabledChange"/>
+ <waitForProperty objectName="transitionList" propertyName="enabled" value="true"/>
+ </waitForComposed>
+ <nextStep id="edit slide transition start after selecting the transition"/>
+ </reaction>
+ </step>
+ <step id="edit slide transition start after selecting the transition">
+ <text><para>The start position of the slide is defined by the button toggled in the <link url="widget:Wipeval_UI/groupBox">start parameters</link> of the <emphasis>slide transition</emphasis>. So, to start from the bottom, just toggle the <link url="widget:start_down">bottom button</link>.</para>
+
+<para>If you check the project monitor after toggling the bottom button you will see how the transition has changed, sliding as expected from the bottom instead of from the left.</para>
+
+<para>And that is all. We have seen how to add a <emphasis>slide</emphasis> transition between two clips and how to make some basic changes on that transition.</para></text>
+ </step>
+</tutorial>
Added: trunk/web-src/data/files/examples/kdenlive.patch
===================================================================
--- trunk/web-src/data/files/examples/kdenlive.patch (rev 0)
+++ trunk/web-src/data/files/examples/kdenlive.patch 2012-08-30 14:34:37 UTC (rev 383)
@@ -0,0 +1,415 @@
+diff --git a/Messages.sh b/Messages.sh
+index f69bd55..44a01a4 100755
+--- a/Messages.sh
++++ b/Messages.sh
+@@ -5,5 +5,5 @@ kdenlive_subdirs="plugins renderer src src/widgets"
+ $EXTRACTRC --tag=name --tag=description --tag=label --tag=comment --tag=paramlistdisplay effects/*.xml data/kdenliveeffectscategory.rc >> rc.cpp
+ $EXTRACTRC `find $kdenlive_subdirs -name \*.rc -a ! -name encodingprofiles.rc -o -name \*.ui` >> rc.cpp
+
+-$XGETTEXT `find $kdenlive_subdirs -name \*.cpp -o -name \*.h` *.cpp -o $podir/kdenlive.pot
++$XGETTEXT `find $kdenlive_subdirs -name \*.cpp -o -name \*.h` `find data -name \*.js` *.cpp -o $podir/kdenlive.pot
+ rm -f rc.cpp
+diff --git a/data/CMakeLists.txt b/data/CMakeLists.txt
+index b593105..47e0c65 100644
+--- a/data/CMakeLists.txt
++++ b/data/CMakeLists.txt
+@@ -2,3 +2,5 @@ install(FILES banner.png timeline_nothumbs.png timeline_athumbs.png timeline_vth
+ install( FILES kdenliveeffectscategory.rc DESTINATION ${CONFIG_INSTALL_DIR} )
+ install (FILES kdenlive.xpm DESTINATION share/pixmaps)
+ install (FILES kdenlive.menu DESTINATION share/menu RENAME kdenlive)
++
++install(FILES simpleSlideTransitionBetweenTwoClips.js DESTINATION ${DATA_INSTALL_DIR}/kdenlive/tutorials)
+diff --git a/data/simpleSlideTransitionBetweenTwoClips.js b/data/simpleSlideTransitionBetweenTwoClips.js
+new file mode 100644
+index 0000000..375f877
+--- /dev/null
++++ b/data/simpleSlideTransitionBetweenTwoClips.js
+@@ -0,0 +1,310 @@
++/*********************************************************************************************************************************************
++ * Copyright (C) 2012 by Daniel Calviño Sánchez <dan...@gm...> *
++ * *
++ * This tutorial is licensed under the Creative Commons Attribution-ShareAlike License (http://creativecommons.org/licenses/by-sa/3.0/). *
++ *********************************************************************************************************************************************/
++
++t = Kross.module("kdetranslation");
++
++tutorial.tutorialInformationAsObject().setName(t.i18n("Simple slide transition between two clips"));
++tutorial.tutorialInformationAsObject().setDescription(t.i18n("Basic usage of \"slide\" transition."));
++
++//Step start
++startStep = ktutorial.newStep("start");
++startStep.setText(t.i18nc("@info", "<para>In this tutorial you will learn how to add a <emphasis>slide</emphasis> transition between two clips and how to do some basic changes in the transition.</para>\n\n<para>For this tutorial you will need a project with at least two video tracks in the <link url=\"widget:TimeLine_UI\">timeline</link>, and you will need too two clips.</para>\n\n<para>Do you want to use your own clips, or do you want to add two example clips just for this tutorial?</para>"));
++
++function startStepSetup(step) {
++ iWillUseMyOwnClipsOption = ktutorial.newOption(t.i18nc("@action Tutorial option", "I will use my own clips"));
++ step.addOption(iWillUseMyOwnClipsOption, "add clips to timeline");
++
++ letSAddTheExampleClipsOption = ktutorial.newOption(t.i18nc("@action Tutorial option", "Let's add the example clips"));
++ step.addOption(letSAddTheExampleClipsOption, "add the first color clip");
++}
++connect(startStep, "setup(QObject*)",
++ this, "startStepSetup(QObject*)");
++
++tutorial.addStep(startStep);
++
++//Step add the first color clip
++addTheFirstColorClipStep = ktutorial.newStep("add the first color clip");
++addTheFirstColorClipStep.setText(t.i18nc("@info", "<para>First, we will add a new color clip.</para>\n\n<para>To do this there are several options:\n<list>\n<item>In the menu bar, you can select <interface>Project|Add color clip</interface>.</item>\n\n<item>In the <link url=\"widget:project_tree\">project tree</link>, you can click with the right mouse button on the clip list and then select <interface>Add color clip</interface>.</item>\n\n<item>In the project tree, you can click with the left mouse button on the arrow near to the <interface>Add clip</interface> button (its icon is a film with a <emphasis>+</emphasis> sign), and then select <interface>Add color clip</interface>.</item>\n</list>\n</para>"));
++
++function addTheFirstColorClipStepSetup(step) {
++ waitForColorClip_UIToBeShown = ktutorial.newWaitFor("WaitForWindow");
++ waitForColorClip_UIToBeShown.setWindowObjectName("ColorClip_UI");
++ step.addWaitFor(waitForColorClip_UIToBeShown, "set name for first color clip");
++}
++connect(addTheFirstColorClipStep, "setup(QObject*)",
++ this, "addTheFirstColorClipStepSetup(QObject*)");
++
++tutorial.addStep(addTheFirstColorClipStep);
++
++//Step set name for first color clip
++setNameForFirstColorClipStep = ktutorial.newStep("set name for first color clip");
++setNameForFirstColorClipStep.setText(t.i18nc("@info", "<para>In the dialog that has just been opened, change the <link url=\"widget:clip_name\">clip name</link> to <emphasis>First clip</emphasis>.</para>"));
++
++function setNameForFirstColorClipStepSetup(step) {
++ waitForTextInClip_name = ktutorial.newWaitFor("WaitForProperty");
++ waitForTextInClip_name.setProperty(ktutorial.findObject("clip_name"), "text", t.i18n("First clip"));
++ step.addWaitFor(waitForTextInClip_name, "set color for first color clip");
++}
++connect(setNameForFirstColorClipStep, "setup(QObject*)",
++ this, "setNameForFirstColorClipStepSetup(QObject*)");
++
++tutorial.addStep(setNameForFirstColorClipStep);
++
++//Step set color for first color clip
++setColorForFirstColorClipStep = ktutorial.newStep("set color for first color clip");
++setColorForFirstColorClipStep.setText(t.i18nc("@info", "<para>Change the <link url=\"widget:clip_color\">color</link> to black.</para>"));
++
++function setColorForFirstColorClipStepSetup(step) {
++ waitForStepActivation = ktutorial.newWaitFor("WaitForStepActivation");
++ waitForStepActivation.setStep(tutorial, step);
++
++ waitForColorInClip_color = ktutorial.newWaitFor("WaitForProperty");
++ waitForColorInClip_color.setProperty(ktutorial.findObject("clip_color"), "color", "#000000");
++
++ waitForAnd = ktutorial.newWaitFor("WaitForAnd");
++ waitForAnd.add(waitForStepActivation);
++ waitForAnd.add(waitForColorInClip_color);
++ step.addWaitFor(waitForAnd, "set duration for first color clip");
++
++ waitForColorInClip_color2 = ktutorial.newWaitFor("WaitForProperty");
++ waitForColorInClip_color2.setProperty(ktutorial.findObject("clip_color"), "color", "#000000");
++ step.addWaitFor(waitForColorInClip_color2, "set duration for first color clip");
++}
++connect(setColorForFirstColorClipStep, "setup(QObject*)",
++ this, "setColorForFirstColorClipStepSetup(QObject*)");
++
++tutorial.addStep(setColorForFirstColorClipStep);
++
++//Step set duration for first color clip
++setDurationForFirstColorClipStep = ktutorial.newStep("set duration for first color clip");
++setDurationForFirstColorClipStep.setText(t.i18nc("@info/plain", "Set the clip duration to something around 4 or 5 seconds and then accept the dialog."));
++
++function setDurationForFirstColorClipStepSetup(step) {
++ waitForAcceptedByColorClip_UI = ktutorial.newWaitFor("WaitForSignal");
++ waitForAcceptedByColorClip_UI.setSignal(ktutorial.findObject("ColorClip_UI"), "accepted()");
++ step.addWaitFor(waitForAcceptedByColorClip_UI, "add the second color clip");
++}
++connect(setDurationForFirstColorClipStep, "setup(QObject*)",
++ this, "setDurationForFirstColorClipStepSetup(QObject*)");
++
++tutorial.addStep(setDurationForFirstColorClipStep);
++
++//Step add the second color clip
++addTheSecondColorClipStep = ktutorial.newStep("add the second color clip");
++addTheSecondColorClipStep.setText(t.i18nc("@info", "<para>Now add another new color clip.</para>"));
++
++function addTheSecondColorClipStepSetup(step) {
++ waitForColorClip_UIToBeShown = ktutorial.newWaitFor("WaitForWindow");
++ waitForColorClip_UIToBeShown.setWindowObjectName("ColorClip_UI");
++ step.addWaitFor(waitForColorClip_UIToBeShown, "set name for second color clip");
++}
++connect(addTheSecondColorClipStep, "setup(QObject*)",
++ this, "addTheSecondColorClipStepSetup(QObject*)");
++
++tutorial.addStep(addTheSecondColorClipStep);
++
++//Step set name for second color clip
++setNameForSecondColorClipStep = ktutorial.newStep("set name for second color clip");
++setNameForSecondColorClipStep.setText(t.i18nc("@info", "<para>Change the <link url=\"widget:clip_name\">clip name</link> to <emphasis>Second clip</emphasis>.</para>"));
++
++function setNameForSecondColorClipStepSetup(step) {
++ waitForTextInClip_name = ktutorial.newWaitFor("WaitForProperty");
++ waitForTextInClip_name.setProperty(ktutorial.findObject("clip_name"), "text", t.i18n("Second clip"));
++ step.addWaitFor(waitForTextInClip_name, "set color for second color clip");
++}
++connect(setNameForSecondColorClipStep, "setup(QObject*)",
++ this, "setNameForSecondColorClipStepSetup(QObject*)");
++
++tutorial.addStep(setNameForSecondColorClipStep);
++
++//Step set color for second color clip
++setColorForSecondColorClipStep = ktutorial.newStep("set color for second color clip");
++setColorForSecondColorClipStep.setText(t.i18nc("@info", "<para>Change the <link url=\"widget:clip_color\">color</link> to white.</para>"));
++
++function setColorForSecondColorClipStepSetup(step) {
++ waitForStepActivation = ktutorial.newWaitFor("WaitForStepActivation");
++ waitForStepActivation.setStep(tutorial, step);
++
++ waitForColorInClip_color = ktutorial.newWaitFor("WaitForProperty");
++ waitForColorInClip_color.setProperty(ktutorial.findObject("clip_color"), "color", "#FFFFFF");
++
++ waitForAnd = ktutorial.newWaitFor("WaitForAnd");
++ waitForAnd.add(waitForStepActivation);
++ waitForAnd.add(waitForColorInClip_color);
++ step.addWaitFor(waitForAnd, "set duration for second color clip");
++
++ waitForColorInClip_color2 = ktutorial.newWaitFor("WaitForProperty");
++ waitForColorInClip_color2.setProperty(ktutorial.findObject("clip_color"), "color", "#FFFFFF");
++ step.addWaitFor(waitForColorInClip_color2, "set duration for second color clip");
++}
++connect(setColorForSecondColorClipStep, "setup(QObject*)",
++ this, "setColorForSecondColorClipStepSetup(QObject*)");
++
++tutorial.addStep(setColorForSecondColorClipStep);
++
++//Step set duration for second color clip
++setDurationForSecondColorClipStep = ktutorial.newStep("set duration for second color clip");
++setDurationForSecondColorClipStep.setText(t.i18nc("@info/plain", "Set the clip duration to something around 4 or 5 seconds and then accept the dialog."));
++
++function setDurationForSecondColorClipStepSetup(step) {
++ waitForAcceptedByColorClip_UI = ktutorial.newWaitFor("WaitForSignal");
++ waitForAcceptedByColorClip_UI.setSignal(ktutorial.findObject("ColorClip_UI"), "accepted()");
++ step.addWaitFor(waitForAcceptedByColorClip_UI, "add clips to timeline");
++}
++connect(setDurationForSecondColorClipStep, "setup(QObject*)",
++ this, "setDurationForSecondColorClipStepSetup(QObject*)");
++
++tutorial.addStep(setDurationForSecondColorClipStep);
++
++//Step add clips to timeline
++addClipsToTimelineStep = ktutorial.newStep("add clips to timeline");
++addClipsToTimelineStep.setText(t.i18nc("@info", "<para>Add the first clip to a video track in the <link url=\"widget:tracks_frame\">timeline</link>. The track must have at least another video track below it.</para>\n\n<para>Then add the second clip to the track below the track of the first clip. Make sure that the two clips overlap by one or two seconds.</para>\n\n<para>Now it is time to add the <emphasis>slide</emphasis> transition. Look at the first clip in the timeline. One of its lower corners overlaps the second clip. Put the cursor on that corner, and an arrow will appear on it. Then, click with the right button of the mouse and, in the menu that pops up, select <interface>Add transition|Slide</interface>.</para>"));
++
++function addClipsToTimelineStepSetup(step) {
++ waitForActivatedByTransition_slide = ktutorial.newWaitFor("WaitForSignal");
++ waitForActivatedByTransition_slide.setSignal(ktutorial.findObject("transition_slide"), "activated()");
++ step.addWaitFor(waitForActivatedByTransition_slide, "select slide transition");
++}
++connect(addClipsToTimelineStep, "setup(QObject*)",
++ this, "addClipsToTimelineStepSetup(QObject*)");
++
++tutorial.addStep(addClipsToTimelineStep);
++
++//Step select slide transition
++selectSlideTransitionStep = ktutorial.newStep("select slide transition");
++selectSlideTransitionStep.setText(t.i18nc("@info", "<para>A <emphasis>slide</emphasis> transition has been added between the first and the second clip. You can see it by the yellow rectangle placed between the clips, in the area they overlap.</para>\n\n<para>Click with the left mouse button on that yellow rectangle to see the transition properties. Note that if you click in the upper part or in the lower part of the yellow rectangle you may select the clips instead; if that happens, just try again to select the yellow rectangle.</para>"));
++
++function selectSlideTransitionStepSetup(step) {
++ waitForStepActivation = ktutorial.newWaitFor("WaitForStepActivation");
++ waitForStepActivation.setStep(tutorial, step);
++
++ waitForVisibleInTransition = ktutorial.newWaitFor("WaitForProperty");
++ waitFo...
[truncated message content] |
|
From: <dan...@us...> - 2012-09-04 22:38:51
|
Revision: 388
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=388&view=rev
Author: danxuliu
Date: 2012-09-04 22:38:45 +0000 (Tue, 04 Sep 2012)
Log Message:
-----------
Update web page to reflect the license change from GPLv3+ to GPLv2+. Two of the example tutorials where also licensed under the GPLv2+ (the third one was a derivated work, so I couldn't change its license).
Modified Paths:
--------------
trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml
trunk/web-src/data/files/examples/gwenview.patch
trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml
trunk/web-src/data/files/examples/kdenlive.patch
trunk/web-src/newsList.xml
trunk/web-src/pages/about.xml
trunk/web-src/pages/index.xml
trunk/web-src/pages/news.xml
Modified: trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml
===================================================================
--- trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/data/files/examples/gwenview-fullScreenInterface.xml 2012-09-04 22:38:45 UTC (rev 388)
@@ -1,6 +1,20 @@
<?xml version="1.0" encoding="utf-8"?>
<tutorial name="Full screen interface">
<description>An overview of the full screen interface of Gwenview.</description>
+ <license>Copyright (C) 2012 by Daniel Calviño Sánchez <dan...@gm...>
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; If not, see <http://www.gnu.org/licenses/>.</license>
<step id="start">
<text><para>Gwenview features two modes: browse and view. In versions prior to 2.9 only the view mode had also a full screen interface. In Gwenview 2.9 a full screen interface was added for the browse mode too.</para>
Modified: trunk/web-src/data/files/examples/gwenview.patch
===================================================================
--- trunk/web-src/data/files/examples/gwenview.patch 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/data/files/examples/gwenview.patch 2012-09-04 22:38:45 UTC (rev 388)
@@ -110,10 +110,27 @@
+install(FILES fullScreenInterface.js DESTINATION ${DATA_INSTALL_DIR}/gwenview/tutorials/)
diff --git a/tutorials/fullScreenInterface.js b/tutorials/fullScreenInterface.js
new file mode 100644
-index 0000000..0c4153d
+index 0000000..92665f0
--- /dev/null
+++ b/tutorials/fullScreenInterface.js
-@@ -0,0 +1,191 @@
+@@ -0,0 +1,208 @@
++/****************************************************************************
++ * Copyright (C) 2012 by Daniel Calviño Sánchez <dan...@gm...> *
++ * *
++ * This program is free software; you can redistribute it and/or modify *
++ * it under the terms of the GNU General Public License as published by *
++ * the Free Software Foundation; either version 2 of the License, or *
++ * (at your option) any later version. *
++ * *
++ * This program is distributed in the hope that it will be useful, *
++ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *
++ * GNU General Public License for more details. *
++ * *
++ * You should have received a copy of the GNU General Public License *
++ * along with this program; If not, see <http://www.gnu.org/licenses/>. *
++ ****************************************************************************/
++
+t = Kross.module("kdetranslation");
+
+tutorial.tutorialInformationAsObject().setName(t.i18n("Full screen interface"));
Modified: trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml
===================================================================
--- trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/data/files/examples/kdenlive-simpleSlideTransitionBetweenTwoClips.xml 2012-09-04 22:38:45 UTC (rev 388)
@@ -3,7 +3,18 @@
<description>Basic usage of "slide" transition.</description>
<license>Copyright (C) 2012 by Daniel Calviño Sánchez <dan...@gm...>
-This tutorial is licensed under the Creative Commons Attribution-ShareAlike License (http://creativecommons.org/licenses/by-sa/3.0/).</license>
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; If not, see <http://www.gnu.org/licenses/>.</license>
<step id="start">
<text><para>In this tutorial you will learn how to add a <emphasis>slide</emphasis> transition between two clips and how to do some basic changes in the transition.</para>
Modified: trunk/web-src/data/files/examples/kdenlive.patch
===================================================================
--- trunk/web-src/data/files/examples/kdenlive.patch 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/data/files/examples/kdenlive.patch 2012-09-04 22:38:45 UTC (rev 388)
@@ -21,15 +21,26 @@
+install(FILES simpleSlideTransitionBetweenTwoClips.js DESTINATION ${DATA_INSTALL_DIR}/kdenlive/tutorials)
diff --git a/data/simpleSlideTransitionBetweenTwoClips.js b/data/simpleSlideTransitionBetweenTwoClips.js
new file mode 100644
-index 0000000..375f877
+index 0000000..a05a9cf
--- /dev/null
+++ b/data/simpleSlideTransitionBetweenTwoClips.js
-@@ -0,0 +1,310 @@
-+/*********************************************************************************************************************************************
-+ * Copyright (C) 2012 by Daniel Calviño Sánchez <dan...@gm...> *
-+ * *
-+ * This tutorial is licensed under the Creative Commons Attribution-ShareAlike License (http://creativecommons.org/licenses/by-sa/3.0/). *
-+ *********************************************************************************************************************************************/
+@@ -0,0 +1,321 @@
++/****************************************************************************
++ * Copyright (C) 2012 by Daniel Calviño Sánchez <dan...@gm...> *
++ * *
++ * This program is free software; you can redistribute it and/or modify *
++ * it under the terms of the GNU General Public License as published by *
++ * the Free Software Foundation; either version 2 of the License, or *
++ * (at your option) any later version. *
++ * *
++ * This program is distributed in the hope that it will be useful, *
++ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *
++ * GNU General Public License for more details. *
++ * *
++ * You should have received a copy of the GNU General Public License *
++ * along with this program; If not, see <http://www.gnu.org/licenses/>. *
++ ****************************************************************************/
+
+t = Kross.module("kdetranslation");
+
Modified: trunk/web-src/newsList.xml
===================================================================
--- trunk/web-src/newsList.xml 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/newsList.xml 2012-09-04 22:38:45 UTC (rev 388)
@@ -79,4 +79,17 @@
<date>2012-08-30</date>
</fullDate>
</new>
+
+ <new>
+ <title>License changed from GPLv3+ to GPLv2+</title>
+ <summary>
+ <div xmlns="http://www.w3.org/1999/xhtml">
+ <p>I have changed the KTutorial license from GPLv3+ to GPLv2+ to ensure that any KDE application can use KTutorial (with the previous license it could be used only in applications that did not link against any GPLv2 only libraries) and to be able to move the code to KDE repositories.</p>
+ <p>I will release a new KTutorial version featuring the new license soon.</p>
+ </div>
+ </summary>
+ <fullDate>
+ <date>2012-09-04</date>
+ </fullDate>
+ </new>
</news>
Modified: trunk/web-src/pages/about.xml
===================================================================
--- trunk/web-src/pages/about.xml 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/pages/about.xml 2012-09-04 22:38:45 UTC (rev 388)
@@ -18,7 +18,7 @@
<h2><a id="project" class="anchorLink">Project overview</a></h2>
</div>
<p>KTutorial is a library (and a graphical editor) for interactive tutorials in KDE applications. Tutorials are embeded in the application itself, and react to user actions: wait for some task to be accomplished, warn if something wasn't done as it should, etcetera. As the tutorial is being followed, the system gives feedback to the user.</p>
- <p>It is licensed under the <a href="http://www.gnu.org/copyleft/gpl.html" title="GNU General Public License page">GNU GPL license</a>. It is also free as in "free beer".</p>
+ <p>It is licensed under the <a href="http://www.gnu.org/copyleft/gpl.html" title="GNU General Public License page">GNU GPL version 2 or later</a>. It is also free as in "free beer".</p>
<div class="h2Rounded">
<h2><a id="author" class="anchorLink">Author</a></h2>
@@ -34,6 +34,6 @@
<p>The web is divided in several sections that can be accessed through the links in the menu in each page. I'm not going to explain its structure, as it seems very clear and I have better things to spend my time on :P</p>
<p>You can find information about how this web is built in its own page: <a href="aboutWeb.html" title="About KTutorial project web building">About web</a>.</p>
- <p class="lastUpdated">Last updated: 2012-08-21</p>
+ <p class="lastUpdated">Last updated: 2012-09-04</p>
</page:content>
</page>
Modified: trunk/web-src/pages/index.xml
===================================================================
--- trunk/web-src/pages/index.xml 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/pages/index.xml 2012-09-04 22:38:45 UTC (rev 388)
@@ -16,7 +16,7 @@
<page:content xmlns:page="http://lusi.berlios.de/namespaces/page" xmlns="http://www.w3.org/1999/xhtml">
<h1>Main</h1>
<p>KTutorial is a library for interactive tutorials in KDE applications. Tutorials are embeded in the application itself, and reacts to user actions: waits for some task to be accomplished, warns if something wasn't done as it should, etcetera. As the tutorial is being followed, the system gives feedback to the user.</p>
- <p>It is licensed under the <a href="http://www.gnu.org/copyleft/gpl.html" title="GNU General Public License page">GNU GPL license</a>. It is also free as in "free beer".</p>
+ <p>It is licensed under the <a href="http://www.gnu.org/copyleft/gpl.html" title="GNU General Public License page">GNU GPL version 2 or later</a>. It is also free as in "free beer".</p>
<h1>News</h1>
<p id="rssFeed">
<a href="feed/atom/news.xml" type="application/atom+xml" title="Atom feed">
@@ -26,6 +26,20 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId7" class="anchorLink">License changed from GPLv3+ to GPLv2+</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2012-09-04</p>
+ <div class="newContent">
+ <div>
+ <p>I have changed the KTutorial license from GPLv3+ to GPLv2+ to ensure that any KDE application can use KTutorial (with the previous license it could be used only in applications that did not link against any GPLv2 only libraries) and to be able to move the code to KDE repositories.</p>
+ <p>I will release a new KTutorial version featuring the new license soon.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId6" class="anchorLink">Examples of KTutorial for the real world</a>
</h2>
<div class="newBody">
Modified: trunk/web-src/pages/news.xml
===================================================================
--- trunk/web-src/pages/news.xml 2012-09-04 21:48:04 UTC (rev 387)
+++ trunk/web-src/pages/news.xml 2012-09-04 22:38:45 UTC (rev 388)
@@ -23,6 +23,20 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId7" class="anchorLink">License changed from GPLv3+ to GPLv2+</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2012-09-04</p>
+ <div class="newContent">
+ <div>
+ <p>I have changed the KTutorial license from GPLv3+ to GPLv2+ to ensure that any KDE application can use KTutorial (with the previous license it could be used only in applications that did not link against any GPLv2 only libraries) and to be able to move the code to KDE repositories.</p>
+ <p>I will release a new KTutorial version featuring the new license soon.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId6" class="anchorLink">Examples of KTutorial for the real world</a>
</h2>
<div class="newBody">
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dan...@us...> - 2012-12-07 10:43:39
|
Revision: 389
http://ktutorial.svn.sourceforge.net/ktutorial/?rev=389&view=rev
Author: danxuliu
Date: 2012-12-07 10:43:32 +0000 (Fri, 07 Dec 2012)
Log Message:
-----------
Update pages for 0.5.1 release.
Modified Paths:
--------------
trunk/web-src/newsList.xml
trunk/web-src/pages/download.xml
trunk/web-src/pages/index.xml
trunk/web-src/pages/news.xml
Modified: trunk/web-src/newsList.xml
===================================================================
--- trunk/web-src/newsList.xml 2012-09-04 22:38:45 UTC (rev 388)
+++ trunk/web-src/newsList.xml 2012-12-07 10:43:32 UTC (rev 389)
@@ -92,4 +92,19 @@
<date>2012-09-04</date>
</fullDate>
</new>
+
+ <new>
+ <title>KTutorial 0.5.1 released!</title>
+ <summary>
+ <div xmlns="http://www.w3.org/1999/xhtml">
+ <p>This is the first release licensed under the GPLv2+, and the first one containing translations provided by the KDE localization teams (thank you for your work! :) ).</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5.1/README/view" title="KTutorial 0.5.1 release notes">release notes</a> contain more information about the changes from 0.5 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ <p>And yes, I know, I have a very loose concept of "soon" :P</p>
+ </div>
+ </summary>
+ <fullDate>
+ <date>2012-12-06</date>
+ </fullDate>
+ </new>
</news>
Modified: trunk/web-src/pages/download.xml
===================================================================
--- trunk/web-src/pages/download.xml 2012-09-04 22:38:45 UTC (rev 388)
+++ trunk/web-src/pages/download.xml 2012-12-07 10:43:32 UTC (rev 389)
@@ -17,8 +17,8 @@
<div class="h2Rounded">
<h2><a id="releases" class="anchorLink">Releases</a></h2>
</div>
- <p>Current release is 0.5. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5/ktutorial-0.5.tar.gz/download" title="KTutorial 0.5 release in tar.gz">ktutorial-0.5.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
- <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5/README/view" title="KTutorial 0.5 release notes">release notes</a>, which list the changes from the previous release.</p>
+ <p>Current release is 0.5.1. You can download <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5.1/ktutorial-0.5.1.tar.gz/download" title="KTutorial 0.5.1 release in tar.gz">ktutorial-0.5.1.tar.gz</a> from <a href="http://sourceforge.net/projects/ktutorial/files/" title="KTutorial project files">project's file list</a>.</p>
+ <p>You can also see the <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5.1/README/view" title="KTutorial 0.5.1 release notes">release notes</a>, which list the changes from the previous release.</p>
<p>See below for build instructions, in <a href="#build" title="Build instructions">building section</a>.</p>
<p>If you do know what you are doing ;) , you can also checkout KTutorial sources from <acronym title="Subversion">SVN</acronym> repository. Go on reading to know how to do it.</p>
@@ -39,8 +39,9 @@
<p>In order to build KTutorial, it doesn't matter if you downloaded it from a release or from <acronym title="Subversion">SVN</acronym>.</p>
<p>You will need <a href="http://www.cmake.org" title="CMake project web">CMake</a>, and Qt >= 4.6 and KDE 4 kdelibs development packages installed in your system. It can be built like any other KDE 4 library or application.</p>
<p>Create a <em>build</em> subdirectory in <em>ktutorial</em> directory, and change to it. Now, in a terminal, just run <strong>cmake ../ && make</strong> and it will configure and build KTutorial in the <em>build</em> directory. Once built, execute <strong>make install</strong> and you are done (you will likely need to change to root user, as default KDE installation is usually only root writable).</p>
- <p>If you want to specify a prefix to install KTutorial to, instead of using KDE default installation directory, call CMake using the parameter <strong>-DCMAKE_INSTALL_PREFIX=/installation/prefix</strong>. For debugging purposes, use <strong>-DCMAKE_BUILD_TYPE=debugfull</strong>. To automatically build the unit tests when the project is built, use <strong>-DKDE4_BUILD_TESTS=ON</strong>.</p>
+ <p>If you want to specify a prefix to install KTutorial to, instead of using KDE default installation directory, call CMake using the parameter <strong>-DCMAKE_INSTALL_PREFIX=/installation/prefix</strong>. For debugging purposes, use <strong>-DCMAKE_BUILD_TYPE=debugfull</strong>. If you want to prevent some directory to be built (for example, the one for the test application), use <strong>BUILD_ktutorial-test-app=NO</strong>. To automatically build the unit tests when the project is built, use <strong>-DKDE4_BUILD_TESTS=ON</strong>.</p>
+ <p>If you intend to run the unit tests you may find this little trick valuable: <a href="http://ktutorial.wordpress.com/2012/12/06/preventing-graphical-automated-tests-from-interrupting-you/" title="Preventing graphical automated tests from interrupting you article in KTutorial project blog">Preventing graphical automated tests from interrupting you</a>.</p>
- <p class="lastUpdated">Last updated: 2012-08-21</p>
+ <p class="lastUpdated">Last updated: 2012-12-06</p>
</page:content>
</page>
Modified: trunk/web-src/pages/index.xml
===================================================================
--- trunk/web-src/pages/index.xml 2012-09-04 22:38:45 UTC (rev 388)
+++ trunk/web-src/pages/index.xml 2012-12-07 10:43:32 UTC (rev 389)
@@ -26,6 +26,22 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId8" class="anchorLink">KTutorial 0.5.1 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2012-12-06</p>
+ <div class="newContent">
+ <div>
+ <p>This is the first release licensed under the GPLv2+, and the first one containing translations provided by the KDE localization teams (thank you for your work! :) ).</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5.1/README/view" title="KTutorial 0.5.1 release notes">release notes</a> contain more information about the changes from 0.5 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ <p>And yes, I know, I have a very loose concept of "soon" :P</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId7" class="anchorLink">License changed from GPLv3+ to GPLv2+</a>
</h2>
<div class="newBody">
Modified: trunk/web-src/pages/news.xml
===================================================================
--- trunk/web-src/pages/news.xml 2012-09-04 22:38:45 UTC (rev 388)
+++ trunk/web-src/pages/news.xml 2012-12-07 10:43:32 UTC (rev 389)
@@ -23,6 +23,22 @@
<div id="news">
<div class="new">
<h2 class="newTitle">
+ <a id="newId8" class="anchorLink">KTutorial 0.5.1 released!</a>
+ </h2>
+ <div class="newBody">
+ <p class="newDate">2012-12-06</p>
+ <div class="newContent">
+ <div>
+ <p>This is the first release licensed under the GPLv2+, and the first one containing translations provided by the KDE localization teams (thank you for your work! :) ).</p>
+ <p>The <a href="http://sourceforge.net/projects/ktutorial/files/ktutorial-0.5.1/README/view" title="KTutorial 0.5.1 release notes">release notes</a> contain more information about the changes from 0.5 release.</p>
+ <p>Check the <a href="download.html" title="Download page in KTutorial web">download page</a> for information about downloading and building KTutorial.</p>
+ <p>And yes, I know, I have a very loose concept of "soon" :P</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="new">
+ <h2 class="newTitle">
<a id="newId7" class="anchorLink">License changed from GPLv3+ to GPLv2+</a>
</h2>
<div class="newBody">
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X