December 2017 - Pharo-users

Re: [Pharo-users] Learning Morphic

by Offray Vladimir Luna CÃ¡rdenas

On 28/12/17 08:13, Stephan Eggermont wrote: > T.D. Telford <doug(a)dougtelford.com> wrote: >> Perhaps someone could point me to Morphic documentation (or supply >> examples) on my area of interest that includes a lot of examples. Thanks. > There are some screencasts with links to source starting at > https://vimeo.com/130781061 > > Stephan > > Stephan's screencasts are really good and they will give you an overview of what is possible and which interesting experiments can be explored. Cheers, Offray

Dec. 28, 2017

Re: [Pharo-users] Learning Morphic

by Stephan Eggermont

T.D. Telford <doug(a)dougtelford.com> wrote: >Perhaps someone could point me to Morphic documentation (or supply > examples) on my area of interest that includes a lot of examples. Thanks. There are some screencasts with links to source starting at https://vimeo.com/130781061 Stephan

Dec. 28, 2017

Re: [Pharo-users] Object Persistence

by Stephan Eggermont

Torsten Bergmann <astares(a)gmx.de> wrote: > For a full Magma version on Pharo: > I doubt that will happen as Chris Muller was and still is more oriented towards Squeak as > development platform. He is the author of Magma and beside the port it would cost him > (or anyone who would do such a port) more effort to maintain another > Pharo specific version. A Magma version on Pharo is perfectly doable, and Chris has always said he'd be willing to support anyone willing to do the port. It is a significant amount of work, and only makes sense when someone is willing to commit to maintaining it on successive Pharo versions, i.e. has a commercial use case that can afford to upgrade it. The first port will be significant as it needs to take into account a few years of upgrades and deprecations. It is also a job not so suited to a student as it requires a lot of email history digging and experience with Squeak and Pharo. Stephan

Dec. 28, 2017

Re: [Pharo-users] Commander feedback

by Denis Kudriashov

Only Calypso is not ready. 2017-12-28 13:03 GMT+01:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: > Hi Denis, > > thanks! I will read it soon. > > You say that Calypso chapter is in wrong state. What chapters are > up-to-date? I guess that Chapter 3 is what you updated recently, right? > > Cheers, > Juraj > > > On Dec 28, 2017, at 07:03, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > > 2017-12-28 11:02 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> Hi >> >> 2017-12-27 19:15 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> >>> Denis Kudriashov wrote >>> > https://github.com/SquareBracketAssociates/Booklet-Infrastructure >>> >>> Cool! Can't wait to read :) >> >> > Also notice, the Calypso chapter is in wrong state. Do not try read it. > Next year I will push it > > >> >> And feel free to pull requests. >> >> >>> One small question: why >>> "Booklet-Infrastructure"? That doesn't seem to match up to "A booklet on >>> the >>> infrastructure of the Calypso tool suite"â¦ >>> >> >> It's question to Stef :). I just updated prepared chapters. >> >> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >> > >

Dec. 28, 2017

Re: [Pharo-users] Commander feedback

by Juraj Kubelka

Hi Denis, thanks! I will read it soon. You say that Calypso chapter is in wrong state. What chapters are up-to-date? I guess that Chapter 3 is what you updated recently, right? Cheers, Juraj > On Dec 28, 2017, at 07:03, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > > 2017-12-28 11:02 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>>: > Hi > > 2017-12-27 19:15 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>>: > Denis Kudriashov wrote > > https://github.com/SquareBracketAssociates/Booklet-Infrastructure <https://github.com/SquareBracketAssociates/Booklet-Infrastructure> > > Cool! Can't wait to read :) > > Also notice, the Calypso chapter is in wrong state. Do not try read it. Next year I will push it > > > And feel free to pull requests. > > One small question: why > "Booklet-Infrastructure"? That doesn't seem to match up to "A booklet on the > infrastructure of the Calypso tool suite"â¦ > > It's question to Stef :). I just updated prepared chapters. > > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> > > >

Dec. 28, 2017

Re: [Pharo-users] Is there a way to set form colours using a 'fuzzy' option?

by Nicolai Hess

You can draw a new form with copybits and use your own color mapping. First, I thought there would be a bitblt operation that you could use without explicit calculating the color mapping, a paint operation that would convert a gray-value to an alpha value. But I could find it. In this special case (black text on white background) you can use an existing method for calculating this color map. This method is used by strike font to create apropriate glyph forms from its font bitmap. (A large bitmap with black characters on a white background.) Here is an example that first, creates a form with black text on white background, and than computes the color map and copys the source form in a new form: "create a test form " sourceForm := Form extent: 300@150 depth: 32. sourceForm fillColor: Color white. "draw some black, bold text" text := 'Hello World' asText. text addAttribute: (TextFontReference toFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 32)). text addAttribute: (TextColor color: Color black). text addAttribute: (TextEmphasis bold). text asMorph drawOn: sourceForm getCanvas. "create a morph for displaying this form" sourceImageMorph := ImageMorph withForm: sourceForm. sourceImageMorph openInWorld; topLeft: 300@300. "calculate the colormap" colorMap := Color computeColorConvertingMap: Color black from: 32 to: 32 keepSubPixelAA: false. "copy the source form bits to a new form of the same size" newForm := sourceForm deepCopy copyBits: sourceForm boundingBox from: sourceForm at: 0@0 colorMap: (colorMap). "create a morph for displaying this form" newImageMorph := ImageMorph withForm: newForm. newImageMorph openInWorld; topLeft: 300@500. 2017-12-27 22:43 GMT+01:00 Andy Burnett <andy.burnett(a)knowinnovation.com>: > I have an image with black text, and a white background. I would like to > set the white pixels to transparent. I worked out how to do this, but of > course it leaves me with a white halo around the text, where the border > pixels are almost white, but not quite. > > In googling about this, I discovered that RMagick has the idea of > replacing pixels which are almost any particular colour. I didn't find > anything similar in the ColorForm class. Is there a way to do this within > Pharo? > > Cheers > Andy >

Dec. 28, 2017

Re: [Pharo-users] Commander feedback

by Denis Kudriashov

2017-12-28 11:02 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi > > 2017-12-27 19:15 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > >> Denis Kudriashov wrote >> > https://github.com/SquareBracketAssociates/Booklet-Infrastructure >> >> Cool! Can't wait to read :) > > Also notice, the Calypso chapter is in wrong state. Do not try read it. Next year I will push it > > And feel free to pull requests. > > >> One small question: why >> "Booklet-Infrastructure"? That doesn't seem to match up to "A booklet on >> the >> infrastructure of the Calypso tool suite"â¦ >> > > It's question to Stef :). I just updated prepared chapters. > > >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >

Dec. 28, 2017

Re: [Pharo-users] Commander feedback

by Denis Kudriashov

Hi 2017-12-27 19:15 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > https://github.com/SquareBracketAssociates/Booklet-Infrastructure > > Cool! Can't wait to read :) And feel free to pull requests. > One small question: why > "Booklet-Infrastructure"? That doesn't seem to match up to "A booklet on > the > infrastructure of the Calypso tool suite"â¦ > It's question to Stef :). I just updated prepared chapters. > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Dec. 28, 2017

Re: [Pharo-users] image/vm mismatch on raspberry pi model 3

by Denis Kudriashov

Hi Greg. 2017-12-28 4:05 GMT+01:00 Greg Lewin <greg.lewin(a)gmail.com>: > (I want to try https://github.com/pharo-iot/PharoThings on the pi) - I > now see there is another VM on there ... I have just tried it with > better results. Matching image-VM versions does seem to be a problem > with Smalltalk. > So with github instruction you are succeed, right? Problem that CI job which you found is super outdated. Probably we should remove it. There was major VM release called Spur VM which produced incompatibility with old image versions. Normally you will not see such problems because major updates are very rare. > > ... > > On 28 December 2017 at 02:34, Greg Lewin <greg.lewin(a)gmail.com> wrote: > > Hi, > > > > > > Having copied a viable pair of image+changes and its associated > > sources file to a pi 3, in the same directory as the directory from > > the zip file (from > > https://ci.inria.fr/pharo/view/RaspberryPi/job/ > RaspberryPi-Publish/ws/64.zip) > > containing the VM code for a rpi, > > > > on running > > > > ./PharoS Pharo6.1 > > > > I get the message > > > > "This interpreter (vers. 6505) cannot read image file (vers. 6521)." > > > > How does one ensure a match between VM and image+sources on raspberry pi > ? > > > > I have also tried one image pair from an earlier version and get a > > similar message. > > > > thanks > > > > Greg > >

Dec. 28, 2017

Re: [Pharo-users] in-image pharo user objet ?

by Peter UhnÃ¡k

> When contributing it is associated to licence so I just find the actual model a bit weak. I don't think that this is the case anymore. Pharo itself (and more and more pharo projects) are moving to git, so the Author string is not really used outside of the given image --- the author is based on git config (author) and github account (comiter). In respect to code authorship, you can even sign your commits with git (I guess this could be an option in Iceberg at some future point in time). > Could we imagine a user id instead ? I think the most common "user id" tends to be email, as it is the most unambiguous id tied to a specific user (and easy to verify for ownership). But ensuring that someone else cannot use my "id" can be counter-productive in some scenarios -- e.g. when moving projects from sthub to github I had to "pretend" that I am someone else when creating the commits so the authorship is properly preserved for all contributors. > Another question is if an image may be used by several people ? I don't know the precise semantics, but when you move image the Author (the class where this is stored) should be reset. So if you send your image to someone else they should be asked to provide the name. > having an external personal system that could be plugged upon each new image startup. I would very much like this, as right now I have to store all passwords and credentials in plaintext in the image (settings) loaded from a startup script that I have publicly on github... ( https://github.com/peteruhnak/pharo-scripts/blob/master/config/6.0/iceberg-… ) But iirc iceberg can now use credential managers? (not sure what is the state) Cheers, Peter On Thu, Dec 28, 2017 at 10:23 AM, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > Of course this can be enough but this could be more objectified. A string > cannot be called a model to me. > > For now nothing prevents from having somebody use the id of someone else. > When contributing it is associated to licence so I just find the actual > model a bit weak. > > Then, additional functionalities could be built like storing other > informations, certificates, having an external personal system that could > be plugged upon each new image startup. > > But yes the actual solution is ok. Was just thinking loud as I try to > develop personal information system, this is something that could be > interesting for my use case ;-) > > Cheers, > > Cedrick > > > Le 27 dÃ©c. 2017 Ã 21:44, Offray Vladimir Luna CÃ¡rdenas < > offray.luna(a)mutabit.com> a Ã©crit : > > > > Hi, > > > > I wonder why first and last name are not good enough. I have found the > > model clear and privacy aware. Such image id is complemented with remote > > credentials in remote repositories (SmalltalkHub, GitHub, etc) and I > > deploy distinct images for distinct projects or releases (which is now > > easier with PharoLauncher), so I fail to see other use cases. > > > > Cheers, > > > > Offray > > > > > >> On 27/12/17 08:05, CÃ©drick BÃ©ler wrote: > >> Hi all, > >> > >> For now, it is asked (by convention) a string containing our first name > and last name (when code is submitted). > >> Just wandering if you could have a better representation of a user of a > Pharo image. > >> > >> Could we imagine a user id instead ? > >> That shouldnât be heavy to deal with and eventually one could add more > functionalities (one being the authentification to a pharo based > application). > >> > >> The difficulty is to find a proper universal user id. I would have used > something that encode date and place of birth in the id but it suffers some > privacy related issues. Any ideas ? > >> Another question is if an image may be used by several people ? To me > allowing one user is ok for a developer image but it might be interesting > to switch user spaces if itâs for a pharo application ? > >> > >> Cheers, > >> > >> CÃ©drick > >> > > > > > >

Dec. 28, 2017