Hey everyone, I''ve been refactoring Mechanize for an 0.7.0 release. Basically I''m trying to clean the code up and there are a few features that I think are unnecessary, but I would like to ask people first. 1) REXML as a parser. I want to remove support for REXML. I don''t use it. Hpricot seems to do everything I need. 2) 1.8.2 thru 1.8.4 support I''ve got a bunch of monkey patches for 1.8.2 thru 1.8.4. I''d like to remove these because I think most people are on 1.8.5 or up. 3) Page#watch_for_set I am going to remove this method. It made sense when REXML was the main parser, since REXML was so slow. I think that Hpricot is fast enough that this method is not so useful. I''m going to make 0.7.0 lazily build up form and link objects, which should give everyone a slight speed increase but makes watch_for_set obsolete (sort of). I''m changing around the class names to be better organized, but they should all have the same methods. Also, if there are any feature requests, let me know! -- Aaron Patterson http://tenderlovemaking.com/
Quoting Aaron Patterson <aaron at tenderlovemaking.com>:> Hey everyone, > > I''ve been refactoring Mechanize for an 0.7.0 release. Basically I''m > trying to clean the code up and there are a few features that I think > are unnecessary, but I would like to ask people first. > > 1) REXML as a parser. > > I want to remove support for REXML. I don''t use it. Hpricot seems to > do everything I need. > > 2) 1.8.2 thru 1.8.4 support > > I''ve got a bunch of monkey patches for 1.8.2 thru 1.8.4. I''d like to > remove these because I think most people are on 1.8.5 or up.I''m only one person, but I''m still on 1.8.4 (this assumes you are talking about Ruby 1.8.4). Doesn''t seem likely that we would be upgrading to 1.8.5 anytime soon. I guess I better get with the program! :)> > 3) Page#watch_for_set > > I am going to remove this method. It made sense when REXML was the main > parser, since REXML was so slow. I think that Hpricot is fast enough > that this method is not so useful. > > I''m going to make 0.7.0 lazily build up form and link objects, which > should give everyone a slight speed increase but makes watch_for_set > obsolete (sort of). > > I''m changing around the class names to be better organized, but they > should all have the same methods. Also, if there are any feature > requests, let me know!I''m interested in the possibility of interacting with Java scripts...not sure if that is even possible though. I thought someone had mentioned it in the past, but since you were asking... :) Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Mon, Dec 10, 2007 at 11:32:08AM -0900, barsalou wrote:> Quoting Aaron Patterson <aaron at tenderlovemaking.com>: > >> Hey everyone, >> >> I''ve been refactoring Mechanize for an 0.7.0 release. Basically I''m >> trying to clean the code up and there are a few features that I think >> are unnecessary, but I would like to ask people first. >> >> 1) REXML as a parser. >> >> I want to remove support for REXML. I don''t use it. Hpricot seems to >> do everything I need. >> >> 2) 1.8.2 thru 1.8.4 support >> >> I''ve got a bunch of monkey patches for 1.8.2 thru 1.8.4. I''d like to >> remove these because I think most people are on 1.8.5 or up. > > I''m only one person, but I''m still on 1.8.4 (this assumes you are talking > about Ruby 1.8.4). Doesn''t seem likely that we would be upgrading to 1.8.5 > anytime soon. > > I guess I better get with the program! :)Okay, I''ll leave my ruby 1.8.4 monkey patches in. I''m going to add deprecation warnings though.> >> >> 3) Page#watch_for_set >> >> I am going to remove this method. It made sense when REXML was the main >> parser, since REXML was so slow. I think that Hpricot is fast enough >> that this method is not so useful. >> >> I''m going to make 0.7.0 lazily build up form and link objects, which >> should give everyone a slight speed increase but makes watch_for_set >> obsolete (sort of). >> >> I''m changing around the class names to be better organized, but they >> should all have the same methods. Also, if there are any feature >> requests, let me know! > > I''m interested in the possibility of interacting with Java scripts...not > sure if that is even possible though. > > I thought someone had mentioned it in the past, but since you were > asking... :)Yes. I''m still working on it. Mechanize 0.7.0 is a midpoint. I''m refactoring it in preparation for 1.0.0. I''m planning on 1.0.0 to have javascript support, but it will have some (maybe many!) api incompatibilities. I want JS support too, so I''m working on it! -- Aaron Patterson http://tenderlovemaking.com/
Quoting Aaron Patterson <aaron at tenderlovemaking.com>:> On Mon, Dec 10, 2007 at 11:32:08AM -0900, barsalou wrote: >> Quoting Aaron Patterson <aaron at tenderlovemaking.com>: >><snip>> Okay, I''ll leave my ruby 1.8.4 monkey patches in. I''m going to add > deprecation warnings though. >Thanks. I''ll work on powers that be to move to 1.8.6.>><snip>> > Yes. I''m still working on it. Mechanize 0.7.0 is a midpoint. I''m > refactoring it in preparation for 1.0.0. I''m planning on 1.0.0 to have > javascript support, but it will have some (maybe many!) api > incompatibilities. > > I want JS support too, so I''m working on it!Mechanize is a good library. Thanks for creating it. Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.