=== Scratchpad ===
Contributors: jk2228,  kem226
Tags: notepad, notes, helper, compose, scratch, scratchpad, pad, sticky note
Donate link: http://example.com/[a]
Requires at least: 4.1
Tested up to: 4.2
Stable tag:[b] trunk
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Scratchpad provides users with a running notepad while composing a post in Distraction Free Mode. Notes are saved along with the post!

== Description ==

Have you ever wanted to keep running notes when composing your posts ? Scratchpad is here to make composing easy and fast! Your notes are saved with the post you’re composing!


Scratchpad can be used to keep an outline for the post, visible next to the post, or to have a list of links or snippets to refer to.

== Installation ==


= From your WordPress dashboard =


1. Visit 'Plugins > Add New'
2. Search for 'Scratchpad'
3. Activate BuddyPress from your Plugins page. (You will be greeted with a Welcome page.)


= From WordPress.org =


1. Download Scratchpad.
2. Upload the 'scratchpad' directory to your '/wp-content/plugins/' directory, using your favorite method (ftp, sftp, scp, etc...)
3. Activate Scratchpad from your Plugins page.

== Frequently Asked Questions ==

= Where will I see the scratchpad? =
When you click on distraction free mode, the scratchpad pops up to the right of the editor.




= How do I save my scratchpad notes? =
Updating a post saves the scratchpad notes as well.



= Are my notes lost if I leave distraction free mode? =
No, your notes persist as long as you remain on the post and will reappear when you go back to Distraction Free Mode. If you leave the post with unsaved changes on your scratchpad, they will not persist.

[c]
== Screenshots ==

1. Scratchpad in use with a new post.

== Changelog ==

= 1.0 =
* Release version.

== Upgrade Notice ==

= 1.0 =
* First release, stable version.
[a]The validator fails without this link, what should it be ?
[b]We're not sure how to set this stable tag. The instruction said : ' Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for
stable. ' Should this be 1.0?




More instructions we don't understand: Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used
for displaying information about the plugin.  In this situation, the only thing considered from the trunk `readme.txt` is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version
that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.


 If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where
you put the stable version, in order to eliminate any doubt.
[c]Should we add a ""Where can I report a bug" section and what's the best way to do that ?