Robin2:
Apart from very simple libraries with very limited functionality (the servo library being a good example) I believe it would be more useful to spend time writing a tutorial from which Arduino people could learn how to do something rather than spending the same amount of time writing some code to save them the trouble of learning it.With a tutorial you would be sharing your knowledge with the Arduino community and less experienced people would learn stuff, and probably learn incidental skills and techniques with wider application.
Complex libraries usually (always?) go wrong (or don't exactly meet the user's need) so that the user just wastes time trying to understand and fix the library which would be better spent on their own project.
Of course I might be tempted to soften my views if you intend to include extensive documentation with your library - the sort one would expect to find with a commercial product.
Just my 3 cents worth.
...R
I am not sure if I am qualified to try to teach others my concept. My library should be simple. it is the web side code that becomes complex. all the library will do is initialize a simple web page that has a link to a JavaScript file located on a web server. from here the client computer takes over when to request information based on the programming of the JavaScript. The Arduino library needs to be able to gather data for sending over the internet (which is why I needed help in the first place with PWM stuff) and eventually being able to set that data when requested by the client side JavaScript request this should be easy. For now I hope to create a clean simple sketch, a JavaScript file and CSS to tidy up where everything should go. I hope that this will allows me to play with my UNO from my web browser by clicking images of lights to turn them on/off and even entering a value into a form field to easily set PWM levels. all this with direct link feed back to the browser so i can know if anything changes through the automation i will be adding.