Changes between Initial Version and Version 1 of Ticket #10558


Ignore:
Timestamp:
2014-09-26T11:12:44+02:00 (11 years ago)
Author:
Don-vip
Comment:

This is already implemented:

                <combo key="generator:type" text="Generator Type" values_searchable="true">
                    <list_entry value="BWR-1" display_value="Boiling Water Reactor 1 (BWR-1)" short_description="fission" />
                    <list_entry value="BWR-2" display_value="Boiling Water Reactor 2 (BWR-2)" short_description="fission" />
                    <list_entry value="BWR-3" display_value="Boiling Water Reactor 3 (BWR-3)" short_description="fission" />
                    <list_entry value="BWR-4" display_value="Boiling Water Reactor 4 (BWR-4)" short_description="fission" />
                    <list_entry value="BWR-5" display_value="Boiling Water Reactor 5 (BWR-5)" short_description="fission" />
                    <list_entry value="BWR-6" display_value="Boiling Water Reactor 6 (BWR-6)" short_description="fission" />
...
                </combo>

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10558

    • Property Resolutionworksforme
    • Property Status newclosed
  • Ticket #10558 – Description

    initial v1  
    44
    55Can't it be possible to move towards a more HTML-like approach ?
     6{{{
     7#!xml
    68<combo key="highway" text="">
    79  <option value="service">Service</option>
     
    1012  ...
    1113</combo>
     14}}}
    1215
    1316My point is providing the ability to do so, no to edit the whole defaultpresets.xml like that.