- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Trying to load a stateful trait in a stateless version. in bootstrap when loading newSpec?

by ducasse

Well it is not me but the spec 2.0.0 PR. Stef > On 27 Feb 2019, at 17:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Is pretty clear :) > You are trying to load a stateful Trait in a version of Pharo that does not supports it (I guess Pharo 6.1?) > > Esteban > > >> On 27 Feb 2019, at 17:05, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: >> >> >> 'VersionInfo: Pharo7.0-PR-g3b248856a5586a2a13853d32e10596969926e951' >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] 'Errors in script loaded from /builds/workspace/uest_and_branch_Pipeline_PR-2735/32/bootstrap/scripts/bootstrap.st <http://bootstrap.st/>' >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Error: Trying to load a stateful trait in a stateless version. >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser(Object)>>error: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ self >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] error: 'Trying to load a stateful trait in a stateless version.' ] in TonelParser>>validateStatelessTraitIsBeingRead: in Block: [ self... >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] BlockClosure>>cull: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Set(Collection)>>ifNotEmpty: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>validateStatelessTraitIsBeingRead: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>newStatelessTraitDefinitionFrom: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>newTraitDefinitionFrom: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>newTypeDefinitionFrom: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>typeDef >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>document >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>start >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser class>>parseStream: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :s | TonelParser parseStream: s ] in [ :each | each readStreamDo: [ :s | TonelParser parseStream: s ] ] in TonelReader>>loadDefinitions in Block: [ :s | TonelParser parseStream: s ] >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ aBlock value: stream ] in FileReference(AbstractFileReference)>>readStreamDo: in Block: [ aBlock value: stream ] >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] BlockClosure>>ensure: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] FileReference(AbstractFileReference)>>readStreamDo: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] FileSystemDirectoryEntry>>readStreamDo: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :each | each readStreamDo: [ :s | TonelParser parseStream: s ] ] in TonelReader>>loadDefinitions in Block: [ :each | each readStreamDo: [ :s | TonelParser pa...etc... >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Array(SequenceableCollection)>>collect: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelReader>>loadDefinitions >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelReader(MCVersionReader)>>definitions >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelReader(MCVersionReader)>>snapshot >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ self snapshot ] in TonelReader(MCVersionReader)>>basicVersion in Block: [ self snapshot ] >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCVersion>>snapshot >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCMczWriter>>writeDefinitions: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCMczWriter>>writeVersion: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCMczWriter class>>fileOut:on: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCVersion>>fileOutOn: >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :s | aVersion fileOutOn: s ] in MCCacheRepository(MCFileBasedRepository)>>basicStoreVersion: in Block: [ :s | aVersion fileOutOn: s ] >> >> >> <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :stream | aBlock value: stream ] in MCCacheRepository(MCDirectoryRepository)>>writeStreamForFileNamed:replace:do: in Block: [ :stream | aBlock value: stream ] >> >> >

Feb. 27, 2019

Re: [Pharo-dev] Trying to load a stateful trait in a stateless version. in bootstrap when loading newSpec?

by Esteban Lorenzano

Is pretty clear :) You are trying to load a stateful Trait in a version of Pharo that does not supports it (I guess Pharo 6.1?) Esteban > On 27 Feb 2019, at 17:05, ducasse <stepharo(a)netcourrier.com> wrote: > > > 'VersionInfo: Pharo7.0-PR-g3b248856a5586a2a13853d32e10596969926e951' > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] 'Errors in script loaded from /builds/workspace/uest_and_branch_Pipeline_PR-2735/32/bootstrap/scripts/bootstrap.st <http://bootstrap.st/>' > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Error: Trying to load a stateful trait in a stateless version. > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser(Object)>>error: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ self > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] error: 'Trying to load a stateful trait in a stateless version.' ] in TonelParser>>validateStatelessTraitIsBeingRead: in Block: [ self... > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] BlockClosure>>cull: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Set(Collection)>>ifNotEmpty: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>validateStatelessTraitIsBeingRead: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>newStatelessTraitDefinitionFrom: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>newTraitDefinitionFrom: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>newTypeDefinitionFrom: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>typeDef > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>document > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser>>start > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelParser class>>parseStream: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :s | TonelParser parseStream: s ] in [ :each | each readStreamDo: [ :s | TonelParser parseStream: s ] ] in TonelReader>>loadDefinitions in Block: [ :s | TonelParser parseStream: s ] > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ aBlock value: stream ] in FileReference(AbstractFileReference)>>readStreamDo: in Block: [ aBlock value: stream ] > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] BlockClosure>>ensure: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] FileReference(AbstractFileReference)>>readStreamDo: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] FileSystemDirectoryEntry>>readStreamDo: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :each | each readStreamDo: [ :s | TonelParser parseStream: s ] ] in TonelReader>>loadDefinitions in Block: [ :each | each readStreamDo: [ :s | TonelParser pa...etc... > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Array(SequenceableCollection)>>collect: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelReader>>loadDefinitions > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelReader(MCVersionReader)>>definitions > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] TonelReader(MCVersionReader)>>snapshot > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ self snapshot ] in TonelReader(MCVersionReader)>>basicVersion in Block: [ self snapshot ] > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCVersion>>snapshot > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCMczWriter>>writeDefinitions: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCMczWriter>>writeVersion: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCMczWriter class>>fileOut:on: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCVersion>>fileOutOn: > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :s | aVersion fileOutOn: s ] in MCCacheRepository(MCFileBasedRepository)>>basicStoreVersion: in Block: [ :s | aVersion fileOutOn: s ] > > > <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] [ :stream | aBlock value: stream ] in MCCacheRepository(MCDirectoryRepository)>>writeStreamForFileNamed:replace:do: in Block: [ :stream | aBlock value: stream ] > >

Feb. 27, 2019

Trying to load a stateful trait in a stateless version. in bootstrap when loading newSpec?

by ducasse

Feb. 27, 2019

Re: [Pharo-dev] AWS SDK for Pharo

by Paul DeBruicker

Richard Prinz made one for Google's APIs The code is here: https://github.com/seandenigris/St-Google-API (also Sean - maybe merge them PRs! :) ) The blog post describing what he did is here: https://www.min.at/prinz/?x=entry:entry150318-104537 Maybe Amazon publishes a similar resource you can use. Stefan Krecher-3 wrote > Hi, > I'm aware that there is already an AWS SDK implementation for Smalltalk ( > https://github.com/newapplesho/aws-sdk-smalltalk ) > This implementation doesn't seem to be a complete implementation to access > all AWS services. > Using a live-programming environment like Pharo would be so cool, > flexible, > productive and intuitive to control/ manage AWS resources - but > implementing the SDK by hand is probably not a good idea, since it would > be > so hard to keep it up-to-date, because AWS adds new features weekly ... > I contacted the AWS enterprise support and they gave me some great hints. > There are many 3rd party SDK's available that utilizes the json files > provided in botocore to automatically generate SDKs: Botocore: > https://github.com/boto/botocore > <https://github.com/boto/botocore>Example service.json: > <https://github.com/boto/botocore> > https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/… > They can then automatically generate an SDK based off of these json > definitions. One example of this is Rusoto, the AWS SDK for Rust: > Rusoto: https://github.com/rusoto/rusoto Automatic generation portion: > https://github.com/rusoto/rusoto/tree/master/service_crategen > > Would anyone interested in supporting this kind of project? > What would be a good starting-point? > Although I am (to be honest: I was) a Smalltalk-Programmer, I have too > little experience with Pharo - but maybe others might find this useful. It > would also be useful to "spread the word" - AWS scripting/ automation is > so > popular, there would be so many occasions to showcase Pharo + AWS or to > create Products that are based on AWS services. > > Regards > Stefan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 27, 2019

Re: [Pharo-dev] AWS SDK for Pharo

by Jan van de Sandt

Hi, Here is yet another (very) partial implementation of an AWS SDK for Pharo: https://github.com/jvdsandt/pharo-aws-toolbox But it does have the latest (V4) signing algoritm! It would be very nice if you can generate a Pharo implemetation of an AWS service from a meta description! Jan. On Wed, Feb 27, 2019 at 2:02 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > This is interesting indeed. > The meta descriptions in JSON are cool and most probably usable. > It would be a huge project, though, given how many APIs/products there > are, even with auto generation. > > A long time ago I did a AWS S3 client that is still part of Zinc HTTP > Components (https://github.com/svenvc/zinc) although I believe the > authentication/signing model is old now. > > Sven > > > On 27 Feb 2019, at 12:37, Stefan Krecher <stefan.krecher(a)gmail.com> > wrote: > > > > Hi, > > I'm aware that there is already an AWS SDK implementation for Smalltalk > ( https://github.com/newapplesho/aws-sdk-smalltalk ) > > This implementation doesn't seem to be a complete implementation to > access all AWS services. > > Using a live-programming environment like Pharo would be so cool, > flexible, productive and intuitive to control/ manage AWS resources - but > implementing the SDK by hand is probably not a good idea, since it would be > so hard to keep it up-to-date, because AWS adds new features weekly ... > > I contacted the AWS enterprise support and they gave me some great hints. > > There are many 3rd party SDK's available that utilizes the json files > provided in botocore to automatically generate SDKs: > > Botocore: > > https://github.com/boto/botocore > > Example service.json: > https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/… > > They can then automatically generate an SDK based off of these json > definitions. One example of this is Rusoto, the AWS SDK for Rust: > > Rusoto: https://github.com/rusoto/rusoto > > > > Automatic generation portion: > > https://github.com/rusoto/rusoto/tree/master/service_crategen > > > > Would anyone interested in supporting this kind of project? > > What would be a good starting-point? > > Although I am (to be honest: I was) a Smalltalk-Programmer, I have too > little experience with Pharo - but maybe others might find this useful. It > would also be useful to "spread the word" - AWS scripting/ automation is so > popular, there would be so many occasions to showcase Pharo + AWS or to > create Products that are based on AWS services. > > > > Regards > > Stefan > > >

Feb. 27, 2019

Re: [Pharo-dev] AWS SDK for Pharo

by ducasse

Take one feature and see how difficult it is to build it. Stef > On 27 Feb 2019, at 15:34, Stefan Krecher <stefan.krecher(a)gmail.com> wrote: > > How would a controlled experiment look like? > > Am Mi., 27. Feb. 2019 um 13:18 Uhr schrieb ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>>: > It would be cool to have some bindings. > > I remember that > https://www.min.at/prinz/?x=entry:entry150318-104537 <https://www.min.at/prinz/?x=entry:entry150318-104537> > It would be nice to make it work in Pharo 70. > > Now are you sure that this is complex to take json description and generate SDKs > Did you run a controlled experiment? > > > Stef > >> On 27 Feb 2019, at 12:37, Stefan Krecher <stefan.krecher(a)gmail.com <mailto:stefan.krecher@gmail.com>> wrote: >> >> Hi, >> I'm aware that there is already an AWS SDK implementation for Smalltalk ( https://github.com/newapplesho/aws-sdk-smalltalk <https://github.com/newapplesho/aws-sdk-smalltalk> ) >> This implementation doesn't seem to be a complete implementation to access all AWS services. >> Using a live-programming environment like Pharo would be so cool, flexible, productive and intuitive to control/ manage AWS resources - but implementing the SDK by hand is probably not a good idea, since it would be so hard to keep it up-to-date, because AWS adds new features weekly ... >> I contacted the AWS enterprise support and they gave me some great hints. >> There are many 3rd party SDK's available that utilizes the json files provided in botocore to automatically generate SDKs: >> Botocore: https://github.com/boto/botocore <https://github.com/boto/botocore> >> <https://github.com/boto/botocore>Example service.json: <https://github.com/boto/botocore>https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/… <https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/…> >> They can then automatically generate an SDK based off of these json definitions. One example of this is Rusoto, the AWS SDK for Rust: >> Rusoto: https://github.com/rusoto/rusoto <https://github.com/rusoto/rusoto> >> Automatic generation portion: https://github.com/rusoto/rusoto/tree/master/service_crategen <https://github.com/rusoto/rusoto/tree/master/service_crategen> >> >> Would anyone interested in supporting this kind of project? >> What would be a good starting-point? >> Although I am (to be honest: I was) a Smalltalk-Programmer, I have too little experience with Pharo - but maybe others might find this useful. It would also be useful to "spread the word" - AWS scripting/ automation is so popular, there would be so many occasions to showcase Pharo + AWS or to create Products that are based on AWS services. >> >> Regards >> Stefan > > > > -- > Dipl.-Wirtsch.-Inf. Stefan Krecher > Neulander Str. 17, 27374 VisselhÃ¶vede > Tel +49(0)4262 958848 > mobil +49(0)172 4396852

Feb. 27, 2019

Re: [Pharo-dev] AWS SDK for Pharo

by Stefan Krecher

How would a controlled experiment look like? Am Mi., 27. Feb. 2019 um 13:18 Uhr schrieb ducasse <stepharo(a)netcourrier.com >: > It would be cool to have some bindings. > > I remember that > https://www.min.at/prinz/?x=entry:entry150318-104537 > It would be nice to make it work in Pharo 70. > > Now are you sure that this is complex to take json description and > generate SDKs > Did you run a controlled experiment? > > > Stef > > On 27 Feb 2019, at 12:37, Stefan Krecher <stefan.krecher(a)gmail.com> wrote: > > Hi, > I'm aware that there is already an AWS SDK implementation for Smalltalk ( > https://github.com/newapplesho/aws-sdk-smalltalk ) > This implementation doesn't seem to be a complete implementation to access > all AWS services. > Using a live-programming environment like Pharo would be so cool, > flexible, productive and intuitive to control/ manage AWS resources - but > implementing the SDK by hand is probably not a good idea, since it would be > so hard to keep it up-to-date, because AWS adds new features weekly ... > I contacted the AWS enterprise support and they gave me some great hints. > There are many 3rd party SDK's available that utilizes the json files > provided in botocore to automatically generate SDKs: Botocore: > https://github.com/boto/botocore > <https://github.com/boto/botocore>Example service.json: > <https://github.com/boto/botocore> > https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/… > They can then automatically generate an SDK based off of these json > definitions. One example of this is Rusoto, the AWS SDK for Rust: > Rusoto: https://github.com/rusoto/rusoto Automatic generation portion: > https://github.com/rusoto/rusoto/tree/master/service_crategen > > Would anyone interested in supporting this kind of project? > What would be a good starting-point? > Although I am (to be honest: I was) a Smalltalk-Programmer, I have too > little experience with Pharo - but maybe others might find this useful. It > would also be useful to "spread the word" - AWS scripting/ automation is so > popular, there would be so many occasions to showcase Pharo + AWS or to > create Products that are based on AWS services. > > Regards > Stefan > > > -- Dipl.-Wirtsch.-Inf. Stefan Krecher Neulander Str. 17, 27374 VisselhÃ¶vede Tel +49(0)4262 958848 mobil +49(0)172 4396852

Feb. 27, 2019

Re: [Pharo-dev] AWS SDK for Pharo

by Sven Van Caekenberghe

Hi, This is interesting indeed. The meta descriptions in JSON are cool and most probably usable. It would be a huge project, though, given how many APIs/products there are, even with auto generation. A long time ago I did a AWS S3 client that is still part of Zinc HTTP Components (https://github.com/svenvc/zinc) although I believe the authentication/signing model is old now. Sven > On 27 Feb 2019, at 12:37, Stefan Krecher <stefan.krecher(a)gmail.com> wrote: > > Hi, > I'm aware that there is already an AWS SDK implementation for Smalltalk ( https://github.com/newapplesho/aws-sdk-smalltalk ) > This implementation doesn't seem to be a complete implementation to access all AWS services. > Using a live-programming environment like Pharo would be so cool, flexible, productive and intuitive to control/ manage AWS resources - but implementing the SDK by hand is probably not a good idea, since it would be so hard to keep it up-to-date, because AWS adds new features weekly ... > I contacted the AWS enterprise support and they gave me some great hints. > There are many 3rd party SDK's available that utilizes the json files provided in botocore to automatically generate SDKs: > Botocore: > https://github.com/boto/botocore > Example service.json:https://github.com/boto/botocore/blob/develop/botocore/data/ec… > They can then automatically generate an SDK based off of these json definitions. One example of this is Rusoto, the AWS SDK for Rust: > Rusoto: https://github.com/rusoto/rusoto > > Automatic generation portion: > https://github.com/rusoto/rusoto/tree/master/service_crategen > > Would anyone interested in supporting this kind of project? > What would be a good starting-point? > Although I am (to be honest: I was) a Smalltalk-Programmer, I have too little experience with Pharo - but maybe others might find this useful. It would also be useful to "spread the word" - AWS scripting/ automation is so popular, there would be so many occasions to showcase Pharo + AWS or to create Products that are based on AWS services. > > Regards > Stefan

Feb. 27, 2019

Re: [Pharo-dev] AWS SDK for Pharo

by ducasse

It would be cool to have some bindings. I remember that https://www.min.at/prinz/?x=entry:entry150318-104537 <https://www.min.at/prinz/?x=entry:entry150318-104537> It would be nice to make it work in Pharo 70. Now are you sure that this is complex to take json description and generate SDKs Did you run a controlled experiment? Stef > On 27 Feb 2019, at 12:37, Stefan Krecher <stefan.krecher(a)gmail.com> wrote: > > Hi, > I'm aware that there is already an AWS SDK implementation for Smalltalk ( https://github.com/newapplesho/aws-sdk-smalltalk <https://github.com/newapplesho/aws-sdk-smalltalk> ) > This implementation doesn't seem to be a complete implementation to access all AWS services. > Using a live-programming environment like Pharo would be so cool, flexible, productive and intuitive to control/ manage AWS resources - but implementing the SDK by hand is probably not a good idea, since it would be so hard to keep it up-to-date, because AWS adds new features weekly ... > I contacted the AWS enterprise support and they gave me some great hints. > There are many 3rd party SDK's available that utilizes the json files provided in botocore to automatically generate SDKs: > Botocore: https://github.com/boto/botocore <https://github.com/boto/botocore> > <https://github.com/boto/botocore>Example service.json: <https://github.com/boto/botocore>https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/… <https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/…> > They can then automatically generate an SDK based off of these json definitions. One example of this is Rusoto, the AWS SDK for Rust: > Rusoto: https://github.com/rusoto/rusoto <https://github.com/rusoto/rusoto> > Automatic generation portion: https://github.com/rusoto/rusoto/tree/master/service_crategen <https://github.com/rusoto/rusoto/tree/master/service_crategen> > > Would anyone interested in supporting this kind of project? > What would be a good starting-point? > Although I am (to be honest: I was) a Smalltalk-Programmer, I have too little experience with Pharo - but maybe others might find this useful. It would also be useful to "spread the word" - AWS scripting/ automation is so popular, there would be so many occasions to showcase Pharo + AWS or to create Products that are based on AWS services. > > Regards > Stefan

Feb. 27, 2019

AWS SDK for Pharo

by Stefan Krecher

Hi, I'm aware that there is already an AWS SDK implementation for Smalltalk ( https://github.com/newapplesho/aws-sdk-smalltalk ) This implementation doesn't seem to be a complete implementation to access all AWS services. Using a live-programming environment like Pharo would be so cool, flexible, productive and intuitive to control/ manage AWS resources - but implementing the SDK by hand is probably not a good idea, since it would be so hard to keep it up-to-date, because AWS adds new features weekly ... I contacted the AWS enterprise support and they gave me some great hints. There are many 3rd party SDK's available that utilizes the json files provided in botocore to automatically generate SDKs: Botocore: https://github.com/boto/botocore <https://github.com/boto/botocore>Example service.json: <https://github.com/boto/botocore> https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/… They can then automatically generate an SDK based off of these json definitions. One example of this is Rusoto, the AWS SDK for Rust: Rusoto: https://github.com/rusoto/rusoto Automatic generation portion: https://github.com/rusoto/rusoto/tree/master/service_crategen Would anyone interested in supporting this kind of project? What would be a good starting-point? Although I am (to be honest: I was) a Smalltalk-Programmer, I have too little experience with Pharo - but maybe others might find this useful. It would also be useful to "spread the word" - AWS scripting/ automation is so popular, there would be so many occasions to showcase Pharo + AWS or to create Products that are based on AWS services. Regards Stefan

Feb. 27, 2019