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

QUESTION about smalltalkhub.com/projectList

by Esteban Lorenzano

Hi, Soâ¦ I had some time this morning so I added the required /json to project list. is /json and not ?format=json because 1) it will be just one output format so no point on having a parameter, and 2) is easier to add the filter that way :) This is still NOT in productionâ¦ it will be on monday, following the advice of ânot deploying during week endsâ but nowâ¦ doing this idea came to my mind: actually, the name /projectList is bad (super bad), because it is not a list of projects, but a list of repositories. Soâ¦ I think link should be: /list ot /repositoriesList instead. It will be a lot clearerâ¦ specially because Iâm also working on a page for real projects (taken from the catalog made by Stef and Damien). So, what do you think? Can I rename the repositories list link? Esteban

March 14, 2015

Re: [Pharo-dev] Automatically rewriting deprecations

by stepharo

>> I do not know if you know but there is a support for automatically >> rewriting deprecated methods :) >> It is there but is not used. > > Nice. Looks like more deprecations should be done that way. > What would be needed to make that fit in the CI workflow well? I do not know. Now what would be good is to use this mecanism and learn. Stef

March 14, 2015

Re: [Pharo-dev] [Issue tracker] Pharo3 issues

by Esteban Lorenzano

Pharo 3 release date was 1yr ago. I think we are 2 weeks from releasing Pharo4â¦ I do not think we should take action on those items (move the ones still valid to Pharo4 and close them in Pharo3). Esteban > On 14 Mar 2015, at 11:56, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Marcus Denker-4 wrote >> There are 10 issues with an explicit Pharo3 tag: > > What is the release date? Or is it just when there are no more issues? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Issue-tracker-Pharo3-issues-tp4811844p4811849.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 14, 2015

Re: [Pharo-dev] [Issue tracker] Pharo3 issues

by Sean P. DeNigris

Marcus Denker-4 wrote > There are 10 issues with an explicit Pharo3 tag: What is the release date? Or is it just when there are no more issues? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-tracker-Pharo3-issues-tp4811844p4811849.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 14, 2015

[Issue tracker] Pharo3 issues

by Marcus Denker

Hi, There are 10 issues with an explicit Pharo3 tag: https://pharo.fogbugz.com/f/filters/99/3-0-All <https://pharo.fogbugz.com/f/filters/99/3-0-All> What do we do with them? Marcus

March 14, 2015

[Issue Tracker] open issues down to 644

by Marcus Denker

Hi, We managed to get the issue tracker to 644 open issuesâ¦. with e.g. 60 issues closed the last 7 days alone. For one this is nice: number of issues is decreasing even though new issues are reported. Yes 644 is very high. Ca everyone please check the reports, especially you own old ones? Maybe an issue open since >12 months of the âwould be niceâ kind actually can be closed? Or things that only you care about but even that not enough to actually do something? Keep in mind that it would be trivial to add literally *thousands* of âthis looks strangeâ âmaybe this could be simplerâ or âit would be nice ifâ issues. Just that it does not help anyone, as nobody will ever do this if it is already not important enough for *you* to do. Marcus

March 14, 2015

Automatically rewriting deprecations

by Stephan Eggermont

On 13/03/15 18:01, stepharo wrote:(in Re: #milliseconds versus #milliSeconds) > Le 3/3/15 22:37, Stephan Eggermont a Ã©crit : >> On 03/03/15 14:37, Sean P. DeNigris wrote: >>> I definitely recall feeling "lots of pain" with the subStringXyz -> >>> substringXyz that we're still dealing with in recent updates (I think I >>> started that push as a naive newbie), but I'm not sure about the "little >>> gain" part. It's hard to quantify the negative effect of >>> inconsistency in >>> the system, or the empowering effect of uniformity. >> >> These kind of changes should be accompanied by a rewrite script, b.t.w. >> Upgrading is much easier if you can just select the rewrites you want >> to apply. > > I do not know if you know but there is a support for automatically > rewriting deprecated methods :) > It is there but is not used. Nice. Looks like more deprecations should be done that way. What would be needed to make that fit in the CI workflow well? Stephan

March 14, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V1.0

by Juan Pablo Sandoval Alcocer

Hi, I was trying to use RProjectConnector in my Mac (1.9.1) and i have some issues :(. I have copied the dynamic libraries of R to /usr/lib directory (.i.e. libR.dylib). But PharoVM does not find the libraries. For instance, this line of code returns always nil. self nbGetSymbolAddress: 'Rf_initEmbeddedR' module: #R "copied from the project" I also tried copying the libraries to folder Pharo.app/Contents/MacOS/Plugins. or passing the library name as parameter like: self nbGetSymbolAddress: 'Rf_initEmbeddedR' module: 'libR.dylib' or self nbGetSymbolAddress: 'Rf_initEmbeddedR' module: '/usr/lib/libR.dylib' But i had not success. Could someone help me? I am doing something wrong? Thanks, Juampi 2014-12-08 11:10 GMT-03:00 Blondeau Vincent <vincent.blondeau(a)worldline.com> : > Hello everyone, > > > > I am glad to announce the first version of the RProjectConnector, a > binding between Pharo and R using NativeBoost. > > > > You can now call directly your R methods from Pharo: > > data := (1 to: 1000) collect: #yourself. > > res := (#acf asRFunctionWith: {data}) eval > > > > To use it, you should copy the R libraries near the Pharo VM (see the > documentation on SmalltalkHub to see how to proceed) and > > Gofer it > > smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector'; > > configuration; > > loadStable > > Donât forget to relaunch Pharo after the installation to be able to use > the connector. > > > > The sources are available on Smalltalkhub: > > http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector > > > > if you want to participate, just ask me! > > > > Cheers, > > > > Vincent BLONDEAU > > ------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. > -- Saludos, Juan Pablo

March 13, 2015

Re: [Pharo-dev] ZnUrl: Constructing without Scheme

by Norbert Hartl

> Am 13.03.2015 um 20:04 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > I know you mean well, but you cannot confuse things. Without some context, not much can be done. #asZnUrl has totally no context. > Maybe this is misunderstanding. My point was that there is no context given by #asUrl. So it is not a locator at all therefor the leading slash is confusing to me. > I recently added ZnUrl>>#withRelativeReference: reference > "Return a new URL by parsing & resolving the relative reference using myself as base URL. > This implements the process described in RFC 3986 Section 5" > > See also #testReferenceResolution > > The specs (RFCs) do count, the rest is often wishful thinking that does not take all use cases into account. > Agreed, I'll consult the specs again. > Of course, ZnUrl is not the final answer to this broad problem, just some answer that started in the HTTP world. > > I don't want to change its parsing unless there is a very clear reason and explanation why/how. > I didn't want to complain. Your stuff is pretty awesome and there should be really good reasons to change it. History just introduced the ambiguity between URL and URl. An URI is just an identifier. A scheme puts additional meaning on how to interpret stuff. Sorry if I confused anything. Norbert >> On 13 Mar 2015, at 19:18, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >>> Am 13.03.2015 um 17:29 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> >>>> On 13 Mar 2015, at 17:20, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>> My concern is more that >>>> >>>> 'urn:foo:bar' asUrl >>>> >>>> doesn't do what it should :) >>> >>> That is because #urn is not in #schemesNotUsingDoubleSlash, it should probably be added. >>> >>> But then I have to read more about it first. >>> >>> https://en.wikipedia.org/wiki/Uniform_resource_name >> >> I need to dig into it, too. I just wondered why >> >> 'abc' asUrl >> >> prints '/abc' >> >> That doesn't appear right. What do you think? It is just a URI path or a relative URL (depending how you like to put it). A relative URL resolved by a base URI will work because 'http://foo.com/foo//abc' (<â double slash) is still valid. >> >> I think that scheme is supposed to be a class and the parsing of the remaining string is delegated to that scheme. That would make it more easy to have URL (the locator part) as specialization to plain URI. But then it will make the code base a lot more complex and performance wise it probably has its cost. But then there would be a scheme registry that can easily extended by custom schemes. >> >> Just some quick thoughts, >> >> Norbert > >

March 13, 2015

Re: [Pharo-dev] Athens BitBlt bug?

by stepharo

I do not know. May be igor is reading this mailing-list but I doubt. 2015-01-27 21:46 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: > > Anyone knows what this BitBlt bug is or was? > 12818 <https://pharo.fogbugz.com/default.asp?12818> Last row missing > 13236 <https://pharo.fogbugz.com/default.asp?13236> Fix 1 extra > height for Cairo surface > > Because with the fix in 13236, it is not (easily) possible to make > a repeating (vertical) pattern paint with 1 pixel height: > 14813 <https://pharo.fogbugz.com/default.asp?14813> Wrong size for > Athens surface pattern paint from a Form > > > nicolai > > > > BUMP > > >

March 13, 2015