- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [website] new news entry: talk NDC Oslo

by Tudor Girba

I think you are referring to the playground/inspector. Indeed it takes more space than the other inspector, but only if you want to see multiple objects at the same time. You can choose to see just one object at a time, and then you get in a situation similar to the existing tool. It's just that it turns out that once you can see more related objects, you choose to do so and you get more aggressive in exploration. And then you do not want to go back :). Doru On Fri, Jun 13, 2014 at 9:38 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 13 Jun 2014, at 09:31, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > If the fonts get much larger, having several panes side-by-side makes > things look ugly and you kind of lose the perspective :(. > > I think the GTTools take up too much screen space. I know that today we > have bigger screens and we should use them, but still. > > This is of course a subjective opinion, a feeling. > -- www.tudorgirba.com "Every thing has its own flow"

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Sven Van Caekenberghe

On 14 Jun 2014, at 12:18, Ben Coman <btc(a)openInWorld.com> wrote: > Sven Van Caekenberghe wrote: >> In any case, the server socket used is normally listening on all interfaces [0.0.0.0] >> >> Sven >> >> > > Maybe it matters that [0.0.0.0] is the IPv4-Unspecified-Address > and it might make a difference to use IPv6-Unspecified-Address [0:0:0:0:0:0:0:0] or [::] > > cheers -ben I guess it all depends on the Socket plugin. ZnServer has #bindingAddress: which eventually calls Socket>>#listenOn:backlogSize:interface: but the question is, what is acceptable as last argument. And how is the difference between v4 and v6 handled. There is a 'primitives-ipv6' category, but no #listenOn with an interface there.

June 14, 2014

Re: [Pharo-dev] Brainstorming Pharo4

by stepharo

> As Kilon say, this is a personal wishlist. Any direction you mentioned > is worth and will have impact. > > However, here's my personal top 5: > > - **Git in the image**, that would be awesome to be able integrate the > gitflow way of developing in team. Easy branching/merging is a must. > - **Slots**. I still need to check the current implementation and see > what's possible (Property slots?) but as I have understood you've > planned even more for pharo4? > - **Text Editor with sensible keybindings**. > - **ARM support** > - **Athens** We are getting there. > > > On Wed, Jun 4, 2014 at 9:06 PM, jannik laval <jannik.laval(a)gmail.com > <mailto:jannik.laval@gmail.com>> wrote: > > Hi all, > > >From my point of view, I like the progrss on the ARM VM. > I hope to have an Android VM that works. > Also I hope to see Pharo3.0 and Pharo4.0 working on iOS. > > Another question is about two interesting plugins: Mpeg3Plugin and > CameraPlugin. > Is it possible to integrate them in the VM build ? > > Thank you guys for all the work done. > Jannik > > > 2014-06-04 20:53 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > > Hi Esteban, > > As you mentioned a lot of new tools and protocols were > introduced, > people (me included) does not well about those ones. > As an example I am slowly discovering announcement and now > AFAIK the > image use three different protocols for this: > change/update, observer > and Announcement! > > Yes we know that the situation is not ideal. > We started to move more to announcement. The problem is that > some of the widgets > requires the change/update. For the observer I do not know > what you mean. > > > Personally I beg for a great Pharo 4.x series of iterative > cleaning+consolidations. > > Thanks > > Hilaire > > Le 04/06/2014 17:36, Esteban Lorenzano a Ã©crit : > > Hi, > > A couple of weeks ago we started to plan Pharo4. This > work became stagnated for many reasons, but mainly > because I needed to travel to Argentina. > Now I'm slowly resuming the work and I wanted to share > with you what we have been talking/dreaming. > In esence, we have two important drivers for this release: > > 1) Improving tools > Turns out that we have introduced a lot of kernel > improvements (opal compiler, layouts, slots, etc.) and > tools are still not aware of them. Even worst: we have > traits since a lot of time and our tools are still now > aware enough to provide good interoperability. > But not just that: we have introduced things that are > not well used yet: keybindings (who do not want a > better keybindings structure... coherent and > editable?), spec should allow us to continue enhancing > existing tools and to replace old ones. > > 2) Modularisation > One of the fundamental ideas behind Pharo is to > provide a modular environment. But well... since Pharo > start to the moment, we prepared things to allow it, > but still few direct effort has been made. > In our dreams, Pharo should be built starting for a > small kernel image and adding different modules to get > a complete version. In this idea > Pharo=Kernel+GUI(Morphic)+Tools. > This has huge advantages (I do not think is necesary > to explain them, isn't ;)?) > > We brainstomed around this and we get this list of > issues (not all of them directly related to the > objectives, but well... good stuff also :) ) > > Web site: > - add catalog > - add videos > - enhance it in general > > Infrastructure: > - support more vm platforms > > VM: > - spur > - 64bits > - make vm embedable and UI independent (with SDL2 and > OSWindow) > > Image: > - Modularisation > - Removing old compiler > - Repackage Morphic (to allow better modularisation) > - Athens (replace old bitblt) > > Tools > - Replace changes with Ombu/Epicea > - Replace sources with a better abstraction > - Git support inside image (with libgit2 + tools) > - Pass on Spec > - Include Glamour? > - Make Ring unloadable > - Fonts with FreeType > > And lots of bugfixes :) > > We would like to exchange ideas with you. > So, what do you think? > > Esteban > > > > > > > > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://www.phratch.com > http://car.mines-douai.fr/ > >

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Ben Coman

Sven Van Caekenberghe wrote: > In any case, the server socket used is normally listening on all interfaces [0.0.0.0] > > Sven > > Maybe it matters that [0.0.0.0] is the IPv4-Unspecified-Address and it might make a difference to use IPv6-Unspecified-Address [0:0:0:0:0:0:0:0] or [::] cheers -ben

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Ben Coman

June 14, 2014

Re: [Pharo-dev] PharoVM with latests changes

by Pablo R. Digonzelli

Thanks!!! downloading.. Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714 ----- Mensaje original ----- De: "Esteban A. Maringolo" <emaringolo(a)gmail.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviados: MiÃ©rcoles, 11 de Junio 2014 17:32:02 Asunto: Re: [Pharo-dev] PharoVM with latests changes Thank you! I'm downloading it right now. Esteban A. Maringolo 2014-06-11 17:16 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > Soâ¦ last days Iâve been working in new versions of the PharoVM based in > latest Eliot sources. > New vmâs can be found at: > > http://files.pharo.org/vm/pharo/ > http://files.pharo.org/vm/pharoS/ > > under âlatest.zipâ > > and you can also take it from zeroconf using âvmLatestâ > > and here is an explanation of what this work is so annoying: > > http://smallworks.eu/web/blog/2014-06-11-fighting-entropy > > So, please test, report, etc. > > Expectations: Everything is solved (including the annoying âsmall int bugâ) > and even faster than before. > Realistic expectations: Everything works fine, we are aligned to latest > sources, and now I can start working on the SpurVM implementation. > > Cheers, > Esteban

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Sven Van Caekenberghe

I must admit that I haven't given the whole IPv6 issue much thought. It is good that you/users provide feedback, it is more an OS thing I think/hope. On 14 Jun 2014, at 11:37, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi Sven, > > $ telnet localhost 1701 > works perfectly but I noticed that it first tries to connect to ::1 and then switch to 127.0.0.1 > > Trying ::1... > telnet: connect to address ::1: Connection refused > Trying 127.0.0.1... > Connected to localhost > > but I suspected that curl does the same and do not fallback to 127.0.0.1 > and yes this one works: > > curl --ipv4 http://localhost:1701 > > so by default my curl works on ipv6 > > I do not know why ::1 is before 127.0.0.1 on my mac 10.9.3. > Is there a global option? > in /etc/hosts 127.0.0.1 if first > > anyway, thanks > problem solved and not related with Zinc ;-) > > Luc > > > 2014-06-14 11:03 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Luc, > > I have seen this kind of weirdness before, but I mostly see it with ab (apache benchmark tool). I really have no idea. Have you tried with telnet to do a manual HTTP request ? > > $ telnet localhost 1701 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > GET /random HTTP/1.1 > Host:localhost:1701 > > HTTP/1.1 200 OK > Content-Type: text/plain;charset=utf-8 > Content-Length: 64 > Date: Sat, 14 Jun 2014 08:58:48 GMT > Server: Zinc HTTP Components 1.0 > > EF97C091498F3FEA3F79F65D36C40ECAFD116A68BA31F45D027DB61EBDD1579 > ^] > telnet> close > Connection closed. > > You could also try using the same or a second Pharo image to do the request. > > $ ./pharo Pharo.image eval "ZnClient new get: 'http://localhost:8080/random'" > '766EF4E6E5664EF4C5163D30125B5C35BFE2AED408835CB6D6206DF0A7A15FD > ' > > In any case, the server socket used is normally listening on all interfaces [0.0.0.0] > > Sven > > On 14 Jun 2014, at 09:17, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > > > > > > 2014-06-14 6:04 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > > Luc Fabresse wrote: > >> Hi, > >> > >> I experiencing a strange difference between localhost and 127.0.0.1. > >> > >> In Pharo I do: > >> > >> (ZnServer startDefaultOn: 4444) > >> onRequestRespond: [ :request | ZnResponse ok: (ZnEntity text: 'hello') ] > >> > >> In bash: > >> > >> $ lsof -Pi | grep Pharo > >> Pharo 2718 luc 7u IPv4 0x1e64a2e9381f409b 0t0 TCP *:4444 (LISTEN) > >> > >> I perfectly listen on port 4444 from all interfaces * > >> > >> $ curl http://127.0.0.1:4444 > >> hello > >> > >> $ curl http://localhost:4444 > >> curl: (7) Failed to connect to localhost port 4444: Connection refused <- why ? > >> > >> localhost is correctly resolved on my mac > >> $ ping localhost > >> PING localhost (127.0.0.1): 56 data bytes > >> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.044 ms > >> > >> I tested with other programs than Zinc to open listening sockets and it works. > >> > >> Any idea? > >> > >> #Luc > > maybe http://sourceforge.net/p/curl/bugs/1337/ > > > > Humm, I use curl 7.36.0, so yes perhaps this bug fix is not integrated... > > > > Anyway, I was also suspecting curl but I tested with server: Apache on port 8888 and here curl works: > > > > httpd 621 luc 5u IPv6 0x6ea19c1d988f10db 0t0 TCP *:8888 <-- same as Zinc > > > > but both: > > > > curl http://127.0.0.1:8888 > > curl http://localhost:8888 > > > > are working. > > > > wget always works (Apache and Zinc): > > > > wget -qO- http://127.0.0.1:8888 > > wget -qO- http://localhost:8888 > > > > Thanks Max and Ben, > > > > Luc > > > > >

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Luc Fabresse

Hi Sven, $ telnet localhost 1701 works perfectly but I noticed that it first tries to connect to ::1 and then switch to 127.0.0.1 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost but I suspected that curl does the same and do not fallback to 127.0.0.1 and yes this one works: curl --ipv4 http://localhost:1701 so by default my curl works on ipv6 I do not know why ::1 is before 127.0.0.1 on my mac 10.9.3. Is there a global option? in /etc/hosts 127.0.0.1 if first anyway, thanks problem solved and not related with Zinc ;-) Luc 2014-06-14 11:03 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Luc, > > I have seen this kind of weirdness before, but I mostly see it with ab > (apache benchmark tool). I really have no idea. Have you tried with telnet > to do a manual HTTP request ? > > $ telnet localhost 1701 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > GET /random HTTP/1.1 > Host:localhost:1701 > > HTTP/1.1 200 OK > Content-Type: text/plain;charset=utf-8 > Content-Length: 64 > Date: Sat, 14 Jun 2014 08:58:48 GMT > Server: Zinc HTTP Components 1.0 > > EF97C091498F3FEA3F79F65D36C40ECAFD116A68BA31F45D027DB61EBDD1579 > ^] > telnet> close > Connection closed. > > You could also try using the same or a second Pharo image to do the > request. > > $ ./pharo Pharo.image eval "ZnClient new get: ' > http://localhost:8080/random'" > '766EF4E6E5664EF4C5163D30125B5C35BFE2AED408835CB6D6206DF0A7A15FD > ' > > In any case, the server socket used is normally listening on all > interfaces [0.0.0.0] > > Sven > > On 14 Jun 2014, at 09:17, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > > > > > > 2014-06-14 6:04 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > > Luc Fabresse wrote: > >> Hi, > >> > >> I experiencing a strange difference between localhost and 127.0.0.1. > >> > >> In Pharo I do: > >> > >> (ZnServer startDefaultOn: 4444) > >> onRequestRespond: [ :request | ZnResponse ok: (ZnEntity text: > 'hello') ] > >> > >> In bash: > >> > >> $ lsof -Pi | grep Pharo > >> Pharo 2718 luc 7u IPv4 0x1e64a2e9381f409b 0t0 TCP *:4444 > (LISTEN) > >> > >> I perfectly listen on port 4444 from all interfaces * > >> > >> $ curl http://127.0.0.1:4444 > >> hello > >> > >> $ curl http://localhost:4444 > >> curl: (7) Failed to connect to localhost port 4444: Connection refused > <- why ? > >> > >> localhost is correctly resolved on my mac > >> $ ping localhost > >> PING localhost (127.0.0.1): 56 data bytes > >> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.044 ms > >> > >> I tested with other programs than Zinc to open listening sockets and it > works. > >> > >> Any idea? > >> > >> #Luc > > maybe http://sourceforge.net/p/curl/bugs/1337/ > > > > Humm, I use curl 7.36.0, so yes perhaps this bug fix is not integrated... > > > > Anyway, I was also suspecting curl but I tested with server: Apache on > port 8888 and here curl works: > > > > httpd 621 luc 5u IPv6 0x6ea19c1d988f10db 0t0 TCP *:8888 > <-- same as Zinc > > > > but both: > > > > curl http://127.0.0.1:8888 > > curl http://localhost:8888 > > > > are working. > > > > wget always works (Apache and Zinc): > > > > wget -qO- http://127.0.0.1:8888 > > wget -qO- http://localhost:8888 > > > > Thanks Max and Ben, > > > > Luc > > > > >

June 14, 2014

Desktop deployment

by Noury Bouraqadi

Hi, In the chapter on desktop deployment [1], what do the installers do? I'm more specifically interested in the Mac OS one. I guess it builds a .dmg file. What should I provide as input ? [1] https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… Thanks Noury -- http://twitter.com/#!/NouryBouraqadi http://car.mines-douai.fr/noury

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Sven Van Caekenberghe

Luc, I have seen this kind of weirdness before, but I mostly see it with ab (apache benchmark tool). I really have no idea. Have you tried with telnet to do a manual HTTP request ? $ telnet localhost 1701 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. GET /random HTTP/1.1 Host:localhost:1701 HTTP/1.1 200 OK Content-Type: text/plain;charset=utf-8 Content-Length: 64 Date: Sat, 14 Jun 2014 08:58:48 GMT Server: Zinc HTTP Components 1.0 EF97C091498F3FEA3F79F65D36C40ECAFD116A68BA31F45D027DB61EBDD1579 ^] telnet> close Connection closed. You could also try using the same or a second Pharo image to do the request. $ ./pharo Pharo.image eval "ZnClient new get: 'http://localhost:8080/random'" '766EF4E6E5664EF4C5163D30125B5C35BFE2AED408835CB6D6206DF0A7A15FD ' In any case, the server socket used is normally listening on all interfaces [0.0.0.0] Sven On 14 Jun 2014, at 09:17, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > > 2014-06-14 6:04 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > Luc Fabresse wrote: >> Hi, >> >> I experiencing a strange difference between localhost and 127.0.0.1. >> >> In Pharo I do: >> >> (ZnServer startDefaultOn: 4444) >> onRequestRespond: [ :request | ZnResponse ok: (ZnEntity text: 'hello') ] >> >> In bash: >> >> $ lsof -Pi | grep Pharo >> Pharo 2718 luc 7u IPv4 0x1e64a2e9381f409b 0t0 TCP *:4444 (LISTEN) >> >> I perfectly listen on port 4444 from all interfaces * >> >> $ curl http://127.0.0.1:4444 >> hello >> >> $ curl http://localhost:4444 >> curl: (7) Failed to connect to localhost port 4444: Connection refused <- why ? >> >> localhost is correctly resolved on my mac >> $ ping localhost >> PING localhost (127.0.0.1): 56 data bytes >> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.044 ms >> >> I tested with other programs than Zinc to open listening sockets and it works. >> >> Any idea? >> >> #Luc > maybe http://sourceforge.net/p/curl/bugs/1337/ > > Humm, I use curl 7.36.0, so yes perhaps this bug fix is not integrated... > > Anyway, I was also suspecting curl but I tested with server: Apache on port 8888 and here curl works: > > httpd 621 luc 5u IPv6 0x6ea19c1d988f10db 0t0 TCP *:8888 <-- same as Zinc > > but both: > > curl http://127.0.0.1:8888 > curl http://localhost:8888 > > are working. > > wget always works (Apache and Zinc): > > wget -qO- http://127.0.0.1:8888 > wget -qO- http://localhost:8888 > > Thanks Max and Ben, > > Luc >

June 14, 2014