i started using DCH++ a few weeks back and i think its great. only thing im not too happy with is that it doesnt have a GUI. But u have to make sacrifices for better software i guess. With this in mind i would like to suggest that DCH come with a built in webserver which can be accessed by the plugin interface. So if a plugin wants to use a webpage for its settings it can register with the plugin manager.
EG if someone goes to say http://127.0.0.1/ then DCH++ can give a simple list of plugins that have registered themselves and make links like http://127.0.0.1/pluginname/
The pluginmanager would then fire an event to the requested plugin and that plugin would have to handle the request.
I would do this myself but im just not that advanced with C++
Web interface for DCH++
Moderator: Moderators
-
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us
Re: Web interface for DCH++
arnetheduck made the plugin interface so that a 3rd party could make such a plugin if they wanted. The lack of a GUI is intentional; perhaps you'd be happier with YnHub, which is great software?LispWarez wrote:I would do this myself but im just not that advanced with C++
u missed the point of what i was trying to say. i dont want the developers to make a whole webpage for DCH++. just the webserver part. This way _all_ plugins can have access to a "web" interface and can all share one interface. what if there were 2 plugins that had a web server built into it. you would have to run them both on different ports and it would use up more resources and there would have to be different auth metheds for both of them. with what i suggest is just a very basic webserver which can auth agains the registered users on the hub (of course with a certain level)
-
- Posts: 506
- Joined: 2003-01-03 07:33