April 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Ben Coman

April 29, 2014

Re: [Pharo-dev] [Pharo-users] [Pharo3] New Sources file starting 30841/30842

by Tudor Girba

Moose passed all tests. I am trying it on Mac OS X and I see no troubles. Great job! Doru On Tue, Apr 29, 2014 at 4:49 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 29 Apr 2014, at 16:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > On 29 Apr 2014, at 15:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> > >> On 29 Apr 2014, at 15:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> > >>> > >>> On 29 Apr 2014, at 15:32, Robert Shiplett <grshiplett(a)gmail.com> > wrote: > >>> > >>>> looked through 2 PDF's for "pharo.ini" and "sources" but did not find > this mentioned ... it is probably staring right at me, since the image DID > open... > >>>> > >>> > >>> I never use windows. But I think it would be strange if the sources > file would be referenced there. Makes no sense to me > >>> (but as I said, never used windows since win 3.11) > >> > >> One thing I found is that the full zip releases (e.g. Pharo3.0-win.zip) > do just have the V2 sourcesâ¦ fixing that now. > >> > > > > This is fixed nowâ¦ > > > > Marcus > > I did a quick test on Windows 8.1 downloading > http://files.pharo.org/platform/Pharo3.0-win.zip and it works perfectly ! > > Super. > > We're very close now. > > > -- www.tudorgirba.com "Every thing has its own flow"

April 29, 2014

Re: [Pharo-dev] Amber-Pharo based coding dojo in a coworking space

by Sebastian Sastre

On Apr 29, 2014, at 10:03 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > is this not the cases if you cannot beat them join them ? Do you seriously believe Amber or Pharo can compete AngularJS , correct me if I am wrong, when behind this framework is Google itself ? Against is a no-chance thing. Itâs either you do it better or you join on top. Iâm curious about where are we going

April 29, 2014

Re: [Pharo-dev] Amber-Pharo based coding dojo in a coworking space

by Sebastian Sastre

On Apr 29, 2014, at 10:49 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Who is people? Is it inside Inria? If not it might be a good idea to make it visible to the public so a few more people could chime in. > > Norbert That question brings us to: Get the Heck Out of the Building in Founderâs School: Part 2 http://steveblank.com/2014/03/18/get-the-heck-out-of-the-building-in-founde… and this: http://www.gv.com/lib/getting-out-of-the-building-isnt-enough

April 29, 2014

Re: [Pharo-dev] [Pharo-users] [Pharo3] New Sources file starting 30841/30842

by Sven Van Caekenberghe

On 29 Apr 2014, at 16:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 29 Apr 2014, at 15:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 29 Apr 2014, at 15:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> >>> On 29 Apr 2014, at 15:32, Robert Shiplett <grshiplett(a)gmail.com> wrote: >>> >>>> looked through 2 PDF's for "pharo.ini" and "sources" but did not find this mentioned ... it is probably staring right at me, since the image DID open... >>>> >>> >>> I never use windows. But I think it would be strange if the sources file would be referenced there. Makes no sense to me >>> (but as I said, never used windows since win 3.11) >> >> One thing I found is that the full zip releases (e.g. Pharo3.0-win.zip) do just have the V2 sourcesâ¦ fixing that now. >> > > This is fixed nowâ¦ > > Marcus I did a quick test on Windows 8.1 downloading http://files.pharo.org/platform/Pharo3.0-win.zip and it works perfectly ! Super. We're very close now.

April 29, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Sean P. DeNigris

Esteban A. Maringolo wrote > This is my point, who uses WebDAV as its file support? > It is a "workaround" to enable file based development. A VERY CLEVER > one, but still. A tool is always a layer of abstraction over the real model. I wouldn't say it's any more of a workaround than a System Browser is a workaround to enable source code based development instead of the real underlying bytecode model ;) But what I'm seeing in this conversation is a useful marketing path. What if we collected the most common objections to Smalltalk and worked on making the solutions easy and well-documented. We have the building blocks, but I mean packaging and explaining them from an outsiders point of view. For example, even though we Smalltalkers may not want to edit St code in emacs/vim (although I do miss the bindings - Igor, help we need that new text editor ha ha!), it might be a good investment to make sure it can be done easily in Pharo and prominently display that feature on the website. FAQ Q: Can I develop in my favorite text editor A: Yes! Choose "enable external editor" from the world menu... And maybe not even mention that developing outside the live, dynamic environment is not a good idea. Maybe that's the teddy bear they need to hold onto in a scary new world until they get comfortable and realize the power and advantage of giving that up for themselves. Same goes with Unix interop. REPL is easy, but is it documented and marketed? What would it take to easily pipe output of other programs to Pharo? Maybe be able to sourceCodeString exportAsUnixCommand: '/usr/bin/my_cool_command' We're usually do screencasts of "blue plane ideas that people don't even know they need". A series of "pink plane things that people are attached to, even if they would probably give them up if they grokked Smalltalk", but presented as serious how-tos, could really help us grow to critical mass. ----- Cheers, Sean -- View this message in context: http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4757055… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 29, 2014

Re: [Pharo-dev] [pharo-project/pharo-core]

by Eliot Miranda

Hi Marcus, On Apr 29, 2014, at 6:31 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 29 Apr 2014, at 15:29, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> Without any information on what has been changed these GitHub messages are almost pure noise. It's more than tedious to expect someone to follow the link to get more info. Can the system not include at least the commit comment? > > There are two mails: > > 1) useless > 2) it has *everything* > -> changed methods and classes > -> commit comments > -> Link to get the diffs very nicely formatted. > > Sadly we did not find a way to turn of this one useless mail. There is sadly no option. So who develops github? Are they willing to provide a third option? Another potential solution would be to direct the full commit to a server that filters/edits down the full messages and resends. Personally I'd like to keep up with the GitHub commits through email but right now I just delete them. I could filter them out but that's no better. :-( > >> Eliot (phone) >> >> On Apr 29, 2014, at 4:12 AM, GitHub <noreply(a)github.com> wrote: >> >>> Branch: refs/tags/30843 >>> Home: https://github.com/pharo-project/pharo-core > >

April 29, 2014

Re: [Pharo-dev] Amber-Pharo based coding dojo in a coworking space

by Norbert Hartl

Am 29.04.2014 um 15:22 schrieb Nicolas Petton <petton.nicolas(a)gmail.com>: > > Esteban Lorenzano writes: >>> Pharo being the front end , the IDE for amber, using Pharo to live code a website. That would be a very cool demo. Especially if Amber could leverage the Pharo debugger. >> >> Iâm trying to convince Nico to do that for *ages* but he does not sees >> the advantages/coolness of that approach. > > Esteban, > > That is just not true (and unfair). > > I in fact started a project called Nemo with Ben some time ago but my > time is limited just like everyone else. People have worked on it since > then, but AFAIK it's still far from being complete. > Who is people? Is it inside Inria? If not it might be a good idea to make it visible to the public so a few more people could chime in. Norbert

April 29, 2014

Re: [Pharo-dev] Amber-Pharo based coding dojo in a coworking space

by Esteban Lorenzano

On 29 Apr 2014, at 15:42, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > > On Apr 29, 2014, at 10:22 AM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: > >>> >>> Iâm trying to convince Nico to do that for *ages* but he does not sees >>> the advantages/coolness of that approach. >> >> Esteban, >> >> That is just not true (and unfair). >> >> I in fact started a project called Nemo with Ben some time ago but my >> time is limited just like everyone else. People have worked on it since >> then, but AFAIK it's still far from being complete. My bad. Iâm sorry. >> >> Cheers, >> Nico > > > sounds cool > > But we should address that problem, right? > > The only way I see is by throwing more talent on the problem > > Here is one thing that accelerates that process and catalyses everything and we are NOT doing: > > 1. workshops, barcamps, talks, breaking our faces shamelessly out there and taking notes on the feedback we hear and share with smalltalkers > 2. having regular hangouts to expand all that, wildly > > Here is another thing we can do: > > 1. stay like it is now and > 2. loose current talent > > If we take the first road we donât know what could happen > > If we take the second road, we know what will happen > > The problem is not being small, the problem is thinking small and preserving that attitude > > So the question is are we willing to review the things that weâre doing that arenât bringing the results we expect? and whatâs the action decided for next week? and the next? > >

April 29, 2014

Re: [Pharo-dev] Amber-Pharo based coding dojo in a coworking space

by Sebastian Sastre

On Apr 29, 2014, at 10:22 AM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: >> >> Iâm trying to convince Nico to do that for *ages* but he does not sees >> the advantages/coolness of that approach. > > Esteban, > > That is just not true (and unfair). > > I in fact started a project called Nemo with Ben some time ago but my > time is limited just like everyone else. People have worked on it since > then, but AFAIK it's still far from being complete. > > Cheers, > Nico sounds cool But we should address that problem, right? The only way I see is by throwing more talent on the problem Here is one thing that accelerates that process and catalyses everything and we are NOT doing: 1. workshops, barcamps, talks, breaking our faces shamelessly out there and taking notes on the feedback we hear and share with smalltalkers 2. having regular hangouts to expand all that, wildly Here is another thing we can do: 1. stay like it is now and 2. loose current talent If we take the first road we donât know what could happen If we take the second road, we know what will happen The problem is not being small, the problem is thinking small and preserving that attitude So the question is are we willing to review the things that weâre doing that arenât bringing the results we expect? and whatâs the action decided for next week? and the next?

April 29, 2014