Textfield instead of Input in plugin configuration

---

Hello,

i am working on a little plugin to add custom css to the mobile frontend.

I want to add my custom styles without editing the frontend css file (so that they not get deleted while updating the mobile-frontent-plugin).

At the moment i have a custom css file wich works very nicely but i want to extend the functionality to add the css via the plugin configuration so there is no need to edit a file.

Now my question: Is there any possibility to show a html textfield in the device config for an attribute instead of an simple input field from type text?

Regards

@fbeek very interesting project.
Sorry but I have some problem with English.
You can explain better what have to do, so I can see if I can help you

@fbeek said in Textfield instead of Input in plugin configuration:

Now my question: Is there any possibility to show a html textfield in the device config for an attribute instead of an simple input field from type text?

No. What should this html textfield look like? Isn’t it CSS you want to edit, btw? I am confused

My 2 cents: Maybe you can work around this by having the possibility to edit name/value pairs which might be sufficient many use cases. For example, you have an attribute “styles” of type array with item properties name and value.

module.exports = {
  title: "pimatic-whatever plugin config options"
  type: "object"
  properties:
    styles:
      description: "CSS Custom Styles"
      type: "array"
      default: []
      items:
        type: "object"
        properties:
          name:
            type: "string"
            description: A CSS property name"
          value:
            type: "string"
            description: "A CSS property value"
...

Hello.

@Zacca : Thanks for your offer.
@mwittig: Thanks for your two cents

I thought of something like the textarea in the screenshot.

You can input css into this field. It will then be saved base64encoded in the config, so that the json format is valid. Then when pimatic starts my plugin checks if there is css a file or some text in this field.

If there is a file,then this will be included. If there are some data in the config attribute, this content will be decoded and linted. If it is valid css then the content is written to a file and included as asset.

So you can manipulate the css of the mobile frontent direct in the plugin settings.

What do you think?

I released the first version of the plugin pimatic-customcss.

At the moment without direct input support via plugin config.

Have fun with it

Regards

fbeek