- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by Sebastian Sastre

On Oct 10, 2014, at 11:16 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > sebastian(a)flowingconcept.com wrote >> Your thoughts and further questions are welcomed > > "How does it compare to Tide" seems like a popular question ;) > Card for that here: https://trello.com/c/nCzIHxc9/49-how-does-it-flow-compare-to-tide > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ANN-flow-a-living-full-stack-framework-for-the-web-tp… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 10, 2014

Re: [Pharo-dev] OSProcess in 3.0

by David T. Lewis

> 2014-10-10 14:09 GMT+02:00 David T. Lewis <lewis(a)mail.msen.com>: > >> >> Right. But please do test it in your applications to be sure, I really >> only >> did simple testing and I am sure there may still chances for problems in >> this area. >> > > Hi Dave, > > Would it has a chance of slowing down things a lot? > > There is apparently something going very very slow compared to OSProcess > 4.5.11 when used from GitFileTree. So slow that I killed the image > building > script before it was over. Reverting GitFileTree to 4.5.11 solved it. > I don't this so, but I am not certain. The update for PipeableOSProcess affects only the methods in PipeableOSProcess class>>command: and closely related methods. If GitFileTree is using that idiom, then it is certainly possible that I have introduced a bug that does not show up in my unit tests. > The absence of the AioPlugin warning may also be problematic, since it > appears on stdout or stderr when Pharo is used on the command line. > Yes I should get rid that annoyance. Thanks, Dave > Thierry > > >> >> > >> > Also, I see that there is apparently no AioPlugin support in Pharo >> 3.0. >> Or >> > so say the tests of OSProcess. >> > >> > What is the state of affairs there? >> > >> >> Ask someone to include AioPlugin in the VM builds. >> >> Dave >> >> >> >

Oct. 10, 2014

Re: [Pharo-dev] OSProcess in 3.0

by phil＠highoctane.be

Yes, the AioPlugin warning is annoying. The lack of it also, for a number of use cases I am currently on. Phil On Fri, Oct 10, 2014 at 5:04 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2014-10-10 14:09 GMT+02:00 David T. Lewis <lewis(a)mail.msen.com>: > >> >> Right. But please do test it in your applications to be sure, I really >> only >> did simple testing and I am sure there may still chances for problems in >> this area. >> > > Hi Dave, > > Would it has a chance of slowing down things a lot? > > There is apparently something going very very slow compared to OSProcess > 4.5.11 when used from GitFileTree. So slow that I killed the image building > script before it was over. Reverting GitFileTree to 4.5.11 solved it. > > The absence of the AioPlugin warning may also be problematic, since it > appears on stdout or stderr when Pharo is used on the command line. > > Thierry > > >> >> > >> > Also, I see that there is apparently no AioPlugin support in Pharo 3.0. >> Or >> > so say the tests of OSProcess. >> > >> > What is the state of affairs there? >> > >> >> Ask someone to include AioPlugin in the VM builds. >> >> Dave >> >> >> >

Oct. 10, 2014

Re: [Pharo-dev] OSProcess in 3.0

by Thierry Goubier

2014-10-10 14:09 GMT+02:00 David T. Lewis <lewis(a)mail.msen.com>: > > Right. But please do test it in your applications to be sure, I really only > did simple testing and I am sure there may still chances for problems in > this area. > Hi Dave, Would it has a chance of slowing down things a lot? There is apparently something going very very slow compared to OSProcess 4.5.11 when used from GitFileTree. So slow that I killed the image building script before it was over. Reverting GitFileTree to 4.5.11 solved it. The absence of the AioPlugin warning may also be problematic, since it appears on stdout or stderr when Pharo is used on the command line. Thierry > > > > > Also, I see that there is apparently no AioPlugin support in Pharo 3.0. > Or > > so say the tests of OSProcess. > > > > What is the state of affairs there? > > > > Ask someone to include AioPlugin in the VM builds. > > Dave > > >

Oct. 10, 2014

Re: [Pharo-dev] https://ci.inria.fr/pharo-contribution down

by Yuriy Tymchuk

Up now. Thanks :) > On 10 Oct 2014, at 16:54, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Can someone restart it? >

Oct. 10, 2014

https://ci.inria.fr/pharo-contribution down

by Yuriy Tymchuk

Can someone restart it?

Oct. 10, 2014

Re: [Pharo-dev] About ways to participate in community and general negativity

by Tim Mackinnon

Hi guys - this was an interesting thread - and exactly the reason why I brought up âZapp Empowermentâ at ESUG this year. I felt the passion from every single one of you - and in fact, everyone had an interesting point to make. I got a bit nervous as I worked up the 40+ replies, but I was pleased that no-one seemed to take great offence as we covered a wide range of related ideas. If I could make one small comment - sometimes I think the gems in a reply can easily get lost if you donât pay special attention to how the person(s) reading it might react. I think we all agree that we do like this community and the amazing work it has done (and continues to do) - and so its worth acknowledging someoneâs ideas and then building on them. If you disagree with them however - try acknowledging what they have said and then suggest that there is an equally valid point of view/idea that they can also consider. But Iâm also glad we arenât afraid to cover difficult conversations. I do think we can all practice giving and receiving feedback in a way that can keep the energy high. Personally I really like that many of the old things are being modernised (GT Inspector blew me away - as it has done for colleagues who donât even use Smalltalk). Equally, finding a way to get some community input via a survey/vote sounds quite interesting to prioritise a few things (possibly not for everything - as we are asking people to invest their spare time and energy on a labor of love - so we should go where the energy is). Equally, anything we can do to help keep the engineering high is equally appreciated - and I have seen it get better and better over the years. Tim On 3 Oct 2014, at 12:44, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > Iâm writing this because Iâm sad about what is happening in this list. > Iâm seeing a lot of general negativity and non constructive ways to discuss things. > Iâm also seeing more and more people using Pharo for their particular interests (which is of course a good thing) but less and less people who contribute back to Pharo. > Finally, Iâm seeing more frequently an attitude of âcustomerâ, more than the conviction than this, Pharo, is also yoursâ¦ > > Please people, we (the pharo âcoreâ team) cannot do everything. We do not have the manpower or the resources to hire manpower. We would like, but we just do not have the resources (is already a blessing that we can work on this, for now: INRIA is paying, but what it pays is *research*, not âpharo the languageâ, so this is a collateral advantageâ¦.) > > So, having an OPEN SOURCE project, with limited resources means that there is a lot of things that depend on the community. > It depends on the community not just to fix, but to enlarge the ecosystem in general too. > > So, I refuse to believe that we cannot be a cool and helpful community. > I refuse to believe that general negativity and bad humor can overcome the joy of participating in this collective effort. > > So, here some recommendations for enhance the way we participate: > > - Be positive. Just âthis is a s**tâ does not help. Even if it is. > - Be propositional. Just âthis is a s**tâ, and not telling what you want/prefer does not help. > - Be proactive. Just âthis is a s**tâ, and not report, discuss and (at least time to time) provide a fix/enhancement does not help. > > In conclusion: not helping does not help :) > After all, this is the âpharo-devâ list. I mean, the list of people wanting to participate from this great, community effort. > > cheers, > Esteban, still grateful of belonging to this community > > >

Oct. 10, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by Sean P. DeNigris

sebastian(a)flowingconcept.com wrote > Your thoughts and further questions are welcomed "How does it compare to Tide" seems like a popular question ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-flow-a-living-full-stack-framework-for-the-web-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 10, 2014

Re: [Pharo-dev] Some methods missing in Behavior

by Marcus Denker

> On 10 Oct 2014, at 14:36, jdelgado(a)lsi.upc.edu wrote: > > Yes, evaluate: > > (Behavior new) compile: 'thisIsATest ^2' > > ah, that indeed should workâ¦ I will check and fix it in Pharo3 and Pharo4 Marcus

Oct. 10, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by Sebastian Sastre

And now following Sven suggestion, thanks Sven!, Iâve published here is the first post about flow In this I set the starting point, showing reception and mission and starting the conversation on next steps https://medium.com/@sebastianconcpt/flow-a-living-full-stack-framework-for-… Your thoughts and further questions are welcomed On Oct 6, 2014, at 4:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 06 Oct 2014, at 07:43, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > >> The links has the step by step. I am running it as I type.. > > Yeah, put that is more a setup guide, it end by saying 'and now you are ready to build your app', that is the part that I am interested in. > > Maybe a simplified Reddit clone, like in https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 - this would be ideal, since we could then compare things better. > > Sven

Oct. 10, 2014