- Pharo-users - lists.pharo.org

what must be instead of the ??

by Roelof Wobben

Hello, I try to solve a adventofcode challenge where I must find out when santa is first at the basement. the floor is there -1. So I thought I use a while loop like this : santaFloorOnBasement Â Â Â "calculates which step take Santa to the basement" Â Â Â Â | index| Â Â Â Â index := 1. Â Â Â Â ??? when: (floor >=0 ) do: Â Â Â Â Â Â Â [ floor := (input at: index = '(' ) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ floor + 1 ] Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ floor - 1 ]. Â Â Â Â Â Â Â Â index := index + 1 ]. but I cannot find out what must be instead of the ?? index is the index of the string which has to start with a 1. floorÂ and input are both instance variables. floor contains the current floor and input the input of the challenge. Can someone help me figure this out so the next time I can do this on my own. Roelof

Nov. 9, 2018

Re: [Pharo-users] using latest iceberg with Pharo 6.1 / 7.0

by Sanjay Minni

Thanks Sven, Guille, I am only looking at iceberg for development / loading of a software project being developed in Pharo (i.e. not develop iceberg itself ... if the question was on iceberg development maybe I would have posted in Pharo-developers group ;) ). so it seems there is nothing to be done to "use" iceberg. I have some questions ... pardon if they are naive but I am pretty green in the pharo environment. Question 1: This is on the sequence for cloning a repository and loading the project from bitbucket with a Metacello configuration defined. - I have cloned on pharo 6.1... after that do I have to load the project / packages as a separate step ? after cloning, iceberg shows as follows Name CurrBranch loaded version Status myProject development No Package Loaded not loaded Question 2: what are the steps to pull the latest version of the project and overwrite the existing package versions already loaded Question 3: Are class side initialize scripts triggerred on first time load and on reload Question 4: the project has several external files .jpegs, .css .json etc, ... are they also pulled / pushed alongwith pharo code thru iceberg Question 5: how do I update iceberg 1.4.0 in pharo 6.1 image / 7.0 image Question 6: is there documentation / guide available for iceberg like the monticello / metacello guide in Deep Into Pharo thanks Sanjay Guillermo Polito wrote > On Fri, Nov 2, 2018 at 6:25 PM Sanjay Minni < > sm@ > > wrote: > >> If I want to use iceberg then should I first update pharo image as >> mentioned >> on github iceberg homepage (https://github.com/pharo-vcs/iceberg) >> > > I'd also insist here with Sven. Could you please explain better what are > you trying to accomplish? > > >> for 6.1: should I run the script as given on the homepage or is there an >> easier way to upgrade (i.e. some UI - point and click) ? >> > > This is ok, and this will update latest release (not latest dev version). > Usually from a user perspective yor may want only latest release and > that's > ok. > > >> >> for 7.0: its mentioned to clone iceberg and pull changes >> - i run iceberg ... >> - dialog opens:repositories - there is a line "iceberg ... local >> repositories missing". >> how should i proceed from here ? >> > [SNIP] > > Actually, here what you were doing is loading latest version of iceberg to > contribute to it. > If you want to use Iceberg, you need to do nothing :) The latest iceberg > version is already in Pharo7 and you had nothing to do. > > Cheers, > Guille ----- --- Regards, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 8, 2018

Re: [Pharo-users] using latest iceberg with Pharo 6.1 / 7.0

by Guillermo Polito

On Fri, Nov 2, 2018 at 6:25 PM Sanjay Minni <sm(a)planage.com> wrote: > If I want to use iceberg then should I first update pharo image as > mentioned > on github iceberg homepage (https://github.com/pharo-vcs/iceberg) > I'd also insist here with Sven. Could you please explain better what are you trying to accomplish? > for 6.1: should I run the script as given on the homepage or is there an > easier way to upgrade (i.e. some UI - point and click) ? > This is ok, and this will update latest release (not latest dev version). Usually from a user perspective yor may want only latest release and that's ok. > > for 7.0: its mentioned to clone iceberg and pull changes > - i run iceberg ... > - dialog opens:repositories - there is a line "iceberg ... local > repositories missing". > how should i proceed from here ? > [SNIP] Actually, here what you were doing is loading latest version of iceberg to contribute to it. If you want to use Iceberg, you need to do nothing :) The latest iceberg version is already in Pharo7 and you had nothing to do. Cheers, Guille

Nov. 8, 2018

glamorous toolkit - moldable method coder

by Tudor Girba

Hi, We design the Glamorous Toolkit to enable moldable development. This is a new take on programming that is predicated on the idea that tools must adapt to the context of the software system in order to be effective. Until now, we mainly applied moldability to how we inspect/debug/search existing code and objects. The first incarnation of GT, the tools that are present in the Pharo distribution, already showed how moldable development can provide dramatic productivity gains, especially when combined with examples. To make the experience complete, more recently we started to build moldability into Coder, the new set of tools for creating code. The first tool we created is Method Coder, an editor for a single method. This is a working editor that has multiple new features, one of which being that it can be collapsed to only see the method pattern (header), and that the body is editable without affecting the method pattern. This editor is versatile and can be used in various places, such as class coder or a search: https://twitter.com/feenkcom/status/1058003761262743552 Yesterday, we reached a new milestone. In the example below we see how adding/removing <gtExample> to a method changes the shape of the method Coder dynamically without requiring a save. In our case, the changes affect: the example status label, the in-place example expanding toggle, and the run button. https://twitter.com/feenkcom/status/1060290294749560833 This just an example that is specific to the examples engine, but it shows how typing can be linked live to all details that make the surrounding tool. Of course, the mechanism behind the scene is available for you to adapt the editor to your code. This is a whole new uncharted world, and we think there is a great deal of potential in this area. Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

Nov. 8, 2018

Re: [Pharo-users] New convenience method: ZnClient>>forJsonREST

by Tudor Girba

This is nice! Doru > On Nov 7, 2018, at 5:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > I added a new convenience method to Zinc HTTP Components: ZnClient>>forJsonREST. This configures a ZnClient (HTTP client) to talk to standard JSON REST web services. Here are a couple of examples: > > ZnClient new > forJsonREST; > get: 'https://jsonplaceholder.typicode.com/users'. > > What #forJsonREST does is 3 things: set the 'Accept' header to 'application/json', install a #contentReader that parses incoming JSON as well as a #contentWriter that generates JSON. > > ZnClient new > systemPolicy; > forJsonREST; > url: 'https://jsonplaceholder.typicode.com/posts'; > contents: { #foo->1. #bar->2 } asDictionary; > post. > > As you can see, the full ZnClient API can be combined when needed. > > ZnClient new > forJsonREST; > post: 'https://jsonplaceholder.typicode.com/posts' > contents: (NeoJSONObject new foo: 1; bar: 2; yourself). > > #post:contents: combines separate #url: #contents: and #post message. > > #forJsonREST uses NeoJSON[Object|Writer] if found, else STONJSON. If both are missing, this results in an error. > > ZnClient new > systemPolicy; > forJsonREST; > url: 'http://easy.t3-platform.net/rest/geo-ip'; > queryAt: #address put: '81.83.7.35'; > get. > > Finally, here is a more sophisticated example, doing a DNS request over HTTPS: > > ZnClient new > systemPolicy; > beOneShot; > forJsonREST; > accept: 'application/dns-json'; > url: 'https://cloudflare-dns.com/dns-query'; > queryAt: #name put: 'stfx.eu'; > queryAt: #type put: #AAAA; > get. > > Note that in most cases, you will configure one client to a specific endpoint and keep on reusing it. At one point in time it might be good to #close the client (although that happens on finalise as well). For single requests, you can use #beOneShot. > > All this can be found in #bleedingEdge (HEAD). There are unit tests as well. > > Sven > > -- www.feenk.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

Nov. 7, 2018

Re: [Pharo-users] New convenience method: ZnClient>>forJsonREST

by CÃ©drick BÃ©ler

Youâre (one of) my heroes ! Thanks Sven a lot for all your great contributions ! CÃ©drick Side note: perfect late binding information for the lecture I do tomorrow with Pharo where I show students client server interaction with ZnClient, ZnServer â¦ ^_^ > Le 7 nov. 2018 Ã 17:36, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > Hi, > > I added a new convenience method to Zinc HTTP Components: ZnClient>>forJsonREST. This configures a ZnClient (HTTP client) to talk to standard JSON REST web services. Here are a couple of examples: > > ZnClient new > forJsonREST; > get: 'https://jsonplaceholder.typicode.com/users'. > > What #forJsonREST does is 3 things: set the 'Accept' header to 'application/json', install a #contentReader that parses incoming JSON as well as a #contentWriter that generates JSON. > > ZnClient new > systemPolicy; > forJsonREST; > url: 'https://jsonplaceholder.typicode.com/posts'; > contents: { #foo->1. #bar->2 } asDictionary; > post. > > As you can see, the full ZnClient API can be combined when needed. > > ZnClient new > forJsonREST; > post: 'https://jsonplaceholder.typicode.com/posts' > contents: (NeoJSONObject new foo: 1; bar: 2; yourself). > > #post:contents: combines separate #url: #contents: and #post message. > > #forJsonREST uses NeoJSON[Object|Writer] if found, else STONJSON. If both are missing, this results in an error. > > ZnClient new > systemPolicy; > forJsonREST; > url: 'http://easy.t3-platform.net/rest/geo-ip'; > queryAt: #address put: '81.83.7.35'; > get. > > Finally, here is a more sophisticated example, doing a DNS request over HTTPS: > > ZnClient new > systemPolicy; > beOneShot; > forJsonREST; > accept: 'application/dns-json'; > url: 'https://cloudflare-dns.com/dns-query'; > queryAt: #name put: 'stfx.eu'; > queryAt: #type put: #AAAA; > get. > > Note that in most cases, you will configure one client to a specific endpoint and keep on reusing it. At one point in time it might be good to #close the client (although that happens on finalise as well). For single requests, you can use #beOneShot. > > All this can be found in #bleedingEdge (HEAD). There are unit tests as well. > > Sven > >

Nov. 7, 2018

New convenience method: ZnClient>>forJsonREST

by Sven Van Caekenberghe

Hi, I added a new convenience method to Zinc HTTP Components: ZnClient>>forJsonREST. This configures a ZnClient (HTTP client) to talk to standard JSON REST web services. Here are a couple of examples: ZnClient new forJsonREST; get: 'https://jsonplaceholder.typicode.com/users'. What #forJsonREST does is 3 things: set the 'Accept' header to 'application/json', install a #contentReader that parses incoming JSON as well as a #contentWriter that generates JSON. ZnClient new systemPolicy; forJsonREST; url: 'https://jsonplaceholder.typicode.com/posts'; contents: { #foo->1. #bar->2 } asDictionary; post. As you can see, the full ZnClient API can be combined when needed. ZnClient new forJsonREST; post: 'https://jsonplaceholder.typicode.com/posts' contents: (NeoJSONObject new foo: 1; bar: 2; yourself). #post:contents: combines separate #url: #contents: and #post message. #forJsonREST uses NeoJSON[Object|Writer] if found, else STONJSON. If both are missing, this results in an error. ZnClient new systemPolicy; forJsonREST; url: 'http://easy.t3-platform.net/rest/geo-ip'; queryAt: #address put: '81.83.7.35'; get. Finally, here is a more sophisticated example, doing a DNS request over HTTPS: ZnClient new systemPolicy; beOneShot; forJsonREST; accept: 'application/dns-json'; url: 'https://cloudflare-dns.com/dns-query'; queryAt: #name put: 'stfx.eu'; queryAt: #type put: #AAAA; get. Note that in most cases, you will configure one client to a specific endpoint and keep on reusing it. At one point in time it might be good to #close the client (although that happens on finalise as well). For single requests, you can use #beOneShot. All this can be found in #bleedingEdge (HEAD). There are unit tests as well. Sven

Nov. 7, 2018

Re: [Pharo-users] [ANN] Iceberg v1.3.1

by Offray Vladimir Luna CÃ¡rdenas

Really nice. Just a quick question: Self hosted GitLab support can be used for self hosted Gitea[1] support? What would be needed for that? (I'm thinking in using Gitea as a bridge between Pharo and Fossil). [1] https://gitea.io/en-us/ Cheers, Offray On 11/5/18 8:15 AM, Cyril Ferlicot wrote: > Hello! > > This week we are releasing the version v1.3 of Iceberg. > (https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.0 > +https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.1) > > This version will be available after we merge this PR: > > https://github.com/pharo-project/pharo/pull/1951 > > This release contains some new features such as the support of self > hosted gitlab, integration with github, etc. > It also contains multiple bug fixes, cleanups and enhancements. > > On the CI part, Guille made the Appveyor build green! This will > increase the stability of the windows support. > > Thanks to all contributors. > > Enjoy! > > Full changelog: > > Features > > #1021 Self hosted gitlab support > #1027 Improved new tag dialog to generate semantic versionning tags > #1044 Show a button "View on Github" when creating a PR > #1008 Add "create branch from GitHub issue" option > #1048 Add commands to open remotes on Github > #1010 Add menu entry in extras to force calculate diff > > Bug corrections > > #975 Metacello asks too many times what to install when there are > conflicting versions > #980 Iceberg should Identify better the packages and the normal files > #982 The Edit Project should have a Warning if it will affect the packages > #986 Iceberg does not realize changes in extended classes > #999 Pulling and pushing to a gitolite server asks password > #984 Conversion to Tonel generates corrupted .properties > #1041 Filter in repository view don't work with capital letters > #1019 Metacello Integration leaves Monticello leftover repositories > #859 Creating a branch and pushing does not sets the upstream > #1043 Packages starting with lowercase not recognized > #991 Error on right click in the project editon wizard > #775 Reviewing a PR is broken > #1036 Debugger if we try to merge without selecting a branch > #1064 Fix failing tests regarding clean code in Pharo > > Enhancements > > #988 Iceberg should load the packages in a single MCLoader (This will > make the loads of packages atomic) > #1001 Use "instance creation" instead of "instance-creation" for > method protocol name > #1004 Use displayScaleFactor in UI > #977 Add ToolTip help to the Commands > #1030 Better support for binary files > #1034 SSH passphrase is now hidden > > Cleanups > > #1018 Iceberg UI relies on deprecated classes from Spec and Commander > #1051 Clean useless huge hierarchy in Github plugin UI > > Infrastructure Enhancements > > #1023 Fix CI for windows >

Nov. 7, 2018

Re: [Pharo-dev] [ANN] Iceberg v1.4.0

by Ben Coman

On Wed, 7 Nov 2018 at 17:09, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hello! > > This week we are releasing the version v1.4.0 of Iceberg. > (https://github.com/pharo-vcs/iceberg/releases/tag/v1.4.0) > > This version is available in the latest Pharo 7. > > This release fixes a bug introduced in v1.3. It also add new features > in the repository view, add some cleaning and also re-introduce a > feature that was lost. > > Thanks to all contributors. > > Enjoy! > > Full changelog: > > Bugfixes > > #1068 'There is no associated repository configured.' warning on right > clicking missing repository > > Features > > #1077 Repository view: Allow to collapse branches/remotes/tags trees > #847 Move tags under remotes in Repository view Ohh, those two are very nice. I'm meant to be working on something else but needed to try those out. That long list of tags had been mildly annoying me for a while, but not enough for me to get around to complaining about it. Glad its fixed already. > #1070 set upstream if missing > > Cleanups > > #1066 Pharo 7: PackageManifest subclasses should be packaged with "Manifest" > #1015 Replace usages of Glamour in the Github Plugin > #1063 1061-Introduce-iconNamed-in-IceDefinition-and-IceTipModel-and-remove-all-the-terrible-Smalltalk-ui-icons Cool. I like the way the changes are reported and the semantic versioning. cheers -ben

Nov. 7, 2018

Re: [Pharo-users] MetaLink>>level: failing?

by Marcus Denker

Hi, I added https://pharo.fogbugz.com/f/cases/22642/instead-links-and-meta-level-origin… as a workaround, you can use a #before link with an explicit return: choice := true. link := MetaLink new metaObject: [ :object :selector :arguments :context | UIManager default alert: 'Linked Version'. choice ifTrue: [ context sender sender sender sender return: (object perform: selector withArguments: arguments)]. ]; selector: #value:value:value:value:; arguments: #(#object #selector #arguments #context); control: #before; level: 0. (TestMetaLink >> #execute) ast link: link. TestMetaLink new execute. link uninstall. (yes, the context sender sender sender shows that #context needs to do the right thing when using level: 0. or notâ¦ another thing to fix) Marcus > On 7 Nov 2018, at 15:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > I added a fist issue (and fix) for parts of the problem > > https://pharo.fogbugz.com/f/cases/22641/Semantic-analysis-needs-to-take-ins… <https://pharo.fogbugz.com/f/cases/22641/Semantic-analysis-needs-to-take-ins…> > https://github.com/pharo-project/pharo/pull/1960 <https://github.com/pharo-project/pharo/pull/1960> > > But after this, it does not work as the level just turns off calling the meta level code, but does not execute the > original code where the #instead is put. > (#instead in general needs more work in this implementation). > > I will open another issue for that. > > Marcus > >> On 31 Oct 2018, at 18:03, Vitor Medina Cruz <vitormcruz(a)gmail.com <mailto:vitormcruz@gmail.com>> wrote: >> >> Thanks! Is there an issue on fogbuzz where I can be notified of resolution? Do you need me to create it? >> >> After that how can update the code? Software update is safe or should I create a new image? >> >> regards, >> Vitor >> >> On Mon, Oct 29, 2018 at 12:08 PM Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> >>> On 25 Oct 2018, at 01:33, Vitor Medina Cruz <vitormcruz(a)gmail.com <mailto:vitormcruz@gmail.com>> wrote: >>> >>> Hello, >>> >>> I am playing with MetaLink, really cool!, but I am having issues that I am unsure if it's some erro or if I am doing something wrong (I am using Pharo 6.1 32 bits in windows.). Consider: >>> >>> TestMetaLink>>execute >>> UIManager default alert: 'Actual Version'. >>> >>> And in Playground: >>> >>> | link | >>> >>> link := MetaLink new metaObject: [ :object | UIManager default alert: 'Linked Version' ]; >>> selector: #value:; >>> arguments: #(#object); >>> control: #instead. >>> >>> >>> (TestMetaLink >> #execute) ast link: link. >>> TestMetaLink new execute. >>> link uninstall. >>> >>> This works as expected, an alert with 'Linked Version' is promped. But then suppose I want to execute the actual node alongside with the linked one considering some condition: >>> >>> | link choice | >>> >>> choice := true. >>> link := MetaLink new metaObject: [ :object :selector :arguments | >>> UIManager default alert: 'Linked Version'. >>> choice ifTrue: [ object perform: selector withArguments: arguments]. >>> ]; >>> selector: #value:value:value:; >>> arguments: #(#object #selector #arguments); >>> control: #instead; >>> level: 0. >>> >>> >>> (TestMetaLink >> #execute) ast link: link. >>> TestMetaLink new execute. >>> link uninstall. >>> >>> As I understand, level:0 is necessary in order to avoid an infinite loop, but then I get an error: >>> >>> KeyNotFound: key #RFArgumentsReificationVar not found in Dictionary >>> >>> Am I doing something wrong? Is that an error? >>> >> Hello, >> >> Yes, this looks like a bug. I will fix it over the next days. >> >> Marcus >> >> >> >> >> >> >> >

Nov. 7, 2018