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

Re: [Pharo-dev] Peek

by Sven Van Caekenberghe

Hi Diego, Streams as they are currently defined, especially ReadStreams, can hardly be called IO streams. Many operations assume that there is a single collection over which you can move in any direction without restrictions. As a consequence most parsing code relies this ability, looking forward and going back multiple times, like using #skip: with a negative argument. Real IO ReadStreams like a SocketStreams or FileStreams cannot be assumed to keep more than just a buffer in memory, hence the unrestricted operations are not implementable. IMO, parsing code should be written against a much more restricted API, assuming at most a one element peek/buffer. I always try to do that, I even have Mock ReadStreams that ensure this. While benchmarking I have also found that slow #peek behaviour can be a bottleneck, especially on some of the more complex streams. Sven PS: Have a look at ZnCharacterReadStream for example, which implements this restricted behaviour: it is not positionable, but allows a one character peek using a one character internal buffer. On 04 Nov 2013, at 09:57, Diego Lont <diego.lont(a)delware.nl> wrote: > Working on Petit Delphi we found a strange implementation for asPetitStream: > Stream>asPetitStream > ^ self contents asPetitStream > > Further investigation showed that the basic peek was not fast enough for Petit Parser, as it is used a lot. So it implemented a "improved unchecked peek": > PPStream>peek > "An improved version of peek, that is slightly faster than the built in version." > ^ self atEnd ifFalse: [ collection at: position + 1 ] > > PPStream>uncheckedPeek > "An unchecked version of peek that throws an error if we try to peek over the end of the stream, even faster than #peek." > ^ collection at: position + 1 > > But in my knowledge a basic peek should be fast. The real problem is the peek in the underlying peek: > PositionableStream>peek > "Answer what would be returned if the message next were sent to the > receiver. If the receiver is at the end, answer nil." > > | nextObject | > self atEnd ifTrue: [^nil]. > nextObject := self next. > position := position - 1. > ^nextObject > > That actually uses "self next". The least thing one should do is to cache the next object. But isn't there a primitive for peek in a file stream? Because al overriding peeks of PositionableStream have basically the same implementation: reading the next and restoring the state to before the peek (that is slow). So we would like to be able to remove PPStream without causing performance issues, as the only added method is the "improved peek". > > Stephan and Diego

Nov. 4, 2013

Re: [Pharo-dev] Feature request poll

by kilon alios

I agree too, at worse this poll will show that Pharo is not abandonware and a community that takes seriously popular feature requests. I would also love to see a progress bar per feature request or WIP features. I am not talking here 100 features, even 10 will be enough to say that we are moving forward. In irc I had several people pop in asking why pharo chose smalltalk and is it not smalltalk "dead" etc ? So definetly this could help kick the smalltalk stereotype from the mind of newcomers and show them we are not big, but none the less quite active and open minded community. On Mon, Nov 4, 2013 at 10:52 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 04 Nov 2013, at 09:41, Norbert Hartl <norbert(a)hartl.name> wrote: > > > I don't think our community ever lacked of ideas. It is primarily > time/contributed work that is missing. > I think that you are right on this. Thatâs why I think we need this ideas > portal. So all the ideas are collected in one place and you can spot and > when someone has time to contribute ha can check what ideas have the most > amount of votes, etcâ¦ > > Uko > > > It is too easy to have a quick opinion that is based only on my current > mood. Should these guide the future development of pharo? That could do > more harm than it helps. > > Nevertheless nice idea ;) > > > > Norbert > > > >> Am 04.11.2013 um 09:19 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > >> > >> 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] Github and Pharo

by kilon alios

I can document this , but not before I get really familiar with the process. Also I have not forgotten my promise to document Nativeboost, expect a blog post about that really soon. I tried to use this in windows and I get a failure ExternalWindowsOSProcess class(Object)>>doesNotUnderstand: #defaultShellPath PipeableOSProcess class>>command:environment:workingDir:input:output:error:errorPipelineStream:shellSyntax: PipeableOSProcess class>>command:environment:workingDir:input:output:error:errorPipelineStream: PipeableOSProcess class>>command: MCFileTreeGitRepository>>gitVersions MCFileTreeGitRepository>>loadAncestry MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... BlockClosure>>cull: Job>>run in Block: [ result := block cull: self ] BlockClosure>>on:do: Job>>run in Block: [ ... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MCFileTreeGitRepository>>loadAllFileNames MCFileTreeGitRepository>>allFileNames MCFileTreeGitRepository>>readableFileNames MCFileTreeGitRepository>>packageDescriptionsFromReadableFileNames MCFileTreeGitRepository(MCFileBasedRepository)>>retrieveVersionsWithPackageNames: MCFileTreeGitRepositoryInspector(MCFileRepositoryInspector)>>refresh MCFileTreeGitRepositoryInspector(MCFileRepositoryInspector)>>setRepository:workingCopy: in Block: [ ... BlockClosure>>newProcess in Block: [ ... I have loaded both OSProcess and OSWindows , are there other dependencies on Windows I need to load ? On Mon, Nov 4, 2013 at 6:46 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Exactly. This would be a valuable contribution. Screencasts would be very > helpful as well. > > Doru > > > > > On Mon, Nov 4, 2013 at 12:04 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> one of you should write a blog entry on Git support and the process :) >> Because we will get this repeat that often. >> >> Stef >> >> >> >> On Nov 3, 2013, at 2:11 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >> >> ok it was my bad, i had not correctly initialized my git repo. Now it >> works fine. Thanks for the help this awesome. >> >> >> On Sun, Nov 3, 2013 at 2:56 PM, kilon alios <kilon.alios(a)gmail.com>wrote: >> >>> I installed OSProcess but I get a new Error : Git Error : bad default >>> revision 'Head' >>> >>> just to clarify i try to commit to an existing git repo that I have >>> create manually via terminal. >>> >>> >>> MCFileTreeGitRepository(Object)>>error: >>> MCFileTreeGitRepository>>gitVersions >>> MCFileTreeGitRepository>>loadAncestry >>> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCFileTreeGitRepository>>loadAllFileNames >>> MCFileTreeGitRepository>>allFileNames >>> MCFileTreeGitRepository>>readableFileNames >>> >>> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >>> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >>> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >>> BlockClosure>>cull: >>> Job>>run in Block: [ result := block cull: self ] >>> BlockClosure>>on:do: >>> Job>>run in Block: [ ... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> ByteString(String)>>displayProgressFrom:to:during: >>> MCWorkingCopy>>uniqueVersionNameIn: >>> MCWorkingCopy>>newVersionIn: >>> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >>> WorldState>>runStepMethodsIn: >>> >>> >>> >>> On Sun, Nov 3, 2013 at 2:40 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr>wrote: >>> >>>> Oh sorry, the OSProcess dependency is missing :( >>>> >>>> You can install OSProcess from the configuration browser in your Pharo >>>> image or, on the command line : >>>> >>>> $ pharo Pharo.image config >>>> http://ss3.gemstone.com/ss/MetaRepoForPharo20 ConfigurationOfOSProcess >>>> --install=stable >>>> >>>> Thierry >>>> >>>> ------------------------------ >>>> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de >>>> kilon alios [kilon.alios(a)gmail.com] >>>> *Date d'envoi :* dimanche 3 novembre 2013 13:30 >>>> >>>> *Ã :* Pharo Development List >>>> *Objet :* Re: [Pharo-dev] Github and Pharo >>>> >>>> look like it cant find PipeableOSProcess on Macos, any idea where I >>>> can find this object ? >>>> >>>> UndefinedObject(Object)>>doesNotUnderstand: #command: >>>> MCFileTreeGitRepository>>gitVersions >>>> MCFileTreeGitRepository>>loadAncestry >>>> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >>>> BlockClosure>>cull: >>>> Job>>run in Block: [ result := block cull: self ] >>>> BlockClosure>>on:do: >>>> Job>>run in Block: [ ... >>>> BlockClosure>>ensure: >>>> Job>>run >>>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>>> ByteString(String)>>displayProgressFrom:to:during: >>>> MCFileTreeGitRepository>>loadAllFileNames >>>> MCFileTreeGitRepository>>allFileNames >>>> MCFileTreeGitRepository>>readableFileNames >>>> >>>> MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: >>>> MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: >>>> MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... >>>> BlockClosure>>cull: >>>> Job>>run in Block: [ result := block cull: self ] >>>> BlockClosure>>on:do: >>>> Job>>run in Block: [ ... >>>> BlockClosure>>ensure: >>>> Job>>run >>>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>>> ByteString(String)>>displayProgressFrom:to:during: >>>> MCWorkingCopy>>uniqueVersionNameIn: >>>> MCWorkingCopy>>newVersionIn: >>>> MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... >>>> WorldState>>runStepMethodsIn: >>>> >>>> >>>> >>>> On Sun, Nov 3, 2013 at 12:41 PM, GOUBIER Thierry < >>>> thierry.goubier(a)cea.fr> wrote: >>>> >>>>> This is where you use GitFileTree. >>>>> >>>>> GitFileTree will do you the commit, browsing the git logs and >>>>> accessing all versions of your package in the git repo (browsing, loading, >>>>> changes with the same GUI and look as a smalltalkhub repo). It won't do the >>>>> push, however(*). It will show you the current branch in the repo too (**). >>>>> >>>>> For pharo3, GitFileTree is available with: >>>>> >>>>> $ pharo Pharo.image eval --save Gofer new url: \' >>>>> http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main\'\; >>>>> package: \'MonticelloFileTree-Git\'\; load >>>>> >>>>> For pharo2, there is a group named 'MonticelloFileTree-Git' in >>>>> FileTree configuration. >>>>> >>>>> Feel free to ask if you have any questions or suggestions on it! >>>>> >>>>> Thierry >>>>> >>>>> (*) It would be easy to do commit + push in one go, but, I'm not sure >>>>> I'd like to do a push each time I do a commit. I tend to prefer a push a >>>>> day. Maybe something like a marker in the repository inspector to remind me >>>>> I have something to push? >>>>> (**) It doesn't change branches, and there is no support for branches >>>>> in Monticello... This tend to trigger bugs in MC package cache. >>>>> >>>>> ------------------------------ >>>>> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de >>>>> kilon alios [kilon.alios(a)gmail.com] >>>>> *Date d'envoi :* dimanche 3 novembre 2013 10:16 >>>>> *Ã :* Pharo Development List >>>>> *Objet :* Re: [Pharo-dev] Github and Pharo >>>>> >>>>> Thank you for your efforts , I have installed filetree using the >>>>> instructions provided in the github pages for pharo 3. I was also >>>>> successful into generating the local files for my packages that I have >>>>> inserted to my git folder. I can manually git commit and git push them from >>>>> terminal but how I do this from inside Monticello-Filetree ? >>>>> >>>>> >>>>> On Sun, Nov 3, 2013 at 9:53 AM, GOUBIER Thierry < >>>>> thierry.goubier(a)cea.fr> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I've used github and work_owned git repositories as primary >>>>>> workplaces for more than a year. First with FileTree, then I wrote >>>>>> GitFileTree to make that process simpler. >>>>>> >>>>>> Thierry >>>>>> ------------------------------ >>>>>> *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de >>>>>> kilon alios [kilon.alios(a)gmail.com] >>>>>> *Date d'envoi :* samedi 2 novembre 2013 14:59 >>>>>> *Ã :* Pharo Development List >>>>>> *Objet :* [Pharo-dev] Github and Pharo >>>>>> >>>>>> So any information on how Pharo can be used with Github ? >>>>>> >>>>>> all I have is this >>>>>> >>>>>> https://github.com/dalehenrich/FSGit >>>>>> >>>>>> I dont need much, just basic git pull, push, clone, add and rm >>>>>> should do fine for starter. >>>>>> >>>>>> But of course I am interesting into learning what can be done, what >>>>>> is available , who needs help with what. Github is something really >>>>>> important for me, so I am willing to contribute as much I can into bringing >>>>>> Pharo closer to it. >>>>>> >>>>>> My interest is using Github in place of smalltalkhub and >>>>>> squeaksource. I was planning to implement something like an App Store (not >>>>>> the purchase system) for Pharo libraries and I would love to use github >>>>>> as a backend to it and git of course. >>>>>> >>>>> >>>>> >>>> >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 4, 2013

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

by Stephan Eggermont

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: Put out CFP for FOSDEM2014 devroom Lots of improvements to PetitDelphi http://www.flickr.com/photos/35787002@N03/sets/72157634356004836/ First step in making QCMagritte use new Bootstrap ### What's next, until 2013-11-17 (*): Handling of compiler directives for PetitDelphi, first ifdefs and includes Still a lot of parse errors to fix Diego & Stephan

Nov. 4, 2013

Peek

by Diego Lont

Working on Petit Delphi we found a strange implementation for asPetitStream: Stream>asPetitStream ^ self contents asPetitStream Further investigation showed that the basic peek was not fast enough for Petit Parser, as it is used a lot. So it implemented a "improved unchecked peek": PPStream>peek "An improved version of peek, that is slightly faster than the built in version." ^ self atEnd ifFalse: [ collection at: position + 1 ] PPStream>uncheckedPeek "An unchecked version of peek that throws an error if we try to peek over the end of the stream, even faster than #peek." ^ collection at: position + 1 But in my knowledge a basic peek should be fast. The real problem is the peek in the underlying peek: PositionableStream>peek "Answer what would be returned if the message next were sent to the receiver. If the receiver is at the end, answer nil." | nextObject | self atEnd ifTrue: [^nil]. nextObject := self next. position := position - 1. ^nextObject That actually uses "self next". The least thing one should do is to cache the next object. But isn't there a primitive for peek in a file stream? Because al overriding peeks of PositionableStream have basically the same implementation: reading the next and restoring the state to before the peek (that is slow). So we would like to be able to remove PPStream without causing performance issues, as the only added method is the "improved peek". Stephan and Diego

Nov. 4, 2013

Re: [Pharo-dev] Feature request poll

by Yuriy Tymchuk

On 04 Nov 2013, at 09:41, Norbert Hartl <norbert(a)hartl.name> wrote: > I don't think our community ever lacked of ideas. It is primarily time/contributed work that is missing. I think that you are right on this. Thatâs why I think we need this ideas portal. So all the ideas are collected in one place and you can spot and when someone has time to contribute ha can check what ideas have the most amount of votes, etcâ¦ Uko > It is too easy to have a quick opinion that is based only on my current mood. Should these guide the future development of pharo? That could do more harm than it helps. > Nevertheless nice idea ;) > > Norbert > >> Am 04.11.2013 um 09:19 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >> 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 Norbert Hartl

I don't think our community ever lacked of ideas. It is primarily time/contributed work that is missing. It is too easy to have a quick opinion that is based only on my current mood. Should these guide the future development of pharo? That could do more harm than it helps. Nevertheless nice idea ;) Norbert > Am 04.11.2013 um 09:19 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > > 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

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30546 Home: https://github.com/pharo-project/pharo-core

Nov. 4, 2013

[pharo-project/pharo-core] b9350c: 30546

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: b9350cb501d63bc764ddf6ac110d7f53977a798a https://github.com/pharo-project/pharo-core/commit/b9350cb501d63bc764ddf6ac… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-04 (Mon, 04 Nov 2013) Changed paths: M Fuel.package/extension/LargeNegativeInteger/instance/fuelAccept_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/beginTestCase_time_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/endTestCase.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/stackTraceString_of_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/writeError_stack_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/writeFailure_stack_.st M HudsonBuildTools20.package/HDTestReport.class/instance/running/setUp.st M HudsonBuildTools20.package/HDTestReport.class/instance/running/tearDown.st M Morphic-Base.package/TextAnchor.class/instance/visiting/emphasizeScanner_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script201.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30546.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30546 12052 Fuel could store LargeNegativeInteger up to 32bits magnitude https://pharo.fogbugz.com/f/cases/12052 12067 A TextAnchor should never try to placeEmbeddedObject: by itself https://pharo.fogbugz.com/f/cases/12067 11906 HDTestReport measures the wrong duration https://pharo.fogbugz.com/f/cases/11906 http://files.pharo.org/image/30/30546.zip

Nov. 4, 2013

Re: [Pharo-dev] Feature request poll

by Norbert Hartl

> Am 04.11.2013 um 09:15 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > >> 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" > +1 Gets more important every day as I don't find time for contributing. Norbert

Nov. 4, 2013