November 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] two question about fasttable

by stepharo

Ok so I never understand it that way. What a bad name. Stef > >> On 28 Nov 2016, at 22:25, Henrik Nergaard <henrik.nergaard(a)uia.no> >> wrote: >> >> The datasource is a wrapper/binding between the real object and the >> view (table/list) and provides the necessary stuff for >>display and >> interaction between them. Returning custom UI elements (cells and rows) >> from the datasource is part of what >>makes it possible to reuse the >> same table/container morph for lists/tables/trees. > > this ^ :) > > Esteban > -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 29, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60309 Home: https://github.com/pharo-project/pharo-core

Nov. 29, 2016

[pharo-project/pharo-core] d3b9dd: 60309

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d3b9ddfa772a6a07ca98f1292196c1af632d4ca3 https://github.com/pharo-project/pharo-core/commit/d3b9ddfa772a6a07ca98f129… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-11-29 (Tue, 29 Nov 2016) Changed paths: M Alien.package/AlienWeakTable.class/instance/adding/add_finalizing_.st M ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/symbolic versions/stable_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F25_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60308.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60309.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60308.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60309.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI.package/FFIExternalStructure.class/class/accessing/structureAlignment.st A UnifiedFFI.package/extension/ByteArray/instance/readStringUTF8.st A UnifiedFFI.package/extension/ExternalData/instance/readStringUTF8.st Log Message: ----------- 60309 19406 integrate UFFI v0.25 https://pharo.fogbugz.com/f/cases/19406 19403 Find and replace dialog first field is unreadable in dark theme https://pharo.fogbugz.com/f/cases/19403 http://files.pharo.org/image/60/60309.zip

Nov. 29, 2016

Re: [Pharo-dev] Bloc: Problems Running

by Sean P. DeNigris

Tudor Girba-2 wrote > If you do not want to install wget, please try to load the Bloc code using > the scripts directly in a Pharo image: > > https://github.com/pharo-graphics/Bloc/blob/master/INSTALL.md#all-in-one-us… I thought that's what I was doing ha ha with: Metacello new baseline:'Bloc';repository:'github://pharo-graphics/Bloc/src';load:#git:development. Tudor Girba-2 wrote >> If you don't know what it means install User version of Bloc, as >> described in INSTALL.md I will. Tudor Girba-2 wrote >> Do you find installation guide hard to read or understand? Maybe it would be helpful to give a quick description of the motivation for the diffferent options e.g. user vs dev. Denis and I both thought "we're developers, we should install that" and apparently went down the wrong path. What would it take to add the various setups to the CI matrix? This complexity will be a high barrier to feedback... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Problems-Running-tp4924930p4925162.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 29, 2016

Re: [Pharo-dev] Stack underflow with meta links on message nodes

by Denis Kudriashov

2016-11-29 16:52 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Is there any workaround for this issue? Or maybe someone knows how to fix > this. Because the issue is present both in Pharo 5 and the latest Pharo 6. Probably meta level is not defined somewhere on MetaLink's part. When MetaLink start execution it checks current meta level and if it is higher than where it was installed then link should be ignored. For example recursion could happen if #value:value is used to resolve some #control object and meta level not defined for this part.

Nov. 29, 2016

Re: [Pharo-dev] Stack underflow with meta links on message nodes

by Marcus Denker

Hi, This looks like a bug, I will check (but tomorrow). Marcus > On 29 Nov 2016, at 16:52, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi, Iâm trying to use methinks on message nodes that are executed before the node itself and have receiver and the node as arguments. But sadly Iâm getting âstack underflowâ error when the annotated method is executed. You can use this code snippet to reproduce the error: > > > | link class | > > link := MetaLink new > metaObject: [ :v1 :v2 | ]; > control: #before; > selector: #value:value:; > arguments: #(receiver node). > > class := Object newAnonymousSubclass. > class compile: 'method 1+1'. > (class >> #method) ast statements first link: link. > > class new method. > > link uninstall > > > Is there any workaround for this issue? Or maybe someone knows how to fix this. Because the issue is present both in Pharo 5 and the latest Pharo 6. > > Cheers. > Uko

Nov. 29, 2016

Stack underflow with meta links on message nodes

by Yuriy Tymchuk

Hi, Iâm trying to use methinks on message nodes that are executed before the node itself and have receiver and the node as arguments. But sadly Iâm getting âstack underflowâ error when the annotated method is executed. You can use this code snippet to reproduce the error: | link class | link := MetaLink new metaObject: [ :v1 :v2 | ]; control: #before; selector: #value:value:; arguments: #(receiver node). class := Object newAnonymousSubclass. class compile: 'method 1+1'. (class >> #method) ast statements first link: link. class new method. link uninstall Is there any workaround for this issue? Or maybe someone knows how to fix this. Because the issue is present both in Pharo 5 and the latest Pharo 6. Cheers. Uko

Nov. 29, 2016

Re: [Pharo-dev] How to report website text bugs?

by Tim Mackinnon

Ok - great. But I will remember that for future reference. I noticed a number of small textual/grammatical things in the Pharo 5 UI as well, so I will dust of the cobwebs on how to create some some slices and see if I can help in a small way. Tim > On 29 Nov 2016, at 08:41, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > yes, but no needâ¦ I already fixed it :) > >> On 29 Nov 2016, at 09:29, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >> >> Report them on pharo.fogbugz.com <http://pharo.fogbugz.com/> >> >> http://pharo.org/contribute-report-bug <http://pharo.org/contribute-report-bug> >> >> Use Project: Websites as the reference. >> >> Phil >> >> On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> Hi Guys - how is the best way to report website and text bugs? >> >> As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can. >> >> I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed) >> >> Are you using macOS Sierra? >> Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder. >> We are working to fix this temporary inconvenience. >> >> >> Also - the Hello world command line example on the front page doesnât work on a standard Terminal on a Mac (you get an error: >> >> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'" >> -bash: !'": event not found >> >> The culprit is of course the â!â Character so a better example might be: >> >> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'" >> Hello WorldStdioStream: 'stdout' >> >> Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:â¦.?). I think its an impressive example, but it just doesnât quite look right? >> >> >> Tim >> >

Nov. 29, 2016

Re: [Pharo-dev] [Esug-list] Any Pharo 5 in the industrial setup?

by Alejandro Infante

Hi Yuriy, Iâm planning on porting my start-up app from Pharo4 to Pharo5 in mid-december. Maybe we could talk on January after I spend some time using it :). Alejandro > On Nov 29, 2016, at 7:45 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Dear all, > > my name is Yuriy Tymchuk, I am a researcher from Bern University and the author of QualityAssistant and other quality-related tweaks and experiments in Pharo. > > I am interested to know is anybody uses Pharo 5 in industry as I've spent plenty of time to develop QualityAssistant and I am interested to know if it is useful in the industrial setup. So if you know any project please let me know. If you are an industrial developer working on Pharo 5 Iâm interested in a short chat. If you donât have a time for chat maybe you can spend a couple of minutes on a small questioner because I really want to make QA useful for developers. > > Cheers. > Yuriy > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

Nov. 29, 2016

Re: [Pharo-dev] Bloc: Problems Running

by Tudor Girba

Hi, > On Nov 29, 2016, at 1:08 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2016-11-29 12:46 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > I would really like to help you. > Could you explain why you want to install #git:development? > > If you don't know what it means install User version of Bloc, > > It was same problem for me because as developer I choose development version :) > As I understand dev version uses Iceberg and user version is not. And my problem was related to feature/issue of Iceberg to require github keys. Indeed, the dev versions first installs Iceberg and then loads the code. This essentially ensures that we get an updated Iceberg repository in the image which is ready to be played with. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

Nov. 29, 2016