June 2012 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] NeoJSON

by Igor Stasenko

On 22 June 2012 22:02, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 22 Jun 2012, at 21:35, Sean P. DeNigris wrote: > >> Someone's been busy!! ;-) > > You are far busier lately, these are nice standalone projects, nothing like changing Pharo while we're all working on it. > But nevertheless, you making them publicly available, while most "business" people prefer to keep their code in own treasury, behind safe doors, guarded by lawyers armed with licenses. :) > Sven -- Best regards, Igor Stasenko.

June 22, 2012

Re: [Pharo-users] [ANN] ZTimestamp

by Igor Stasenko

On 22 June 2012 20:46, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > We have DateAndTime and TimeStamp, which are generally useful objects with lots of features. > > But for a lot of applications, they are too heavy. In server side code, timestamps are almost always in UTC (timezone zero). In most cases, nanosecond or millisecond precision are not (really) needed. Unix/Posix time has only second precision. > > I wrote ZTimestamp as an alternative for DateAndTime and TimeStamp. > It has second precision and lives in the UTC/GMT/Zulu timezone. > It uses ISO/International conventions and protocols only. > ZTimestamp is more efficient: it uses half the memory of DateAndTime and is faster. > > You can find it in > > Â Â Â Â http://mc.stfx.eu/Neo > > ConfigurationOfZTimestamp is also available from > > Â Â Â Â http://www.squeaksource.com/MetacelloRepository > Â Â Â Â http://squeaksource.com/MetaRepoForPharo14 > Â Â Â Â http://ss3.gemstone.com/ss/MetaRepoForPharo20 > > Here are some benchmarks: > > [ 1000 timesRepeat: [ ZTimestamp now ] ] bench '1,910 per second.' > [ 1000 timesRepeat: [ DateAndTime now ] ] bench '253 per second.' what? 253 per second? what it doing there? > > [ 1000 timesRepeat: [ ZTimestamp fromString: '2012-06-18T07:51:40Z' ] ] bench '161 per second.' > [ 1000 timesRepeat: [ DateAndTime fromString: '2012-06-18T07:51:40Z' ] ] bench '44.9 per second.' > > [ 1000 timesRepeat: [ ZTimestamp now printString ] ] bench '212 per second.' > [ 1000 timesRepeat: [ DateAndTime now printString ] ] bench '82.3 per second.' > [ 1000 timesRepeat: [ TimeStamp now printString ] ] bench '54.2 per second.' > > > [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) = (ZTimestamp fromUnixTime: 2540006939) ] ] bench '377 per second.' > [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) = (DateAndTime fromUnixTime: 2540006939) ] ] bench '142 per second.' > > [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) < (ZTimestamp fromUnixTime: 2540006939) ] ] bench '376 per second.' > [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) < (DateAndTime fromUnixTime: 2540006939) ] ] bench '134 per second.' > > [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) + 10 days ] ] bench '604 per second.' > [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) + 10 days ] ] bench '142 per second.' > > [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) - (ZTimestamp fromUnixTime: 2540006939) ] ] bench '239 per second.' > [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) - (DateAndTime fromUnixTime: 2540006939) ] ] bench '98.8 per second.' > > > [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) = (ZTimestamp year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '2,040 per second.' > [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) = (DateAndTime year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '1,800 per second.' > > [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) < (ZTimestamp year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '2,220 per second.' > [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) < (DateAndTime year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '1,050 per second.' > > [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) + 10 days ] ] bench '1,970 per second.' > [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) + 10 days ] ] bench '245 per second.' > > [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) - (ZTimestamp year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '1,440 per second.' > [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) - (DateAndTime year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '767 per second.' > > > ZTimestamp is *not* meant as a general replacement for DateAndTime or TimeStamp. But in a lot of cases, it can be more efficient. > > Feedback and users are welcome. > > > Sven > > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > > -- Best regards, Igor Stasenko.

June 22, 2012

Re: [Pharo-users] [ANN] NeoJSON

by Sven Van Caekenberghe

On 22 Jun 2012, at 21:35, Sean P. DeNigris wrote: > Someone's been busy!! ;-) You are far busier lately, these are nice standalone projects, nothing like changing Pharo while we're all working on it. Sven

June 22, 2012

Re: [Pharo-users] [ANN] NeoJSON

by Sean P. DeNigris

Someone's been busy!! ;-) -- View this message in context: http://forum.world.st/ANN-NeoJSON-tp4636209p4636211.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 22, 2012

[ANN] NeoJSON

by Sven Van Caekenberghe

JSON (JavaScript Object Notation) is a popular data-interchange format. A number of implementations of this simple format already exist. NeoJSON is a more flexible and more efficient reader and writer for this format. You can find it in http://mc.stfx.eu/Neo ConfigurationOfNeoJSON is also available from http://www.squeaksource.com/MetacelloRepository http://squeaksource.com/MetaRepoForPharo14 http://ss3.gemstone.com/ss/MetaRepoForPharo20 Documentation can be found here https://github.com/svenvc/docs/blob/master/neo/neo-json-paper.md Feedback and users are welcome. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

June 22, 2012

[ANN] NeoCSV

by Sven Van Caekenberghe

CSV (Comma Separated Values) and more generally other delimiter-separated-value formats like TSV are probably the most common data exchange format. A number of implementations of this simple format already exist. NeoCSV is a more flexible and more efficient reader and writer for this format. You can find it in http://mc.stfx.eu/Neo ConfigurationOfNeoCSV is also available from http://www.squeaksource.com/MetacelloRepository http://squeaksource.com/MetaRepoForPharo14 http://ss3.gemstone.com/ss/MetaRepoForPharo20 Documentation can be found here https://github.com/svenvc/docs/blob/master/neo/neo-csv-paper.md Feedback and users are welcome. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

June 22, 2012

Re: [Pharo-users] Versionner a GUI for metacello

by Sean P. DeNigris

Juan Pablo Sandoval wrote > > Thank you for the new version of the config. > > As Stef wrote, I am working in a Spec version of Versionner :). I will > send > a notification when ready. > Hey Juan! I've been playing with the old Glamour version and it's fun to have a tool for Metacello :) A few quick things about the config: * while you're working on the spec version, please integrate my config so we can play with it without loading the full Glamour :) It only changes the 1.0 baseline, so it should not effect your current work (and remove Glamour from the load instructions since it's loaded automatically now) * I noticed you are creating version 1.20, 1.21, etc., all with little fixes and "blessing: #'development'". After many conversations with Dale, I now understand that the point of marking a version #'development' is so you can change it without making new version numbers. * the default for Metacello is to load all packages, so the last line of your baselines (spec group: 'default' with: #(...).) is unnecessary and creates the burden of having to be manually updated if your project structure changes -- View this message in context: http://forum.world.st/Versionner-a-GUI-for-metacello-tp4607220p4636207.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 22, 2012

[ANN] ZTimestamp

by Sven Van Caekenberghe

We have DateAndTime and TimeStamp, which are generally useful objects with lots of features. But for a lot of applications, they are too heavy. In server side code, timestamps are almost always in UTC (timezone zero). In most cases, nanosecond or millisecond precision are not (really) needed. Unix/Posix time has only second precision. I wrote ZTimestamp as an alternative for DateAndTime and TimeStamp. It has second precision and lives in the UTC/GMT/Zulu timezone. It uses ISO/International conventions and protocols only. ZTimestamp is more efficient: it uses half the memory of DateAndTime and is faster. You can find it in http://mc.stfx.eu/Neo ConfigurationOfZTimestamp is also available from http://www.squeaksource.com/MetacelloRepository http://squeaksource.com/MetaRepoForPharo14 http://ss3.gemstone.com/ss/MetaRepoForPharo20 Here are some benchmarks: [ 1000 timesRepeat: [ ZTimestamp now ] ] bench '1,910 per second.' [ 1000 timesRepeat: [ DateAndTime now ] ] bench '253 per second.' [ 1000 timesRepeat: [ ZTimestamp fromString: '2012-06-18T07:51:40Z' ] ] bench '161 per second.' [ 1000 timesRepeat: [ DateAndTime fromString: '2012-06-18T07:51:40Z' ] ] bench '44.9 per second.' [ 1000 timesRepeat: [ ZTimestamp now printString ] ] bench '212 per second.' [ 1000 timesRepeat: [ DateAndTime now printString ] ] bench '82.3 per second.' [ 1000 timesRepeat: [ TimeStamp now printString ] ] bench '54.2 per second.' [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) = (ZTimestamp fromUnixTime: 2540006939) ] ] bench '377 per second.' [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) = (DateAndTime fromUnixTime: 2540006939) ] ] bench '142 per second.' [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) < (ZTimestamp fromUnixTime: 2540006939) ] ] bench '376 per second.' [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) < (DateAndTime fromUnixTime: 2540006939) ] ] bench '134 per second.' [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) + 10 days ] ] bench '604 per second.' [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) + 10 days ] ] bench '142 per second.' [ 1000 timesRepeat: [ (ZTimestamp fromUnixTime: 1340006939) - (ZTimestamp fromUnixTime: 2540006939) ] ] bench '239 per second.' [ 1000 timesRepeat: [ (DateAndTime fromUnixTime: 1340006939) - (DateAndTime fromUnixTime: 2540006939) ] ] bench '98.8 per second.' [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) = (ZTimestamp year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '2,040 per second.' [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) = (DateAndTime year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '1,800 per second.' [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) < (ZTimestamp year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '2,220 per second.' [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) < (DateAndTime year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '1,050 per second.' [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) + 10 days ] ] bench '1,970 per second.' [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) + 10 days ] ] bench '245 per second.' [ 1000 timesRepeat: [ (ZTimestamp year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) - (ZTimestamp year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '1,440 per second.' [ 1000 timesRepeat: [ (DateAndTime year: 2012 month: 7 day: 1 hour: 8 minute: 8 second: 8) - (DateAndTime year: 2011 month: 5 day: 2 hour: 4 minute: 4 second: 4) ] ] bench '767 per second.' ZTimestamp is *not* meant as a general replacement for DateAndTime or TimeStamp. But in a lot of cases, it can be more efficient. Feedback and users are welcome. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

June 22, 2012

Where are our ancestors buried?

by Sean P. DeNigris

I want to view changes between Announcements-Core-StephaneDucasse.31 (the current version) and Announcements-Core-MarcusDenker.30 The current version is in http://ss3.gemstone.com/ss/Pharo20, but where is Announcements-Core-MarcusDenker.30? Thanks, Sean -- View this message in context: http://forum.world.st/Where-are-our-ancestors-buried-tp4636205.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 22, 2012

Re: [Pharo-users] Evaluating Nautilus

by Johan Fabry

On 22 Jun 2012, at 05:18, Benjamin wrote: [...] > On the other hand, the code pane modification can be made within an hour (maybe two if you are not confident with morphic, but it doesn't seems to be the case) using the plugin mecanism (Johan Fabry can testify ^^). I testify! :-P > Then, Nautilus is not cross platform, but we have developed Spec with the goal to use it for Nautilus, and Spec is(will be ^^) cross platform. So one day, Nautilus will be cross platform. Sadly, I will not be soon (I have to rewrite the whole ui). [...] Looking at the video, I think your best option if you do not want to use glamour is to build a custom browser using Spec. It does not seem like a lot of work, certainly since you already have the logic of the actions in place. The only thing that Spec does not do AFAIK is the dynamic adding of lists in the top pane. Ben is going to have a look at dynamic widget placement etc and this looks like a nice case study :-) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry jfabry(a)dcc.uchile.cl - http://www.dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

June 22, 2012