May 2017 - Pharo-dev - lists.pharo.org

Git, FileTree/Cypress, missing Traits comments

by Ben Coman

Is this of concern for Pharo...? "Pull requests on GitHub where the Trait comments get removed (because they were not loaded with the package in the first place)." http://forum.world.st/Re-The-Inbox-System-jr-919-mcz-td4941798.html#none http://forum.world.st/The-Inbox-System-jr-919-mcz-td4933985.html cheers -ben

May 21, 2017

Re: [Pharo-dev] QualityImprovements assured by tests

by Yuriy Tymchuk

I think that the most important question is: did we integrate some code with these issues in pharo 6? Because definitely everyone is lazy to go and fix issues, but we should not integrate the new ones (especially when we have monkey checking that stuff). Uko > On 20 May 2017, at 14:13, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I agree with you. > This is why I worked on the auto categoriser. then I improve the categorizer inside the image. > Now I have a tool to analyse the categories but no time and I did not want to break everything > but we could push some rules. > > if people would have published slices on such issues I'm quite sure that we would have integrated them, now the question > is that it takes time and we were focused on other urgent tasks. > > Stef > > > On Sat, May 20, 2017 at 12:25 AM, Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: > Hi, > > One year later we are close to a final release for Pharo 6 and either with Pharo 6 or upcoming Pharo 7 > I would really like to see some checks that ensure a quality image and tests who keep us all more > disciplined in the future. > > Because: > > 1. We should not have undocumented classes: > > (Object allSubclasses select: [:cls| cls hasComment not ]) > > but we have a lot in Pharo 6 now since we introduced new packages in this release iteration > > 2. We should not have class instance variables in uppercase but: > > (Object allSubclasses select: [:cls| cls isMeta]) select: [:cls| cls > instVarNames anySatisfy: [:n | n first isUppercase]] > > is not empty - although this was already discussed back in 2008 (!), see > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2008-November/00… <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2008-November/00…> > > 3. We should not have uncategorized methods but: > > (Object allSubclasses select: [:cls| (cls selectorsInProtocol: Protocol unclassified) notEmpty ]) > > we still have them. > > 4. I've seen methods with unused temporary variables. Dont know about unused ivars or other. > > 5. add you own here ... > > I know this is often boring to comment or categorize - but we should do our homework as we wanted to > better compared to the past. Also if the base image is not following rules how should we expect others > to provide quality packages on top of it? > > IMHO we should raise the bar. Either in Pharo 6 or in early Pharo 7. We can fix these once and for > all AND assure with unit tests that we keep the standard image on this quality level. > > Thx > T. > > > > >

May 20, 2017

Re: [Pharo-dev] [ bloc]'Pulse loop must be running in order to request a pulse'

by Stephane Ducasse

Thanks! On Sat, May 20, 2017 at 3:01 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > https://github.com/pharo-graphics/Bloc/issues/20 > > Cheers, > Alex > > On 20 May 2017 at 14:58, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > >> Hi Stef, >> >> Yes, sometimes that might happen. >> However, there is silver bullet: >> >> BlUniverse reset >> >> Cheers, >> Alex >> >> On May 20, 2017 2:09 PM, "Stephane Ducasse" <stepharo.self(a)gmail.com> >> wrote: >> >> I wanted to work on the bloc booklet and >> when I reopen my image I get >> >> 'Pulse loop must be running in order to request a pulse' >> >> >> >

May 20, 2017

Re: [Pharo-dev] [ bloc]'Pulse loop must be running in order to request a pulse'

by Aliaksei Syrel

https://github.com/pharo-graphics/Bloc/issues/20 Cheers, Alex On 20 May 2017 at 14:58, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi Stef, > > Yes, sometimes that might happen. > However, there is silver bullet: > > BlUniverse reset > > Cheers, > Alex > > On May 20, 2017 2:09 PM, "Stephane Ducasse" <stepharo.self(a)gmail.com> > wrote: > > I wanted to work on the bloc booklet and > when I reopen my image I get > > 'Pulse loop must be running in order to request a pulse' > > >

May 20, 2017

Re: [Pharo-dev] [ bloc]'Pulse loop must be running in order to request a pulse'

by Aliaksei Syrel

Hi Stef, Yes, sometimes that might happen. However, there is silver bullet: BlUniverse reset Cheers, Alex On May 20, 2017 2:09 PM, "Stephane Ducasse" <stepharo.self(a)gmail.com> wrote: I wanted to work on the bloc booklet and when I reopen my image I get 'Pulse loop must be running in order to request a pulse'

May 20, 2017

Re: [Pharo-dev] QualityImprovements assured by tests

by Stephane Ducasse

I agree with you. This is why I worked on the auto categoriser. then I improve the categorizer inside the image. Now I have a tool to analyse the categories but no time and I did not want to break everything but we could push some rules. if people would have published slices on such issues I'm quite sure that we would have integrated them, now the question is that it takes time and we were focused on other urgent tasks. Stef On Sat, May 20, 2017 at 12:25 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > One year later we are close to a final release for Pharo 6 and either with > Pharo 6 or upcoming Pharo 7 > I would really like to see some checks that ensure a quality image and > tests who keep us all more > disciplined in the future. > > Because: > > 1. We should not have undocumented classes: > > (Object allSubclasses select: [:cls| cls hasComment not ]) > > but we have a lot in Pharo 6 now since we introduced new packages in > this release iteration > > 2. We should not have class instance variables in uppercase but: > > (Object allSubclasses select: [:cls| cls isMeta]) select: [:cls| cls > instVarNames anySatisfy: [:n | n first isUppercase]] > > is not empty - although this was already discussed back in 2008 (!), > see > http://lists.pharo.org/pipermail/pharo-dev_lists. > pharo.org/2008-November/003366.html > > 3. We should not have uncategorized methods but: > > (Object allSubclasses select: [:cls| (cls selectorsInProtocol: > Protocol unclassified) notEmpty ]) > > we still have them. > > 4. I've seen methods with unused temporary variables. Dont know about > unused ivars or other. > > 5. add you own here ... > > I know this is often boring to comment or categorize - but we should do > our homework as we wanted to > better compared to the past. Also if the base image is not following rules > how should we expect others > to provide quality packages on top of it? > > IMHO we should raise the bar. Either in Pharo 6 or in early Pharo 7. We > can fix these once and for > all AND assure with unit tests that we keep the standard image on this > quality level. > > Thx > T. > > > > >

May 20, 2017

[ bloc]'Pulse loop must be running in order to request a pulse'

by Stephane Ducasse

I wanted to work on the bloc booklet and when I reopen my image I get 'Pulse loop must be running in order to request a pulse'

May 20, 2017

Re: [Pharo-dev] Calypso technology preview.

by Norbert Hartl

> Am 20.05.2017 um 09:54 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Hi ben > > It is better to load it because for example I could not load a new version the last time I tried to update. > We should lower the stress of the releasers. Yes, and release twice as often ð Norbert > > Stef > > >> On Sat, May 20, 2017 at 4:47 AM, Ben Coman <btc(a)openinworld.com> wrote: >> It is probably much too late to suggest this, but if Calypso is a candidate for our next browser, perhaps it could be included in Pharo 6 as a technology preview? >> Or maybe in a half-year point release Pharo 6.x ? >> >> cheers -ben >

May 20, 2017

Re: [Pharo-dev] Calypso technology preview.

by Stephane Ducasse

Hi ben It is better to load it because for example I could not load a new version the last time I tried to update. We should lower the stress of the releasers. Stef On Sat, May 20, 2017 at 4:47 AM, Ben Coman <btc(a)openinworld.com> wrote: > It is probably much too late to suggest this, but if Calypso is a > candidate for our next browser, perhaps it could be included in Pharo 6 as > a technology preview? > Or maybe in a half-year point release Pharo 6.x ? > > cheers -ben >

May 20, 2017

Re: [Pharo-dev] Embeddable/scalable Smalltalk VM needs funding for release (repost/update from squeak-dev)

by S Krish

Great Work..!! On Mon, May 15, 2017 at 1:01 PM, Zak Fenton <zak.fenton(a)outlook.com> wrote: > Hi folks. I posted earlier in squeak-dev about a Smalltalk implementation > I've been working on. The first post was a bit unwieldy, but there was at > least some interest so I'm posting an update to vm-dev and pharo-dev. > > > Main strong points are that it's embeddable (like Lua or SQLite) and > scalable (like Erlang). There are weak points too, of course (e.g. hot loop > performance will be much worse than Squeak/Pharo at this point). > > > The VM itself is pure C and has no dependencies apart from libc and libm. > It doesn't require a filesystem (you can pipe VM images through custom > stream implementations or arrays) and it should run well in tight (~1MB) > memory situations. > > > The extension system is similar to the Unix system call and virtual > filesystem APIs, so it's kind-of object oriented but in a very "C" way. All > extension resources are managed properly (so the system can clean up safely > and/or warn you if you allocate memory and don't deallocate it, for > example). > > > Extensions are available for cells (threads/individual VMs), shared memory > (so different cells can communicate efficiently - but also with memory > protection and calling features for implementing domain-specific JIT > compilers), windowing and event handling (based on SDL2) and 2D graphics > rendering (based on Cairo). There are some higher-level libraries (stylable > GUI system, tight OS integration, 3D modelling, etc.). > > > It's polished in some ways (there's a test suite, an integrated help > system, colour shell, etc.), but it needs a lot more refinement in others > (the current GUI style is terrible, it needs more documentation, there's > only minimal support for keyboard entry, no networking library, etc.). > > > I'd like to release it (ideally as 100% public domain/CC0), but I don't > want to do so without some way of funding development. The project promises > a lot and I want to actually deliver with some ongoing updates and support > (and being able to pay rent next week would also be a plus), so I'm not > interested in just dumping it on GitHub and calling it a day. > > > So I'm open to any suggestions as to how to fund this project at least in > the short term and how it might fit into the wider Squeak/Pharo/Smalltalk > ecosystems, as well as any technical criticism relating to the > implementation itself. > > > I've put together a basic website describing the implementation in a bit > more detail (sorry, no downloads yet): http://a4vm.info/ > > > -Zak. >

May 20, 2017