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

Re: [Pharo-dev] Feature request poll

by Yuriy Tymchuk

I think that if we want to have it, we have to make something simple with an option to create ideas and simple voting. If it will be used then we can extend it. Uko On 04 Nov 2013, at 09:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 04 Nov 2013, at 09:04, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> >> On 2013-11-04, at 08:56, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> >>>> Am 04.11.2013 um 00:26 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >>>> >>>> Hi everyone, >>>> >>>> Iâve just got an idea (not something extra ordinary) to try out. Maybe we can make some kind of poll where community will be able to add new feature requests and vote for them. This way we can get an idea what is important to most of people. Eg. see how many votes are for the stateful traits and how many for the ability to quit image without prompt for saving. After writing last sentence Iâve figured out that itâs a good idea to be able also to vote down :) >>>> >>>> But I think that this can be a nice experiment. Also as we are promoting and idea that âPharo is made by youâ, then new feature poll is nice to have. >>> >>> I have this gut feeling there should something around three levels of acknowledgement: >>> >>> - I like it >>> - I need it really >>> - I like or need it and will spend time doing it >> >> yes, the "I am willing to contribute" is important! > > or even, âI am willing to pay" > >

Nov. 4, 2013

Re: [Pharo-dev] Feature request poll

by Sven Van Caekenberghe

On 04 Nov 2013, at 09:04, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-11-04, at 08:56, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> >>> Am 04.11.2013 um 00:26 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >>> >>> Hi everyone, >>> >>> Iâve just got an idea (not something extra ordinary) to try out. Maybe we can make some kind of poll where community will be able to add new feature requests and vote for them. This way we can get an idea what is important to most of people. Eg. see how many votes are for the stateful traits and how many for the ability to quit image without prompt for saving. After writing last sentence Iâve figured out that itâs a good idea to be able also to vote down :) >>> >>> But I think that this can be a nice experiment. Also as we are promoting and idea that âPharo is made by youâ, then new feature poll is nice to have. >> >> I have this gut feeling there should something around three levels of acknowledgement: >> >> - I like it >> - I need it really >> - I like or need it and will spend time doing it > > yes, the "I am willing to contribute" is important! or even, âI am willing to pay"

Nov. 4, 2013

Re: [Pharo-dev] Feature request poll

by Camillo Bruni

On 2013-11-04, at 08:56, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 04.11.2013 um 00:26 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >> Hi everyone, >> >> Iâve just got an idea (not something extra ordinary) to try out. Maybe we can make some kind of poll where community will be able to add new feature requests and vote for them. This way we can get an idea what is important to most of people. Eg. see how many votes are for the stateful traits and how many for the ability to quit image without prompt for saving. After writing last sentence Iâve figured out that itâs a good idea to be able also to vote down :) >> >> But I think that this can be a nice experiment. Also as we are promoting and idea that âPharo is made by youâ, then new feature poll is nice to have. > > I have this gut feeling there should something around three levels of acknowledgement: > > - I like it > - I need it really > - I like or need it and will spend time doing it yes, the "I am willing to contribute" is important!

Nov. 4, 2013

Re: [Pharo-dev] WhatsUp from: 2013-11-04 until: 2013-11-17

by Camillo Bruni

On 2013-11-04, at 07:00, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: Automatic Issue Validation: --------------------------- stable release ahead, 1 failing test left (only under headless linux): - fancy twitter bootstrap based reports - simplified command line reporter - exceptions are reported with stack traces - merge conflicts are listed in detail with a diff - lint rules are shown with their descriptions and the list of problematic elements (methods / classes) - test failures still need some more love (missing stack trace for example) ImageWorker: ------------ To make the issue validation work, we have to run blocks in a separate image. For instance to load a slice, we do not want to pollute the main image, since we cannot guarantee anything. The ImageWorker takes care of this and spawns a new image with OSProcess: ImageWorker do: [ ... ] Additionally, if an error happens in the remote image, the error is passed back to the main image and resignaled locally: ImageWorker do: [ 1/0 ] This allows for a very natural interaction, as the remotely evaluated blocks behave almost like local ones.

Nov. 4, 2013

Re: [Pharo-dev] Feature request poll

by Norbert Hartl

> Am 04.11.2013 um 00:26 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > > Hi everyone, > > Iâve just got an idea (not something extra ordinary) to try out. Maybe we can make some kind of poll where community will be able to add new feature requests and vote for them. This way we can get an idea what is important to most of people. Eg. see how many votes are for the stateful traits and how many for the ability to quit image without prompt for saving. After writing last sentence Iâve figured out that itâs a good idea to be able also to vote down :) > > But I think that this can be a nice experiment. Also as we are promoting and idea that âPharo is made by youâ, then new feature poll is nice to have. I have this gut feeling there should something around three levels of acknowledgement: - I like it - I need it really - I like or need it and will spend time doing it Norbert

Nov. 4, 2013

https://gitorious.org/cogvm

by Camillo Bruni

I cannot update the repository description on gitorious: https://gitorious.org/cogvm Who is in charge of the cogvm project on gitorious? Can the owner please add a link to the new github repository? #Moved to <http://github.com/pharo-project/pharo-vm>

Nov. 4, 2013

Re: [Pharo-dev] About BitBlt current -> BitBlt (Fuel)

by Max Leske

Did #hackBits: come with Fuel? Itâs not an extension methodâ¦ On 04.11.2013, at 01:10, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Indeed. That's why I want to move it to a separate class. > > > On Fri, Nov 1, 2013 at 5:18 PM, Max Leske <maxleske(a)gmail.com> wrote: > Wowâ¦ Form is mindnumbingâ¦ > > > On 30.10.2013, at 23:00, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> hehehe sorry, it was #hackBits: :) >> >> >> On Wed, Oct 30, 2013 at 6:52 PM, Max Leske <maxleske(a)gmail.com> wrote: >> Where did you find that method? I couldnât find any implementors or referencesâ¦ >> >> On 30.10.2013, at 21:42, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >>> BTW....it is time to move the hashBits: to a more general class....but the question is where? >>> >>> >>> On Wed, Oct 30, 2013 at 6:21 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Fuel was using BitBlt current and I change that to BitBlt >>> >>> Stef >>> >>> On Oct 29, 2013, at 10:55 AM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> > Stef, what exactly is the influence on Fuel? I looked at the changes of your slice and couldnât find anythingâ¦ >>> > >>> > Max >>> > >>> > >>> > On 25.10.2013, at 16:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> > >>> >> Hi >>> >> >>> >> I just pushed a change cleaning some strange usage. >>> >> BitBlt was sometimes invoked via BitBlt current (which just returned the BitBlt class). >>> >> Apparently in Squeak they removed it too. >>> >> >>> >> Now it touches Fuel so Fuel guys can you merge on your side too? >>> >> >>> >> https://pharo.fogbugz.com/f/cases/12009/BitBlt-current-BitBlt >>> >> >>> >> Stef >>> > >>> > >>> >>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com

Nov. 4, 2013

Re: [Pharo-dev] Fuel: fix for Squeak trunk

by Max Leske

Good idea. What would we put there? I canât think of anything else than globalsâ¦ If globals is the only thing then Iâm not sure that itâs worth the effort. Max On 04.11.2013, at 01:04, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > I would love a quick and easy refactor in which we add a FLSmalltalkPlatform with some utility methods such as #globals. Then concrete subclasses like FLPharoPlatform which implements #globals in our current way. That refactor would be quite easy and useful. I don't want to add Grease or whatever layer.. but just very concrete examples like this one. > Thoughts? > > > On Sat, Nov 2, 2013 at 12:46 PM, Max Leske <maxleske(a)gmail.com> wrote: > Thanks Nicolas, weâll take a look at it. > > Max > > > On 02.11.2013, at 14:43, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> I've opened https://code.google.com/p/fuel/issues/detail?id=204 with an attachment >> >> Also note https://pharo.fogbugz.com/f/cases/12052/Fuel-could-store-LargeNegativeInteg… >> >> >> 2013/11/2 Max Leske <maxleske(a)gmail.com> >> So far we donât have a public inbox and Iâm not too familiar with STHub and read/write permissions. Concerning your suggestion from the other thread a public inbox would certainly make sense though. >> Iâll let you know what we can come up with (STHub seems to be down right now so I canât even give you access right now. But you can send me your fix through mail). >> >> Max >> >> On 02.11.2013, at 09:46, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> Thanks, and is there a public .mcz inbox, or does it require special rights? >>> >>> >>> 2013/11/2 Max Leske <maxleske(a)gmail.com> >>> The Fuel bug tracker is hosted by Google: https://code.google.com/p/fuel/ >>> >>> On 01.11.2013, at 22:42, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> > I have an easy fix for Fuel on Squeak trunk. >>> > It concerns the FuelCompatibility layer, so I hesitate to publish on Pharo fogbugz... >>> > Is there a dedicated bug tracker? >>> > What is the preferred procedure? >>> > >>> > Nicolas >>> >>> >>> >> >> > > > > > -- > Mariano > http://marianopeck.wordpress.com

Nov. 4, 2013

Re: [Pharo-dev] [update 3.0] #30545

by Camillo Bruni

On 2013-11-04, at 03:36, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > StÃ©phane Ducasse wrote >> Issue 12066: Add Image support in Spec >> https://pharo.fogbugz.com/f/cases/12066/Add-Image-support >> Thanks Benjamin van Ryseghem and Sergi Reyner >> ... >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Examples-StephaneDucasse… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-MorphicAdapters-Stephane… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-StephaneDucasse.196… > > It would be great to improve this template. Issue 12066 sounds interesting, > but: > 1. there is no use case, steps to reproduce, etc. in the issue > 2. The links all require login (would be better to link to Penelope for our > wider audience, and core members who may not be able to log in e.g. using a > public computer) > 3. The diffs are not separated by issue. We have to guess where to look > 4. The diffs I guessed did not even exist > > All this presents a pretty high barrier to follow improvements (which is a > much better problem then not improving!!)... ... that's why there's the github diff :P

Nov. 4, 2013

Re: [Pharo-dev] Feature request poll

by Yuriy Tymchuk

On 04 Nov 2013, at 07:40, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > We had this idea with Marcus, and I think itâs nice :) > > What would fit in that is if n gold-members vote for an issue as âweek fixedâ then itâs automatically integrated :) Yes, true. But my idea was originally oriented on bigger scales. For example to see that community wantâs traits improvements over git integration, or vice versa. I think that Jet Brains has something like that. Uko > > Ben > > On 04 Nov 2013, at 00:26, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Hi everyone, >> >> Iâve just got an idea (not something extra ordinary) to try out. Maybe we can make some kind of poll where community will be able to add new feature requests and vote for them. This way we can get an idea what is important to most of people. Eg. see how many votes are for the stateful traits and how many for the ability to quit image without prompt for saving. After writing last sentence Iâve figured out that itâs a good idea to be able also to vote down :) >> >> But I think that this can be a nice experiment. Also as we are promoting and idea that âPharo is made by youâ, then new feature poll is nice to have. >> >> Cheers. >> Uko >

Nov. 4, 2013