Hi Everyone! It's that time again nearing the end of a development cycle, and I'm pretty much ready to get started on writing/editing documentation.
So far I've updated the README file and turned it from just a simple .txt file into an .rst file, which GitHub so graciously formats for us. You can find the latest changes in the 0.7-devel branch to get an idea here: http://bit.ly/cqtQzX -- to say the least, nicer documentation would definitely go a long way IMO. Also, if you guys have any time to write up examples on how to use the HTTP client and the server in concert, I would really like to get some help in that regard. I have my ideas, but I'd like to hear yours and see if they're better than mine. The Twitter client idea might be a little tricky I think especially now that Twitter has gone OAuth exclusively -- this will require a developer account and third-party tools for computing the HMAC-SHA1 for the requests. A SOA example might be useful, but I don't have a lot of ideas as to what service to build. Anyway, it's real late on my side of the world so I'll look forward to your inputs. Have a good day everyone and I look forward to hearing from you soon! -- Dean Michael Berris deanberris.com ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Cpp-netlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
