×
This forum has been locked. Please submit new Feature Requests on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
custom joomla form FIELDS
Søren Beck Jensen
Administrador
Posts: 81
9 años 9 meses antes #654
por Søren Beck Jensen
Søren Beck Jensen
Founder, Component-Creator.com
Respuesta de Søren Beck Jensen sobre el tema Vote your Favourite Feature Suggestions!
Hi Pete,
Thanks for clarifying. I think we could simply create for instance 8 key value fields that would allow you to enter your own pairs. Such as
Then we can guarantee that the XML we generate is correct and it should give enough flexibility.
Let me know what you think.
Thanks for clarifying. I think we could simply create for instance 8 key value fields that would allow you to enter your own pairs. Such as
- Key: name Value: backgroundcolor
- Key: type Value: color
Then we can guarantee that the XML we generate is correct and it should give enough flexibility.
Let me know what you think.
Søren Beck Jensen
Founder, Component-Creator.com
Por favor, Identificarse o Crear cuenta para unirse a la conversación.
Pete
Navegador Junior
Posts: 27
9 años 9 meses antes - 9 años 9 meses antes #655
por Pete
Respuesta de Pete sobre el tema Vote your Favourite Feature Suggestions!
Hi Søren,
Yes - this may be a slightly safer option
Although it would maybe be more flexible to make mandatory Fixed key pair fields for the generic essential values (name, type etc) and then some optional 'repeatable' parameters (where you can keep "add" ing them - like the SELECT LIST option values..
However, this system will not allow us to force in things like "repeat fields", but having said that, repeat fields are unique, and should be fairly simple to add? Its basically just a field 'group' placeholder..
Which adds the following to the top of the group:
<field name="list_templates"
type="Repeatable"
icon="list"
description="PLG_TINY_FIELD_TEMPLATE_FIELD_ELEMENTS_DESC"
label="PLG_TINY_FIELD_TEMPLATE_FIELD_ELEMENTS_LABEL"
default="{'template':,'location':,'description':}">
<fields name="params">
<fieldset hidden="true" name="list_templates_modal" repeat="true">
*Your normal generated fields (including custom ones) here*
And then
</fieldset>
</fields>
</field>
To close of the repeat bit
If you add both Custom AND repeatable then I think you have all my requirements covered - I do need both for my current project but custom is more important at this point !!
Thanks for the responding so enthusiastically.. and let me know if any of this is unclear - I have been staying up too late recently watching too much Breaking Bad to communicate well at the moment lol !
Cheers,
Pete
Yes - this may be a slightly safer option
Although it would maybe be more flexible to make mandatory Fixed key pair fields for the generic essential values (name, type etc) and then some optional 'repeatable' parameters (where you can keep "add" ing them - like the SELECT LIST option values..
However, this system will not allow us to force in things like "repeat fields", but having said that, repeat fields are unique, and should be fairly simple to add? Its basically just a field 'group' placeholder..
Which adds the following to the top of the group:
<field name="list_templates"
type="Repeatable"
icon="list"
description="PLG_TINY_FIELD_TEMPLATE_FIELD_ELEMENTS_DESC"
label="PLG_TINY_FIELD_TEMPLATE_FIELD_ELEMENTS_LABEL"
default="{'template':,'location':,'description':}">
<fields name="params">
<fieldset hidden="true" name="list_templates_modal" repeat="true">
*Your normal generated fields (including custom ones) here*
And then
</fieldset>
</fields>
</field>
To close of the repeat bit
If you add both Custom AND repeatable then I think you have all my requirements covered - I do need both for my current project but custom is more important at this point !!
Thanks for the responding so enthusiastically.. and let me know if any of this is unclear - I have been staying up too late recently watching too much Breaking Bad to communicate well at the moment lol !
Cheers,
Pete
Última Edición: 9 años 9 meses antes por Pete.
Por favor, Identificarse o Crear cuenta para unirse a la conversación.
Pete
Navegador Junior
Posts: 27
9 años 8 meses antes #662
por Pete
Respuesta de Pete sobre el tema Vote your Favourite Feature Suggestions!
Hi Folks, any news as to whether this *may* be implemented in the near future ? If not I am going to have to try the XML override plugin system, which is a little less simple
Thank,
Pete
Thank,
Pete
Por favor, Identificarse o Crear cuenta para unirse a la conversación.
Søren Beck Jensen
Administrador
Posts: 81
9 años 8 meses antes #663
por Søren Beck Jensen
Søren Beck Jensen
Founder, Component-Creator.com
Respuesta de Søren Beck Jensen sobre el tema Vote your Favourite Feature Suggestions!
Hi Pete. This will definitely be implemented in one form or another, but I don't think we will be able to do so for at least a month and probably more like 2-3 months.
Sorry
Sorry
Søren Beck Jensen
Founder, Component-Creator.com
Por favor, Identificarse o Crear cuenta para unirse a la conversación.
Pete
Navegador Junior
Posts: 27
9 años 8 meses antes #664
por Pete
Respuesta de Pete sobre el tema Vote your Favourite Feature Suggestions!
Hi Søren,
Thanks for letting me know - my 3 month subscription (and project) will be expired then But its worth having for future projects..
Cheers,
Pete
Thanks for letting me know - my 3 month subscription (and project) will be expired then But its worth having for future projects..
Cheers,
Pete
Por favor, Identificarse o Crear cuenta para unirse a la conversación.
Pete
Navegador Junior
Posts: 27
9 años 2 meses antes #957
por Pete
Respuesta de Pete sobre el tema Vote your Favourite Feature Suggestions!
Well - that was 6 months ago! I am voting for this in the Poll. It takes component creator to a much more serious level.
Por favor, Identificarse o Crear cuenta para unirse a la conversación.
Tiempo de carga de la página: 0.054 segundos