February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] NativeBoost project moved to new hosting: smalltalkhub

by StÃ©phane Ducasse

Nice questions and I love our answers! Stef > Ask yourself: > - why do we have tests? > - why do multiple people work together? > - why do we want publicly available artifacts? > - why do we want these artifacts tested publicly? > - why do we write configurations? > - why do we try to following coding standards? > - why do we program in Smalltalk? > - why do we mostly write deterministic code? > - why do we work on Pharo? > - why do we build a jenkins infrastructure? > - why do we write down documentation? > > > After successfully answering these questions you will understand!

Feb. 5, 2013

Re: [Pharo-project] [update 2.0] #20514 (Zinc Update)

by StÃ©phane Ducasse

I ***love*** such kind of mail :) Stef On Feb 5, 2013, at 1:51 PM, Marcus Denker wrote: > Issue 7375: Zinc Update January 2013 > http://code.google.com/p/pharo/issues/detail?id=7375 > > > Sven explains: > > Since http://code.google.com/p/pharo/issues/detail?id=7180 there were the following changes: > > - support for server routes (session affinity, sticky sessions) > - new API to access the server URL (#url, #serverUrl, #scheme) > - ZnResponse class>>#redirect: and #created: now accept absolute URLs as well (thx Jan van de Sandt) > - New ZnRequest API (all suggested by Jan van de Sandt): > #host to return the Host: header field as ZnUrl > #relativeUrl to explicitely request the request line uri as a relative URL > #absoluteUrl to combine the request line URL with the host URL into an absolute URL > #mergedFields to return a multi value dictionary combining query fields and application url encoded form fields > - ZnClient>>#redirectUrl now uses ZnUrl>>#inContextOf: > - Reimplemented ZnApplicationUrlEncodedEntity>>#addAll: and ZnHeaders>>#addAll: > using ZnMultiValueDictionary>>#addAllMulti: > - fix ZnUtils class>>#signalProgress:total: bug when total was nil: #format: index should be 1 not 0 (Thx Camillo Bruni !) > - added ZnMessage>>#writeToTranscript > - Bugfix to ZnApplicationFormUrlEncodedEntity>>#readFrom: which failed when content-length was not specified (Thx Jan van de Sandt) > - Extended ZnClient>>#url: to accept the new user info (username and password) component of ZnUrl when present > - ZnRequestLine>>#uri: now explicitely calls #enforceKnownScheme > - various refactorings, cleanups > - moved ZnMonticelloServerDelegate from Zinc-HTTP-Client-Server to Zinc-FileSystem and Zinc-FileSystem-Legacy > - ZnServer's #handleRequestProtected: will now also do a #logServerError unless #logServerDetails is false - this gives exception, > signaller context details and a stack trace of depth 8 when an unhandled error occurs > - There is also a new package, Zinc-Resource-Meta-FileSystem, containing bidirectional conversions between ZnUrl and > FileReference using #asZnUrl and #asFileReference. > > > >

Feb. 5, 2013

Re: [Pharo-project] [Pharo-users] Slides Fosdem13 from this morning

by StÃ©phane Ducasse

>> Hi, >> >> Here are my slides from the talk today at FOSDEM; >> >> http://marcusdenker.de/talks/13Fosdem/2013-FOSDEM-Pharo.pdf > > And on SlideShare (with >1000 views in a day, not badâ¦) I would say quite good! > > http://www.slideshare.net/MarcusDenker/fosdem-13-pharo-20-update

Feb. 5, 2013

Re: [Pharo-project] Nanosecond-precision DateAndTime?

by StÃ©phane Ducasse

> > > A bit offtopic maybe but could you explain (or somebody) difference between DateAndTime and TimeStamp? When I need date and time object I always start to think what class I should use. TimeStamp is the rest of an old design because DateAndTime should just be able to print itself correctly. stef

Feb. 5, 2013