-
Notifications
You must be signed in to change notification settings - Fork 29
FeatureBrainstorming.md
Some features are going to require a ton of infrastructure and build-up. Many of them we don't support at all yet. Some of them we won't ever support. Here's where we can dump design notes, research, early work toward them, etc. as we build in different directions.
A lot of these are based on Shoes3, but not all of them.
- Packaging apps to run with their own Ruby and gems - including for multiple platforms
- Multi-File Apps - we'd like to be able to include local images and fonts, multiple source files, etc.
- Splash App - Shoes3 showed a little interface window to run apps, package apps, etc.
- Scarpe-Party - the ability to run Scarpe apps from a remote app registry
Shoes3 had a bunch of drawables we don't support. A lot seem to have been added well after the "Nobody Knows Shoes" days.
- Shape and Mask Support - this is challenging, especially for Webview
- Images as Slots - old Shoes let you use an image like a flow or stack and put in a bunch of drawables
- Backgrounds, Borders, Fills, Patterns - Shoes had a Pattern type that we only partly support
- Color Type - Shoes3 had a color type and Scarpe doesn't
- Free-Standing Alerts - old Shoes let you start an alert outside any Shoes.app block, or when none even exist
- Menubar drawable to support OS menubars
- SVG drawable - was this even a good idea?
- Graph/plot drawable
- Dynamic default values - there are some oddities in when Shoes3 would update visually based on defaults
- Default values per-drawable for specific slots - it looks like Shoes3 used to allow pretty intricate default values; do we want the same?
- Shoes3 had a lot of styles on a lot of drawables - we support some of them, but not all
We're currently doing a lot with Shoes-Spec, but testing can be a huge, diverse topic.
Old Shoes3 used to have a shared error console across multiple apps. You could use Shoes URLs to switch a window between Shoes apps. You could open multiple app windows from different Shoes apps and they could generally see each other and interact.
- Display Server - we want to support a persistent Shoes display server, shared across multiple apps and app runs
- Get Hackety-Hack Working - this is a huge audacious goal, frankly. We're far away.
Shoes3 had various interesting features included by default, like how we have Bloops.
- HTML Parsing - HTML parsing with hpricot used to be built in
- SQLite3 used to be built in
- ftsearch
- chipmunk - see notes. A 2D physics engine (video)