Re: [Pharo-dev] FFI without the Pharo sources

[Marcus Denker]

I wil merge the PR after the test ran a last time.

> On 31 Jan 2018, at 08:30, Vincent BLONDEAU 
>  wrote:
> 
> Now, yes it is. See FFICompilerPlugin :)
> 
> Vincent
> 
> -Original Message-
> From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of 
> Stephane Ducasse
> Sent: mardi 30 janvier 2018 23:15
> To: Pharo Development List
> Subject: Re: [Pharo-dev] FFI without the Pharo sources
> 
> Thanks vincent.
> is it the comment of some classes?
> 
> Stef
> 
> On Wed, Jan 31, 2018 at 3:12 AM,   wrote:
>> Hi,
>> 
>> So, I suggest this solution: 
>> https://github.com/pharo-project/pharo/pull/750
>> 
>> It is a plugin for the OpalCompiler that can be activated with the command 
>> "FFICompilerPlugin install."
>> The plugin is pragma-based to detect the methods where the arguments names 
>> should be remembered.
>> The pragma should be added in the FFI API methods, i.e., the methods that 
>> are called by the FFI methods where the arguments have to be remembered.
>> Example:
>> 
>> This FFI method should remember the name of the argument named "config":
>> 
>> repository_config: config
>>^ self
>>call: #(#LGitReturnCodeEnum #git_repository_config 
>> #(#LGitConfig #* #config #, #self))
>>options: #()
>> 
>> So, the FFI function should wear the pragma :
>> 
>> call: fnSpec options: options
>>
>>^ (self safeFFICalloutIn: thisContext sender)
>>cdecl;
>>options: options;
>>function: fnSpec module: self ffiLibraryName
>> 
>> To remove to be able to remove the sources (.changes and .sources), you only 
>> have to activate the plugin, no recompilation is necessary. You can even 
>> import new FFI methods or change the FFI API.
>> 
>> N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> 
>> call:options:) also have to wear the pragma.
>> 
>> Cheers,
>> Vincent
>> 
>> -Original Message-
>> From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf 
>> Of Stephane Ducasse
>> Sent: Wednesday, January 24, 2018 9:21
>> To: Pharo Development List 
>> Subject: Re: [Pharo-dev] FFI without the Pharo sources
>> 
>> So if you implement a cool solution we will integrate it immediately 
>> :)
>> 
>> On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse  
>> wrote:
>>> Thanks Vincent we are interested to make the independence on source 
>>> much simpler.
>>> 
>>> Stef
>>> 
>>> 
>>> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda  
>>> wrote:
 Hi Vincent,
 
> On Jan 23, 2018, at 4:54 PM,  
>  wrote:
> 
> Hi,
> 
> I am working to be able to create some standalone apps in Pharo. And for 
> this, I would like to remove of the .sources and .changes. But, by 
> removing them, the args names are reset to arg1, arg2, arg3, ... and the 
> FFI cannot be used anymore.
> 
> Does someone (Esteban?) have a solution that I could implement to fix 
> this issue?
 
 One avenue that should be easy to implement would be to modify the 
 compiler to save the temporary names as a property of the method.
 
 
> 
> Thanks!
> 
> Vincent
 
 _,,,^..^,,,_ (phone)
>> 
> 
> 
> 

Re: [Pharo-dev] FFI without the Pharo sources

[Vincent BLONDEAU]

Now, yes it is. See FFICompilerPlugin :)

Vincent

-Original Message-
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of 
Stephane Ducasse
Sent: mardi 30 janvier 2018 23:15
To: Pharo Development List
Subject: Re: [Pharo-dev] FFI without the Pharo sources

Thanks vincent.
is it the comment of some classes?

Stef

On Wed, Jan 31, 2018 at 3:12 AM,   wrote:
> Hi,
>
> So, I suggest this solution: 
> https://github.com/pharo-project/pharo/pull/750
>
> It is a plugin for the OpalCompiler that can be activated with the command 
> "FFICompilerPlugin install."
> The plugin is pragma-based to detect the methods where the arguments names 
> should be remembered.
> The pragma should be added in the FFI API methods, i.e., the methods that are 
> called by the FFI methods where the arguments have to be remembered.
> Example:
>
> This FFI method should remember the name of the argument named "config":
>
> repository_config: config
> ^ self
> call: #(#LGitReturnCodeEnum #git_repository_config 
> #(#LGitConfig #* #config #, #self))
> options: #()
>
> So, the FFI function should wear the pragma :
>
> call: fnSpec options: options
> 
> ^ (self safeFFICalloutIn: thisContext sender)
> cdecl;
> options: options;
> function: fnSpec module: self ffiLibraryName
>
> To remove to be able to remove the sources (.changes and .sources), you only 
> have to activate the plugin, no recompilation is necessary. You can even 
> import new FFI methods or change the FFI API.
>
> N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> 
> call:options:) also have to wear the pragma.
>
> Cheers,
> Vincent
>
> -Original Message-
> From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf 
> Of Stephane Ducasse
> Sent: Wednesday, January 24, 2018 9:21
> To: Pharo Development List 
> Subject: Re: [Pharo-dev] FFI without the Pharo sources
>
> So if you implement a cool solution we will integrate it immediately 
> :)
>
> On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse  
> wrote:
>> Thanks Vincent we are interested to make the independence on source 
>> much simpler.
>>
>> Stef
>>
>>
>> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda  
>> wrote:
>>> Hi Vincent,
>>>
 On Jan 23, 2018, at 4:54 PM,  
  wrote:

 Hi,

 I am working to be able to create some standalone apps in Pharo. And for 
 this, I would like to remove of the .sources and .changes. But, by 
 removing them, the args names are reset to arg1, arg2, arg3, ... and the 
 FFI cannot be used anymore.

 Does someone (Esteban?) have a solution that I could implement to fix this 
 issue?
>>>
>>> One avenue that should be easy to implement would be to modify the compiler 
>>> to save the temporary names as a property of the method.
>>>
>>>

 Thanks!

 Vincent
>>>
>>> _,,,^..^,,,_ (phone)
>

Re: [Pharo-dev] FFI without the Pharo sources

[Stephane Ducasse]

Thanks vincent.
is it the comment of some classes?

Stef

On Wed, Jan 31, 2018 at 3:12 AM,   wrote:
> Hi,
>
> So, I suggest this solution: https://github.com/pharo-project/pharo/pull/750
>
> It is a plugin for the OpalCompiler that can be activated with the command 
> "FFICompilerPlugin install."
> The plugin is pragma-based to detect the methods where the arguments names 
> should be remembered.
> The pragma should be added in the FFI API methods, i.e., the methods that are 
> called by the FFI methods where the arguments have to be remembered.
> Example:
>
> This FFI method should remember the name of the argument named "config":
>
> repository_config: config
> ^ self
> call: #(#LGitReturnCodeEnum #git_repository_config 
> #(#LGitConfig #* #config #, #self))
> options: #()
>
> So, the FFI function should wear the pragma :
>
> call: fnSpec options: options
> 
> ^ (self safeFFICalloutIn: thisContext sender)
> cdecl;
> options: options;
> function: fnSpec module: self ffiLibraryName
>
> To remove to be able to remove the sources (.changes and .sources), you only 
> have to activate the plugin, no recompilation is necessary. You can even 
> import new FFI methods or change the FFI API.
>
> N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> 
> call:options:) also have to wear the pragma.
>
> Cheers,
> Vincent
>
> -Original Message-
> From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of 
> Stephane Ducasse
> Sent: Wednesday, January 24, 2018 9:21
> To: Pharo Development List 
> Subject: Re: [Pharo-dev] FFI without the Pharo sources
>
> So if you implement a cool solution we will integrate it immediately :)
>
> On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse  
> wrote:
>> Thanks Vincent we are interested to make the independence on source
>> much simpler.
>>
>> Stef
>>
>>
>> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda  
>> wrote:
>>> Hi Vincent,
>>>
 On Jan 23, 2018, at 4:54 PM,  
  wrote:

 Hi,

 I am working to be able to create some standalone apps in Pharo. And for 
 this, I would like to remove of the .sources and .changes. But, by 
 removing them, the args names are reset to arg1, arg2, arg3, ... and the 
 FFI cannot be used anymore.

 Does someone (Esteban?) have a solution that I could implement to fix this 
 issue?
>>>
>>> One avenue that should be easy to implement would be to modify the compiler 
>>> to save the temporary names as a property of the method.
>>>
>>>

 Thanks!

 Vincent
>>>
>>> _,,,^..^,,,_ (phone)
>

Re: [Pharo-dev] FFI without the Pharo sources

[Vincent.Blondeau]

Hi,

So, I suggest this solution: https://github.com/pharo-project/pharo/pull/750

It is a plugin for the OpalCompiler that can be activated with the command 
"FFICompilerPlugin install."
The plugin is pragma-based to detect the methods where the arguments names 
should be remembered.
The pragma should be added in the FFI API methods, i.e., the methods that are 
called by the FFI methods where the arguments have to be remembered.
Example:

This FFI method should remember the name of the argument named "config":

repository_config: config
^ self
call: #(#LGitReturnCodeEnum #git_repository_config 
#(#LGitConfig #* #config #, #self))
options: #()

So, the FFI function should wear the pragma :

call: fnSpec options: options

^ (self safeFFICalloutIn: thisContext sender)
cdecl;
options: options;
function: fnSpec module: self ffiLibraryName

To remove to be able to remove the sources (.changes and .sources), you only 
have to activate the plugin, no recompilation is necessary. You can even import 
new FFI methods or change the FFI API.

N.B: Users that redefine the FFI API (like TLGitCalloutTrait >> call:options:) 
also have to wear the pragma.

Cheers,
Vincent

-Original Message-
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of 
Stephane Ducasse
Sent: Wednesday, January 24, 2018 9:21
To: Pharo Development List 
Subject: Re: [Pharo-dev] FFI without the Pharo sources

So if you implement a cool solution we will integrate it immediately :)

On Wed, Jan 24, 2018 at 6:20 PM, Stephane Ducasse  
wrote:
> Thanks Vincent we are interested to make the independence on source 
> much simpler.
>
> Stef
>
>
> On Wed, Jan 24, 2018 at 5:09 PM, Eliot Miranda  
> wrote:
>> Hi Vincent,
>>
>>> On Jan 23, 2018, at 4:54 PM,  
>>>  wrote:
>>>
>>> Hi,
>>>
>>> I am working to be able to create some standalone apps in Pharo. And for 
>>> this, I would like to remove of the .sources and .changes. But, by removing 
>>> them, the args names are reset to arg1, arg2, arg3, ... and the FFI cannot 
>>> be used anymore.
>>>
>>> Does someone (Esteban?) have a solution that I could implement to fix this 
>>> issue?
>>
>> One avenue that should be easy to implement would be to modify the compiler 
>> to save the temporary names as a property of the method.
>>
>>
>>>
>>> Thanks!
>>>
>>> Vincent
>>
>> _,,,^..^,,,_ (phone)

Re: [Pharo-dev] Help browser in tools menu?

[Stephane Ducasse]

Yes the same.
Now I think that in the future (when we have finished to refactor
pillar) we could import directly some chapters from the book.
This we would reduce the duplication.

Stef

On Tue, Jan 30, 2018 at 2:26 PM, Sven Van Caekenberghe  wrote:
> Not in World Menu > Help > Help Browser ?
>
>> On 30 Jan 2018, at 14:21, Stephane Ducasse  wrote:
>>
>> Hi guys
>>
>> in my 70 image (not recent one) the help browser is not proposed via a
>> menu and I think that it would make sense.
>> What do you think?
>>
>> Stef
>>
>
>

Re: [Pharo-dev] [CI] Retiring Pharo5 CI jobs

[Stephane Ducasse]

tx! Cleaning is as important as the rest.


On Tue, Jan 30, 2018 at 4:38 PM, Marcus Denker  wrote:
> Hello,
>
> To conserve resources, we retire Pharo 5 CI build infrastructure.
>
> This means all jobs in:
>
> https://ci.inria.fr/pharo/view/5.0/
> https://ci.inria.fr/pharo/view/5.0-VM-Spur/
> https://ci.inria.fr/pharo/view/5.0-VM-Legacy/
>
>
> Al the releases themselves of course will be archived forever at
> http://files.pharo.org
>
> Marcus

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

[Santiago Bragagnolo]

Hahahaha, of course is not disturb :)

On Tue, 30 Jan 2018 at 16:16 Stephane Ducasse 
wrote:

> Sure go ahead you are not disturbing anybody.
>
> On Tue, Jan 30, 2018 at 10:12 AM, Rafael Luque
>  wrote:
> > Hi Santiago,
> >
> > Maybe I could try to add the event support if I could manage to find the
> > time and I can disturb you with my noob questions.
> >
> > Rafa.
> >
> > 2018-01-29 18:55 GMT+00:00 Santiago Bragagnolo
> > :
> >>
> >> Hi Rafael!
> >> Events are not yet supported sadly.
> >> If you are willing to do something about, we can discuss. By my side I
> >> will be kind of busy during february.
> >>
> >> I hope to be able to do something about on march, but i cannot guarantee
> >> it
> >>
> >> Santiago
> >>
> >>
> >> On Mon, 29 Jan 2018 at 17:40 Rafael Luque  >
> >> wrote:
> >>>
> >>> Hi Santiago,
> >>>
> >>> I'm currently playing with Dapps on Ethereum using Truffle and web3.js,
> >>> but it would be great to be able to use Pharo.
> >>>
> >>> I've downloaded Fog and started to read the tests and code, but I don't
> >>> see support for events that is something I need for my current use
> cases.
> >>> Maybe I don't know where to look or events are not (yet) supported?
> >>>
> >>> In any case, thank you for this contribution.
> >>>
> >>>
> >>> 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo
> >>> :
> 
>  You are welcome :). We are doing some experiments for looking some
>  research branches on it.
>  So, writing some Dapps but not really productive. or not yet.
>  Any way, we still using solidity as language for the contracts.
> 
>  Santiago
> 
> 
> 
>  On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo <
> emaring...@gmail.com>
>  wrote:
> >
> > Very Nice! Thank you for building it.
> >
> > I started a similar project for the Bitcoin blockchain, but then I
> > drifted away and never got back to it.
> >
> > Are you writing DAPPs?
> >
> > Best regards,
> >
> > Esteban A. Maringolo
> >
> >
> > 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo
> > :
> > > Hi all. Im happy to announce a pre release of the Fog ethereum
> driver
> > > that
> > > we develop in the space of an Inria project.
> > >
> > > It still not complete but is already usable for some experiments
> and
> > > simple
> > > projects.
> > >
> > > You can downloadit from
> > > https://github.com/sbragagnolo/Fog/
> > > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1)
> > >
> > > Dependencies
> > >
> > > RHash
> > >
> > >  sudo apt-get install rhash
> > >
> > > Solidity
> > >
> > >  npm install solc
> > >
> > > Download code
> > >
> > > Iceberg / Baseline
> > >
> > > Metacello
> > > new
> > > baseline: 'Fog';
> > > repository:  'github://sbragagnolo/Fog:v0.1.1.1/src';
> > > load.
> > >
> > > By hand
> > >
> > > You may want to use this version for having access to some scripts
> > > and
> > > contracts samples.
> > >
> > > git checkout g...@github.com:sbragagnolo/Fog.git
> > >
> > > git checkout v0.1.1.1
> > >
> > > Metacello
> > > new
> > > baseline: 'Fog';
> > > repository: 'filetree:///path/to/git-repository/Fog/src';;
> > > load.
> > >
> > >
> > > It's based on the standar API for javascript
> > > (https://github.com/ethereum/wiki/wiki/JavaScript-API) .
> > >
> > > It provides interaction with remote contracts, it do as well
> provides
> > > a way
> > > for navigating the architecture objects: blocks, transactions,
> > > accounts and
> > > contracts.
> > >
> > > I hope you find it useful.
> > >
> > > Feel free to fill the github issue tracker with anything you find
> :).
> > >
> > >
> > > I will come to you with some new exciting news about ethereum soon
> :)
> > >
> > > Santiago.
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >>>
> >
>
>

[Pharo-dev] Techtalk starting: Genetic Algorithms

[Marcus Denker]

TechTalk is starting now. Link is: https://www.youtube.com/watch?v=ZB1U259wPaA

Pharo TechTalk: Genetic Algorithms
https://association.pharo.org/event-2757884

[Pharo-dev] [CI] Retiring Pharo5 CI jobs

[Marcus Denker]

Hello,

To conserve resources, we retire Pharo 5 CI build infrastructure. 

This means all jobs in:

https://ci.inria.fr/pharo/view/5.0/ 

https://ci.inria.fr/pharo/view/5.0-VM-Spur/ 

https://ci.inria.fr/pharo/view/5.0-VM-Legacy/ 



Al the releases themselves of course will be archived forever at 
http://files.pharo.org 

Marcus

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

[Stephane Ducasse]

Sure go ahead you are not disturbing anybody.

On Tue, Jan 30, 2018 at 10:12 AM, Rafael Luque
 wrote:
> Hi Santiago,
>
> Maybe I could try to add the event support if I could manage to find the
> time and I can disturb you with my noob questions.
>
> Rafa.
>
> 2018-01-29 18:55 GMT+00:00 Santiago Bragagnolo
> :
>>
>> Hi Rafael!
>> Events are not yet supported sadly.
>> If you are willing to do something about, we can discuss. By my side I
>> will be kind of busy during february.
>>
>> I hope to be able to do something about on march, but i cannot guarantee
>> it
>>
>> Santiago
>>
>>
>> On Mon, 29 Jan 2018 at 17:40 Rafael Luque 
>> wrote:
>>>
>>> Hi Santiago,
>>>
>>> I'm currently playing with Dapps on Ethereum using Truffle and web3.js,
>>> but it would be great to be able to use Pharo.
>>>
>>> I've downloaded Fog and started to read the tests and code, but I don't
>>> see support for events that is something I need for my current use cases.
>>> Maybe I don't know where to look or events are not (yet) supported?
>>>
>>> In any case, thank you for this contribution.
>>>
>>>
>>> 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo
>>> :

 You are welcome :). We are doing some experiments for looking some
 research branches on it.
 So, writing some Dapps but not really productive. or not yet.
 Any way, we still using solidity as language for the contracts.

 Santiago



 On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo 
 wrote:
>
> Very Nice! Thank you for building it.
>
> I started a similar project for the Bitcoin blockchain, but then I
> drifted away and never got back to it.
>
> Are you writing DAPPs?
>
> Best regards,
>
> Esteban A. Maringolo
>
>
> 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo
> :
> > Hi all. Im happy to announce a pre release of the Fog ethereum driver
> > that
> > we develop in the space of an Inria project.
> >
> > It still not complete but is already usable for some experiments and
> > simple
> > projects.
> >
> > You can downloadit from
> > https://github.com/sbragagnolo/Fog/
> > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1)
> >
> > Dependencies
> >
> > RHash
> >
> >  sudo apt-get install rhash
> >
> > Solidity
> >
> >  npm install solc
> >
> > Download code
> >
> > Iceberg / Baseline
> >
> > Metacello
> > new
> > baseline: 'Fog';
> > repository:  'github://sbragagnolo/Fog:v0.1.1.1/src';
> > load.
> >
> > By hand
> >
> > You may want to use this version for having access to some scripts
> > and
> > contracts samples.
> >
> > git checkout g...@github.com:sbragagnolo/Fog.git
> >
> > git checkout v0.1.1.1
> >
> > Metacello
> > new
> > baseline: 'Fog';
> > repository: 'filetree:///path/to/git-repository/Fog/src';;
> > load.
> >
> >
> > It's based on the standar API for javascript
> > (https://github.com/ethereum/wiki/wiki/JavaScript-API) .
> >
> > It provides interaction with remote contracts, it do as well provides
> > a way
> > for navigating the architecture objects: blocks, transactions,
> > accounts and
> > contracts.
> >
> > I hope you find it useful.
> >
> > Feel free to fill the github issue tracker with anything you find :).
> >
> >
> > I will come to you with some new exciting news about ethereum soon :)
> >
> > Santiago.
> >
> >
> >
> >
> >
> >
>
>>>
>

[Pharo-dev] [Pharo 7.0-dev] Build #480: 21179-sendersOfCritic-should-not-use-AbstractTool

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #480 was: SUCCESS.

The Pull Request #774 was integrated: 
"21179-sendersOfCritic-should-not-use-AbstractTool"
Pull request url: https://github.com/pharo-project/pharo/pull/774

Issue Url: https://pharo.fogbugz.com/f/cases/21179
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/480/

[Pharo-dev] [Pharo 7.0-dev] Build #479: 21171-allMethodsWithSourceStringmatchCase-should-not-sort-

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #479 was: SUCCESS.

The Pull Request #775 was integrated: 
"21171-allMethodsWithSourceStringmatchCase-should-not-sort-"
Pull request url: https://github.com/pharo-project/pharo/pull/775

Issue Url: https://pharo.fogbugz.com/f/cases/21171
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/479/

Re: [Pharo-dev] Help browser in tools menu?

[Sven Van Caekenberghe]

Not in World Menu > Help > Help Browser ?

> On 30 Jan 2018, at 14:21, Stephane Ducasse  wrote:
> 
> Hi guys
> 
> in my 70 image (not recent one) the help browser is not proposed via a
> menu and I think that it would make sense.
> What do you think?
> 
> Stef
> 

[Pharo-dev] Help browser in tools menu?

[Stephane Ducasse]

Hi guys

in my 70 image (not recent one) the help browser is not proposed via a
menu and I think that it would make sense.
What do you think?

Stef

[Pharo-dev] [Pharo 7.0-dev] Build #478: 21164-EncoderForSistaV1-update

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #478 was: SUCCESS.

The Pull Request #741 was integrated: "21164-EncoderForSistaV1-update"
Pull request url: https://github.com/pharo-project/pharo/pull/741

Issue Url: https://pharo.fogbugz.com/f/cases/21164
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/478/

Re: [Pharo-dev] [Issue Tracker] Problem with Spam

[Marcus Denker]

With the help of the Fogbugz support I have disabled the anon submission page 
for now.

> On 26 Jan 2018, at 10:18, Marcus Denker  wrote:
> 
> I have not yet found a way to do it.
> 
> https://forum.manuscript.com/t/dozens-of-spam-emails-a-day-how-do-i-turn-off-public-email-address/
>  
> 
> 
> 
>> On 26 Jan 2018, at 10:13, Sven Van Caekenberghe > > wrote:
>> 
>> I guess these are anonymous submissions ?
>> Can't this (for now at least) not be restricted to actual users that need to 
>> authenticate first ?
>> 
>>> On 26 Jan 2018, at 10:09, Marcus Denker >> > wrote:
>>> 
>>> Hi,
>>> 
>>> Since some days we get ~20 spam cases per day on the issue tracker.
>>> 
>>> -> I have asked on the Forums what we can do
>>> -> As long as there is no solution, I am closing them the morning.
>>> 
>>> Marcus
>>> 
>> 
>> 
> 

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

[Rafael Luque]

Hi Santiago,

Maybe I could try to add the event support if I could manage to find the
time and I can disturb you with my noob questions.

Rafa.

2018-01-29 18:55 GMT+00:00 Santiago Bragagnolo :

> Hi Rafael!
> Events are not yet supported sadly.
> If you are willing to do something about, we can discuss. By my side I
> will be kind of busy during february.
>
> I hope to be able to do something about on march, but i cannot guarantee
> it
>
> Santiago
>
>
> On Mon, 29 Jan 2018 at 17:40 Rafael Luque 
> wrote:
>
>> Hi Santiago,
>>
>> I'm currently playing with Dapps on Ethereum using Truffle and web3.js,
>> but it would be great to be able to use Pharo.
>>
>> I've downloaded Fog and started to read the tests and code, but I don't
>> see support for events that is something I need for my current use cases.
>> Maybe I don't know where to look or events are not (yet) supported?
>>
>> In any case, thank you for this contribution.
>>
>>
>> 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo <
>> santiagobragagn...@gmail.com>:
>>
>>> You are welcome :). We are doing some experiments for looking some
>>> research branches on it.
>>> So, writing some Dapps but not really productive. or not yet.
>>> Any way, we still using solidity as language for the contracts.
>>>
>>> Santiago
>>>
>>>
>>>
>>> On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo 
>>> wrote:
>>>
 Very Nice! Thank you for building it.

 I started a similar project for the Bitcoin blockchain, but then I
 drifted away and never got back to it.

 Are you writing DAPPs?

 Best regards,

 Esteban A. Maringolo


 2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo <
 santiagobragagn...@gmail.com>:
 > Hi all. Im happy to announce a pre release of the Fog ethereum driver
 that
 > we develop in the space of an Inria project.
 >
 > It still not complete but is already usable for some experiments and
 simple
 > projects.
 >
 > You can downloadit from
 > https://github.com/sbragagnolo/Fog/
 > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1)
 >
 > Dependencies
 >
 > RHash
 >
 >  sudo apt-get install rhash
 >
 > Solidity
 >
 >  npm install solc
 >
 > Download code
 >
 > Iceberg / Baseline
 >
 > Metacello
 > new
 > baseline: 'Fog';
 > repository:  'github://sbragagnolo/Fog:v0.1.1.1/src';
 > load.
 >
 > By hand
 >
 > You may want to use this version for having access to some scripts and
 > contracts samples.
 >
 > git checkout g...@github.com:sbragagnolo/Fog.git
 >
 > git checkout v0.1.1.1
 >
 > Metacello
 > new
 > baseline: 'Fog';
 > repository: 'filetree:///path/to/git-repository/Fog/src';;
 > load.
 >
 >
 > It's based on the standar API for javascript
 > (https://github.com/ethereum/wiki/wiki/JavaScript-API) .
 >
 > It provides interaction with remote contracts, it do as well provides
 a way
 > for navigating the architecture objects: blocks, transactions,
 accounts and
 > contracts.
 >
 > I hope you find it useful.
 >
 > Feel free to fill the github issue tracker with anything you find :).
 >
 >
 > I will come to you with some new exciting news about ethereum soon :)
 >
 > Santiago.
 >
 >
 >
 >
 >
 >


>>

Re: [Pharo-dev] [ANN] Fog - Ethereum driver

[Rafael Luque]

Hi Ben,

I did these courses and they were very useful for me:
https://www.zastrin.com/

Also the book "Blockchain Applications: A Hands-On Approach":
https://www.amazon.com/Blockchain-Applications-Hands-Arshdeep-Bahga/dp/0996025553

Btw, Manning has the following MEAP:
https://www.manning.com/books/building-ethereum-dapps

Rafa.

2018-01-29 22:28 GMT+00:00 Ben Coman :

> btw, I started doing this course...
> https://www.udemy.com/ethereum-dapp/
> and hopefully this knowledge can transfer over to Pharo.
>
> Can anyone recommend other learning resources?
>
> cheers -ben
>
> On 30 January 2018 at 02:55, Santiago Bragagnolo
>  wrote:
> > Hi Rafael!
> > Events are not yet supported sadly.
> > If you are willing to do something about, we can discuss. By my side I
> will
> > be kind of busy during february.
> >
> > I hope to be able to do something about on march, but i cannot guarantee
> it
> >
> > Santiago
> >
> >
> > On Mon, 29 Jan 2018 at 17:40 Rafael Luque 
> > wrote:
> >>
> >> Hi Santiago,
> >>
> >> I'm currently playing with Dapps on Ethereum using Truffle and web3.js,
> >> but it would be great to be able to use Pharo.
> >>
> >> I've downloaded Fog and started to read the tests and code, but I don't
> >> see support for events that is something I need for my current use
> cases.
> >> Maybe I don't know where to look or events are not (yet) supported?
> >>
> >> In any case, thank you for this contribution.
> >>
> >>
> >> 2017-03-14 9:51 GMT+00:00 Santiago Bragagnolo
> >> :
> >>>
> >>> You are welcome :). We are doing some experiments for looking some
> >>> research branches on it.
> >>> So, writing some Dapps but not really productive. or not yet.
> >>> Any way, we still using solidity as language for the contracts.
> >>>
> >>> Santiago
> >>>
> >>>
> >>>
> >>> On Mon, 13 Mar 2017 at 19:44 Esteban A. Maringolo <
> emaring...@gmail.com>
> >>> wrote:
> 
>  Very Nice! Thank you for building it.
> 
>  I started a similar project for the Bitcoin blockchain, but then I
>  drifted away and never got back to it.
> 
>  Are you writing DAPPs?
> 
>  Best regards,
> 
>  Esteban A. Maringolo
> 
> 
>  2017-03-13 12:00 GMT-03:00 Santiago Bragagnolo
>  :
>  > Hi all. Im happy to announce a pre release of the Fog ethereum
> driver
>  > that
>  > we develop in the space of an Inria project.
>  >
>  > It still not complete but is already usable for some experiments and
>  > simple
>  > projects.
>  >
>  > You can downloadit from
>  > https://github.com/sbragagnolo/Fog/
>  > (https://github.com/sbragagnolo/Fog/releases/tag/v0.1.1.1)
>  >
>  > Dependencies
>  >
>  > RHash
>  >
>  >  sudo apt-get install rhash
>  >
>  > Solidity
>  >
>  >  npm install solc
>  >
>  > Download code
>  >
>  > Iceberg / Baseline
>  >
>  > Metacello
>  > new
>  > baseline: 'Fog';
>  > repository:  'github://sbragagnolo/Fog:v0.1.1.1/src';
>  > load.
>  >
>  > By hand
>  >
>  > You may want to use this version for having access to some scripts
> and
>  > contracts samples.
>  >
>  > git checkout g...@github.com:sbragagnolo/Fog.git
>  >
>  > git checkout v0.1.1.1
>  >
>  > Metacello
>  > new
>  > baseline: 'Fog';
>  > repository: 'filetree:///path/to/git-repository/Fog/src';;
>  > load.
>  >
>  >
>  > It's based on the standar API for javascript
>  > (https://github.com/ethereum/wiki/wiki/JavaScript-API) .
>  >
>  > It provides interaction with remote contracts, it do as well
> provides
>  > a way
>  > for navigating the architecture objects: blocks, transactions,
>  > accounts and
>  > contracts.
>  >
>  > I hope you find it useful.
>  >
>  > Feel free to fill the github issue tracker with anything you find
> :).
>  >
>  >
>  > I will come to you with some new exciting news about ethereum soon
> :)
>  >
>  > Santiago.
>  >
>  >
>  >
>  >
>  >
>  >
> 
> >>
> >
>
>