update roadmap

README.md

@@ -36,14 +36,7 @@ Bevy is still in the _very_ stages of development. APIs can and will change. Imp
 
 ## Planned Features
 
-* Physically Based Rendering
-* Load scenes from files
-* Editor (built using Bevy)
-* Live Plugin Reloading
-* GLTF model loading
-* Gamepad support
-* Networking
-* More Platforms: Android, iOS, Web
+See our [ROADMAP.md](~/ROADMAP.md) for the current list of planned features.
 
 ## Getting Started
 

ROADMAP.md

@@ -1,18 +1,35 @@
 # Bevy Roadmap
 
+Here is the current list of planned features. All items are sorted in approximate priority order, but actual implementation order will vary based on individual interest and/or funding.
+
 * UI Framework
-    * Box model rendering
-    * Use entity hierarchy for tree structure
+    * Text
     * Styling
 * Rendering
-    * Consider reworking current RenderGraph to be more graph-like
+    * Textures
+    * Physically based rendering
+    * Skeletal animation
     * Macro to produce vertex buffer attributes (and maybe descriptors) from structs
     * Dynamic / user defined shaders
         * consider using shaderc-rs. but this introduces compile complexity and requires other C++ build systems
-* Physics
-    * High level physics data types
-    * Integrate with nphysics
+* Input
+    * Keyboard and mouse events
+    * Gamepad events
+* Assets
+    * Load GLTF files
+* Scene
+    * Define scene format
+    * Load scenes from files (likely RON)
+* Plugins
+    * Live plugin reloading
 * Editor
     * Editor <-> game communication protocol
     * Build UI using bevy UI framework
-    * Consider supporting embedding parts of the editor directly into games
+    * Consider supporting embedding parts of the editor directly into games
+* Physics
+    * High level physics data types
+    * Integrate with nphysics
+* Platform Support
+    * Android
+    * iOS
+    * Web