This page is likely outdated. Visit the new documentation for updated content.

1-widget-per-file

Status Owner Importance Complexity MD Version
In Progress Krzysztof Marecki Normal Medium

Move stetic to a 1-widget-per-file model, so that each foo.stetic file contains a single window or widget, and has a foo.stetic.designer.cs partial class file grouped, etc. This would not only mirror .NET idiom, but would also help to reduce the stetic startup time and memory use, and make it easier to copy/move widget between projects, make VCS changesets more readable, etc.

Lightweight project model

Status Owner Importance Complexity MD Version
Pending Normal Medium

Now that stetic is part of MD, it should use the MD project model and parser services more directly, instead of maintaining its own equivalents. This would reduce the stetic startup time and memory use a lot, and would improve maintainability.

Don’t try to regenerate code every build

Status Owner Importance Complexity MD Version
In Progress Krzysztof Marecki Normal Medium

Make stetic regenerate designer code less often, to make builds quicker. Reduce churn in generated code that pollutes svn status listings.

Run designer out-of-process, support for native widgets

Status Owner Importance Complexity MD Version
Pending Normal Medium

Run the stetic designer surface in a separate process so that it can load and render custom-rendered widgets.

Support for GtkBuilder

Status Owner Importance Complexity MD Version
Pending Normal Medium

Add support for the GtkBuilder file format. Perhaps also support a XAML-like codebehind system.