- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Iceberg ?

by Esteban Lorenzano

Hi, is not weird because git uses other authentication services and for now we just implemented ssh/ssh-agent :) solution is to execute this in command line: ssh-add -K ~/.ssh/id_rsa then it will be ok. (I will add an entry for this in the FAQ) > On 22 May 2017, at 20:48, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > I got the very same error. And this is weird because I can commit from the command line or using any Git client. > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On May 21, 2017, at 5:31 AM, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: >> >> On mac with latest pharo vm and latest pharo 60 >> Metacello new >> baseline: 'Bloc'; >> repository: 'github://pharo-graphics/Bloc/src <github://pharo-graphics/Bloc/src>'; >> load:#core >> >> Then I got LGit_GIT_ERROR no ssh-agent suitable credentials found >> >> >

May 22, 2017

Can this regex be implemented in Pharo's one?

by Mariano Martinez Peck

Hi guys, I have this Javascript regex to prefix CSS rules to a given ID: css = css.replace(/([,|\}][\s$]*)([\.#]?-?[_a-zA-Z]+[_a-zA-Z0-9-]*)/g, "$1" + "#myDiv" + " $2"); I am trying to make this work on Pharo (and then I will need in GemStone) but I am getting errors while trying to create the regex itself. I am very far from being a regex expert (I got that regex from StackOverflow). Any help is appreciated. Cheers, -- Mariano http://marianopeck.wordpress.com

May 22, 2017

Re: [Pharo-dev] Iceberg ?

by Alexandre Bergel

I got the very same error. And this is weird because I can commit from the command line or using any Git client. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 21, 2017, at 5:31 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > On mac with latest pharo vm and latest pharo 60 > Metacello new > baseline: 'Bloc'; > repository: 'github://pharo-graphics/Bloc/src'; > load:#core > > Then I got LGit_GIT_ERROR no ssh-agent suitable credentials found > >

May 22, 2017

Re: [Pharo-dev] Iceberg ?

by Stephane Ducasse

Tx I will have a look. On Sun, May 21, 2017 at 11:43 AM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Well it is a bit different with iceberg. Have a look at the FAQ > <https://github.com/pharo-vcs/iceberg#FAQ> section here, and here > <https://help.github.com/articles/connecting-to-github-with-ssh/>'s a > general guide regarding connecting github with ssh. Let me know if this > helps > > On 21 May 2017 at 12:35, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > >> yes and I should publish it on my git account? >> I use git daily so I do not get why I should do something different with >> iceberg/ >> >> On Sun, May 21, 2017 at 11:33 AM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua >> > wrote: >> >>> Have you got a ssh key? >>> >>> On 21 May 2017 at 12:31, Stephane Ducasse <stepharo.self(a)gmail.com> >>> wrote: >>> >>>> On mac with latest pharo vm and latest pharo 60 >>>> Metacello new >>>> baseline: 'Bloc'; >>>> repository: 'github://pharo-graphics/Bloc/src'; >>>> load:#core >>>> >>>> Then I got LGit_GIT_ERROR no ssh-agent suitable credentials found >>>> >>>> >>>> >>> >>> >>> -- >>> Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, >>> ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº. >>> >> >> > > > -- > Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, > ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº. >

May 22, 2017

Re: [Pharo-dev] Class syntax brainstorming

by Stephane Ducasse

Yes this is the idea. We should the combinatorial explosion :) On Mon, May 22, 2017 at 1:27 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > If we can get rid off the myriad of class creation methods count me in. :) > > I would do something like: > > ClassBuilder new > name: #A; > superclass: Object; > addInstanceVariableNamed: 'a'; > addInstanceVariableNamed: 'c'; > addBooleanSlotNamed: 'z'; > addClassVariableNamed: 'D'; > use: SomeTrait; > use: SomeOtherTrait; > beWeak "if you want a weak subclass"; > build > > With all of this optional. If we can avoid to pass nil as superclass for > the cases you don't have a superclass that would be good, maybe an specific > method in the builder ? > > On Mon, May 22, 2017 at 4:25 AM, Luc Fabresse <luc.fabresse(a)gmail.com> > wrote: > >> Hi, >> >> Following Pharo Days, I brainstormed about some possible class definition >> syntaxes. >> What I have in mind: >> >> "basic mechanics, only THIS one in the image!" >> ClassDefinition new >> superclass: Object; "optional. If not specified, Object by default ;-)" >> name: #A; "optional and create an anonymous class if not specified" >> instVars: 'a b c'; >> traits: {TEquality}; >> package: 'Plop'; >> createClass. " this message sent might be hidden by the browser when >> accepting" >> >> "---------------" >> "Some IDEAS (but I did not find one that I really like) of >> scripting/shorter syntaxes that must ALWAYS end up calling the above basic >> mechanics at the end:" >> >> Class fromDefinition: [ :def | >> def name: #sub; >> instVars: 'w r g'; >> superclass: Object ]. >> >> Object subclass "<-- returns a subclass of Object but the problem is >> that the new class is muted each time and the class definition is not >> explicit" >> name: #A; >> ivs: 'a b c'; >> traits: { TEquality }. >> >> { #superclass -> Object. >> #name -> #sub. >> #instVars -> 'a b c' } asClass. >> >> { Object asSuperclass. >> #sub asClassName. >> 'a b c' asInstVars. >> 'c' asClassVar } asClass. >> >> "litteral approach" >> #( name A >> superclass Object >> instVars #(a b c) >> instVar d >> ) asClass >> >> >> #Luc >> > >

May 22, 2017

Is there any implementation of gnupg (PGP) signature/encryption in pharo?

by Casimiro de Almeida Barreto - GMAIL

Good evening, Is there a implementation of PGP signature/encryption protocols in pharo? Best regards, Casimiro

May 22, 2017

Re: [Pharo-dev] Class syntax brainstorming

by Pavel Krivanek

...do not forget on method tags -- Pavel 2017-05-22 16:44 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Nice. We will have troubles with slots because that will mix model and > real instances (and slot definitions can contain any Smalltalk code) > > -- Pavel > > 2017-05-22 9:25 GMT+02:00 Luc Fabresse <luc.fabresse(a)gmail.com>: > >> Hi, >> >> Following Pharo Days, I brainstormed about some possible class definition >> syntaxes. >> What I have in mind: >> >> "basic mechanics, only THIS one in the image!" >> ClassDefinition new >> superclass: Object; "optional. If not specified, Object by default ;-)" >> name: #A; "optional and create an anonymous class if not specified" >> instVars: 'a b c'; >> traits: {TEquality}; >> package: 'Plop'; >> createClass. " this message sent might be hidden by the browser when >> accepting" >> >> "---------------" >> "Some IDEAS (but I did not find one that I really like) of >> scripting/shorter syntaxes that must ALWAYS end up calling the above basic >> mechanics at the end:" >> >> Class fromDefinition: [ :def | >> def name: #sub; >> instVars: 'w r g'; >> superclass: Object ]. >> >> Object subclass "<-- returns a subclass of Object but the problem is >> that the new class is muted each time and the class definition is not >> explicit" >> name: #A; >> ivs: 'a b c'; >> traits: { TEquality }. >> >> { #superclass -> Object. >> #name -> #sub. >> #instVars -> 'a b c' } asClass. >> >> { Object asSuperclass. >> #sub asClassName. >> 'a b c' asInstVars. >> 'c' asClassVar } asClass. >> >> "litteral approach" >> #( name A >> superclass Object >> instVars #(a b c) >> instVar d >> ) asClass >> >> >> #Luc >> > >

May 22, 2017

Re: [Pharo-dev] Class syntax brainstorming

by Pavel Krivanek

Nice. We will have troubles with slots because that will mix model and real instances (and slot definitions can contain any Smalltalk code) -- Pavel 2017-05-22 9:25 GMT+02:00 Luc Fabresse <luc.fabresse(a)gmail.com>: > Hi, > > Following Pharo Days, I brainstormed about some possible class definition > syntaxes. > What I have in mind: > > "basic mechanics, only THIS one in the image!" > ClassDefinition new > superclass: Object; "optional. If not specified, Object by default ;-)" > name: #A; "optional and create an anonymous class if not specified" > instVars: 'a b c'; > traits: {TEquality}; > package: 'Plop'; > createClass. " this message sent might be hidden by the browser when > accepting" > > "---------------" > "Some IDEAS (but I did not find one that I really like) of > scripting/shorter syntaxes that must ALWAYS end up calling the above basic > mechanics at the end:" > > Class fromDefinition: [ :def | > def name: #sub; > instVars: 'w r g'; > superclass: Object ]. > > Object subclass "<-- returns a subclass of Object but the problem is that > the new class is muted each time and the class definition is not explicit" > name: #A; > ivs: 'a b c'; > traits: { TEquality }. > > { #superclass -> Object. > #name -> #sub. > #instVars -> 'a b c' } asClass. > > { Object asSuperclass. > #sub asClassName. > 'a b c' asInstVars. > 'c' asClassVar } asClass. > > "litteral approach" > #( name A > superclass Object > instVars #(a b c) > instVar d > ) asClass > > > #Luc >

May 22, 2017

Re: [Pharo-dev] Class syntax brainstorming

by Alexandre Bergel

I like very much the idea! Creating a class can be done in many different ways. The Factory design pattern should be applied here I think. Something like ClassFactory Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 22, 2017, at 3:25 AM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > Hi, > > Following Pharo Days, I brainstormed about some possible class definition syntaxes. > What I have in mind: > > "basic mechanics, only THIS one in the image!" > ClassDefinition new > superclass: Object; "optional. If not specified, Object by default ;-)" > name: #A; "optional and create an anonymous class if not specified" > instVars: 'a b c'; > traits: {TEquality}; > package: 'Plop'; > createClass. " this message sent might be hidden by the browser when accepting" > > "---------------" > "Some IDEAS (but I did not find one that I really like) of scripting/shorter syntaxes that must ALWAYS end up calling the above basic mechanics at the end:" > > Class fromDefinition: [ :def | > def name: #sub; > instVars: 'w r g'; > superclass: Object ]. > > Object subclass "<-- returns a subclass of Object but the problem is that the new class is muted each time and the class definition is not explicit" > name: #A; > ivs: 'a b c'; > traits: { TEquality }. > > { #superclass -> Object. > #name -> #sub. > #instVars -> 'a b c' } asClass. > > { Object asSuperclass. > #sub asClassName. > 'a b c' asInstVars. > 'c' asClassVar } asClass. > > "litteral approach" > #( name A > superclass Object > instVars #(a b c) > instVar d > ) asClass > > > #Luc

May 22, 2017

Re: [Pharo-dev] Class syntax brainstorming

by Mariano Martinez Peck

Honestly, I do not like that much having a more declarative (less Smalltalksish) definition. In fact, one of the things I was always proud of showing to Smalltalk newcomers, that when they created a class, all they were doing was a "DoIt" to tell the superclass to create the new subclass. And then showing how they could copy and paste that into a workspace and DoIt. Or Debug it. So..if it were for me, I would keep a Smalltalk syntax with a plain message send. Sure, a builder kind of API is better to me, like Luc proposes. Also, I do prefer too the #createAndInstall kind of message so that we can have a flavour of #createClass that only creates the class but doesn't install it into the system. Cheers, On Mon, May 22, 2017 at 10:48 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Mon, May 22, 2017 at 3:25 PM, Luc Fabresse <luc.fabresse(a)gmail.com> > wrote: > >> Hi, >> >> Following Pharo Days, I brainstormed about some possible class definition >> syntaxes. >> What I have in mind: >> >> "basic mechanics, only THIS one in the image!" >> ClassDefinition new >> superclass: Object; "optional. If not specified, Object by default ;-)" >> name: #A; "optional and create an anonymous class if not specified" >> instVars: 'a b c'; >> traits: {TEquality}; >> package: 'Plop'; >> createClass. " this message sent might be hidden by the browser when >> accepting" >> >> "---------------" >> "Some IDEAS (but I did not find one that I really like) of >> scripting/shorter syntaxes that must ALWAYS end up calling the above basic >> mechanics at the end:" >> >> Class fromDefinition: [ :def | >> def name: #sub; >> instVars: 'w r g'; >> superclass: Object ]. >> >> Object subclass "<-- returns a subclass of Object but the problem is >> that the new class is muted >> > > (btw, I assume you mean mutated.) > > >> each time and the class definition is not explicit" >> name: #A; >> ivs: 'a b c'; >> traits: { TEquality }. >> > > What about... > > Object subclass: [ :def | def > name: 'MyClass' ; "optional and create an anonymous class if not > specified" > instanceVariables: 'a b c' ; > classVariables: 'M N O'; > classInstanceVariables: 'x y z' ; > traits: {TEquality} ; > package: 'Plop']. > > Object>>subclass: builderBlock > ^ (builderBlock value: ClassDefinition new) createClass > > or similar to Guille's declarative proposal... > > Object subclass: { > name: 'Myclass', > a: InstVar, > b: InstVar, > c: InstVar > } > > > cheers -ben > -- Mariano http://marianopeck.wordpress.com

May 22, 2017