0.7 Roadmap

[cmyr]

0.7 Roadmap, June 2020

finishing the must-haves

Goals

Druid 1.0 is still very far away, but we are slowly reaching a point where we could, with a straight face, suggest druid for certain small utilities. Our goal for 0.7 is to focus on on a few key projects that we think are currently barriers to serious use.

0.7 Roadmap

This roadmap is intended to cover approximately July, August, and September, and covers only planned, major projects; other smaller features and improvements will certainly happen in this timeframe as well.

• text improvements (issue text work planning & discussion #883, @cmyr) there is a large chunk of work necessary to improve druid's text API. In addition to the improvements outlined in text work planning & discussion #883, there are a number of other text-related projects
  • an improved font resolution API, with support for 'system' fonts (New text integration #1182)
  • a reworked TextBox widget (Start updating TextBox for piet text changes #1274)
  • [ ] (maybe) a non-toy text implementation on cairo
  • support for 'baseline alignment' of all system widgets, and an API for supporting baseline alignment in custom widgets. (Expose baseline on TextLayout, add Baseline alignment to Flex #1295)
• a reworked KeyEvent API (KeyEvent rework #1040, @raphlinus) we are commited to taking a principled, research-based approach to the design of our low-level APIs; our current KeyEvent API has some limitations, and will be replaced.
• asset bundling (Add a "resource bundle" for files like images, fonts, and localization #397) we would like to have a user friendly, type safe API for accessing bundled resources like images and fonts. This should be closely integrated into druid-shell, and be agnostic about where resources are actually stored on disk; this is also necessary in order to fully support localization.
• packaging apps (cargo-druid #1047) in order to distrubute a druid application, we need to a way to build a native application package for our target platforms.
• Alerts (Add alerts and their macOS implementation. #1039, @xStrom) for easy time sensitive notifications.
  • Modal windows (Modal windows #1055) to enable building custom modal features.
• continued work on the X11 backend (@jneem)

maybes

• tracing (integrate tracing #102) we want to do this eventually, and it's just a matter of having a free week.
• an experimental android backend (needs issue) either this cycle or next, we would like to land an android backend, and experiment with druid on mobile. This will be limited in scope, but will require the addition of a multitouch event API.

not yets

There are a number of projects that we recognize are very important and that we would like to acknowledge, while conceding they are not currently scheduled.

• accessibilty: this is a huge and hugely important project, and will be a priority if druid has demonstrated its viability and is in real use.
• an improved animation API: animation is a very important tool for creating rich interactions, and we have exciting ideas for animation APIs, but we can survive without it for the time being.
• async: similarly we have exciting ideas about how druid could be modified to fully support async task execution, but this will also have to wait until we have more of the basics in place.

Druid 0.6

Druid 0.6 was a rollup of a whole bunch of fixes and improvements; full details are available in the changelog.

[x3ro]

It appears that 0.7.0 has been released on crates.io. Could you please create a tag in this repository to reflect that? :)

[cmyr]

@x3ro done, thanks!

[IWANABETHATGUY]

Since 0.7 has been released for one month, are there any plan for 0.8?

[arthmis]

Hello can this issue be updated to 0.8 roadmap?

[cmyr]

I will do an updated roadmap when I next evaluate my needs for runebender, although it will likely focus on the two last items here, around asset bundling and app packaging. :)

[PoignardAzur]

We should probably write a new roadmap at some point =)