Looking at the sample plugin and the SDK I am still seeing plenty of areas that are going to lead to some really messy plugin code.
How Open is HST on improving their "SDK" so that we can improve our plugin's code without having to depend on, in my case, an external DLL to do most of the heavy lifting?
For instance, the idea that I can't just register a "web page class" and have the SDK auto delegate to those classes for methods like PostBackProc is insane to me. I'm not trying to be mean, but no one should be putting a switch/case to handle all their pages.
I have a library that does a bunch of auto-wiring for my plugins (devices, web pages, actions/triggers, etc). I was hoping I could move away from this, but it appears I'm not.
I was going to release my library anyways, so I need to know how interested is HST in absorbing some of these changes directly into the SDK?
How Open is HST on improving their "SDK" so that we can improve our plugin's code without having to depend on, in my case, an external DLL to do most of the heavy lifting?
For instance, the idea that I can't just register a "web page class" and have the SDK auto delegate to those classes for methods like PostBackProc is insane to me. I'm not trying to be mean, but no one should be putting a switch/case to handle all their pages.
I have a library that does a bunch of auto-wiring for my plugins (devices, web pages, actions/triggers, etc). I was hoping I could move away from this, but it appears I'm not.
I was going to release my library anyways, so I need to know how interested is HST in absorbing some of these changes directly into the SDK?
Comment