20,741
edits
No edit summary  | 
				|||
| Line 222: | Line 222: | ||
While it would definitely be possible to implement widgets by directly creating a canvas via the property tree, that would probably be counter-productive, because we clearly don't want any hard coded C++ special cases.  | While it would definitely be possible to implement widgets by directly creating a canvas via the property tree, that would probably be counter-productive, because we clearly don't want any hard coded C++ special cases.  | ||
Now, if someone really wants to implement some custom canvas widget that cannot/shouldn't be modeled in scripting space, then the canvas infrastructure can be extended.    | Now, if someone really wants to implement some custom canvas widget that cannot/shouldn't be modeled in scripting space, then the canvas infrastructure can be extended (see [[Canvas Development]].    | ||
Just take a look at how the existing [[Canvas Maps]] are implemented currently. The same approach could be used to provide support for new/more specific drawing modes, such as:  | Just take a look at how the existing [[Canvas Maps]] are implemented currently. The same approach could be used to provide support for new/more specific drawing modes, such as:  | ||