Canvas widgets: Difference between revisions

Canvas widgets (view source)

725 bytes removed , 23 June 2014

m

20,741

edits

@@ Line 243: / Line 243: @@
 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.
-=== Layout Management ({{Not done}}) ===
-* [https://gitorious.org/fg/fgdata/blobs/master/Docs/README.layout [[$FG_ROOT]]/Docs/README.layout]
-* [https://qt.gitorious.org/qt/qtbase/source/1a6a763254b1844cb3f951e724d58a0fd29f62b5:src/widgets/kernel/qlayoutengine.cpp Qt Layout Engine]
-Have you thought where the layout logic will work in this scheme? Right now it's all in C++, and a layout manager might make sense for the canvas in general (think about laying out text or elements on an MFD or EICAS), possibly even in C++, but again you maybe already have a solution.
-I think the best place would be doing it with Nasal, as there is already all the information needed available. C++ doesn't know
-anything about widgets...
 === Styling, Theming and Skinning (XSL/CSS via SVG) ===