Fix Issue waterbearlang#79 by removing todos and bugs from README

README.md

@@ -78,81 +78,3 @@ limitations under the License.
 <a rel="license" href="http://creativecommons.org/licenses/by/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by/3.0/88x31.png" /></a><br /><span xmlns:dct="http://purl.org/dc/terms/" href="http://purl.org/dc/dcmitype/Text" property="dct:title" rel="dct:type">Waterbear Documentation</span> by <a xmlns:cc="http://creativecommons.org/ns#" href="http://waterbearlang.com/" property="cc:attributionName" rel="cc:attributionURL">Dethe Elza</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 Unported License</a>.<br />Permissions beyond the scope of this license may be available at <a xmlns:cc="http://creativecommons.org/ns#" href="http://www.apache.org/licenses/LICENSE-2.0" rel="cc:morePermissions">http://www.apache.org/licenses/LICENSE-2.0</a>.
 
 
-# Coming Features
-
-* Make scripts left-aligned instead of free-floating
-* Add local variable selection to top of containers
-* Create and manipulate arrays and objects
-* Create new functions
-* Move block scripts aside, don't store with blocks on stage or saved blocks
-* Support for any() type variables (fix String troubles)
-* √ Add disclosure triangles to containers
-* √ Make front page about Waterbear, start IDE on subsequent page
-* √ Wrap scripts to avoid global pollution on run, not on display
-* Move JS, Raphael, Sketchy, Arduino to plugins
-* Format UI from plugins
-* √ Move wrap_scripts to language plugin
-* √ Use a library loader (YepNope)
-* Autogenerate variable names
-* Full web site with tutorial and forums
-* Zoom into script view
-* Build new blocks in Workspace
-* Show all blocks (workaround for block drift bug) or autolayout
-* Larger script workspace, with scrollbars
-* Multiple script workspaces (allows one per sprite, for instance)
-* [optional] Allow contained blocks to overflow right edge of block without growing block
-* Contribution guidelines
-* Contributor list
-* Credits, inspirations, alternatives
-* Built-in demos
-* Test, specs, features, examples
-* Reach out: Facebook, IRC
-* Get design help, especially for workspace
-* Waterbear logo
-* √ Better code formatting for code view
-* Script embedding
-* Server for saving and sharing scripts
-* Two ways to beautify JS:
-  - √ https://github.com/einars/js-beautify/blob/master/beautify.js
-  - https://github.com/douglascrockford/JSLint/blob/master/jslint.js
-  - try 'em both, see what sticks
-* JS to coffeescript:
-  - https://github.com/mindynamics/js2cs
-  - (more recent) http://ricostacruz.com/js2coffee/
-* Flared borders: http://orderedlist.com/blog/articles/flared-borders-with-css/
-* High-level components like Android AppInventor:
-  - UI: Button, canvas, checkbox, clock, image, label, listpicker, password, textbox, tinydb???
-  - Media: Camera, imagepicker, player, sound, videoplayer
-  - Animation: Ball, imagesprite
-  - Social: Contact picker, email picker, phone call, phone number picker, texting, twitter
-  - Sensors: Accelerometer, location, orientation
-  - Screen arrangement: Vertical, horizontal, table
-  - Mindstorms: Color sensor, directions, drive, light sensor, sound sensor, touch sensor, ultrasonic sensor
-  - Other: Activity starter, barcode scanner, bluetooth scanner, bluetooth server, notifier, speech recognizer, text to speech, tinywebdb, web
-* Also like AppInventor: Configuration sheets for high-level components
-
-# On Chromeless (nee
-
->    Absolutely, You can use processes [1], though the api for interacting with external procs is rather miserable at the moment [2]. Or you can use JSCtypes [3], for which there's a tiny toy example you can start from [4].
-
->    lloyd
-
->    [1] http://nochro.me/#module/lib/child_process
->    [2] https://github.com/mozilla/chromeless/issues/130
->    [3] https://wiki.mozilla.org/JSctypes
->    [4] https://github.com/mozilla/chromeless/tree/master/examples/jsctypes
-
-Short answer: No, but if you want to write code for Chromeless to make it work...
-
-# Bugs
-
-* Keypressed sensor block broken
-* Empty blocks insert comments that break scripts
-* When switching languages, clear the scripts
-* When saving and restoring, language matters - restore needed plugins
-* Make sure restore dialogue scrolls
-* √ Dragging block out of a Boolean socket doesn't restore select element
-* Clicking into an input doesn't select contents
-* √ Clicking into an input after the first input puts cursor in first input
-* Visual cues when snapping are overly subtle
-* Snap regions too small