<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Introduction</title><link>https://sourceforge.net/p/epart/wiki/Introduction/</link><description>Recent changes to Introduction</description><atom:link href="https://sourceforge.net/p/epart/wiki/Introduction/feed" rel="self"/><language>en</language><lastBuildDate>Tue, 31 May 2016 19:09:08 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/epart/wiki/Introduction/feed" rel="self" type="application/rss+xml"/><item><title>Introduction modified by Felipe Castro</title><link>https://sourceforge.net/p/epart/wiki/Introduction/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v5
+++ v6
@@ -1,6 +1,6 @@
 What
 ==
-A sheet music reader is a program for presenting a digitised music score for someone to play it, facilitating the work of turning the pages in longer performings, a parallel task which may become an annoying source of trouble.
+A sheet music reader is a program for presenting a digitized music score for someone to play it, facilitating the work of turning the pages in longer performings, a parallel task which may become an annoying source of trouble.

 Why
 ==
@@ -14,11 +14,10 @@
 --
 E-part software features:

-1. Collect paths for PDF-files containing music scores and organize them in play lists.
+1. Collect paths for PDF-files containing music scores and keep them organized in playlists.

-2. For each music (PDF-file), set the scrolling points where to stop and the time it should be parked there during the musical interpretation.
-2. a) If no park-points are defined, the program will set them blindly without regarding if some staff will be truncated in each screen it is shown, because the zoom of scores are automatically fitted to the screen width and the program does not have information about the endings of each staff (FIXME).
+2. For each music (PDF-file), define the scrolling positions where to stop and the time it should be parked there during the musical interpretation.

-3. For playing the music, the page zoom fits the width, and all pages are concatenated in a large continuous scroll up to down. The page turning transition is done dividing the screen horizontally in two: the top part shows the new park-point of the score and the bottom shows the end of the previous park-point. As long as the pages layout are independent from the screen layout, the user should find the best way to read the music by configuring portrait or landscape mode for rendering.
+3. For playing the music, the page zoom fits the width, and all pages are concatenated in a large continuous scroll up to down. The page turning transition is done dividing the screen horizontally in two: the top part shows the new park-position of the score and the bottom shows the end of the previous one. As long as the pages layout are independent from the screen layout, the user should find the best way to read the music by configuring portrait or landscape mode for rendering.

-4. During the play along, the user may advance or return park-points with specific small buttons (rewind/forward) or with mouse clicks (left/rigth). If in programatic auto-turning mode, an advance action also cause a small decrease in timings by some configurable factor, while returns will increase them a little bit. And also, there are specific buttons to stop and resume the playing and a scrollbar to position the park-point cursor in any point of the music.
+4. During the play along, the user may advance or rewind park-positions with specific small on-screen buttons (rewind/forward) or with pgUp/pgDwn signalling. And also, there are specific buttom to stop/resume the playing and a scrollbar to put the park-position cursor in any point of the music.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felipe Castro</dc:creator><pubDate>Tue, 31 May 2016 19:09:08 -0000</pubDate><guid>https://sourceforge.netf6676b2170367222ccbcef2b831128fdf20b9cea</guid></item><item><title>Introduction modified by Felipe Castro</title><link>https://sourceforge.net/p/epart/wiki/Introduction/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v4
+++ v5
@@ -19,6 +19,6 @@
 2. For each music (PDF-file), set the scrolling points where to stop and the time it should be parked there during the musical interpretation.
 2. a) If no park-points are defined, the program will set them blindly without regarding if some staff will be truncated in each screen it is shown, because the zoom of scores are automatically fitted to the screen width and the program does not have information about the endings of each staff (FIXME).

-3. For playing the music, the page zoom fits the width, and all pages are concatenated in a large continuous scroll up to down. The page turning transition is done dividing the screen horizontally in two. The top part shows the new park-point of the score and the bottom shows the end of the previous park-point. As long as the pages layout are independent from the screen layout, the user should find the best way to read the music by configuring portrait or landscape mode for rendering.
+3. For playing the music, the page zoom fits the width, and all pages are concatenated in a large continuous scroll up to down. The page turning transition is done dividing the screen horizontally in two: the top part shows the new park-point of the score and the bottom shows the end of the previous park-point. As long as the pages layout are independent from the screen layout, the user should find the best way to read the music by configuring portrait or landscape mode for rendering.

 4. During the play along, the user may advance or return park-points with specific small buttons (rewind/forward) or with mouse clicks (left/rigth). If in programatic auto-turning mode, an advance action also cause a small decrease in timings by some configurable factor, while returns will increase them a little bit. And also, there are specific buttons to stop and resume the playing and a scrollbar to position the park-point cursor in any point of the music.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felipe Castro</dc:creator><pubDate>Wed, 20 Apr 2016 14:55:14 -0000</pubDate><guid>https://sourceforge.net57b088939a2537db130ef8765db0fdba4d0a6a69</guid></item><item><title>Introduction modified by Felipe Castro</title><link>https://sourceforge.net/p/epart/wiki/Introduction/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v3
+++ v4
@@ -12,8 +12,13 @@

 Sofware Specification
 --
-The E-part software should be able to:
+E-part software features:
+
 1. Collect paths for PDF-files containing music scores and organize them in play lists.
+
 2. For each music (PDF-file), set the scrolling points where to stop and the time it should be parked there during the musical interpretation.
-2. 1. If no park-points are defined, the program will set them blindly without regarding if some staff will be truncated in each screen it is shown, because the zoom of scores are automatically fitted to expand to the screen width and the program does not have information about the endings for each staff (FIXME).
-3. This can be done by imediate commands from the user, with pedals emulating mouse right and left clicks, or 
+2. a) If no park-points are defined, the program will set them blindly without regarding if some staff will be truncated in each screen it is shown, because the zoom of scores are automatically fitted to the screen width and the program does not have information about the endings of each staff (FIXME).
+
+3. For playing the music, the page zoom fits the width, and all pages are concatenated in a large continuous scroll up to down. The page turning transition is done dividing the screen horizontally in two. The top part shows the new park-point of the score and the bottom shows the end of the previous park-point. As long as the pages layout are independent from the screen layout, the user should find the best way to read the music by configuring portrait or landscape mode for rendering.
+
+4. During the play along, the user may advance or return park-points with specific small buttons (rewind/forward) or with mouse clicks (left/rigth). If in programatic auto-turning mode, an advance action also cause a small decrease in timings by some configurable factor, while returns will increase them a little bit. And also, there are specific buttons to stop and resume the playing and a scrollbar to position the park-point cursor in any point of the music.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felipe Castro</dc:creator><pubDate>Wed, 20 Apr 2016 14:53:46 -0000</pubDate><guid>https://sourceforge.net9984551c671d2de818136e9b2510384315ced69e</guid></item><item><title>Introduction modified by Felipe Castro</title><link>https://sourceforge.net/p/epart/wiki/Introduction/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -13,5 +13,7 @@
 Sofware Specification
 --
 The E-part software should be able to:
-1. Read PDF-files containing music scores and organize them in play lists.
-2. For each music (PDF-file), set the scrolling points where to stop and the time it should be parked there.
+1. Collect paths for PDF-files containing music scores and organize them in play lists.
+2. For each music (PDF-file), set the scrolling points where to stop and the time it should be parked there during the musical interpretation.
+2. 1. If no park-points are defined, the program will set them blindly without regarding if some staff will be truncated in each screen it is shown, because the zoom of scores are automatically fitted to expand to the screen width and the program does not have information about the endings for each staff (FIXME).
+3. This can be done by imediate commands from the user, with pedals emulating mouse right and left clicks, or 
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felipe Castro</dc:creator><pubDate>Wed, 20 Apr 2016 14:14:46 -0000</pubDate><guid>https://sourceforge.net7c3b51fa5212a0a8e686cc8efe8e023b650d449b</guid></item><item><title>Introduction modified by Felipe Castro</title><link>https://sourceforge.net/p/epart/wiki/Introduction/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -1,11 +1,17 @@
 What
---
+==
 A sheet music reader is a program for presenting a digitised music score for someone to play it, facilitating the work of turning the pages in longer performings, a parallel task which may become an annoying source of trouble.

 Why
---
-In some cases, the sheets simply get willingness to go flying around and away from the musician's sigth, usually with the help of wind. In other cases, the music simply does not have enough pauses that allow the musician to take one arm off his instrument to quickly turn the page manually. 
+==
+In some cases, the sheets simply get willingness to go flying around and away from the musician's sigth, usually with the help of wind. In other cases, the music simply does not have enough pauses that allow the musician to take one arm off his instrument and quickly turn the page manually. 

 How
+==
+Automating the task of turning pages is done with a small computer: a tablet or preferably an [e-reader](https://en.wikipedia.org/wiki/E-reader). But the last one is primarily designed for reading books, so in order to turn your e-book reader into an **e-part** reader... that's where this program fits.
+
+Sofware Specification
 --
-Automating the task of turning pages is done with a small computer: a tablet or preferably an [e-reader](https://en.wikipedia.org/wiki/E-reader). But the last one is primarily designed for reading books, so in order to turn your e-book reader into an **e-part** reader... that's where this program fits.
+The E-part software should be able to:
+1. Read PDF-files containing music scores and organize them in play lists.
+2. For each music (PDF-file), set the scrolling points where to stop and the time it should be parked there.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felipe Castro</dc:creator><pubDate>Wed, 20 Apr 2016 13:47:09 -0000</pubDate><guid>https://sourceforge.netec3b32793615bafbf717f7ca0915299c7b8e933e</guid></item><item><title>Introduction modified by Felipe Castro</title><link>https://sourceforge.net/p/epart/wiki/Introduction/</link><description>&lt;div class="markdown_content"&gt;&lt;h2 id="what"&gt;What&lt;/h2&gt;
&lt;p&gt;A sheet music reader is a program for presenting a digitised music score for someone to play it, facilitating the work of turning the pages in longer performings, a parallel task which may become an annoying source of trouble.&lt;/p&gt;
&lt;h2 id="why"&gt;Why&lt;/h2&gt;
&lt;p&gt;In some cases, the sheets simply get willingness to go flying around and away from the musician's sigth, usually with the help of wind. In other cases, the music simply does not have enough pauses that allow the musician to take one arm off his instrument to quickly turn the page manually. &lt;/p&gt;
&lt;h2 id="how"&gt;How&lt;/h2&gt;
&lt;p&gt;Automating the task of turning pages is done with a small computer: a tablet or preferably an &lt;a class="" href="https://en.wikipedia.org/wiki/E-reader" rel="nofollow"&gt;e-reader&lt;/a&gt;. But the last one is primarily designed for reading books, so in order to turn your e-book reader into an &lt;strong&gt;e-part&lt;/strong&gt; reader... that's where this program fits.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felipe Castro</dc:creator><pubDate>Wed, 20 Apr 2016 13:17:43 -0000</pubDate><guid>https://sourceforge.net17f2b9a7cabf5188ec9bd4ca2d7fc336b635dc93</guid></item></channel></rss>