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

Re: [Pharo-project] New Issue Tracker

by Nicolas Petton

I really don't like JIRA, I find it bloated, and I always lose myself there. IMHO FogBugs seems *a lot* nicer to use. Nico Camillo Bruni <camillobruni(a)gmail.com> writes: > After a discussion with Christophe which is in favor of JIRA ;) we decided to put a > wiki page online where we should list all the requirements (not just the ones I think > are important :P) > > https://code.google.com/p/pharo/wiki/NewIssueTracker -- Nicolas Petton http://nicolas-petton.fr

Feb. 12, 2013

[Pharo-project] [update 2.0] #20541

by Marcus Denker

20541 ----- Issue 7477: [ENH]: User Interrupt: Inform user if interrupt not possible http://code.google.com/p/pharo/issues/detail?id=7477 Issue 7470: Put completion + smart char and then aaaa( --> DNU http://code.google.com/p/pharo/issues/detail?id=7470 Issue 6017: What to do when removing a trait? http://code.google.com/p/pharo/issues/detail?id=6017 Diff information: http://ss3.gemstone.com/ss/Pharo20/Traits-MarcusDenker.456.diff http://ss3.gemstone.com/ss/Pharo20/Tests-MarcusDenker.510.diff http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.97.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1310.diff

Feb. 12, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

After a discussion with Christophe which is in favor of JIRA ;) we decided to put a wiki page online where we should list all the requirements (not just the ones I think are important :P) https://code.google.com/p/pharo/wiki/NewIssueTracker

Feb. 12, 2013

[Pharo-project] [update 2.0] #20540

by Marcus Denker

20540 ----- Issue 7490: Do a ImageCleaner cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=7490 Issue 7465: Removing a trait from a composition makes dirty organization http://code.google.com/p/pharo/issues/detail?id=7465 Diff information: http://ss3.gemstone.com/ss/Pharo20/Traits-MarcusDenker.454.diff http://ss3.gemstone.com/ss/Pharo20/Tests-MarcusDenker.508.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1309.diff

Feb. 12, 2013

Re: [Pharo-project] SystemNavigation >> #allSelect:

by stephane ducasse

Hi eliot We worked on Ring for more than a year and it is a complete source code meta model and it is just to remove pseudo class and the rest. We should check for the TextReference idea. Stef > On Sun, Feb 10, 2013 at 8:42 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 10 February 2013 16:25, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > Why does SystemNavigation >> #allSelect: return strings of the form 'Array at:' instead of the real methods? > > Probably because the things that use SystemNavigation - Browsers, > MessageSets and the like - want to render lists of things to the user. > > There is one advantage to dumb strings, which is that it's easy to > make a SystemNavigation that works against a remote image. But that's > not much to go on. Changing these kinds of methods to return > MethodReferences might be a useful middle ground (and permit easy > extension to remote tools). > > No, dumb strings are dumb. A className, selector pair (which is what MethodReference is) is the right thing (and what systemNavigation methods return). The dumb strings are a pain in the ass to parse (endlessly looking for ' class' to spot meta classes etc). Whereas the class,selector p[air approach is extensible, e.g. to include a pointer to a specific external entity (be it Monticello package or remote image). MethodReference is what the system has provided for a decade and they're convenient. There are multiple versions of these and I could care less about whether one uses MethodReference or RBMethodDefinition. But that they have a consistent API is really important. Programmatic uses of these things for code editing is something I've depended upon in the VMMaker, and I'm anxious that Pharo and Squeak don't diverge hopelssly on this level of the system. > > In my own work I've ended up with three kinds of code reference object > > a) MethodReference that points to a class,selector pair > b) ClassReference that points to a class > c) TextReference that holds onto a text > > So if one wants to check out a refactoring/edit before applying it one compares a sequence of MethodReference objects and a matching sequence of TextReference objects that hold onto the edited source to a comparison engine. > > If one wants to have a look at all uses of a SharedPool one can supply a list of ClassReference objects to a list browser. > > If one wanted to build a "compare two images" or "compare arbitrary package versions: facility one can extend the reference objects with pointers to specific packages or remote images. > > etc. > > Lots of stuff in the system depends on these kinds of pointer; message list browsers, Monticello's loader, etc. > > What's insane is a) not having a standard set of facilities common between Pharo and Squeak with a well-defined API (e.g. isCodeReference, isMethodReference, isClassReference), b) having some of the API in extension methods in e.g. Monticello. > > This is core reflection protocol and it needs to be well-defined and in what ever package contains base reflection protocol. > > > excuse my ranting. > > > I mention remote tools because I hacked up a proof of concept a while > back that turned a Browser into one that could access a suitably > prepared image through an HTTP API. Development stalled because the > reflection machinery's API is a bit... involved, and it was dog slow, > but I could browse anything I liked. I should really wrap up the work > a bit so I can spread the love. > > frank > > > > > -- > best, > Eliot

Feb. 12, 2013

Re: [Pharo-project] New Issue Tracker

by Marcus Denker

On Feb 11, 2013, at 4:59 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Is there a way to have public access to issues? > I mean, read only access to see the backlog of issues, what's being done, etc. > > With FogBugz all I see at pharo.fogbugz.com is a login page, whilst > with Google Issue Tracking I was able to see the milestones, etc. > Yes, having the list of bugs public we should somehow have. Maybe this plugin can help? http://www.fogcreek.com/fogbugz/plugins/plugin.aspx?sId=communitycaselist%4… But the best would be a read-only way to look at the bugs (by milestone, even) that does not require to log in. Marcus

Feb. 12, 2013

Re: [Pharo-project] New Issue Tracker

by Marcus Denker

On Feb 11, 2013, at 8:21 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-02-11, at 16:47, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > >> On Sat, Feb 9, 2013, at 12:47 PM, stephane ducasse wrote: >>> thanks a lot ben. >>> I'm busy migrating on 10.7 to 10.8 on a new machine and bumping into >>> wellâ¦. glitches :) >>> I will sync with the team monday. >> >> Good timing! The FogBugz team rolled pharo.fogbugz.com over to the beta >> this morning. Each person can opt into or out of the beta individually; >> to avoid disrupting you (the account seems very active at the moment), I >> did *not* preemptively move everyone. To engage the beta UI, in the >> toolbar at the top, you should see a link that says "FogBugz Beta UI is >> disabled. [Enable it.]" Click the link, and, after a full-page refresh, >> you should notice that suddenly everything runs *much* faster. >> Specifically, the new UI speeds up list pages, case/email navigation, >> case/email creation, and the search system. > > indeed looks nice and quite a bit faster ;) > for me it does not work. It just says "Loading" with the progress bar, after a while it adds a link like "Slow, Busted? Go back to old UI"... This is Safari on MacOS 10.8.2 >> While we think the new version is solid, and have been using it >> internally for several months, there may be a bug or two. It's a beta; >> that's the point. If you do hit an issue, you should find a link to go >> back to the "slow" version in the same location, as well as a feedback >> form where you can tell us what we need to fix. >> >> Again, please feel free to bug me if you have any questions, either on >> the list, on IRC (bmp), or directly, and I'll be happy to answer them. >> And, if all of you feel like FogBugz just isn't the right tool for >> Pharo, that's fine, too. I just wanted you to have it as an option. > > So far I think it looks good ;). we started implementing the API to work on > FogBugz. I guess we will decide this week whether or not to migrate to > FogBugz. > Yes, we should check and then decide. Marcus

Feb. 12, 2013

Re: [Pharo-project] Less than 50 issues!

by Sean P. DeNigris

Current stats: 20 Open 2.0 Issues (down from 29) [1] 03 Ready to Review [2] 00 Ready to Integrate [3] ______ = 17 Outstanding [4] (down from 23) Now this is getting exciting! [1] http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D2.0 [2] http://code.google.com/p/pharo/issues/list?can=2&q=label%3AMilestone-2.0+st… [3] http://code.google.com/p/pharo/issues/list?can=2&q=status%3AFixToInclude+Mi… [4] http://code.google.com/p/pharo/issues/list?cursor=pharo%3A7102&q=label%3AMi… -- View this message in context: http://forum.world.st/Less-than-50-issues-tp4667961p4669342.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 12, 2013

Re: [Pharo-project] files.pharo.org yielding a 502

by Camillo Bruni

On 2013-02-11, at 21:00, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 11, 2013, at 8:22 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> We get these fairly often: >> >> -------------------------------------------------------------------------------- >> Resolving files.pharo.org (files.pharo.org) 192.31.186.143 >> Connecting to files.pharo.org (files.pharo.org)|192.31.186.143|:80... connected. >> HTTP request sent, awaiting response... 502 Bad Gateway >> 2013-02-11 20:18:41 ERROR 502: Bad Gateway. >> -------------------------------------------------------------------------------- >> >> is it the pharo.org domain? or the gforge? > > no idea.. we should do it for realâ¦ we need to check what the status is with > that fileserverâ¦ humm, well it happens every 100 requests or so ;) not that much of a problem, right now

Feb. 11, 2013

[Pharo-project] [update 2.0] #20539

by Marcus Denker

20539 ----- Issue 7488: Failing test: #testMethodsWithUnboundGlobals http://code.google.com/p/pharo/issues/detail?id=7488 Issue 7486: Autocompletion fails when superclass is nil. (Generally Traits) http://code.google.com/p/pharo/issues/detail?id=7486 Issue 7482: Starting from #20526, cannot remove non-empty category http://code.google.com/p/pharo/issues/detail?id=7482 Issue 7446: ClassDescription >> correspondingForTest is local http://code.google.com/p/pharo/issues/detail?id=7446 Diff information: http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-MarcusDenker.118.diff http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.95.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.764.diff

Feb. 11, 2013