Stetic
Table of contents
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.
- Tag page
- What links here
[MISSING: skin.common.header-gallery-count]
| Images 0 | ||
|---|---|---|
| No images to display in the gallery. |