Gluon/Creator: Difference between revisions
< Gluon
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
: | : | ||
: Current thinking is to filter out all properties with some kind of prefix - _property or _gluon_property or _gluon_internal_property or similar. This should be standardised and used in all places. | : Current thinking is to filter out all properties with some kind of prefix - _property or _gluon_property or _gluon_internal_property or similar. This should be standardised and used in all places. | ||
;Specialised Katepart-based File Editors | |||
: There are some Gluon-specific file formats used. These currently are opened in Katepart or similar. While there are plans to have a proper extensive node-based editor for these files, an intermediate step would be to create a simple editor based on Katepart for these files. For example, materials are contained in a single file, but it would be nicer for actual editing to use a split editor that separates vertex and fragment shader source. | |||
==Ideas== | ==Ideas== | ||
Latest revision as of 14:59, 4 December 2012
Tasks
- Ignore prefixed dynamic properties
- For static properties we have an easy way to hide them - use the DESIGNABLE attribute. This is however not usable for dynamic properties. It would be useful to have some way to mark internal properties. For example, the material system is heavily based on dynamic properties, yet things like the model/view/projection matrices really shouldn't be exposed in Creator.
- Current thinking is to filter out all properties with some kind of prefix - _property or _gluon_property or _gluon_internal_property or similar. This should be standardised and used in all places.
- Specialised Katepart-based File Editors
- There are some Gluon-specific file formats used. These currently are opened in Katepart or similar. While there are plans to have a proper extensive node-based editor for these files, an intermediate step would be to create a simple editor based on Katepart for these files. For example, materials are contained in a single file, but it would be nicer for actual editing to use a split editor that separates vertex and fragment shader source.
Ideas
- Overlay-based semi-interactive introductory tour
Inspired by the N9's tour. Provide an interactive tour of all the important elements of Creator.- Implemented as part of GSoC in branch creator-qmlintro-shreya.