March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Problems with Critics

by Yuriy Tymchuk

Thank you very much! Uko On 02 Mar 2014, at 18:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > Known problem (12971 CriticBrowser causes error on opening when delivering notification) > The fix just waits for integration. > > > > 2014-03-02 18:31 GMT+01:00 <btc(a)openinworld.com>: > Yuriy Tymchuk wrote: > Hi guys. > > When I run critics on my code i get: 'This block accepts 2 arguments, but was called with 1 argument.â. Iâm not sure whose problem it is, but the related block is [ :a :b | self menu: a shifted: b ]. Any ideas? > > Uko > > > What method is the block being passed to ? It would seem that is expecting a block with one argument and you are passing in a block with two arguments. Try evaluating the following in Workspace.... > > [ :a :b | self menu: a shifted: b ] value > > [ :a :b | self menu: a shifted: b ] value: 1 > > > cheers -ben > > >

March 2, 2014

Re: [Pharo-dev] Problems with Critics

by Nicolai Hess

Known problem (12971 <https://pharo.fogbugz.com/default.asp?12971>CriticBrowser causes error on opening when delivering notification) The fix just waits for integration. 2014-03-02 18:31 GMT+01:00 <btc(a)openinworld.com>: > Yuriy Tymchuk wrote: > >> Hi guys. >> >> When I run critics on my code i get: 'This block accepts 2 arguments, but >> was called with 1 argument.'. I'm not sure whose problem it is, but the >> related block is [ :a :b | self menu: a shifted: b ]. Any ideas? >> >> Uko >> >> >> > What method is the block being passed to ? It would seem that is > expecting a block with one argument and you are passing in a block with two > arguments. Try evaluating the following in Workspace.... > > [ :a :b | self menu: a shifted: b ] value > > [ :a :b | self menu: a shifted: b ] value: 1 > > > cheers -ben > > >

March 2, 2014

Re: [Pharo-dev] Problems with Critics

by btc＠openinworld.com

Yuriy Tymchuk wrote: > Hi guys. > > When I run critics on my code i get: 'This block accepts 2 arguments, but was called with 1 argument.â. Iâm not sure whose problem it is, but the related block is [ :a :b | self menu: a shifted: b ]. Any ideas? > > Uko > > What method is the block being passed to ? It would seem that is expecting a block with one argument and you are passing in a block with two arguments. Try evaluating the following in Workspace.... [ :a :b | self menu: a shifted: b ] value [ :a :b | self menu: a shifted: b ] value: 1 cheers -ben

March 2, 2014

Problems with Critics

by Yuriy Tymchuk

Hi guys. When I run critics on my code i get: 'This block accepts 2 arguments, but was called with 1 argument.â. Iâm not sure whose problem it is, but the related block is [ :a :b | self menu: a shifted: b ]. Any ideas? Uko

March 2, 2014

Re: [Pharo-dev] understanding postgresv2

by Tudor Girba

Another thing I see in the comment of PGConnection is this: Copyright (c) 2001-2003 by Yanni Chiu. All Rights Reserved. Does anyone know the actual license? Doru On Sun, Mar 2, 2014 at 5:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I am trying to understand how PostgresV2 is implemented because I would > like to build some inspector support for it, and I encounter a couple of > issues. In case anyone knows the answer, it would speed up my effort: > > - Why is result an instance variable in PGConnection? Making it a variable > always returns the same object when executing a query and that is a bit of > a pain. > > - Why does the PGResult have the possibility of holding multiple > PGResultSets? When is it possible to have multiple at the same time? (when > you execute a query, the result is being initialized) > > - When running something like > connection execute: 'select * from ...' > the PGResultSet already includes all rows of the query. Is it not possible > to have a stream-like functionality in which the actual rows are retrieved > only on demand? (a similar functionality exists in DBXTalk) > > - What is the difference between PGAsciiRow and PGDataRow? > > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

March 2, 2014

understanding postgresv2

by Tudor Girba

Hi, I am trying to understand how PostgresV2 is implemented because I would like to build some inspector support for it, and I encounter a couple of issues. In case anyone knows the answer, it would speed up my effort: - Why is result an instance variable in PGConnection? Making it a variable always returns the same object when executing a query and that is a bit of a pain. - Why does the PGResult have the possibility of holding multiple PGResultSets? When is it possible to have multiple at the same time? (when you execute a query, the result is being initialized) - When running something like connection execute: 'select * from ...' the PGResultSet already includes all rows of the query. Is it not possible to have a stream-like functionality in which the actual rows are retrieved only on demand? (a similar functionality exists in DBXTalk) - What is the difference between PGAsciiRow and PGDataRow? Doru -- www.tudorgirba.com "Every thing has its own flow"

March 2, 2014

Re: [Pharo-dev] Zinc bug submitting form via GET?

by Pharo4Stef

On 02 Mar 2014, at 12:42, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Pharo4Stef wrote >> Sean how it is different from Soup? > > It adds a layer from a web browsing POV, so you can say "#submit this form" > and "#click the link whose text #beginsWith: 'Whatever'". I used Soup > underneath, since it is the very forgiving of the underlying html is > malformed. Ok I looked a bit at mechanize. Looks nice. > > > Pharo4Stef wrote >> Do you write tests? > > Yes. Excellent! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Zinc-bug-submitting-form-via-GET-tp4747276p4747311.ht… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 2, 2014

Re: [Pharo-dev] Zinc bug submitting form via GET?

by Sven Van Caekenberghe

Hi Sean, On 02 Mar 2014, at 06:49, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > In porting the Mechanize web scraping library from Ruby, I started with the > following example: > a.get('http://google.com/') do |page| > search_result = page.form_with(:name => 'f') do |search| > search.q = 'Hello world' > end.submit > > It GETs > http://www.google.com/search?ie=ISO-8859-1&hl=en&source=hp&q=Hello+world&gb… > > I tried to do that with Zinc via formAt: name put:, but when I sent #get, > the query was empty and the response was another blank search form. It took > me some time to figure out what was going on and change to #queryPut:at: in > the GET case, but now I'm managing form logic from the outside. Since GET is > valid for forms (apparently it is the default per > http://www.w3schools.com/tags/att_form_method.asp) it seems Zinc should > handle this more gracefully. I would expect it to check for form fields and > add them to the query when doing a GET. What do you think? Cool that you are trying to do a project like that. The reason this fails is because it is explicitly prevented in ZnClient>>#method:! If you go there and remove the whole #ifTrue:, sending entities with a GET and your example will work. Making the change, one unit test fails ZnClientTest>>#testGetAfterPost and that is why the code is there: if you re-use a ZnClient instance (with its connection) to the same (REST) host, you are also re-using the request object, and then you don't want to carry over entities from a previous request. This is a feature that we use internally all the time. I have to think about the best solution: like make this an option, and which would best be the default. I'll come back to you. Thanks for the feedback, Sven > n.b. Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'Mechanize'; > package: 'Mechanize'; > load. > > > > > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Zinc-bug-submitting-form-via-GET-tp4747276.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 2, 2014

Re: [Pharo-dev] Zinc bug submitting form via GET?

by Sean P. DeNigris

Pharo4Stef wrote > Sean how it is different from Soup? It adds a layer from a web browsing POV, so you can say "#submit this form" and "#click the link whose text #beginsWith: 'Whatever'". I used Soup underneath, since it is the very forgiving of the underlying html is malformed. Pharo4Stef wrote > Do you write tests? Yes. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Zinc-bug-submitting-form-via-GET-tp4747276p4747311.ht… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 2, 2014

Re: [Pharo-dev] Zinc bug submitting form via GET?

by Pharo4Stef

which parser will you use to parse HTML? On 02 Mar 2014, at 06:49, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > In porting the Mechanize web scraping library from Ruby, I started with the > following example: > a.get('http://google.com/') do |page| > search_result = page.form_with(:name => 'f') do |search| > search.q = 'Hello world' > end.submit > > It GETs > http://www.google.com/search?ie=ISO-8859-1&hl=en&source=hp&q=Hello+world&gb… > > I tried to do that with Zinc via formAt: name put:, but when I sent #get, > the query was empty and the response was another blank search form. It took > me some time to figure out what was going on and change to #queryPut:at: in > the GET case, but now I'm managing form logic from the outside. Since GET is > valid for forms (apparently it is the default per > http://www.w3schools.com/tags/att_form_method.asp) it seems Zinc should > handle this more gracefully. I would expect it to check for form fields and > add them to the query when doing a GET. What do you think? > > n.b. Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'Mechanize'; > package: 'Mechanize'; > load. > > > > > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Zinc-bug-submitting-form-via-GET-tp4747276.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 2, 2014