Re: [Pharo-dev] Class syntax brainstorming

On Monday 22 May 2017 05:32 PM, Denis Kudriashov wrote: package: #MyPackage; tags: #(Core); layout: #MethodDictionaryLayout. How about: properties: { #package->"My Package", ... } A property dictionary would be a better option than named variables as it will not impose a burden on every

Re: [Pharo-dev] Class syntax brainstorming

On 05/22/2017 12:25 AM, Luc Fabresse wrote: > Hi, > > Following Pharo Days, I brainstormed about some possible class > definition syntaxes. There is a class definition syntax defined in ANSI Smalltalk. It's a syntax, purely declarative. I seem to recall seeing at least one implementation of

[Pharo-dev] Do we have a full CSS parser?

If so, where? Thanks! -- Mariano http://marianopeck.wordpress.com

Re: [Pharo-dev] Can this regex be implemented in Pharo's one?

On Mon, May 22, 2017 at 4:30 PM, Max Leske wrote: > > On 22 May 2017, at 20:50, Mariano Martinez Peck > wrote: > > Hi guys, > > I have this Javascript regex to prefix CSS rules to a given ID: > > css =

Re: [Pharo-dev] Iceberg ?

ls -la ~/.ssh wil probably show you that you don’t have a key named “id_rsa”. You have to specify the correct file (e.g. my github key is named “github”). HTH, Max > On 22 May 2017, at 21:47, Stephane Ducasse wrote: > > I get > > ssh-add -K ~/.ssh/id_rsa > > Error

Re: [Pharo-dev] Iceberg ?

I get ssh-add -K ~/.ssh/id_rsa Error connecting to agent: No such file or directory On Mon, May 22, 2017 at 9:46 PM, Stephane Ducasse wrote: > Yes please do because I had no idea and I was trying to look at the > setting but without results. > > On Mon, May 22, 2017

Re: [Pharo-dev] Iceberg ?

Yes please do because I had no idea and I was trying to look at the setting but without results. On Mon, May 22, 2017 at 8:53 PM, Esteban Lorenzano wrote: > Hi, > > is not weird because git uses other authentication services and for now we > just implemented ssh/ssh-agent

Re: [Pharo-dev] Can this regex be implemented in Pharo's one?

> On 22 May 2017, at 20:50, Mariano Martinez Peck wrote: > > 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”);

Re: [Pharo-dev] Iceberg ?

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

[Pharo-dev] Can this regex be implemented in Pharo's one?

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

Re: [Pharo-dev] Iceberg ?

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

Re: [Pharo-dev] Iceberg ?

Tx I will have a look. On Sun, May 21, 2017 at 11:43 AM, Myroslava Romaniuk wrote: > Well it is a bit different with iceberg. Have a look at the FAQ > section here, and here >

Re: [Pharo-dev] Class syntax brainstorming

Yes this is the idea. We should the combinatorial explosion :) On Mon, May 22, 2017 at 1:27 PM, Gabriel Cotelli 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; >

[Pharo-dev] Is there any implementation of gnupg (PGP) signature/encryption in pharo?

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

Re: [Pharo-dev] Class syntax brainstorming

...do not forget on method tags -- Pavel 2017-05-22 16:44 GMT+02:00 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

Re: [Pharo-dev] Class syntax brainstorming

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 : > Hi, > > Following Pharo Days, I brainstormed about some possible class

Re: [Pharo-dev] Class syntax brainstorming

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

Re: [Pharo-dev] Class syntax brainstorming

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

Re: [Pharo-dev] Class syntax brainstorming

On Mon, May 22, 2017 at 3:25 PM, Luc Fabresse 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;

Re: [Pharo-dev] Class syntax brainstorming

--- Begin Message --- >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'; >

Re: [Pharo-dev] Class syntax brainstorming

2017-05-22 13:40 GMT+02:00 Sven Van Caekenberghe : > Why can't instance variables/slots not be Symbols as well ... To me current slot syntax is good enough. Anybody have objections?

Re: [Pharo-dev] Class syntax brainstorming

2017-05-22 13:53 GMT+02:00 Denis Kudriashov : > Class <<< #MyClass > superclass: #Object; > uses: #MyTrait; > vars: { #a. #b }; > classVars: { #A. #B }; > package: #MyPackage; > tags: #(Core); > layout: #MethodDictionaryLayout. And few notes: all messages should be

Re: [Pharo-dev] Class syntax brainstorming

The build / partial object syntaxes are interesting in the way they could be integrated with RB in creating RB actions (RDAddClassChange / RBAddClassVariableChange / RBAddInstanceVariableChange) that could then be played on "build". Gives you a nice undo/redo capability and Epicea integration to

Re: [Pharo-dev] Class syntax brainstorming

Hi. My idea was to ask concrete metaobject for new object definition: Class <<< #MyClass superclass: #Object; uses: #MyTrait; vars: { #a. #b }; classVars: { #A. #B }; package: #MyPackage; tags: #(Core); layout: #MethodDictionaryLayout. for class side: Metaclass <<< #MyClass vars: { }. Or:

Re: [Pharo-dev] Class syntax brainstorming

I'd also put in the pot a more declarative, less-smalltalkish-syntax approach: Class { name: 'A', superclass: Object, a: InstVar, b: InstVar, c: InstVar } Of course this could evolve. Some people will say that this is too verbose if you have lots of instance variables. I'd say that

Re: [Pharo-dev] Class syntax brainstorming

Why can't instance variables/slots not be Symbols as well ... > On 22 May 2017, at 13:27, Gabriel Cotelli 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; >

Re: [Pharo-dev] Class syntax brainstorming

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;

Re: [Pharo-dev] Iceberg help

> On 22 May 2017, at 10:26, Christophe Demarey > wrote: > > Hi Stephane, > > Your url looks wrong. > It should be: g...@github.com:pharo-graphics/Bloc.git or > g...@github.com:ducasse/Bloc.git yes, they are like this :) > >> Le 21 mai 2017 à 11:29, Stephane

[Pharo-dev] [pharo-project/pharo-core] 9c3b4e: 60495

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 9c3b4e263319754e8dff9d15b1ce7d9c91f09ab4 https://github.com/pharo-project/pharo-core/commit/9c3b4e263319754e8dff9d15b1ce7d9c91f09ab4 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60495 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Iceberg help

Hi Stephane, Your url looks wrong. It should be: g...@github.com:pharo-graphics/Bloc.git or g...@github.com:ducasse/Bloc.git > Le 21 mai 2017 à 11:29, Stephane Ducasse a écrit : > > So I tried to use iceberg to contribute to bloc > > I entered g...@github.com >

[Pharo-dev] [Pharo 6] PharoV60.sources with 60493

Hi, Last week we have generated new .sources for Pharo6 (we completely forgot to send a mail, too much stress… even now I am officially on holiday and should not even look at the computer…) There is a PharoV60.sources for Pharo6 now: http://files.pharo.org/sources/PharoV60.sources

[Pharo-dev] Class syntax brainstorming

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

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

On Sunday 21 May 2017 11:34 PM, Dale Henrichs wrote: As part of his work on Cypress 2.0 Martin McClure is planning on supporting a file per class disk format in addition to the file per method format and possibly a file per package format. I'm not sure whether Martin is at the point where he is