October 2017 - Pharo-dev - lists.pharo.org

Esteban's ChangeLog week of 16 October 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 16 October 2017 to 22 October 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=16/10/2017&to=22/10/2017 ChangeLog ========= 17 October 2017: ---------------- * I spent an stupid amount of time creating *platinum* account on [consortium site](http://consortium.pharo.org). :( * I spent a couple of days doing a new bridge for Objective-C (which allow cool stuff on macs, but not only). While this is not "direct-Pharo", I think the new "headless VMs" that will be a thing in the near future will allow more "native-oriented" development and interacting with the underlying platform is needed to make the echosystem boom in that area. There are still some caveats, but is already usable :) New bridge can be found [here](https://github.com/estebanlm/objcbridge). cheers! Esteban

Oct. 23, 2017

Re: [Pharo-dev] Bloc status

by Tudor Girba

Hi Sean, Bloc can be used for constructing element-based scenes. There is no built-in model for widgets yet. We use it in the new generation of the Glamorous Toolkit, and right now we have three such "real life scenariosâ that you can play with: - Transcript - Documenter - Mondrian You can find more details here: https://github.com/feenkcom/gtoolkit Cheers, Doru > On Oct 23, 2017, at 4:27 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Tudor Girba-2 wrote >> Bloc is usable since half a year (the tutorial from ESUG was also given at >> PharoDays and works out of the box). > > [not-a-rant ;)] > After spending a good part of the day playing with Bloc, I'm wondering > whether I am approaching it wrong. When I hear "useable", I think useful in > real life scenarios - maybe not necessarily production, but at least > day-to-day personal/in-house use. With many failing examples, deprecations, > and seemingly minimally working text support (I was playing with > BlTextElement, not looking for a full editor), I didn't find this to be the > case. Am I missing something? Was "useable" meant in the sense of "ready for > experimentation and feedback"? I am not complaining at all. I just want to > be clear on the status so I effectively manage my expectations and find the > best way to help out. Thanks! > [/not-a-rant ;)] > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- www.tudorgirba.com www.feenk.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

Oct. 23, 2017

Re: [Pharo-dev] Bloc status

by Dimitris Chloupis

I agree with Markus on that one , I am really a ârelease first update laterâ kind of guy. Which of course means also that I am against the idea of having only 1 release per year for Pharo. The why has been explained in myriads of online blog posts because I am far from the only one to believe in this. This why I never stuck with the stable release , I never saw any use for me or anyone else. Quite the contrary I think it hurts the development process by delaying bug reports. On Mon, 23 Oct 2017 at 05:27, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote > > Bloc is usable since half a year (the tutorial from ESUG was also given > at > > PharoDays and works out of the box). > > [not-a-rant ;)] > After spending a good part of the day playing with Bloc, I'm wondering > whether I am approaching it wrong. When I hear "useable", I think useful in > real life scenarios - maybe not necessarily production, but at least > day-to-day personal/in-house use. With many failing examples, deprecations, > and seemingly minimally working text support (I was playing with > BlTextElement, not looking for a full editor), I didn't find this to be the > case. Am I missing something? Was "useable" meant in the sense of "ready > for > experimentation and feedback"? I am not complaining at all. I just want to > be clear on the status so I effectively manage my expectations and find the > best way to help out. Thanks! > [/not-a-rant ;)] > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Oct. 23, 2017

Re: [Pharo-dev] XPath chapter...

by HernÃ¡n Morales Durand

I don't know for Pharo development, but I used XPath in Pharo for getting a textual description of gene ontology terms, for example: #('GO:0005623' 'GO:0017071' 'GO:0030680') do: [ : goTerm | | xPath xmlDoc quickGO | quickGO := 'http://www.ebi.ac.uk/QuickGO-Old/GTerm?id={1}&format=oboxml' format: { goTerm }. xmlDoc := (XMLDOMParser on: (ZnEasy get: quickGO) contents) parseDocument. xPath := XPath for: 'normalize-space(/obo/term/name/text())' in: xmlDoc. Transcript show: goTerm; tab; show: xPath; cr ]. Here you've got similar code in Perl and Java so you can compare: https://www.ebi.ac.uk/QuickGO-Old/clients/download-term.pl https://www.ebi.ac.uk/QuickGO-Old/clients/DownloadTerm.java Best regards, HernÃ¡n 2017-10-21 14:04 GMT-03:00 J.F. Rick <self(a)je77.com>: > NICE! I was just using XPath for Selenium testing. It is really great for > that application (commanding a browser like Firefox or Chrome to simulate > user actions). What are the applications for XPath in Pharo? Unit testing of > generating markup? > > Cheers, > > Jeff > > PS After spending significant time with other languages at work, I really > have an appreciation of how wonderful Pharo is as a development environment.

Oct. 23, 2017

Re: [Pharo-dev] Bloc status

by Sean P. DeNigris

Tudor Girba-2 wrote > Bloc is usable since half a year (the tutorial from ESUG was also given at > PharoDays and works out of the box). [not-a-rant ;)] After spending a good part of the day playing with Bloc, I'm wondering whether I am approaching it wrong. When I hear "useable", I think useful in real life scenarios - maybe not necessarily production, but at least day-to-day personal/in-house use. With many failing examples, deprecations, and seemingly minimally working text support (I was playing with BlTextElement, not looking for a full editor), I didn't find this to be the case. Am I missing something? Was "useable" meant in the sense of "ready for experimentation and feedback"? I am not complaining at all. I just want to be clear on the status so I effectively manage my expectations and find the best way to help out. Thanks! [/not-a-rant ;)] ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 23, 2017

Bloc Feedback

by Sean P. DeNigris

Highlights: - BlCornerRadii - 1st class corners - yay to the death of cryptic arrays for this kind of thing :) Questions: - How would one do e.g. a ticking clock in Bloc? The only possibly relevant example I see is BlAnimatedCursor. Is that a typical usage? One thing that I'm not sure how to translate to a BlElement is that the cursor seems to be responsible for starting and stopping the animation via #activateOn:, which doesn't exist for an element. How would one prevent an element's animation from continuing to run after a space was closed? - BlElement has 278 instance-side methods. A frequent battle cry against Morphic was the bloated Morph class with 899. Definitely an improvement, but are we "there yet"? - Does Bloc implement its own keybinding outside of "Keymapping" e.g. BlShortcut? If so, why? Will it ultimately be a replacement? - In BlTextEditElement class>>#exampleText, text construction seems awfully complex (`text := BrRopedText rope: (BrCollectionRope collection: (String loremIpsum: 30)). text attributes: { BrFontWeightAttribute bold }.`. How does that way contrast to e.g. `'X' asRopedText`? Problems: BlBasicExamples - #exampleShapes, select the yellow shape with red border -> inspector -> Transformations Tab -> Click on Composition -> "ShouldNotImplement: #multiplyOn: should not have been implemented in BlCompositeTransformation" - #exampleImageBackground -> "ShouldBeImplemented: #fillPath:withForm: should have been implemented in SpartaCairoFillPainter" BlTextEditElement class>>#exampleText - insert some characters and then press [delete] -> "Error: Illegal sub-sequence end index: 44" - There is aBlSelectionHandler, but I can't seem to select any of the text BrAttributeRopeExamples#>>simpleRope -> inspect return value -> In inspector, click on "Children" tab -> "Error: Improper store into indexable object" - In BlLinearLayoutExamples class>>#exampleVerticalLeftCenterRightRTL, - the red sub-element does `c linear horizontal alignLeft`, which is then overridden by its parent's `BlLinearLayout vertical "rightToLeft"`. Was it intentional to show the precedence because I found it confusing when an element that sent #alignLeft showed up on the right! - the yellow sub-element does not appear at all. Maybe it should do a `c vertical exact: 100.` like its siblings? - All BlAnimationExamples lead to deprecation warnings and DNU's, but *do not even attempt* #exampleBallsAnim or face endlessly multplying debugger windows! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 23, 2017

Re: [Pharo-dev] Some french forgotten in QualityAssistant

by casimiro barreto

Indeed. Anyways the use of one or other word should be uniform. Em 22 de out de 2017 2:05 PM, "Pavel Krivanek" <pavel.krivanek(a)gmail.com> escreveu: > But "critique" IS English (https://en.wikipedia.org/wiki/Critique) " > Critic" is a person who makes critique. Actually, the Quality Assistant > is developed by people from Ukraine and they discovered that they did this > mistake too and they needed to rename all occurrences of the world "critic" > to "critique". > > -- Pavel > > 2017-10-22 17:45 GMT+02:00 casimiro barreto <casimiro.barreto(a)gmail.com>: > >> The packages of QualityAssistant in the catalog browser have some >> 'critique' instead of 'critic'. That causes some trouble. Look at >> ReSingleCritiqueEvent... >> >> Just saying... >> >> -- >> The information contained in this message is confidential and >> intended to the recipients specified in the headers. If you received >> this message by error, notify the sender immediately. The >> unauthorized use, disclosure, copy or alteration of this message >> are strictly forbidden and subjected to civil and criminal sanctions. >> > >

Oct. 23, 2017

Re: [Pharo-dev] Primitive Failed error trying openInExternalWindow

by Eduardo de Oliveira Padoan

Thanks, I will try it. I will check your game too, I like learning from examples. Em dom, 22 de out de 2017 18:14, ClÃ©ment Bera <bera.clement(a)gmail.com> escreveu: > Hi Eduardo, > > Your FFIStructures are not initialised (I thought this was solved in > latest Pharo 7 ? Maybe not integrated yet). Run: > > FFIExternalStructure allSubclassesDo: #rebuildFieldAccessors. > > Then your code should work. > > I wrote a simple game using Pharo/SDL2/Cairo and it works very well (50fps > without problems, responsiveness is really good, etc.), the ReadMe includes > how to run it on Ubuntu/Mac OS X/Windows, check here: > > https://github.com/clementbera/wizard-battle-arena > > Let me know if you have other questions. > > On Sat, Oct 21, 2017 at 6:28 PM, Eduardo de Oliveira Padoan < > eduardo.padoan(a)gmail.com> wrote: > >> Hi, greetings! >> >> I was trying out some examples from the Pharo By Example book on the >> latest development version of Pharo, and I wanted to create a stand-alone >> window for a simple game on Ubuntu. So I found out the openInExternalWindow >> method, the window appears but I get this error that I couldn't understand, >> and could not find any reference to it online. So I'm not sure if it's a >> bug. >> >> The simplest way I found to reproduce it was: >> >> 'Hello' asMorph openInExternalWindow. >> >> I'm using Pharo 7 on Ubuntu 17.10. >> >> A copy of the stack: >> >> ByteArray(Object)>>primitiveFailed: >> ByteArray(Object)>>primitiveFailed >> ByteArray>>integerAt:size:signed: >> ByteArray>>unsignedLongAt: >> SDL_KeyDownEvent>>windowID >> OSSDL2Driver>>convertEvent: >> [ event := self convertEvent: sdlEvent. >> event ifNotNil: [ eventQueue nextPut: event ] ] in >> OSSDL2Driver>>processEvent: in Block: [ event := self convertEvent: >> sdlEvent.... >> BlockClosure>>on:do: >> OSSDL2Driver>>processEvent: >> OSSDL2Driver>>eventLoopProcessWithoutPlugin >> [ self eventLoopProcessWithoutPlugin ] in OSSDL2Driver>>setupEventLoop in >> Block: [ self eventLoopProcessWithoutPlugin ] >> [ self value. >> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self >> value.... >> >> But it seems incomplete. Any more information I can provide? >> >> Thank you. >> > > > > -- > ClÃ©ment BÃ©ra > Pharo consortium engineer > https://clementbera.wordpress.com/ > BÃ¢timent B 40, avenue Halley 59650 > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve+d'Ascq&entry=gmail&source=g>Villeneuve > d > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve+d'Ascq&entry=gmail&source=g> > 'Ascq > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve+d'Ascq&entry=gmail&source=g> >

Oct. 22, 2017

Re: [Pharo-dev] Primitive Failed error trying openInExternalWindow

by Eduardo de Oliveira Padoan

Thanks for the explanation Stef. It would probably be a good idea to have a kind of "reverse depreciation warning" in this method, as it seems like a newbie pitfall :P Em dom, 22 de out de 2017 17:44, Stephane Ducasse <stepharo.self(a)gmail.com> escreveu: > Hello Eduardo > > this method is not done to be invoked like that. In the future Pharo > will move to SDL (in fact to OSWindow based on SDL or other > framework). Right now OSWindow is not ready to be really used. > Right now what you should do is resize the main window the the size of > your largest morph. > We should definitively invest more in the deployment of Application. > > Stef > > On Sat, Oct 21, 2017 at 6:28 PM, Eduardo de Oliveira Padoan > <eduardo.padoan(a)gmail.com> wrote: > > Hi, greetings! > > > > I was trying out some examples from the Pharo By Example book on the > latest > > development version of Pharo, and I wanted to create a stand-alone window > > for a simple game on Ubuntu. So I found out the openInExternalWindow > method, > > the window appears but I get this error that I couldn't understand, and > > could not find any reference to it online. So I'm not sure if it's a bug. > > > > The simplest way I found to reproduce it was: > > > > 'Hello' asMorph openInExternalWindow. > > > > I'm using Pharo 7 on Ubuntu 17.10. > > > > A copy of the stack: > > > > ByteArray(Object)>>primitiveFailed: > > ByteArray(Object)>>primitiveFailed > > ByteArray>>integerAt:size:signed: > > ByteArray>>unsignedLongAt: > > SDL_KeyDownEvent>>windowID > > OSSDL2Driver>>convertEvent: > > [ event := self convertEvent: sdlEvent. > > event ifNotNil: [ eventQueue nextPut: event ] ] in > > OSSDL2Driver>>processEvent: in Block: [ event := self convertEvent: > > sdlEvent.... > > BlockClosure>>on:do: > > OSSDL2Driver>>processEvent: > > OSSDL2Driver>>eventLoopProcessWithoutPlugin > > [ self eventLoopProcessWithoutPlugin ] in OSSDL2Driver>>setupEventLoop in > > Block: [ self eventLoopProcessWithoutPlugin ] > > [ self value. > > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self > > value.... > > > > But it seems incomplete. Any more information I can provide? > > > > Thank you. > >

Oct. 22, 2017

Re: [Pharo-dev] Primitive Failed error trying openInExternalWindow

by ClÃ©ment Bera

Hi Eduardo, Your FFIStructures are not initialised (I thought this was solved in latest Pharo 7 ? Maybe not integrated yet). Run: FFIExternalStructure allSubclassesDo: #rebuildFieldAccessors. Then your code should work. I wrote a simple game using Pharo/SDL2/Cairo and it works very well (50fps without problems, responsiveness is really good, etc.), the ReadMe includes how to run it on Ubuntu/Mac OS X/Windows, check here: https://github.com/clementbera/wizard-battle-arena Let me know if you have other questions. On Sat, Oct 21, 2017 at 6:28 PM, Eduardo de Oliveira Padoan < eduardo.padoan(a)gmail.com> wrote: > Hi, greetings! > > I was trying out some examples from the Pharo By Example book on the > latest development version of Pharo, and I wanted to create a stand-alone > window for a simple game on Ubuntu. So I found out the openInExternalWindow > method, the window appears but I get this error that I couldn't understand, > and could not find any reference to it online. So I'm not sure if it's a > bug. > > The simplest way I found to reproduce it was: > > 'Hello' asMorph openInExternalWindow. > > I'm using Pharo 7 on Ubuntu 17.10. > > A copy of the stack: > > ByteArray(Object)>>primitiveFailed: > ByteArray(Object)>>primitiveFailed > ByteArray>>integerAt:size:signed: > ByteArray>>unsignedLongAt: > SDL_KeyDownEvent>>windowID > OSSDL2Driver>>convertEvent: > [ event := self convertEvent: sdlEvent. > event ifNotNil: [ eventQueue nextPut: event ] ] in > OSSDL2Driver>>processEvent: in Block: [ event := self convertEvent: > sdlEvent.... > BlockClosure>>on:do: > OSSDL2Driver>>processEvent: > OSSDL2Driver>>eventLoopProcessWithoutPlugin > [ self eventLoopProcessWithoutPlugin ] in OSSDL2Driver>>setupEventLoop in > Block: [ self eventLoopProcessWithoutPlugin ] > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self > value.... > > But it seems incomplete. Any more information I can provide? > > Thank you. > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Oct. 22, 2017