November 2017 - Pharo-users

RBRuleIfNotNilDo usage

by Alistair Grant

Hi Everyone, I'm loading some code in to Pharo 7 that tries to use #ifNotNilDo:. There's already a transformation to re-write it to the correct #ifNotNil: - RBRuleIfNotNilDo. How can I apply the transformation to all existing methods in the image that call #ifNotNilDo:? Thanks, Alistair

Nov. 12, 2017

Re: [Pharo-users] LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks on latest 64bit 6.1 image?

by Esteban Lorenzano

> On 12 Nov 2017, at 09:44, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On 8 November 2017 at 16:06, Paulo R. Dellani <dellani(a)pobox.com> wrote: >> You need to configure Iceberg with the path of the SSH key >> files you are using to authenticate with gitlab as well as the >> passphrase to unlock the private key, I only got it working >> after that. Have your done that? >> >> There is more information in the README/FAQ here: >> >> https://github.com/pharo-vcs/iceberg > > Thanks for pointing this out. I had enough other fires that I'd given > up on 64 bit, however it appears to be working now. > > I'll restart my efforts to move to 64 bit. I found a but on 64bit 6.1 version. I will correct that, but in the mean time this is the workaround: LGitExternalStructure allSubclassesDo: #compileFields. Esteban > > Cheers, > Alistair > > > >> Cheers, >> >> Paulo >> >> >> On 11/08/2017 12:26 AM, Tim Mackinnon wrote: >> >> Thanks for confirming this Esteban - perhaps I am doing something wrong - I >> tried using the steps I was using successfully several months ago namely: >> >> curl get.pharo.org/64/ | bash >> ./pharo-ui Pharo.image >> >> Which got me the latest image - which sys info says is (not sure why it >> still says 6.0 tho?): >> >> Pharo 6.0 >> Latest update: #60520 >> >> I then open Iceberg, and click on Clone Repository >> >> In the dialog I enter: >> >> git@gitlab.com:macta/PharoLambda.git >> And put src in the code subdirectory field, and then click on Create. >> >> I get the LGit_GIT_ERROR ??? >> >> Hmm, out of curiosity, I just tried leaving the src field empty and it then >> seemed to put an entry into Iceberg but then a Fetch gave me the same error? >> >> Tim >> >> On 7 Nov 2017, at 11:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> iceberg should work on 64bits, both on Pharo7 and Pharo6. >> Iâve been using it exclusively on 64bits since some months now and I know >> Iâm not the only oneâ¦ can you send a way to reproduce your problem so I can >> take a look? >> >> Esteban >> >> >> On 6 Nov 2017, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - does Iceberg work on a 64bit image yet? Iâve not tried in a while, and >> was surprised when I went to get a new image via the command line that I am >> getting the error: LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks >> >> I can see a post by Alistair in Jun asking about this, and it seems 64bit >> hadnât been updated to work back then - but is this still true in Nov? >> >> We seem very much in turmoil at the moment - and its unclear what should >> work and not work. Is there a stable platform? If 64 bit is only working for >> 7.x - should we remove it from 6.x so that people donât inadvertently try to >> use it? >> >> Tim >

Nov. 12, 2017

Re: [Pharo-users] LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks on latest 64bit 6.1 image?

by Alistair Grant

On 8 November 2017 at 16:06, Paulo R. Dellani <dellani(a)pobox.com> wrote: > You need to configure Iceberg with the path of the SSH key > files you are using to authenticate with gitlab as well as the > passphrase to unlock the private key, I only got it working > after that. Have your done that? > > There is more information in the README/FAQ here: > > https://github.com/pharo-vcs/iceberg Thanks for pointing this out. I had enough other fires that I'd given up on 64 bit, however it appears to be working now. I'll restart my efforts to move to 64 bit. Cheers, Alistair > Cheers, > > Paulo > > > On 11/08/2017 12:26 AM, Tim Mackinnon wrote: > > Thanks for confirming this Esteban - perhaps I am doing something wrong - I > tried using the steps I was using successfully several months ago namely: > > curl get.pharo.org/64/ | bash > ./pharo-ui Pharo.image > > Which got me the latest image - which sys info says is (not sure why it > still says 6.0 tho?): > > Pharo 6.0 > Latest update: #60520 > > I then open Iceberg, and click on Clone Repository > > In the dialog I enter: > > git@gitlab.com:macta/PharoLambda.git > And put src in the code subdirectory field, and then click on Create. > > I get the LGit_GIT_ERROR ??? > > Hmm, out of curiosity, I just tried leaving the src field empty and it then > seemed to put an entry into Iceberg but then a Fetch gave me the same error? > > Tim > > On 7 Nov 2017, at 11:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > iceberg should work on 64bits, both on Pharo7 and Pharo6. > Iâve been using it exclusively on 64bits since some months now and I know > Iâm not the only oneâ¦ can you send a way to reproduce your problem so I can > take a look? > > Esteban > > > On 6 Nov 2017, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - does Iceberg work on a 64bit image yet? Iâve not tried in a while, and > was surprised when I went to get a new image via the command line that I am > getting the error: LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks > > I can see a post by Alistair in Jun asking about this, and it seems 64bit > hadnât been updated to work back then - but is this still true in Nov? > > We seem very much in turmoil at the moment - and its unclear what should > work and not work. Is there a stable platform? If 64 bit is only working for > 7.x - should we remove it from 6.x so that people donât inadvertently try to > use it? > > Tim

Nov. 12, 2017

Re: [Pharo-users] I18n in pharo

by Pavel Krivanek

2017-11-12 13:02 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Excellent Pavel. This is great. > So I do not get it. What is then not working? > The layout of the menu is wrong and everything needs to be proven with the newer versions of the dependent packages. -- Pavel > > Stef > > On Sun, Nov 12, 2017 at 12:13 AM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: > > > > > > 2017-11-10 11:52 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: > >> > >> A cleaner Pharo will help there. > >> > >> To be frank, I found later Pharo releases not inspiring. Bigger, bigger > >> and bigger with added code, protocol changes, and bugs at will. It is > >> becoming too complicated for a hobby use of it. > >> > >> I decided I will not finish porting DrGeo to P6 or P7, and it will > likely > >> die with P3. > > > > > > To run DrGeo on Pharo 7 is not hard (see the screenshot) - of course it > has > > some issues but they can be definitely solved. It would be pity to throw > it > > away - at least you can benefit from 64-bit and faster VM. > > > > -- Pavel > > > >> > >> Pharo should have been clean up to the bones before adding. It was the > >> initial moto, no? > >> > >> > >> Le 10/11/2017 Ã 11:14, Marcus Denker a Ã©crit : > >>> > >>> It would be nice if someone who uses it would take the lead > >>> so we can improve the default that is shipped with Pharo. > >> > >> > >> -- > >> Dr. Geo > >> http://drgeo.eu > >> > >> > >> > > > >

Nov. 12, 2017

Re: [Pharo-users] Anybody in this group in Bangalore or India

by Sanjay Minni

Hi Stef, This is a business application on Fixed Assets Management and I want to use Pharo+Seaside stack to make the current desktop application in the link below into an updated browser based application. http://www.minisoftindia.com/assetage/index.html This will be multi-tenanted hosted application in an internet server and there are features planned for users / tenants inter-connectivity so as to increase colloboration between users. Its planned as a subscription based model and if possible there will also be a desktop (local hosted) version as well. 2 Pharo group members took up the assignment / helped me and went along some way to design / build the partially done application but both are currently out of time hence I am looking at some associates. (they can pitch in here) Budget is a constraint as this is self funded hence I am looking at someone in India (preferably Bangalore) since hourly rates in the west works out to 5X rates in India. I though I will also get pharo skills and join hands but I guess learning is not that easy now The various applications at htto://www.minisoftindia.com/products were quite successful sometime back with a fair user base but since then were shelved. I plan to re-introduce them in a new Avatar i will be happy to answer any questions regards Sanjay Stephane Ducasse-3 wrote > Hi sanjay > > tell us more about this interesting project. > BTW I would love to have a success story from india and I know that > some people developed nice frameworks there but I forgot the contact. > > Stef > > On Sun, Nov 12, 2017 at 11:12 AM, Sanjay Minni < > sm@ > > wrote: >> Hi, >> >> Is there anybody in this group located in Bangalore, >> >> You could connect with me at sanjay.minni_at_gmail.com if you would like >> to >> join in an interesting project >> >> regards >> Sanjay >> >> >> >> ----- >> --- >> Regards, Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> ----- --- Regards, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 12, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Stephane Ducasse

Sean why don't you try because this is the moment to push bloc people to produce simpler better solution. I should do it too. I know. Stef On Sun, Nov 12, 2017 at 3:58 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >> That would be another renderer, but it is not difficult to build. That is >> something weâll do soon. > > It would be nice to be able to toggle codes on/off like WS Word > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 12, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

Hilaire Bloc, Brick are not in Pharo yet. So either you want to build on top of Bloc and you use Bloc or not. Easy. Right now in Pharo we have - plain Morphic (with Polymorph but this is the same) - Spec to build user interface independent of the underlying layer (Morphic for now) - Glamour to build browser/navigation Now if you need vector graphics: you use Athens in Pharo. In the future we will have Sparta which is better adapted for Bloc (local coordinates over global coordinates) but this is the same kind of API. So this is not complex. The decision tree is Using plain Pharo or not => Morphic or Bloc Stef On Sat, Nov 11, 2017 at 9:29 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > P6 is definitely a better IDE compare to previous version, and for coming > Calypso looks fantastic, but P6 is a worst vehicle for a desktop > application. There is much more code included and you are on your on to > shrink/clean it to deploy your desktop application to make it looks and > behave user friendly. May be for a specialized audience it could be just > fine to deploy as is. > > About my perception on Pharo, from a distant POV, I see > parallel/overlapping/contiguous layers like Morphic, Athens, Sparta, Bloc, > Brick, Spec, GT, Polymorph all this looks confusing for me and I really > don't know or understand where to put my eggs. > > When I took a look at Pharo keyboard shortcut, it seems to be -- without > been sure 100% -- there are two different implementations. One from GT and > another one, probably a legacy one. How can it happen? Then you wonder about > other part of the system. It makes fells like changes/implementations are > not coherent, and you don't really fell the environment as coherent or > trustful. > > May be the twist is ontological, Pharo (and Squeak) taking too much > responsibilities and not delegating enough to the host environment: GUI, > Freetype, Canvas. The energy required is then out of reach or the needed > coherence in teams works too complex. Don't know, just blind guesses, I will > now shut up. > > > Le 10/11/2017 Ã 12:23, CÃ©drick BÃ©ler a Ã©crit : >> >> But I have the opposite impression (of course I donât have to maintain a >> big project like yours - I wouldnât say youâre the hobby user:) ). But I >> really find P6 more consistent than what I used to try in the past (last >> squeaks up to 3.9 and firsts pharo). > > > -- > Dr. Geo > http://drgeo.eu > > >

Nov. 12, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

Offray Pavel and me have been working to clean and enhance Spec aspects. We are getting slowly but we will continue. I want to support menu in a much better way (declarative). Peter rewrote the Spec Interpreter and I hope that it will finish it, else we will have to do it because the code is "suboptimal". Stef On Sun, Nov 12, 2017 at 12:59 AM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Thanks for the diagram Aliaksei. It helps to understand the Pharo > buildings blocks. Where Spec would be located there? > > Cheers, > > Offray > > On 11/11/17 15:56, Aliaksei Syrel wrote: > > Hi Hilaire, > > About my perception on Pharo, from a distant POV, I see >> parallel/overlapping/contiguous layers like Morphic, Athens, Sparta, >> Bloc, Brick, Spec, GT, > > > Could you, please, explain in a bit more detail why do you think that > Sparta, Bloc, Brick and GT are overlapping layers? > > In attachment you can find a layered architecture diagram that explains > how those technologies are stacked *from our* point of view :) > [image: Inline images 1] > Cheers, > Alex > > On 11 November 2017 at 21:48, stephan <stephan(a)stack.nl> wrote: > >> On 11-11-17 21:18, H. Hirzel wrote: >> >>> On 11/11/17, stephan <stephan(a)stack.nl> wrote: >>> >>>> On 10-11-17 12:23, CÃ©drick BÃ©ler wrote: >>>> >>>>> Plus I have the impression Morphic mess is about to be solved. >>>>> >>>> >>>> There is still an awful lot of essential complexity in beautiful >>>> graphics and typography that is not going away. Microsoft Word still >>>> cannot layout a paragraph of text after 34 years of development >>>> >>> >>> Can you point to an example of this? >>> >> >> https://en.wikipedia.org/wiki/Microtypography >> >> Stephan >> >> >> > >

Nov. 12, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

> Looks like a big sandwich, though. > > Will Athne be throwm away? With Polymorph and Morph? Yes. Morph and Polymorph as well as Athens but Sparta offers a similar API. So conversion should be easy. And Bloc opens a lot of possibilities. Bloc is the result of around 4 years of effort understanding the domain and comparing solutions. Stef

Nov. 12, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

Spec is at the same level than GTtoolkit. On top of available widgets. On Sun, Nov 12, 2017 at 12:59 AM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Thanks for the diagram Aliaksei. It helps to understand the Pharo > buildings blocks. Where Spec would be located there? > > Cheers, > > Offray > > On 11/11/17 15:56, Aliaksei Syrel wrote: > > Hi Hilaire, > > About my perception on Pharo, from a distant POV, I see >> parallel/overlapping/contiguous layers like Morphic, Athens, Sparta, >> Bloc, Brick, Spec, GT, > > > Could you, please, explain in a bit more detail why do you think that > Sparta, Bloc, Brick and GT are overlapping layers? > > In attachment you can find a layered architecture diagram that explains > how those technologies are stacked *from our* point of view :) > [image: Inline images 1] > Cheers, > Alex > > On 11 November 2017 at 21:48, stephan <stephan(a)stack.nl> wrote: > >> On 11-11-17 21:18, H. Hirzel wrote: >> >>> On 11/11/17, stephan <stephan(a)stack.nl> wrote: >>> >>>> On 10-11-17 12:23, CÃ©drick BÃ©ler wrote: >>>> >>>>> Plus I have the impression Morphic mess is about to be solved. >>>>> >>>> >>>> There is still an awful lot of essential complexity in beautiful >>>> graphics and typography that is not going away. Microsoft Word still >>>> cannot layout a paragraph of text after 34 years of development >>>> >>> >>> Can you point to an example of this? >>> >> >> https://en.wikipedia.org/wiki/Microtypography >> >> Stephan >> >> >> > >

Nov. 12, 2017