From Create Wiki

Several things need to be done.

Contents 1 Shell 2 JavaScript and dC Modules 3 Config & Project 4 Other Features

Shell

Shell, currently a simple JavaScript execution utility, needs to replace the actual create engine. A few items have to be scritpable for this to happen, and error handling in JavaScript (something we've been putting off, but probably won't be too difficult) is an absolute must.

We are considering making Shell have two versions: a lightweight version, and a full version. This would allow compiling Shell first, and using it to detect availability of modules, etc., to configure the rest of the platform for compilation (and even trigger the compilation). This process would end up compiling the full Shell.

JavaScript and dC Modules

Currently, JavaScript and dC don't have a very good module pattern. There should be a specific kind of object, called a module, which, when created with a JavaScript or dC context as a parameter, will register all of their components with that context. This approach would be nice and easy to use, and would also allow dynamic loading.

Config & Project

A new component, called Config, is being planned. It will be a JavaScript framework meant to configure things. This may be used to configure the build. It will be used to configure projects made for the Create Framework.

A specific method of creating projects will be created as well. It will probably also be written in JavaScript, and run in the Shell. It is possible that the Create project will itself be made into a project as its compilation pattern.

Other Features

All of the above are workflow-related features.

There are three main other features currently under consideration:

1. PDF-in-PDF. This isn't that tricky. We've written other programs that parse PDF (the trickiest part of this). But that took a few weeks to do properly last time, and though it will likely be easier this time, we currently have other, higher-priority items to attend to.
2. Raster imaging. The priority of this, partially because its apparent ease of implementation using Google's Skia library, may eclipse PDF-in-PDF because we may need to show this off soon (especially in issues regarding transparency).
3. Unicode support. The support would be simple, but present.