Project still alive?

[alekslyse]

Im a developer, but honestly its so hard to understand HS plugin logic its making me insane. Got so many good projects in the pipeline it should be extremely easy to setup a dev environment and "just get it working"

I cant see any progress on this project for about a year, and just wondering if this project was given up on?

If not, as a developer im not good at writing documentation, but please try to make some more examples etc how to setup, override, and the flow of an application. Im happy lending a hand writing documentation, but first I would need to know how active this project is.

[alexdresko]

I like to consider the project alive, but I obviously haven't spent much time on it in a while. I do know that people still download and successfully use the project. And I also know it deserves a lot more attention than it gets.

I have a PR in place that will update the template and all of the packages so they work again. Will try to get that merged and published this weekend.

The goal of this project has always been to greatly simplify Homeseer development. We're getting there, incrementally. "PluginA" was basically, "Here's how it's done traditionally". "PluginB" was "Here's a better way, but it's still painful". "PluginC" is what I'm working on now. It's drastically different than the old model of HS plugin development and significantly easier. Maybe I'll spend some of this long weekend working on that as well.

If you'd like to lend a hand with documentation, I'm all for it. It's a bit hard to point you in the right direction, though. If you have an idea for areas that need attention, just ask and I'll let you know if it's worth your time.

There's probably a some good information in these github issues that could be added to the documentation if you want to take a stab at that.

[alekslyse]

That sounds good, as I tried to use 3 days understanding where to start, and the only references are 4-6 years old.

Hopefully you can create a new package soon and iron out the issues as the version updates coming up is making breaking changes in program.cs

Maybe I would also suggest making some more API layovers like

1. Make sure InitIO automatically is triggering a Task (as by official API suggetion to init it as fast as possible and offload work out of the method) -> maybe trigger it into a worker class that runs as a task and by that way can split the logic a bit more.

2. Some more endpoints for webpages, config setup, state loading etc.

[alexdresko]

In PluginC, InitIO definitely runs in a task atuomatically. I'm planning on simplifying web pages, but that might have to come in PluginD. :)

[alekslyse]

Great. Hopefully you can get the latest out today as I'm experimenting. I think all issues I have should be part of the documentation as I'm a developer, but it's easy for you to be blind of obvious function so you should have a fresh set of eyes

…

On Sun, 2 Sep 2018, 14:07 Alex Dresko, ***@***.***> wrote: In PluginC, InitIO definitely runs in a task atuomatically. I'm planning on simplifying web pages, but that might have to come in PluginD. :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#87 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADghx0FfJNEkzQX3_N6TVVDFzI-oasTOks5uW8n4gaJpZM4WWOzl> .

[oesolberg]

Sorry for not contributing back more. After using HSPI for two plugins (Twilio and RfLink) I have made some small changes in the package creation. I will try to fork latest version and create a PR to include this. This is only minor changes in the powershell script stuff grabbing graphics etc needed for HTML pages.

[alexdresko]

@oesolberg Awesome, brother. Would love to have those changes. You can attach them here if you don't want to go through the fork/PR process.

[oesolberg]

This is in fix-output.ps1. This is just the process of fetching files and adding them to the "end product". I have not made any automatic directory creation (but that should be easy)
Here is the whole file as a gist
https://gist.github.com/oesolberg/796718cfd4348698d6b1e4f2e179b4d5