Hi, I think this is going to be a long thread. So I've made some changes They are visitble in rodc here http://rubytester.com/test/watir/rdoc/
changes so far - I pullled license.rb, readme.rb, changes.rb out from lib and set up the corresponding .rdoc files - switched CHANGES to HISTORY.rdoc and moved the latest 1.6.5 notes from NEWCHANGES - left NEWCHANGES as a placehold for notes on the moving forward place (I assume this is what it's for) - I like hanna rdoc template and I'm stickng with it so I make rake rdoc use hanna/rdoctask if you have it. if you don't you will have a regular old rdoc do do gem install hanna - added commonwatir/lib/**/*.rb to main watir rdoc (only for dev not gemspec) some plan - switch to jeweler/gemcutter the rake task deal with pushing to github and gemcutter and we can generate gemspec easier - make unittests run after installing the gem this has been on my personal plate for a while - copy some verbage from Watir::Browser in commonwatir to README.rdoc - probably remove the unittest from gemspec package. they can't be used anyway. (maybe move all unittests to commonwatir gem so people can run them after gem install?) marekj Watirloo: Semantic Page Objects in UseCases http://github.com/marekj/watirloo/ On Sat, Jan 9, 2010 at 11:29 PM, Alan Baird <[email protected]> wrote: > +1 for including commonwatir in the rdocs (or at least accessible from > them). I never can seem to remember the syntax for > Watir::Waiter.wait_until, which I use occasionally enough for it to be > annoying not to be in the normal places. > Alan > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development > _______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
