Toaster should drive the user options in configuring variables according to reasonable usage of OE-Core variables in a generic manner. Currently the variable configuration page has a hardcoded layout on some variable names (free text entry, single selection - radio button, multiple selection - checkboxes) to drive sensible input from the user. This needs to be changed to a generic mechanism as not to hardcode layout on variable names, which is a approach that doesn't scale.
Adding Paul and Richard for input on how variable type should be reflected in Bitbake itself.
Requirements not clear, I need to drive discovery and research on this one.
Moving to 2.0 due to high complexity of implementation versus Importance.
Moving out of NEEDINFO since I have created a separate bug (bug 7985) describing what needs to be done on the bitbake side to support this. One consideration specific to Toaster though - once the functionality in bug 7985 is implemented, we will need to add an initial parse of the metadata in order to bring in the typing information so we can make use of it within the UI.
(In reply to comment #4) > we will need to add an initial parse of the metadata in > order to bring in the typing information so we can make use of it within the > UI. Is this an initial parse per project? Or an initial parse whenever you start Toaster? I would need to know a bit more to make sure we handle this properly in the UI.
If you want comprehensive support for all variables including those that might be introduced in layers that have been added to the project, then it would need to be per project.
Clearing 2.0 milestone