December 2015 - Pharo-users

Re: [Pharo-users] Mongo configuration for Pharo40

by Sven Van Caekenberghe

Then why not introduce a MongoTimestamp and be done with it ? > On 04 Dec 2015, at 17:41, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > >> On 04 Dec 2015, at 5:22 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> According to http://bsonspec.org/spec.html there are indeed 2 different types >> >> "\x09" e_name int64 UTC datetime >> >> "\x11" e_name int64 Timestamp >> >> I would guess that you need 2 different (sub)classes in Pharo if you want to honour this spec. It has little to do with the almost empty TimeStamp subclass of DateAndTime having been removed. This is an API design issue (decide on the Pharo to BSON type mapping). > > Strictly speaking, Timestamp should've never been mapped; > "Timestamp - Special internal type used by MongoDB replication and sharding. First 4 bytes are an increment, second 4 are a timestamp" > doesn't exactly agree with the smalltalk implementation: > nextTimestampPut: aTimestamp > self nextDateAndTimePut: aTimestamp > > It's a problem when an existing application stored Timestamp instances with the broken type, for the reason I explained. > I'd be fine with having a legacy-compatibility package containing Timestamp class + bson extensions as before (even though it was broken) strictly for use when migrating legacy applications. > > That's what we have Monticello groups for, right? ;) > > Cheers, > Henry

Dec. 4, 2015

Re: [Pharo-users] Datatables

by Gabriel NicolÃ¡s Gonzalez

Hi, I think you can find what you are looking for at http://www.seaside.st/documentation/persistence. Regards, S.T. Gabriel NicolÃ¡s GonzÃ¡lez 2015-12-04 11:58 GMT-03:00 Pablo R. Digonzelli <pdigonzelli(a)gmail.com>: > Hi, I am interesting in using Datatables in a Seaside app. > I know there is wrapper fot this in StHub. Is there is examples how to use > it? > > > TIA > > ------------------------------ > *Ing. Pablo Digonzelli* > Software Solutions > IP-Solutiones SRL > Metrotec SRL > 25 de Mayo 521 > San Miguel de TucumÃ¡n > Email: pdigonzelli(a)softsargentina.com > pdigonzelli(a)gmail.com > Cel: 5493815982714 >

Dec. 4, 2015

Re: [Pharo-users] evolutions of squeakelib & crypto (Reed Solomon)

by Robert Withers

I've created a new SqueakSource project for this: http://www.squeaksource.com/maelstrom.html. All future improvements will go to this repository. Here's where wiki documentation can go: https://github.com/SqueakCryptographySquad/maelstrom/wiki Thank you for prompting this name change. Robert On 12/04/2015 10:57 AM, Robert Withers wrote: > Now I think you are right on with your observation. Additionally, the > number of dialects could increase further with Fuel serialization, > just port SecureSession and bits. > > Alright, I came up with a name and it may border on the egregious ... > presenting ... > > "Maelstrom" > > A new distributed metric will be established in Maelstrom to measure > intra- & inter-vat activity: "Sanguinity". > > Robert > > PS. thanks for pointing out Fuel support for older squeaks. > > On 12/04/2015 10:25 AM, Sven Van Caekenberghe wrote: >> Another suggestion: if you intend to make something cross dialect and >> hope to get traction, I would not use a project name which contains >> one dialect, but something more general like Cryptography, or some >> cool project name, like Seaside, Fuel, ... >> >>> On 04 Dec 2015, at 15:43, Robert Withers >>> <robert.w.withers(a)gmail.com> wrote: >>> >>> I use squeak 5.0 and would want the Fuel support to customize for >>> wire serializations and substitutions, such that Squeak and Pharo >>> could talk to each other, and all other Fuel environments. The Fuel >>> changes I made are in the Pharo port of SqueakElib in the >>> SqueakElib-CapTP-Serialization category and consist of a Decoder, >>> Materializer and a Materialization. >>> >>> Robert >>> >>> On 12/04/2015 09:35 AM, Esteban Lorenzano wrote: >>>> which squeak version? >>>> of what? >>>> >>>>> On 04 Dec 2015, at 12:15, Robert Withers >>>>> <robert.w.withers(a)gmail.com> wrote: >>>>> >>>>> I just realized that the squeak version uses ReferenceStream while >>>>> the Pharo version uses Fuel, so the binary serializations are >>>>> different and they won't speak to each other. Any chance that Fuel >>>>> is ported to Squeak? >>>>> >>>>> Regards, >>>>> Robert >>>>> >>>>> On 12/04/2015 06:11 AM, Robert Withers wrote: >>>>>> I am unable to import these files into SqueakSource, so it may be >>>>>> best done from inside Pharo with Monticello. Here are working >>>>>> Crypto and SqueakElib in Pharo, prior to SecureSession >>>>>> refactoring and Reed Solomon. I include the correct version of >>>>>> LayeredProtocol. >>>>>> >>>>>> Regards, >>>>>> Robert >>>>>> >>>>>> >>>>>> On 12/04/2015 05:47 AM, Robert Withers wrote: >>>>>>> Best Regards >>>>>>> >>>>>>> http://www.squeaksource.com/Cryptography.html >>>>>>> http://www.squeaksource.com/squeakelib.html >>>>>>> >>>>>>> >>>>>>> On 12/04/2015 05:44 AM, Robert Withers wrote: >>>>>>>> After my password reset on squeaksource, I committed to both >>>>>>>> Cryptography and SqueakElib, project links below. >>>>>>>> >>>>>>>> In the case of Cryptography, I had a version ported to Pharo >>>>>>>> ... I will organize Pharo ports of both after Reed Solomon is >>>>>>>> stable, and announce them to the Pharo list. This way both >>>>>>>> environments can be supported through this one repository. >>>>>>>> >>>>>>>> Robert >>>>>>>> >>>>>>>> On 12/04/2015 04:35 AM, Stephan Eggermont wrote: >>>>>>>>> On 03-12-15 23:06, Robert Withers wrote: >>>>>>>>>> Are any of these used by both squeak and Pharo? That would be >>>>>>>>>> the right >>>>>>>>>> move I think. I will ask about getting my password reset for >>>>>>>>>> squeaksource, since that is where the old code resides. >>>>>>>>> All of them. Mostly timing of project start/high activity and >>>>>>>>> who are >>>>>>>>> maintaining it decided on platforms. There was a time when >>>>>>>>> squeaksource was not so stable and then many projects >>>>>>>>> migrated, and I currently hear least about stability issues >>>>>>>>> from ss3, but the load on smalltalkhub is much higher, I >>>>>>>>> assume, as that is used for the pharo ci. >>>>>>>>> >>>>>>>>> In the not so far future Pharo is likely to move to a git >>>>>>>>> based infrastructure, using libgit2. Early adopters are >>>>>>>>> already using it. >>>>>>>>> I haven't heard the squeak ideas about that. >>>>>>>>> >>>>>>>>> Stephan >>>>>>>>> >>>>>>>>> >>>>>>>>> >> >

Dec. 4, 2015

Re: [Pharo-users] Installation

by Rodrigo Coimbra

Thank you Offray! I need Pharo to apply Moose platform...I'm already working on it! Cheers Em Quinta-feira, 3 de Dezembro de 2015 20:43, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> escreveu: Rodrigo, That screen means you're going fine. Next thing is to select an image in the left and click on the play button to open it. Cheers, Offray On 02/12/15 19:40, Rodrigo Coimbra wrote: I've tried the tutorial available atÂ http://pharo.org/gnu-linux-installationÂ and I had this screen:Â Em Quarta-feira, 2 de Dezembro de 2015 14:26, Rodrigo Coimbra <rodrigotavarescoimbra(a)yahoo.com.br> escreveu: How do I definitely install Pharo on Ubuntu 15.04?

Dec. 4, 2015

Re: [Pharo-users] [squeak-dev] Re: evolutions of squeakelib & crypto (Reed Solomon)

by Robert Withers

I had to reconceptualize how substitutions worked in Pharo, while learning Fuel, as it has been awhile since I played with that serialization. I recently came back to smalltalk after years. My real goal is mobile code so it can run where it has most affinity, even though that's not yet known. Enter sanguinity. This is great news and I am excited by the potential to see Squeak and Pharo talking to each other. cheers, Robert On 12/04/2015 11:41 AM, Mariano Martinez Peck wrote: > I think that either Max or Martin did the Spur needed changes for Fuel. > So likely it should be easy to make it work in latest Squeak. > > On Fri, Dec 4, 2015 at 12:57 PM, Robert Withers > <robert.w.withers(a)gmail.com <mailto:robert.w.withers@gmail.com>> wrote: > > Now I think you are right on with your observation. Additionally, > the number of dialects could increase further with Fuel > serialization, just port SecureSession and bits. > > Alright, I came up with a name and it may border on the egregious > ... presenting ... > > "Maelstrom" > > A new distributed metric will be established in Maelstrom to > measure intra- & inter-vat activity: "Sanguinity". > > Robert > > PS. thanks for pointing out Fuel support for older squeaks. > > > On 12/04/2015 10:25 AM, Sven Van Caekenberghe wrote: > > Another suggestion: if you intend to make something cross > dialect and hope to get traction, I would not use a project > name which contains one dialect, but something more general > like Cryptography, or some cool project name, like Seaside, > Fuel, ... > > On 04 Dec 2015, at 15:43, Robert Withers > <robert.w.withers(a)gmail.com > <mailto:robert.w.withers@gmail.com>> wrote: > > I use squeak 5.0 and would want the Fuel support to > customize for wire serializations and substitutions, such > that Squeak and Pharo could talk to each other, and all > other Fuel environments. The Fuel changes I made are in > the Pharo port of SqueakElib in the > SqueakElib-CapTP-Serialization category and consist of a > Decoder, Materializer and a Materialization. > > Robert > > On 12/04/2015 09:35 AM, Esteban Lorenzano wrote: > > which squeak version? > of what? > > On 04 Dec 2015, at 12:15, Robert Withers > <robert.w.withers(a)gmail.com > <mailto:robert.w.withers@gmail.com>> wrote: > > I just realized that the squeak version uses > ReferenceStream while the Pharo version uses Fuel, > so the binary serializations are different and > they won't speak to each other. Any chance that > Fuel is ported to Squeak? > > Regards, > Robert > > On 12/04/2015 06:11 AM, Robert Withers wrote: > > I am unable to import these files into > SqueakSource, so it may be best done from > inside Pharo with Monticello. Here are working > Crypto and SqueakElib in Pharo, prior to > SecureSession refactoring and Reed Solomon. I > include the correct version of LayeredProtocol. > > Regards, > Robert > > > On 12/04/2015 05:47 AM, Robert Withers wrote: > > Best Regards > > http://www.squeaksource.com/Cryptography.html > http://www.squeaksource.com/squeakelib.html > > > On 12/04/2015 05:44 AM, Robert Withers wrote: > > After my password reset on > squeaksource, I committed to both > Cryptography and SqueakElib, project > links below. > > In the case of Cryptography, I had a > version ported to Pharo ... I will > organize Pharo ports of both after > Reed Solomon is stable, and announce > them to the Pharo list. This way both > environments can be supported through > this one repository. > > Robert > > On 12/04/2015 04:35 AM, Stephan > Eggermont wrote: > > On 03-12-15 23:06, Robert Withers > wrote: > > Are any of these used by both > squeak and Pharo? That would > be the right > move I think. I will ask about > getting my password reset for > squeaksource, since that is > where the old code resides. > > All of them. Mostly timing of > project start/high activity and > who are > maintaining it decided on > platforms. There was a time when > squeaksource was not so stable and > then many projects migrated, and I > currently hear least about > stability issues from ss3, but the > load on smalltalkhub is much > higher, I assume, as that is used > for the pharo ci. > > In the not so far future Pharo is > likely to move to a git based > infrastructure, using libgit2. > Early adopters are already using it. > I haven't heard the squeak ideas > about that. > > Stephan > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > >

Dec. 4, 2015

Re: [Pharo-users] ZnClient problem with extensions

by Skip Lentz

Hi, > On Dec 4, 2015, at 11:56 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > because I am clueless with web dev can you help me understand how to do this with ZnClient ? I tried some things, such as this snippet: ZnClient new setIfModifiedSince: DateAndTime now; contentReader: [ :entity | ZipArchive new readFrom: entity readStream ]; get: 'https://api.github.com/repos/kilon/ChronosManager/zipball/master <https://api.github.com/repos/kilon/ChronosManager/zipball/master>' But the response does not have a Last-Modified date. So what you probably want is the date of the latest commit to master (or whatever branch). Considering you do want to minimize dependencies and therefore not use the API bindings, the following could be done: client := ZnClient new. " Get latest commit list, we only care about the response in this case " client setIfModifiedSince: (Date year: 2015 month: 12 day: 1); get: 'https://api.github.com/repos/kilon/ChronosManager/commits?sha=master <https://api.github.com/repos/kilon/ChronosManager/commits?sha=master>'. client response isNotModified ifTrue: [ nil ] ifFalse: [ client contentReader: [ :entity | ZipArchive new readFrom: entity readStream ]; get: 'https://api.github.com/repos/kilon/ChronosManager/zipball/master <https://api.github.com/repos/kilon/ChronosManager/zipball/master>'] So you need in total three GET requests, since the second request responds with a redirect. The first request does not count to the API rate limit if it returns a 304 Not Modified.

Dec. 4, 2015

Re: [Pharo-users] Mongo configuration for Pharo40

by Henrik Johansen

> On 04 Dec 2015, at 5:41 , Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > > That's what we have Monticello groups for, right? ;) > I meant to write *Metacello* groups, obviously... Cheers, Henry

Dec. 4, 2015

Re: [Pharo-users] Mongo configuration for Pharo40

by Henrik Johansen

> On 04 Dec 2015, at 5:22 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > According to http://bsonspec.org/spec.html there are indeed 2 different types > > "\x09" e_name int64 UTC datetime > > "\x11" e_name int64 Timestamp > > I would guess that you need 2 different (sub)classes in Pharo if you want to honour this spec. It has little to do with the almost empty TimeStamp subclass of DateAndTime having been removed. This is an API design issue (decide on the Pharo to BSON type mapping). Strictly speaking, Timestamp should've never been mapped; "Timestamp - Special internal type used by MongoDB replication and sharding. First 4 bytes are an increment, second 4 are a timestamp" doesn't exactly agree with the smalltalk implementation: nextTimestampPut: aTimestamp self nextDateAndTimePut: aTimestamp It's a problem when an existing application stored Timestamp instances with the broken type, for the reason I explained. I'd be fine with having a legacy-compatibility package containing Timestamp class + bson extensions as before (even though it was broken) strictly for use when migrating legacy applications. That's what we have Monticello groups for, right? ;) Cheers, Henry

Dec. 4, 2015

Re: [Pharo-users] [squeak-dev] Re: evolutions of squeakelib & crypto (Reed Solomon)

by Mariano Martinez Peck

I think that either Max or Martin did the Spur needed changes for Fuel. So likely it should be easy to make it work in latest Squeak. On Fri, Dec 4, 2015 at 12:57 PM, Robert Withers <robert.w.withers(a)gmail.com> wrote: > Now I think you are right on with your observation. Additionally, the > number of dialects could increase further with Fuel serialization, just > port SecureSession and bits. > > Alright, I came up with a name and it may border on the egregious ... > presenting ... > > "Maelstrom" > > A new distributed metric will be established in Maelstrom to measure > intra- & inter-vat activity: "Sanguinity". > > Robert > > PS. thanks for pointing out Fuel support for older squeaks. > > > On 12/04/2015 10:25 AM, Sven Van Caekenberghe wrote: > >> Another suggestion: if you intend to make something cross dialect and >> hope to get traction, I would not use a project name which contains one >> dialect, but something more general like Cryptography, or some cool project >> name, like Seaside, Fuel, ... >> >> On 04 Dec 2015, at 15:43, Robert Withers <robert.w.withers(a)gmail.com> >>> wrote: >>> >>> I use squeak 5.0 and would want the Fuel support to customize for wire >>> serializations and substitutions, such that Squeak and Pharo could talk to >>> each other, and all other Fuel environments. The Fuel changes I made are in >>> the Pharo port of SqueakElib in the SqueakElib-CapTP-Serialization category >>> and consist of a Decoder, Materializer and a Materialization. >>> >>> Robert >>> >>> On 12/04/2015 09:35 AM, Esteban Lorenzano wrote: >>> >>>> which squeak version? >>>> of what? >>>> >>>> On 04 Dec 2015, at 12:15, Robert Withers <robert.w.withers(a)gmail.com> >>>>> wrote: >>>>> >>>>> I just realized that the squeak version uses ReferenceStream while the >>>>> Pharo version uses Fuel, so the binary serializations are different and >>>>> they won't speak to each other. Any chance that Fuel is ported to Squeak? >>>>> >>>>> Regards, >>>>> Robert >>>>> >>>>> On 12/04/2015 06:11 AM, Robert Withers wrote: >>>>> >>>>>> I am unable to import these files into SqueakSource, so it may be >>>>>> best done from inside Pharo with Monticello. Here are working Crypto and >>>>>> SqueakElib in Pharo, prior to SecureSession refactoring and Reed Solomon. I >>>>>> include the correct version of LayeredProtocol. >>>>>> >>>>>> Regards, >>>>>> Robert >>>>>> >>>>>> >>>>>> On 12/04/2015 05:47 AM, Robert Withers wrote: >>>>>> >>>>>>> Best Regards >>>>>>> >>>>>>> http://www.squeaksource.com/Cryptography.html >>>>>>> http://www.squeaksource.com/squeakelib.html >>>>>>> >>>>>>> >>>>>>> On 12/04/2015 05:44 AM, Robert Withers wrote: >>>>>>> >>>>>>>> After my password reset on squeaksource, I committed to both >>>>>>>> Cryptography and SqueakElib, project links below. >>>>>>>> >>>>>>>> In the case of Cryptography, I had a version ported to Pharo ... I >>>>>>>> will organize Pharo ports of both after Reed Solomon is stable, and >>>>>>>> announce them to the Pharo list. This way both environments can be >>>>>>>> supported through this one repository. >>>>>>>> >>>>>>>> Robert >>>>>>>> >>>>>>>> On 12/04/2015 04:35 AM, Stephan Eggermont wrote: >>>>>>>> >>>>>>>>> On 03-12-15 23:06, Robert Withers wrote: >>>>>>>>> >>>>>>>>>> Are any of these used by both squeak and Pharo? That would be the >>>>>>>>>> right >>>>>>>>>> move I think. I will ask about getting my password reset for >>>>>>>>>> squeaksource, since that is where the old code resides. >>>>>>>>>> >>>>>>>>> All of them. Mostly timing of project start/high activity and who >>>>>>>>> are >>>>>>>>> maintaining it decided on platforms. There was a time when >>>>>>>>> squeaksource was not so stable and then many projects migrated, and I >>>>>>>>> currently hear least about stability issues from ss3, but the load on >>>>>>>>> smalltalkhub is much higher, I assume, as that is used for the pharo ci. >>>>>>>>> >>>>>>>>> In the not so far future Pharo is likely to move to a git based >>>>>>>>> infrastructure, using libgit2. Early adopters are already using it. >>>>>>>>> I haven't heard the squeak ideas about that. >>>>>>>>> >>>>>>>>> Stephan >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >> > > -- Mariano http://marianopeck.wordpress.com

Dec. 4, 2015

Re: [Pharo-users] Mongo configuration for Pharo40

by Esteban Lorenzano

> On 04 Dec 2015, at 17:25, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 04.12.2015 um 16:40 schrieb Henrik Johansen <henrik.s.johansen(a)veloxit.no>: >> >> >>> On 04 Dec 2015, at 3:49 , Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> Yes I thinkâ¦ I still do not update voyage to Pharo5 (there are not TimeStamps anymore). >>> >>> Esteban >>> >>>> On 04 Dec 2015, at 15:43, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> Does it make sense to have >>>> >>>> Name: ConfigurationOfVoyageMongo-EstebanLorenzano.38 >>>> Author: EstebanLorenzano >>>> Time: 9 May 2015, 8:40:27.23963 am >>>> UUID: 9ba71817-b3f9-4f66-8579-e09e5deb5935 >>>> Ancestors: ConfigurationOfVoyageMongo-EstebanLorenzano.37 >>>> >>>> fixed a problem with the versionner tool >>>> >>>> in the Catalog for Pharo 40? >>>> >>>> Stef >>>> >>> >>> >> >> I found this to be kind of a big deal when trying to remove deprecations in 4.0, as TimeStamps and DateAndTime are mapped to different BSON classes... >> If you change Documents to use DateAndTime now instead of Timestamp now, and write them to a legacy database, they will save just fine, but Mongo will give errors if you try to sort documents by that field due to incompatible types. :/ >> > Wouldn't it then be possible to include a timestamp class in Mongo? yes, but why duplicate? (*if* ZTimestamp is good, I would adopt it) > > Norbert

Dec. 4, 2015