February 2017 - Pharo-users

TextAlignment in Spec

by Pau Guillot

Hello Is possible to do alignment in list? in Label? especially in multilist TextEmphasis work correctly but TextAlignment not " |c| c := OrderedCollection new. 10 timesRepeat: [c add: (Text string: 'a' attribute: TextAlignment centered)]. (ListModel new items: c) openWithSpec. " " |c| c := OrderedCollection new. 10 timesRepeat: [c add: (Text string: 'a' attribute: TextEmphasis bold)]. (ListModel new items: c) openWithSpec " That it's that we have for the moment or we can do better. Thanks, spec is super for newbies. ================================================================ Missatge enviat a travÃ©s del Webmail de Girona.com http://www.girona.com ================================================================

Feb. 17, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Dale Henrichs

Hilaire, Thanks for the detailed information ... I see that you are using the old-style loading of Voyage (`ConfigurationOfVoyageMongo load`) ... when using this style of loading, Metacello has to guess about which projects are loaded and what version of the project is loaded. I is possible that the behavior you are seeing is a direct result of Metacello guessing wrong. I recommend that you load projects using the new style based on `Metacello new`: Metacello new configuration: 'Voyage'; version: '???'; repository: '???'; load When using this style of loading, Metacello maintains a registry of loaded projects and no longer makes guesses what is loaded in the image... From a cursory glance at the transcript output I see that version 3.2.1 of Seaside is being loaded and there appears to be a pretty much wholesale upgrade of Seaside as a bunch of new package versions are being loaded ... Do you happen to know what version of Seaside you originally loaded. I assume that you have an older version of Seaside loaded -- perhaps even Seaside 3.1? As to "Why is a Seaside load being triggered at all?", there is nothing obvious -- I am suspicious that the old-style loading is causing the problem, but I don't have any hard evidence, yet. I will have to start downloading specific configuration versions to complete my analysis and I have limited time left before I have to run some errands so I might not have answers until later this afternoon. If you want to run an experiment in the meantime, you could try using the new-style Metacello load, just to see what happens ... if Seaside is still upgraded, the Transcript output would be useful as it will give me additional information. If VoyageMongo loads correctly, then you are in business:) BTW, you should probably load the latest version of Metacello into your Pharo4.0 image[1] before using the new-style load. Dale [1] https://github.com/dalehenrich/metacello-work#pharo30-pharo40-and-pharo50 On 02/17/2017 10:14 AM, Hilaire wrote: > Hi Dale, > > At first I was more thinking of a problem in the dependencies of Voyage, > but then it seems not as with unload Seaside, Voyage get load. It did > not help anyway becasue Seaside can't be reinstalled (Obsolete class > syndrom hit there) > > Voyage is installed as: > > "VoyageMongo EstebanLorenzano.47" > ConfigurationOfVoyageMongo load > > The transcript output in the attached document > > Thanks > > Le 17/02/2017 Ã 18:54, Dale Henrichs a Ã©crit : >> You don't mention how you are loading Voyage. If I had the load >> expression and Transcript output from the load, I'd pretty much be able >> to tell pretty much what is going on. >> >> I have a couple of theories about what could be going wrong, but without >> the load expression and Transcript output, I'd only be guessing and of >> course there is the possibility that you've discovered a bug in Metacello:) >> >> If you'd like to get to the bottom of this, send me the load expression >> and Transcript output and we'll go from there ... >>

Feb. 17, 2017

Re: [Pharo-users] Team programming with Smalltalk

by Dale Henrichs

On 02/15/2017 02:43 PM, horrido wrote: > In file-based word, the answer is tests and CI. What is the smalltalk way? > And please do not say "It's in the conceptual nature of programming" -- if > the scenario makes no sense in the smalltalk world (maybe you are not > supposed to have 20 people working on the same project?) please say this. > > ----- Well I think that being able to use git (disk based SCMS) for managing Smalltalk code is one step towards making it practical for large teams to work together ... The major piece that I think is still missing is the ability to have a declarative formula/specification for the contents of an image ... The declarative build formula/specification must be something that can be shared and versioned. Today, the closest we can come to this is an ad hoc Smalltalk script and that really isn't a good answer.... I think that some of the missing building blocks for an image-level declarative formula specification are covered in my "Dangerous Liaisons: Smalltalk, files, and git "[1] talk, but I really think that there is additional work that needs to be done to make it really practical for large teams to be able work together on large projects. Dale [1] http://fast.org.ar/talks/dangerous-liaisons-smalltalk-files-and-git

Feb. 17, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Hilaire

Hi Dale, At first I was more thinking of a problem in the dependencies of Voyage, but then it seems not as with unload Seaside, Voyage get load. It did not help anyway becasue Seaside can't be reinstalled (Obsolete class syndrom hit there) Voyage is installed as: "VoyageMongo EstebanLorenzano.47" ConfigurationOfVoyageMongo load The transcript output in the attached document Thanks Le 17/02/2017 Ã 18:54, Dale Henrichs a Ã©crit : > You don't mention how you are loading Voyage. If I had the load > expression and Transcript output from the load, I'd pretty much be able > to tell pretty much what is going on. > > I have a couple of theories about what could be going wrong, but without > the load expression and Transcript output, I'd only be guessing and of > course there is the possibility that you've discovered a bug in Metacello:) > > If you'd like to get to the bottom of this, send me the load expression > and Transcript output and we'll go from there ... > -- Dr. Geo http://drgeo.eu

Feb. 17, 2017

Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

by Jigyasa Grover

Dear All It feels delighted to be nominated as finalist for *Red Hat International Women in Open Source Academic Awards 2017* owing to my significant contributions to the open source community spanning various organisations & projects viz FOSSASIA, Pharo/Smalltalk, European Smalltalk Users Group (ESUG), Hashkat, Women Who Code, Google Developers Group, Learn IT Girl!, various tech stints in Canada, Europe, Singapore & India, etc. and everyone's best wishes. After initial two rounds, final voting round is open now till March 6, 2017. I request and appeal all of you to kindly bless me with your valuable votes. Folks, Some love & maximum clicks please :wink: Details: https://www.redhat.com/en/about/women-in-open-source Vote here: https://engage.redhat.com/opensourceawards-winners-votingform-2017 -- View this message in context: http://forum.world.st/Seeking-support-Vote-for-Jigyasa-Grover-for-Red-Hat-I… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 17, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Dale Henrichs

Hilaire, You don't mention how you are loading Voyage. If I had the load expression and Transcript output from the load, I'd pretty much be able to tell pretty much what is going on. I have a couple of theories about what could be going wrong, but without the load expression and Transcript output, I'd only be guessing and of course there is the possibility that you've discovered a bug in Metacello:) If you'd like to get to the bottom of this, send me the load expression and Transcript output and we'll go from there ... Dale On 02/17/2017 08:56 AM, Hilaire wrote: > Trying to understand this problem: > > From my development image, I uninstalled all seaside, then I installed > Voyage. This time it went fine AND Seaside-core *was not* installed > during the process. > > What the heck is going on? > > When Seaside was present in my dev. image, installing Voyage make > Seaside-core to be installed/upgraded (it was marked as dirty in > Monticello, but no code change in fact) and it resulted in a broken > Seaside installation?? > > Is it Metacello voodoo? >

Feb. 17, 2017

Re: [Pharo-users] Team programming with Smalltalk

by Esteban A. Maringolo

I've used ENVY for a couple of years, and marginally used Store. Store is nothing compared with ENVY, ENVY is far superior. Store is like Monticello, but as such it lacks the "Configuration Map" part of it, that is offered by Metacello in Pharo/Squeak/GemStone. However I find ENVY to be too cumbersome for an agile way of working. I found Dolphin Smalltalk X6/7 using PAX source format which is file based VCS friendly working with Git to be a very good fit, and we used it in a team of up to 10 commiters to the same repository. Monticello together with Metacello offers a very good balance, with integrated tools that enables you to merge and understand the changes. I haven't used Iceberg yet. Esteban A. Maringolo 2017-02-15 20:53 GMT-03:00 Brad Selfridge <bsselfridge(a)gmail.com>: > I have worked with VASmalltalk for 20 years and this included projects > utilizing 10-15 developers. VASmalltalk uses Envy Manager as its VCS. Envy, > in my opinion, is far superior to anything on the market today where it > concerns code management. It has open editions, scratch editions, versions, > application packages, sub-application packages, merges, and doffs. However, > it was built to be used in an internal organization. It is not usable for > open source Smalltalk VCS projects such as Git. I believe that Visualworks > uses a RDBMS product called Store that is similar to Envy. Both of these are > commercial Smalltalks, however. > > > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/Team-programming-with-Smalltalk-tp4934508p4934514.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Feb. 17, 2017

Re: [Pharo-users] Team programming with Smalltalk

by Hilaire

You have a very strong point. The problem you emphasised, without explicitly naming it, comes from the image. Because the image preserves state it is also a great receptacle and accumulator for entropies, and as we know entropies only increase, never decrease! The direct consequence is that, at some time, after some interactions, installing code in some order, or installing broken code, an image breaks, hit the ground and becomes unusable. The image limit is always the chaos (as long as it is used as a living thing and its evolving state is preserved, saved), Entropies always comes with interacting 'living' system. So Smalltalk image comes with this downside of entropies. I don't see how you can bring argument against that to developer team, because it is the Smalltalk weakness, as well its strong point. Very funny. Of course you can try to limit entropies. Versioning your image is probably what to do, for example host task could save version of your image every two hours, daily, etc. GNU Smalltalk took an original approach: it ships a minimal image you don't modify and you install code on top of it. So really you never save your image, entropies remains constant over time. This approach is not really possible with Pharo. Best wishes Hilaire Le 15/02/2017 Ã 23:43, horrido a Ã©crit : > In file-based word, the answer is tests and CI. What is the smalltalk way? > And please do not say "It's in the conceptual nature of programming" -- if > the scenario makes no sense in the smalltalk world (maybe you are not > supposed to have 20 people working on the same project?) please say this. > > ----- > > How would you respond? I know Smalltalk can be used in large team > programming, but since I personally have no experience with this, I cannot > respond intelligently. -- Dr. Geo http://drgeo.eu

Feb. 17, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Hilaire

Trying to understand this problem: >From my development image, I uninstalled all seaside, then I installed Voyage. This time it went fine AND Seaside-core *was not* installed during the process. What the heck is going on? When Seaside was present in my dev. image, installing Voyage make Seaside-core to be installed/upgraded (it was marked as dirty in Monticello, but no code change in fact) and it resulted in a broken Seaside installation?? Is it Metacello voodoo? -- Dr. Geo http://drgeo.eu

Feb. 17, 2017

Re: [Pharo-users] Problem load Magritte

by Vitor Medina Cruz

Thanks, that works! On Fri, Feb 17, 2017 at 1:06 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 17/02/17 12:34, Vitor Medina Cruz wrote:StephanEggermont > >> I am getting the error message while trying to load magritte through the >> Pharo5 Catalog on a Windows machine: >> > > Looks like a wrong version of the configuration. > It looks like ConfigurationOfMagritte3-TudorGirba.122 did not get > copied to the MetaRepo. I've fixed that. > You can also download it from smalltalkhub > Magritte/Magritte3, and then do a ConfigurationOfMagritte3 load > > Stephan > > >

Feb. 17, 2017