Communication class Comm, HID, ... want to publish it, need help with it
-
Hi Guys, there is this home grown class sitting on my hard drive. The result of the last 3 years... Features: It supports easier access to ComPorts, certain kind of HID devices (HIDPOS, IBM-SurePos, Cypress-HidCom). It is extensible for new devices (raw USB bulk?). The differences of the ports are hidden from the user. Enumerates all these devices for the UI. Supports PnP. .... Almost no documentation :-( I started to prepare to publish, but did run in problems. It is just to closly coupled to UI and MFC (contains a few dialogs, references to resource strings, ..). What do you think, shall I remove all UI stuff to get a small comm lib? Who wants to test it / contribute? Dieter :-)
-
Hi Guys, there is this home grown class sitting on my hard drive. The result of the last 3 years... Features: It supports easier access to ComPorts, certain kind of HID devices (HIDPOS, IBM-SurePos, Cypress-HidCom). It is extensible for new devices (raw USB bulk?). The differences of the ports are hidden from the user. Enumerates all these devices for the UI. Supports PnP. .... Almost no documentation :-( I started to prepare to publish, but did run in problems. It is just to closly coupled to UI and MFC (contains a few dialogs, references to resource strings, ..). What do you think, shall I remove all UI stuff to get a small comm lib? Who wants to test it / contribute? Dieter :-)
I think, in general, you can make an article describing how to do what you did and post the code as an example of the implementation. (even with mfc dialogs and rest, just should be compilable). I admire the amount of work being probably behind your code. Therefore if I could recommend you something, focus on writing a documentation and let the sources as they are. I think even than your article will be valuable source of information. The idea behind is, that if anyone is interested, he can learn how to do it and then either reuse parts of your code, or if he wants he can write it at his own, but in any case it will save him a lot of time, because he will have the documentation (and possible related links) at one place (and the sources are some kind of bonus). I think, that you will agree with me, that just put together all links and materials to the subjects you implemented is a huge task. I personally prefer articles with well described idea, how to achieve something (as I am being dumb sometimes, I need quite detailed description :-) ). Then some source code with some sort of implementation is a Good Thing(TM).