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

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Pavel Krivanek

2017-08-12 11:36 GMT+02:00 Holger Freyther <holger(a)freyther.de>: > > > On 26. Jun 2017, at 19:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > Hi, > > Hey! > > thank you for this HOWTO! > > > username := 'YOUR-USER-NAME'. > > repository := IceRepositoryCreator new > > url: 'git@github.com:pharo-project/pharo.git'; > > location: ('pharo-core' asFileReference ensureCreateDirectory); > > subdirectory:'src'; > > createRepository. > > repository checkoutBranch: 'development'. > > repository register. > > > > fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' > format: {username})). > > repository addRemote: fork. > > repository pushRemote: fork. > > repository pullRemote: repository origin. > > I am using "pharo-mac-stable.zip" and "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" > and followed your howto and run into various Iceberg issues. Where would be > the best place to report them? > > Open Iceberg, selech "Pharo", click on Branches > => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. > > Open Iceberg, double click on "Pharo" > => DNU, #/ was sent to nil > UndefinedObject(Object)>>doesNotUnderstand: #/ > ... IceSavedPackage repository location seems to return nil. > > > Are these known? Fogbugz? Github issues of Iceberg? > yes, because this HOWTO is already obsolete. See: https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-P… -- Pavel > > > cheers > holger > > > > >

Aug. 12, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Holger Freyther

> On 26. Jun 2017, at 19:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, Hey! thank you for this HOWTO! > username := 'YOUR-USER-NAME'. > repository := IceRepositoryCreator new > url: 'git@github.com:pharo-project/pharo.git'; > location: ('pharo-core' asFileReference ensureCreateDirectory); > subdirectory:'src'; > createRepository. > repository checkoutBranch: 'development'. > repository register. > > fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' format: {username})). > repository addRemote: fork. > repository pushRemote: fork. > repository pullRemote: repository origin. I am using "pharo-mac-stable.zip" and "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" and followed your howto and run into various Iceberg issues. Where would be the best place to report them? Open Iceberg, selech "Pharo", click on Branches => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. Open Iceberg, double click on "Pharo" => DNU, #/ was sent to nil UndefinedObject(Object)>>doesNotUnderstand: #/ ... IceSavedPackage repository location seems to return nil. Are these known? Fogbugz? Github issues of Iceberg? cheers holger

Aug. 12, 2017

Re: [Pharo-dev] [Pharo-users] [ann] moldable brick editor - alpha

by Tudor Girba

Is this still an issue? Could you also try on another OS (just to make sure)? Cheers, Doru > On Aug 10, 2017, at 2:12 PM, stephan <stephan(a)stack.nl> wrote: > > On 10-08-17 13:09, stephan wrote: >> On 05-08-17 00:19, Tudor Girba wrote: >> >Iceberg enableMetacelloIntegration: true. >> That doesn't work. It hangs the image, keeping one CPU >> busy. > > With 60510 that is non-interruptable, b.t.w. > > Stephan > > > > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Aug. 12, 2017

Re: [Pharo-dev] [Esug-list] [ann] moldable brick editor - alpha

by Tudor Girba

Hi Stef, Sorry for the late reply. Very relevant point. Indeed, this is something we are still thinking about. The main thing we focused on was to have the attributes as objects first, and then an API that is easily extensible. The fluent API comes on top. At the moment, we tend to favor a builder approach that goes in this direction: text attributes textSize: 60. The issue is a bit of a more general concern as we already have the same need in several places in Bloc and we already use a builder pattern. For example: BlKeyCombination builder alt; control; key: Key c; build BlBorder builder dashed; paint: (Color green muchDarker alpha: 0.7); build However, these two are for creating a new instance, while in the text example we have to deal with modifying an existing one (i.e., the text). Decisions, decisions â¦ :) Cheers, Doru > On Aug 5, 2017, at 6:05 PM, StÃ©phane Ducasse <stephane.ducasse(a)gmail.com> wrote: > > A design question. > Do you think that it would not be better to have the constant encapsulated? > > text textSize: 60. > vs. > text attributes: BRFontTextSize size: 60. > > It could be > text attributes textSize: 60. > > Stef > > On Sat, Aug 5, 2017 at 6:02 PM, StÃ©phane Ducasse <stephane.ducasse(a)gmail.com> wrote: > Super cool. > Bloc will change the face of Pharo. > > > On Sat, Aug 5, 2017 at 12:19 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > We are very happy to announce the alpha version of a moldable editor built in Brick (https://github.com/pharo-graphics/Brick) which is based on Bloc (https://github.com/pharo-graphics/Bloc) This is primarily the work of Alex Syrel. The project was initially financially sponsored by ESUG and it is currently supported by feenk. And of course, the project is based on the tremendous work that went into Bloc and Brick by all contributors. > > Take a look at this 2 min video: > https://www.youtube.com/watch?v=2vy6VMJM9W4&feature=youtu.be > > The basic editor works and it is both flexible and scalable. For example, the last example shown in the video is an editor opened on 1M characters, which is reasonably large, and as can be seen see one can interact with it as smoothly as with the one screen text. It actually works just as fine with 100M characters. > > The functionality of the editor includes: rendering, line wrapping, keypress and shortcut handling, navigation, selection and text styling. Currently, the editor is 1260 lines of code including method and class comments. This is not large for a text editor and this is possible because most of the work is done by generic concepts that already exist in Bloc such as layouts and text measurements. Beside the small maintenance cost, the benefit is that we have the option to build all sorts of variations with little effort. That is why we call this a moldable text editor. > > Another benefit of using elements and layouts is that we can also embed other kinds of non-text elements with little effort (such as pictures), and obtain a rich and live text editor. We already have basic examples for this behavior, and we will focus more in the next period on this area. > > The next immediate step is to add syntax highlighting. Beside the text attributes problem, this issue will also exercise the thread-safety the implementation is. The underlying structure (https://en.wikipedia.org/wiki/Rope_(data_structure)) is theoretically thread-safe, but it still needs to be proven in practice. > > We think this is a significant step because the editor was the main piece missing in Brick and it will finally allow us to build value that can be directly perceived by regular users on top of Brick and this, in turn, will generate more traction. Please also note that because now Bloc is directly embeddable in Morphic it means that we can actually start using it right away. For example, the picture below shows the text element being shown through a live preview in the GTInspector. > > <AC36A55F-405C-6147-9E0F-BA1F6F1008BA.png> > > This is another puzzle piece towards the final goal of engineering the future of the Pharo user interface. There is still a long way to go to reach that goal, but considering the work that is behind us, that goal that looked so illusive when Alain and Stef initiated the Bloc project is now palpable. > > We will continue the work on this over the next period and we expect to announce new developments soon. > > If you want to play with it, you can load the code like this (works in both Pharo 6 and 7): > Iceberg enableMetacelloIntegration: true. > Metacello new > baseline: 'Brick'; > repository: 'github://pharo-graphics/Brick/src'; > load: #development > > Please let us know what you think. > > Cheers, > Alex and Doru > > > > -- > www.tudorgirba.com > www.feenk.com > > "What is more important: To be happy, or to make happy?" > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > > -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

Aug. 12, 2017

Re: [Pharo-dev] New line on command line

by Guillermo Polito

Hi Rajula On Sat, Aug 12, 2017 at 12:56 AM, Rajula Vineet <Vineet.Reddy(a)iiitb.org> wrote: > Hey, > > I have been trying to print on the command line as a part of my handler > implementation. I have been using `nextPutAll: aString;lf.` Apparently, > 'lf' > does not seem to work. I tried 'cr' too. I am using the latest 7.0 Pharo-vm > and pharo image. I tried 'OSPlatform current lineEnding' as suggested by > Clement Mastin. But, when I used the 6.0 version the 'lf' message is > working > fine. We did some changes to remodularize a bit more the kernel some weeks ago. The correct way to print a line ending is, as Clement pointed out, 'OSPlatform current lineEnding'. That is because there is no portable character for a new line. Each platform has its own. That said, maybe you found a bug :). Since the image before automatically transformed cr's in line endings for a platform, I did a stream decorator that replaces that behaviour for Pharo 7, I just did it to make it work, did not test it further actually. Could you try the following? - seeing what happens if you print a new line twice? nextPutAll: aString; lf;lf - What is the stream you're using to print out? Transcript or Stdout? Could you show the entire expression you're using? - Can you print out the stream you're using? stream nextPutAll: stream asString; lf. Guille > Please find the attached image which demonstrates the same. The left > terminal is of version 7.0, right one is of 6.0. Can someone help me out > with this? > <http://forum.world.st/file/n4960327/Screenshot_from_2017- > 08-11_00-04-29.png> > > > > -- > View this message in context: http://forum.world.st/New- > line-on-command-line-tp4960327.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 12, 2017

New line on command line

by Rajula Vineet

Hey, I have been trying to print on the command line as a part of my handler implementation. I have been using `nextPutAll: aString;lf.` Apparently, 'lf' does not seem to work. I tried 'cr' too. I am using the latest 7.0 Pharo-vm and pharo image. I tried 'OSPlatform current lineEnding' as suggested by Clement Mastin. But, when I used the 6.0 version the 'lf' message is working fine. Please find the attached image which demonstrates the same. The left terminal is of version 7.0, right one is of 6.0. Can someone help me out with this? <http://forum.world.st/file/n4960327/Screenshot_from_2017-08-11_00-04-29.png> -- View this message in context: http://forum.world.st/New-line-on-command-line-tp4960327.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 11, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Stephane Ducasse

Nicolai I started super simple. I clone and point my fresh dled image to the use the clone. Then I can do simple PR and review the issues. I will do the installation several times to learn (but not clone). I'm not sure that it is needed but I have cd /Users/ducasse/Library/Preferences/pharo/7.0 StartupPreferencesLoader default executeAtomicItems: { StartupAction name: 'Git Settings' code: [ FileStream stdout cr; nextPutAll: 'Setting the ssh credentials'; cr. Iceberg enableMetacelloIntegration: true. IceCredentialsProvider useCustomSsh: true. IceCredentialsProvider sshCredentials username: 'git'; publicKey: '/Users/ducasse/.ssh/id_rsa.pub'; privateKey: '/Users/ducasse/.ssh/id_rsa'. IceCredentialsProvider plaintextCredentials: (IcePlaintextCredentials new username: 'Ducasse'; password: 'xxxx' ; yourself ). FileStream stdout cr; nextPutAll: 'Finished'; cr ]. }. On Fri, Aug 11, 2017 at 9:46 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > I extended the document with some windows specific instructions also. > > On Fri, Aug 11, 2017 at 9:31 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> >> >> On Fri, Aug 11, 2017 at 12:34 AM, Nicolai Hess <nicolaihess(a)gmail.com> >> wrote: >> >>> >>> >>> 2017-08-10 17:17 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: >>> >>>> Hi, >>>> >>>> I've made some write up for the pharo part (not metacello or external >>>> projects) >>>> >>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>>> ribute-a-fix-to-Pharo >>>> >>>> Of course, expect bugs on it :) Not everything is smooth. If you have >>>> comments, they are welcome. >>>> >>> >>> >>> >>> [image: Inline-Bild 1] >>> >>> >>> In option 2, I think this should be "Click on the Edit button", >>> >> >> Thanks, fixed! >> >>> >>> >>> >>> >>>> >>>> Guille >>>> >>>> -- >>>> >>>> >>>> >>>> Guille Polito >>>> >>>> >>>> Research Engineer >>>> >>>> French National Center for Scientific Research - *http://www.cnrs.fr* >>>> <http://www.cnrs.fr> >>>> >>>> >>>> >>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>> >>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>> >>> >>> >> >> >> -- >> >> >> >> Guille Polito >> >> >> Research Engineer >> >> French National Center for Scientific Research - *http://www.cnrs.fr* >> <http://www.cnrs.fr> >> >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > > > -- > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - *http://www.cnrs.fr* > <http://www.cnrs.fr> > > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Aug. 11, 2017

[ Pharo 70 ] build 30 PR 69 Make-sure-Symbol-concatenation-results-in-a-Symbol-not-a-String/

by Stephane Ducasse

PR 69 https://github.com/pharo-project/pharo/pull/69 https://pharo.fogbugz.com/f/cases/19802/Make-sure-Symbol-concatenation-resu…

Aug. 11, 2017

Re: [Pharo-dev] [Ann] libssh2 binding for Pharo

by Max Leske

Very cool! On 11 August 2017 at 16:02:55, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: Hi I just want share my little experiments with libssh2. I think somebody can be interested with it and maybe will improve what I did which is now in very raw and initial state. Libssh2 library is now distributed with Pharo. And it was very enticing to try it from Pharo. Another reason behind it is the idea to make secure transport for Seamless and related remote tools. So I wrapped several functions in libssh2 library. And now I am able to send data to server using secure ssh channel. Also I can execute shell commands on remote server from playground. Look for details on github https://github.com/dionisiydk/libssh2-pharo-bindings. Best regards, Denis

Aug. 11, 2017

WriteUp: the pharo integration process

by Guillermo Polito

For those interested on any of: - how issues are integrated - what does the validation do - what are the built artifacts and where to find them I did write this: https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-P… Next, I'm going to explain a bit more in details the bootstrap from a process perspective, with less technical details. Cheers, Guille -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 11, 2017