20,741
edits
Canvas widgets: Difference between revisions
Jump to navigation
Jump to search
m
→Widget Declaration via SVG
m (→Dialog Parser) |
|||
| Line 239: | Line 239: | ||
The canvas isn't really about end user features, it's a provider of an infrastructure, so that end user features can be more easily expressed and modeled in scripting space, using Nasal. That's why all end user features should be expressible in scripting space, and only the core infrastructure should need C++ extensions to make this easier. The end user APIs will be mostly designed in scripting space. | The canvas isn't really about end user features, it's a provider of an infrastructure, so that end user features can be more easily expressed and modeled in scripting space, using Nasal. That's why all end user features should be expressible in scripting space, and only the core infrastructure should need C++ extensions to make this easier. The end user APIs will be mostly designed in scripting space. | ||
=== Widget Declaration via SVG === | === Widget Declaration via SVG {{Pending}} === | ||
Background: [[Canvas Widgets#Widget declaration: XML vs. Nasal]] | Background: [[Canvas Widgets#Widget declaration: XML vs. Nasal]] | ||