- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Pharo Days 2015. The Pharo summit is back!

by phil＠highoctane.be

What does â¬ 89 â For Pharo Consortium Members (1, 2 or 4 for silver, bronze or gold) mean? Phil --- Philippe Back Visible Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Wed, Dec 3, 2014 at 4:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Pharo Days 2015 > http://pharodays2015.pharo.org > > January 29 & 30, Lille, France > INRIA Lille, building A, 40 avenue Halley, F-59650 Villeneuve dâAscq > > > == General Information == > > Start the year in the right spirit by joining the Pharo community for the > Pharo Days 2015 on Thursday January 29 and Friday January 30 at INRIA, > Lille, France. Meet your online colleagues, programmers and hackers in real > life and experience how much you can pick up in just two days. Learn about > key technologies, talk to core developers and other users, pair program and > contribute to Pharo. Have fun and enjoy yourself. > > Each day has a similar schedule. The morning consists of a handful of > twenty minute tech talks, the afternoon is a coding sprint and open pair > programming workspace. There will be a general assembly of both the Pharo > Consortium and the Pharo Association. On the first days there will be a > parallel Getting Started with Pharo tutorial in the afternoon. > > The very first Pharo conference took place in Annecy in February 2011. In > May 2012 the second Pharo Conference took place, over two days, in Lille. > It was a huge success, with about 60 people participating. It had a very > positive effect on the community and on those who participated. In April > 2013 there was a third well attended Pharo Conference in Bern. In June > 2013, there was also a successful Web specific Pharo one-day event in > Lille. Join us again this time. > > == Pricing == > > The Pharo Days are a two day event with catering included (2 lunches, 1 > diner, drinks and snacks) in a nice environment with full facilities (main > room, auxiliary rooms, office furtniture and wireless network). > > â¬ 199 â Regular > â¬ 149 â For individual Pharo Association Members > â¬ 89 â For individual Pharo Gold Association Members > â¬ 89 â For Pharo Consortium Members (1, 2 or 4 for silver, bronze or gold) > â¬ 39 â Students (excluding diner) > â¬ 19 â Student Volunteers (excluding diner) > > == Registration == > > For official registration we are using EventBrite. You can buy tickets > using PayPal and hence any credit card. If absolutely necessary, you can > opt for an off line payment. Please register on time. > > For social registration you can use Lanyrd or Doodle. Spread the word: > > Summit schedule and relevant data: http://pharodays2015.pharo.org > Register here: > http://www.eventbrite.com/e/pharos-days-2015-tickets-14469423435 > > > >

Dec. 3, 2014

[ANN] Pharo Days 2015. The Pharo summit is back!

by Esteban Lorenzano

Pharo Days 2015 http://pharodays2015.pharo.org January 29 & 30, Lille, France INRIA Lille, building A, 40 avenue Halley, F-59650 Villeneuve dâAscq == General Information == Start the year in the right spirit by joining the Pharo community for the Pharo Days 2015 on Thursday January 29 and Friday January 30 at INRIA, Lille, France. Meet your online colleagues, programmers and hackers in real life and experience how much you can pick up in just two days. Learn about key technologies, talk to core developers and other users, pair program and contribute to Pharo. Have fun and enjoy yourself. Each day has a similar schedule. The morning consists of a handful of twenty minute tech talks, the afternoon is a coding sprint and open pair programming workspace. There will be a general assembly of both the Pharo Consortium and the Pharo Association. On the first days there will be a parallel Getting Started with Pharo tutorial in the afternoon. The very first Pharo conference took place in Annecy in February 2011. In May 2012 the second Pharo Conference took place, over two days, in Lille. It was a huge success, with about 60 people participating. It had a very positive effect on the community and on those who participated. In April 2013 there was a third well attended Pharo Conference in Bern. In June 2013, there was also a successful Web specific Pharo one-day event in Lille. Join us again this time. == Pricing == The Pharo Days are a two day event with catering included (2 lunches, 1 diner, drinks and snacks) in a nice environment with full facilities (main room, auxiliary rooms, office furtniture and wireless network). â¬ 199âââRegular â¬ 149âââFor individual Pharo Association Members â¬ 89âââFor individual Pharo Gold Association Members â¬ 89âââFor Pharo Consortium Members (1, 2 or 4 for silver, bronze or gold) â¬ 39âââStudents (excluding diner) â¬ 19âââStudent Volunteers (excluding diner) == Registration == For official registration we are using EventBrite. You can buy tickets using PayPal and hence any credit card. If absolutely necessary, you can opt for an off line payment. Please register on time. For social registration you can use Lanyrd or Doodle. Spread the word: Summit schedule and relevant data: http://pharodays2015.pharo.org Register here: http://www.eventbrite.com/e/pharos-days-2015-tickets-14469423435

Dec. 3, 2014

Re: [Pharo-users] Umlauts in ZnUrl

by Udo Schneider

On 03/12/14 14:41, Udo Schneider wrote: > ((Smalltalk at: #ConfigurationOfFileSystemNetwork) project version: > #develop) load. This should have been (Smalltalk at: #ConfigurationOfFileSystemNetwork) project version: #development) load. of course. CU, Udo

Dec. 3, 2014

Re: [Pharo-users] Umlauts in ZnUrl

by Udo Schneider

On 03.12.2014 13:57, Sven Van Caekenberghe wrote: > Don't forget: if you get something working that hasn't been done before (it seems you are working on WebDAV), write something short about it to share with the rest of the community. For sure! I'm still shuffling around a lot of code. And there is /no/ documentation yet. I'll make an official announcement once I have the code sorted and documents. But you should be able to get an impression. Try this: "Install packages - all tests should be green given a WebDAV Server" Gofer new url: 'http://smalltalkhub.com/mc/UdoSchneider/FileSystemNetwork/main'; package: 'ConfigurationOfFileSystemNetwork'; load. ((Smalltalk at: #ConfigurationOfFileSystemNetwork) project version: #develop) load. fs := FileSystem webdav: '[URL of a WebDAV server]'. wd := fs workingDirectory. "All the FileReference methods should work" wd children. wd children first basename. wd children first isFile. "wd children first delete." "You can even open a FileList on the working dir" FileList openOn: wd. CU, Udo

Dec. 3, 2014

Re: [Pharo-users] Umlauts in ZnUrl

by Sven Van Caekenberghe

> On 03 Dec 2014, at 13:54, Udo Schneider <Udo.Schneider(a)homeaddress.de> wrote: > > On 03.12.2014 10:19, Sven Van Caekenberghe wrote: >> Hmm, have you seen that ZnClient>>#addPath: actually does this already for non-string arguments (assumed to be collections) ? > No I didn't. That's even better for my purposes! > >> That is too specific, to add for everyone I think. Now, the #split: behaviour is already in there. > I just deleted this method. I can work with intances of Path - so no need to #split: Strings anymore. > >> 'http://myhost.com' asUrl / 'foo' / 'Ã©lÃ¨ve-Ã¼mlaut.txt'. >> >> It is about as short as it gets, right ? >> >> Here is how to get the #split: behaviour: >> >> 'http://myhost.com' asUrl / 'foo/Ã©lÃ¨ve-Ã¼mlaut.txt' >> >> When adding a string, the argument is split on / automatically. > As always I amazed of Smalltalk in general and the design of Zinc specifically ... Good ! Don't forget: if you get something working that hasn't been done before (it seems you are working on WebDAV), write something short about it to share with the rest of the community. Sven

Dec. 3, 2014

Re: [Pharo-users] Umlauts in ZnUrl

by Udo Schneider

On 03.12.2014 10:19, Sven Van Caekenberghe wrote: > Hmm, have you seen that ZnClient>>#addPath: actually does this already for non-string arguments (assumed to be collections) ? No I didn't. That's even better for my purposes! > That is too specific, to add for everyone I think. Now, the #split: behaviour is already in there. I just deleted this method. I can work with intances of Path - so no need to #split: Strings anymore. > 'http://myhost.com' asUrl / 'foo' / 'Ã©lÃ¨ve-Ã¼mlaut.txt'. > > It is about as short as it gets, right ? > > Here is how to get the #split: behaviour: > > 'http://myhost.com' asUrl / 'foo/Ã©lÃ¨ve-Ã¼mlaut.txt' > > When adding a string, the argument is split on / automatically. As always I amazed of Smalltalk in general and the design of Zinc specifically ... CU, Udo

Dec. 3, 2014

Re: [Pharo-users] Alternate browser

by Thierry Goubier

2014-12-03 9:24 GMT+01:00 Craig Johnson <craig(a)hivemind.net>: > > I'm cleaning up a lot of small issues I had with it as I write (mostly > refreshing/deselection issues > > when redefining/renaming classes). > > > > I'm done with the pharo3.0 branch on github; I'm now merging those into > the pharo4.0 branch with git > > (i.e. merging with git on the command line without Monticello merge). > > > > Just tell how it goes for you; even if this is not the browser you like, > > your feedback will tell us where we can improve. > > Thierry > > A few comments on my side. Running AltBrowser Stable in Pharo 4 under > Windows. > * In the code pane - the short-cut key - Meta-S for Save - resets the > dirty code indicator, but does not actually save the code, using the > context menu does. > * Trying to open the Window Menu causes a warning - > "MenuMorph>>add:target:action: is depreciated" > Thanks Craig. I'll correct that. Thierry > > Craig > > > > >

Dec. 3, 2014

Re: [Pharo-users] Umlauts in ZnUrl

by Sven Van Caekenberghe

> On 03 Dec 2014, at 08:49, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: > > Hi Sven, > > the distinction between external and internal representations was the part I didn't get - but it really makes sense. OK. > Your approach with adding pathSegments works perfectly! I'm working with ZnClient though and reusing it for different requests. So I added the following two (three) methods to make my life easier: > > ZnClient>>#addPathSegments: pathSegments > "Modify the receiver's path by adding the elements of pathSegments at the end" > > pathSegments do: [ :each | self addPathSegment: each ] Hmm, have you seen that ZnClient>>#addPath: actually does this already for non-string arguments (assumed to be collections) ? > ZnClient>>#resetPath > self path: '' Yeah, that is maybe useful (there is already #resetEntity). I am also reusing ZnClient instances and I never needed to reset the path like that, I always do #path: and #url: I guess - mostly the second. > I didn't want to overwrite #path: because I only need this for some special edge case. > > ZnClient>>#webdavPath: path > self > resetPath; > addPathSegments: ($/ split: path) That is too specific, to add for everyone I think. Now, the #split: behaviour is already in there. But I also forgot to mention earlier that this works too: 'http://myhost.com' asUrl / 'foo' / 'Ã©lÃ¨ve-Ã¼mlaut.txt'. It is about as short as it gets, right ? Here is how to get the #split: behaviour: 'http://myhost.com' asUrl / 'foo/Ã©lÃ¨ve-Ã¼mlaut.txt' When adding a string, the argument is split on / automatically. > BTW: The whole Zinc framework is a real pleasure to work with. Once I got used to thinking in terms of objects and not only strings I didn't want to look back :-) Thanks. > CU, > > Udo > > > > On 03/12/14 00:02, Sven Van Caekenberghe wrote: >> Hi Udo, >> >> With a URL/URI there are two representations: the external one (the way they are written) and the internal one (what is really meant). ZnUrl follows this distinction. >> >> When you say #asUrl (or #asZnUrl) you are actually parsing an external string representation. When doing so, percent decoding is done by ZnPercentEncoder. This class is strict, in that it does not allow non-safe, non-ascii characters in its input. AFAIK this is correct, but I can imagine a less strict interpretation (like the URL input box of a browser would allow). If you have a reading of the specs that says otherwise I would be very interested. >> >> To save you from doing the encoding yourself, you have to construct the URL from its parts explicitly, like this: >> >> ZnUrl new >> scheme: #http; >> host: 'myhost'; >> addPathSegments: #('path' 'with' 'unlaut' 'Ã¤Ã¶Ã¼.txt'); >> yourself. >> >> => http://myhost/path/with/unlaut/%C3%A4%C3%B6%C3%BC.txt >> >> Class comments and unit tests should help. >> >> There is also this draft: >> >> http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ >> >> HTH, >> >> Sven >> >> PS: Incidentally, this does work >> >> 'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt' asFileReference asUrl. >> >> because #asFileReference works differently. >> >>> On 02 Dec 2014, at 23:32, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: >>> >>> All, >>> >>> What's the expected behavior with non-ASCII characters in URLs. Let's say I want to access a file named "Ã¤Ã¶Ã¼.txt" - My assumption was that Zinc takes care of the UTF-8 -> 7bit (ASCII) -> Escape encoding. But there is either something I don't understand or some manual steps I'm missing. >>> >>> The "straightforward" way doesn't work: >>> 'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt' asUrl. "ZnCharacterEncodingError: ASCII character expected" >>> >>> Although the actual encoding seems to be able to handle it (ignoring the escapes slashes for the moment: >>> 'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt' urlEncoded. >>> "'http%3A%2F%2Fmyhost%2Fpath%2Fwith%2Fumlaut%2F%C3%A4%C3%B6%C3%BC.txt'" >>> >>> Creating a URL from already escaped characters works as well: >>> 'http://myhost/path/with/umlaut/%C3%A4%C3%B6%C3%BC.txt' asUrl. >>> "http://myhost/path/with/umlaut/%C3%A4%C3%B6%C3%BC.txt" >>> >>> As does the decoding of such an URL: >>> 'http://myhost/path/with/umlaut/%C3%A4%C3%B6%C3%BC.txt' urlDecoded. >>> "'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt'" >>> >>> At them moment I'm manually encoding UTF-8 characters in paths segments before trying to build the URL. But is this the correct way? >>> >>> Best Regards, >>> >>> Udo >>> >>> >>> >> >> >> > > >

Dec. 3, 2014

Re: [Pharo-users] Alternate browser

by Craig Johnson

> I'm cleaning up a lot of small issues I had with it as I write (mostly refreshing/deselection issues > when redefining/renaming classes). > > I'm done with the pharo3.0 branch on github; I'm now merging those into the pharo4.0 branch with git > (i.e. merging with git on the command line without Monticello merge). > > Just tell how it goes for you; even if this is not the browser you like, > your feedback will tell us where we can improve. Thierry A few comments on my side. Running AltBrowser Stable in Pharo 4 under Windows. * In the code pane - the short-cut key - Meta-S for Save - resets the dirty code indicator, but does not actually save the code, using the context menu does. * Trying to open the Window Menu causes a warning - "MenuMorph>>add:target:action: is depreciated" Craig

Dec. 3, 2014

Re: [Pharo-users] Umlauts in ZnUrl

by Udo Schneider

Hi Sven, the distinction between external and internal representations was the part I didn't get - but it really makes sense. Your approach with adding pathSegments works perfectly! I'm working with ZnClient though and reusing it for different requests. So I added the following two (three) methods to make my life easier: ZnClient>>#addPathSegments: pathSegments "Modify the receiver's path by adding the elements of pathSegments at the end" pathSegments do: [ :each | self addPathSegment: each ] ZnClient>>#resetPath self path: '' I didn't want to overwrite #path: because I only need this for some special edge case. ZnClient>>#webdavPath: path self resetPath; addPathSegments: ($/ split: path) BTW: The whole Zinc framework is a real pleasure to work with. Once I got used to thinking in terms of objects and not only strings I didn't want to look back :-) CU, Udo On 03/12/14 00:02, Sven Van Caekenberghe wrote: > Hi Udo, > > With a URL/URI there are two representations: the external one (the way they are written) and the internal one (what is really meant). ZnUrl follows this distinction. > > When you say #asUrl (or #asZnUrl) you are actually parsing an external string representation. When doing so, percent decoding is done by ZnPercentEncoder. This class is strict, in that it does not allow non-safe, non-ascii characters in its input. AFAIK this is correct, but I can imagine a less strict interpretation (like the URL input box of a browser would allow). If you have a reading of the specs that says otherwise I would be very interested. > > To save you from doing the encoding yourself, you have to construct the URL from its parts explicitly, like this: > > ZnUrl new > scheme: #http; > host: 'myhost'; > addPathSegments: #('path' 'with' 'unlaut' 'Ã¤Ã¶Ã¼.txt'); > yourself. > > => http://myhost/path/with/unlaut/%C3%A4%C3%B6%C3%BC.txt > > Class comments and unit tests should help. > > There is also this draft: > > http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ > > HTH, > > Sven > > PS: Incidentally, this does work > > 'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt' asFileReference asUrl. > > because #asFileReference works differently. > >> On 02 Dec 2014, at 23:32, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: >> >> All, >> >> What's the expected behavior with non-ASCII characters in URLs. Let's say I want to access a file named "Ã¤Ã¶Ã¼.txt" - My assumption was that Zinc takes care of the UTF-8 -> 7bit (ASCII) -> Escape encoding. But there is either something I don't understand or some manual steps I'm missing. >> >> The "straightforward" way doesn't work: >> 'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt' asUrl. "ZnCharacterEncodingError: ASCII character expected" >> >> Although the actual encoding seems to be able to handle it (ignoring the escapes slashes for the moment: >> 'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt' urlEncoded. >> "'http%3A%2F%2Fmyhost%2Fpath%2Fwith%2Fumlaut%2F%C3%A4%C3%B6%C3%BC.txt'" >> >> Creating a URL from already escaped characters works as well: >> 'http://myhost/path/with/umlaut/%C3%A4%C3%B6%C3%BC.txt' asUrl. >> "http://myhost/path/with/umlaut/%C3%A4%C3%B6%C3%BC.txt" >> >> As does the decoding of such an URL: >> 'http://myhost/path/with/umlaut/%C3%A4%C3%B6%C3%BC.txt' urlDecoded. >> "'http://myhost/path/with/umlaut/Ã¤Ã¶Ã¼.txt'" >> >> At them moment I'm manually encoding UTF-8 characters in paths segments before trying to build the URL. But is this the correct way? >> >> Best Regards, >> >> Udo >> >> >> > > >

Dec. 3, 2014