Friday at 09:00 PM1 day 3 minutes ago, DennisC said:The only reason to create a support ticket is to have your plugins listed in the forum under PG3x and if you are charging for the plugins.If you are charging, there are some tax forms that need to be completed, that UD will send you.Otherwise, go to the eisy plugin page, under Development and complete the form for Publishing.Well these are under the new integrated plugin platform (not PG3x), and I have never submitted anything for plugins yet, so there is an approval process.And these will be free.
Friday at 09:28 PM1 day 22 minutes ago, Guy Lavoie said:Well these are under the new integrated plugin platform (not PG3x), and I have never submitted anything for plugins yet, so there is an approval process.And these will be free.Yes, I understand that.I hadn't realized you were not setup as a Developer already. Per Michel's post, you need to wait for that to be done.After that is finished, within eisy, go to eisy Plugins. You will then see a Development tab. Select that ander under Local Plugins select your plugin, followed by Publish.It will ask about creating a new Plugin and after agreeing, there is a form to fill out.This is from memory, as I am not at my computer but it should be close. I never found any documentation explaining how to publish from eisy-ui.
Friday at 10:45 PM1 day 1 hour ago, DennisC said:Yes, I understand that.I hadn't realized you were not setup as a Developer already. Per Michel's post, you need to wait for that to be done.After that is finished, within eisy, go to eisy Plugins. You will then see a Development tab. Select that ander under Local Plugins select your plugin, followed by Publish.It will ask about creating a new Plugin and after agreeing, there is a form to fill out.This is from memory, as I am not at my computer but it should be close. I never found any documentation explaining how to publish from eisy-ui.Yes, I've just done that. Thanks. They are now submitted. I was able to install them in new slots from the "My Published Plugins" list, so I guess I have the file names and paths correctly set up. I imagine that they now just need approval to appear in the plugins store.
Friday at 10:57 PM1 day 9 minutes ago, Guy Lavoie said:Yes, I've just done that. Thanks. They are now submitted. I was able to install them in new slots from the "My Published Plugins" list, so I guess I have the file names and paths correctly set up.I imagine that they now just need approval to appear in the plugins store.Great, well done!One thing I didn't mention before, if you are set up as Developer, and your plugins are Published, you need to change the "status" from new to active for the plugin to appear in the store.I believe when done from eisy Plugins, it show show up relatively quickly
5 hours ago5 hr FYI here's some stats on token usage for the development of a pluginThe SolarEdge MB plugin (plugin 25, version 1.5.0) has 1,902 lines of Python in its top-level modules. Its tests add another 1,170 lines.Totals for the entire development session (all but the last 2 turns were with pre v2.4 eisy-ai before the major efficiency improvements):Session stats (claude-sonnet-5-5) /session-statssession totals: 47 requests, 6,706,896 input (85% read from cache), 965,037 written 1h / 0 written 5m, 389,131 output, ~$8.92 Compactions: 7 recorded; latest (fork) ~21,034 -> ~3,954 tokens Mid-turn over-budget events: 10 (latest at round 10, ~226,130 tokens)Totals for the final version update which took 2 turns (from anthropic billing site):describing the changes: input tokens 158k, output tokens : 95generating the updated code and installing: input tokens: 1.39M, output tokens 94.6Ksonnet 5.5 costs: cache Read $0.10 / MTok cache Write $2.50 / MTokInput $2 / MTok Output $10 / MTok
Create an account or sign in to comment