August 2016 - Pharo-users - lists.pharo.org

How to properly handle ConnectionClosed with Zinc?

by HernÃ¡n Morales Durand

Hi, I have a situation where downloading lot of data results in ConnectionClosed. >>httpGet: urlString "Get the response from the given url" ^ [ ... .get: urlString ] on: ZnEntityTooLarge, ConnectionClosed do: [ : ex | ex isResumable ifTrue: [ ex resume ] ifFalse: [ self handleNonResumableConnection: ex ] ]. I read a mail from Sven you could change a global setting in ZnNetworkingUtils as follows: >>handleNonResumableConnection: anException | msg | msg := 'We got a non-resumable exception while connecting to ' , self url host asString , '. Re-try switching ZdcSocketStream to SocketStream?'. (self confirm: msg) ifTrue: [ ZnNetworkingUtils default socketStreamClass: SocketStream. anException retry.] But I would like to read about better handling, or recommendations. What do you think? Cheers, HernÃ¡n

Aug. 18, 2016

Google building new OS with Dart

by askoh

It became news a few days ago. It is called Fuchsia and is meant to run on all devices from IoT on up. The interesting thing is that Dart will be the main language. The developers promise to make Fuchsia run on Raspberry Pi 3 shortly. Since Dart is pretty close to Smalltalk, how can Smalltalk be the GUI for Fuchsia? How can it take advantage of Dart VM? Is this an opportunity for Smalltalk to make an impact? Let's brainstorm. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Google-building-new-OS-with-Dart-tp4911649.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 18, 2016

Re: [Pharo-users] Generating custom classes based on attributes from XML Document

by monty

You now can match on attributes too. The attributes: arguments can be any attribute specification object or just an ordinary dict or other association collection (nil values mean a key just must be present with any value). Â And there is visitor pattern support so you don't have to define polymorphic extension methods on every node class or use a bunch of isWhatever testing messages when tree traversing. > Sent: Friday, March 18, 2016 at 10:17 AM > From: "Peter UhnÃ¡k" <i.uhnak(a)gmail.com> > To: "Pharo Users List" <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Generating custom classes based on attributes from XML Document > > I have a XML like this > > > <packagedElement xmi:type="uml:Class" xmi:id="EAID_4A" name="DCEdge" isAbstract="true"> >  > </packagedElement> > <packagedElement xmi:type="uml:Association" xmi:id="EAID_46"> >  > </packagedElement> > > and I would like to generate UmlClass and UmlAssociation classes for this. > > I could use XMLPluggableElementFactory, however that only allows me to specify the target class only on the element's name, such as > > > doc := (XMLDOMParser on: someXML) > nodeFactory: > (XMLPluggableElementFactory new > elementClass: GenericElement; > handleElement: 'packagedElement' withClass: UmlPackagedElement) > parseDocument. > > However I need better granularity, because I would like to have a different class for 'packagedElement[xmi:type="uml:Class"]' and different class for 'packagedElement[xmi:type="uml:Association"]'. > > Of course I could use double visitors (so use the Pluggable stuff to get UmlPackagedElement) and then make another pass on it to get the final classes, > > however I would prefer to have to wanted class directly without the need to go through intermediate representation. > > Is there a way to do this? > > Thanks, > Peter >

Aug. 17, 2016

Re: [Pharo-users] Spec Widget positioning

by Johan Fabry

I do not think so. The chapter is already big and should contain the solution Brad is looking for. Letâs see if he is satisfied, as a case study :-) -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > On Aug 17, 2016, at 16:46, stepharo <stepharo(a)free.fr> wrote: > > Johan > > do you think that this example should be added to the layout chapter? > > Stef > >

Aug. 17, 2016

Re: [Pharo-users] Spec Widget positioning

by stepharo

Johan do you think that this example should be added to the layout chapter? Stef Le 17/8/16 Ã 21:10, Peter UhnÃ¡k a Ã©crit : > Hi, > > you normally control the (relative) sizes through the layout, e.g. > > ui := DynamicComposableModel new. > > ui instantiateModels: #(text TextInputFieldModel btn1 ButtonModel btn2 > ButtonModel). > > ui btn1 label: 'Button 1'. > ui btn2 label: 'Button 2'. > > layout := SpecColumnLayout composed > newRow: [ :row | > row > add: #text; > add: #btn1 width: 60; > add: #btn2 width: 60 > ] height: ComposableModel toolbarHeight; > newRow: [ :row | ]. > > ui openWithSpecLayout: layout. > > If you want want more details, I suggest you read the Spec Booklet > https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la… > > A lot of effort has been put into it recently to update it, so it > should be up-to-date. > > Peter > > On Wed, Aug 17, 2016 at 8:53 PM, Brad Selfridge <bsselfridge(a)gmail.com > <mailto:bsselfridge@gmail.com>> wrote: > > I'm trying to build a toolbar widget that contains two fixed width > buttons, a > variable width textInputBox followed by two more fixed width > buttons. I'm > not sure how to mix fixed and variable width widgets. > > Can someone give me an idea on how to do this? > > Thanks, > > > > ----- > Brad Selfridge > -- > View this message in context: > http://forum.world.st/Spec-Widget-positioning-tp4911599.html > <http://forum.world.st/Spec-Widget-positioning-tp4911599.html> > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > >

Aug. 17, 2016

Re: [Pharo-users] Spec Widget positioning

by Johan Fabry

A small comment with regard to the Spec booklet: Some chapters have not yet been worked on, but the layout chapter is done so I heartily recommend it! -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org <http://emailcharter.org/> . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > On Aug 17, 2016, at 16:10, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > you normally control the (relative) sizes through the layout, e.g. > > ui := DynamicComposableModel new. > > ui instantiateModels: #(text TextInputFieldModel btn1 ButtonModel btn2 ButtonModel). > > ui btn1 label: 'Button 1'. > ui btn2 label: 'Button 2'. > > layout := SpecColumnLayout composed > newRow: [ :row | > row > add: #text; > add: #btn1 width: 60; > add: #btn2 width: 60 > ] height: ComposableModel toolbarHeight; > newRow: [ :row | ]. > > ui openWithSpecLayout: layout. > > If you want want more details, I suggest you read the Spec Booklet https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la… <https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la…> > > A lot of effort has been put into it recently to update it, so it should be up-to-date. > > Peter > > On Wed, Aug 17, 2016 at 8:53 PM, Brad Selfridge <bsselfridge(a)gmail.com <mailto:bsselfridge@gmail.com>> wrote: > I'm trying to build a toolbar widget that contains two fixed width buttons, a > variable width textInputBox followed by two more fixed width buttons. I'm > not sure how to mix fixed and variable width widgets. > > Can someone give me an idea on how to do this? > > Thanks, > > > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/Spec-Widget-positioning-tp4911599.html <http://forum.world.st/Spec-Widget-positioning-tp4911599.html> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 17, 2016

Re: [Pharo-users] Spec Widget positioning

by Peter UhnÃ¡k

Hi, you normally control the (relative) sizes through the layout, e.g. ui := DynamicComposableModel new. ui instantiateModels: #(text TextInputFieldModel btn1 ButtonModel btn2 ButtonModel). ui btn1 label: 'Button 1'. ui btn2 label: 'Button 2'. layout := SpecColumnLayout composed newRow: [ :row | row add: #text; add: #btn1 width: 60; add: #btn2 width: 60 ] height: ComposableModel toolbarHeight; newRow: [ :row | ]. ui openWithSpecLayout: layout. If you want want more details, I suggest you read the Spec Booklet https://ci.inria.fr/pharo-contribution/view/Books/job/BuildingUIWithSpec/la… A lot of effort has been put into it recently to update it, so it should be up-to-date. Peter On Wed, Aug 17, 2016 at 8:53 PM, Brad Selfridge <bsselfridge(a)gmail.com> wrote: > I'm trying to build a toolbar widget that contains two fixed width > buttons, a > variable width textInputBox followed by two more fixed width buttons. I'm > not sure how to mix fixed and variable width widgets. > > Can someone give me an idea on how to do this? > > Thanks, > > > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/Spec- > Widget-positioning-tp4911599.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 17, 2016

Spec Widget positioning

by Brad Selfridge

I'm trying to build a toolbar widget that contains two fixed width buttons, a variable width textInputBox followed by two more fixed width buttons. I'm not sure how to mix fixed and variable width widgets. Can someone give me an idea on how to do this? Thanks, ----- Brad Selfridge -- View this message in context: http://forum.world.st/Spec-Widget-positioning-tp4911599.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 17, 2016

Re: [Pharo-users] MOOC for English learners

by Gour

On Tue, 16 Aug 2016 22:07:26 +0200 stepharo <stepharo(a)free.fr> wrote: > I added all the srt to the file server and now we discovered that we > should convert them in vtt. > So I writing a srt to vtt transformer because I failed to find one > running on mac. Thanks a lot for working on it...much appreciated. Sincerely, Gour -- You have a right to perform your prescribed duty, but you are not entitled to the fruits of action. Never consider yourself the cause of the results of your activities, and never be attached to not doing your duty.

Aug. 17, 2016

Re: [Pharo-users] i18n&l10n & Unicode support in Pharo

by Henrik Johansen

> On 17 Aug 2016, at 9:08 , Gour <gour(a)atmarama.com> wrote: > > Hello, > > just starting with Pharo and I'm thinking about i18n/l10n capabilities > within environment to make one's app read for several langauges. > > I've found out I18n (http://smalltalkhub.com/#!/~TorstenBergmann/I18N) > project but it seems there are no new contrubutions in last 2 years. > > I've also discovered 'Unicode project' thread on dev-list, but would > like to get some pointer about the current (5.0 <= Pharo < 6) state of > affairs in regard writing multi-language-capable and Unicode-aware apps > in Pharo? > > > Sincerely, > Gour For the translation part of l10n, there's also a package providing gettext support if needed. locale support is limited to an API similar to *nix locales. "Unicode-aware" is a wide topic, as reflected by the plethora of functional bits and bobs defined by different parts of the standard. (With base image) Can you represent all Unicode string? Yes. Can you pass them to other systems in Unicode encodings? Yes. Is the text renderer (in image) capable of displaying Unicode code points? Yes, if glyph is included in fonts. (With Unicode project) Can you query Unicode properties of any codepoint? Yes Can you normalize strings in the different forms? Yes. Can you sort strings in Unicode collate order? Yes. (With both) Can you sort strings in CLDR-locale collate order? No. Can you do regexp as per the Unicode spec? No. Does the text renderer (in image) heed Unicode properties such as RTL and combining marks? No Depending on what you want to do, the base image capabilities may be considered sufficient for writing multi-language-capable apps, but for more advanced Unicode functionality, the groundworks is there, (ie, querying properties, normalization, the core collate algorithm) but many practical uses are as of yet unimplemented, the complete lack of CLDR support ranking high. Cheers, Henry The big eyesore in

Aug. 17, 2016