It think it would be great if we had the ability to use other formats for nodes readme etc. could use other formats than .md. With AI generating a lot of code, it is easy to generate e.g. .html files which allows pictures, nicer tables etc. I assume it should be simple as we are now browser based

Hi, Can you give more detail to your idea. I'm not sure I understand what you are suggesting.

Rob

This would be my readme file for Levolor blinds if I could do html.

Are you guys on BETA or STAGING? I am not seeing anything about Readme files in Production.

@Michel Kohanim advised me in a support ticket to me to hold off on installing BETA or STAGING for now, which is why I am wondering.

@Panda88 and @apostolakisl ,

It's a great idea. Just as background:
1. README.md is also available in github in case a plugin is shared in a public repo. So, I think that should stay.

2. I think having a README.html would be awesome too.

With kind regards,
Michel

15 minutes ago, RRalston said:

Are you guys on BETA or STAGING? I am not seeing anything about Readme files in Production.

@Michel Kohanim advised me in a support ticket to me to hold off on installing BETA or STAGING for now, which is why I am wondering.

It sounds like you are talking about eisy firmware, not plugin development as @Panda88 was requesting. Unless you want to deal with bugs, I would stick to the main firmware track.

21 minutes ago, Michel Kohanim said:

@Panda88 and @apostolakisl ,

It's a great idea. Just as background:
1. README.md is also available in github in case a plugin is shared in a public repo. So, I think that should stay.

2. I think having a README.html would be awesome too.

With kind regards,
Michel

Were you thinking html code placed here? The question that would follow is images, where would they be saved? Github maybe?

@apostolakisl ,

As mentioned, we are working on a more dynamic way of configuring eisy-ui with developer contributions either at UI level or plugin level. We are still at the design stage, so this falls into the same category. The main question is not where these go, the question is how can we make it secure.

With kind regards,
Michel

For the nodes/plugin they refer to files (.md) in the PG3x interface - clearly the .md should stay as part of github, but being able to point to an html file from PG3x would be a good start - other things will follow I am sure - I believe it should be part of PG3x to make this happen, but Michel knows better I am sure

I went ahead and put an html page on github and put a link to it in the readme file for Levolor blinds. Readme files appear to just do plain text, so you have to copy it into a browser, no link. Allowing for links in the readme file seems like it wouldn't be that big of an edit for UD?

@Panda88 @Michel Kohanim

EDTI: One of my biggest gripes with plugins is that some of them are a bit short on all of this info. So the opportunity for the plugin creator to make a nice html page might encourage an attractive and complete description/configuration.

Edited September 18Sep 18 by apostolakisl

I tried as well, and in my case it was not interpreted as HTML - I think it mostly picking the correct renderer

Further to your thoughts - if data is presented well the users are more likely to look :-) - AI can help generate this automatically these days

Got it. It was not at all clear this was a developer related discussion for plug-ins/node servers. I saw the word "nodes" in the original post and my

thought went to the "Nodes" part of eisy-ui where all of our devices are defined.

And for the record, part of the requirement to join this group was willingness to at least install BETA code, so I expect we will all be asked to do that at some point soon.

Rob

@apostolakisl ,

Yes, readme is just plain text. POLYGLOT_CONFIG is md.

With kind regards,
Michel

7 minutes ago, RRalston said:

Got it. It was not at all clear this was a developer related discussion for plug-ins/node servers. I saw the word "nodes" in the original post and my

thought went to the "Nodes" part of eisy-ui where all of our devices are defined.

And for the record, part of the requirement to join this group was willingness to at least install BETA code, so I expect we will all be asked to do that at some point soon.

Rob

There is a beta available already under system - with regular updates

8 minutes ago, Panda88 said:

here is a beta available already under system - with regular updates

Yes, I am aware, but @Michel Kohanim advised me to wait. I do not know why, but I am attempting to adhere to such requests. 😁