- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Please clarify which versions to report issues on
by Marcus Denker April 12, 2011

April 12, 2011

On Apr 12, 2011, at 9:33 PM, DougEdmunds wrote: > Where's the best place to get the most recent v 1.3 on any given day? > > Some choices appear to be: > > 1. https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/ > (but which link?) The latest image is this: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/la… > 2. http://www.pharo-project.org/pharo-download : the link to "PharoCore 1.3 > (just core)" Hudson needs to start somewhere, and loading 140 updates is to slow. So we checkpoint all 10-20 updates (good to have anyway), and that is linked here: http://www.pharo-project.org/pharo-download/unstable-core It tends to be a relatively un=broken image, too. The hudson one is build after *every* update, and can be in need of another update to be usable. (But that does not happen often) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Please clarify which versions to report issues on
by Marcus Denker April 12, 2011

April 12, 2011

On Apr 12, 2011, at 7:00 PM, DougEdmunds wrote: > If you start to open a new issue on > http://code.google.com/p/pharo/issues/list > this is what appears: > > "We are currently working on version 1.2, so please verify your issue with > the latest 1.2 Unstable version before reporting it - we improved a lot > the system." > We forgot to update this. So I updated it now. We are working on 1.3. 1.2 will only see fixes of real bugs of the kind that are extremely important. > But on http://www.pharo-project.org/pharo-download, the 'unstable' version > is listed as > Pharo 1.3 image (unstable), with a link to PharoCore 1.3 (just core). > > Is there another place to go to for 1.2 Unstable? Or should everything be > reported against 1.3? > 1.3 > If it is 1.3, can someone update the default text new issue info on > code.google.com? DONE -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] Issue 3062 in pharo: CompilerEvaluationTest >> testEvaluationOfSelfSend dependent on SmalltalkEditor
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Updates: Status: Closed Comment #1 on issue 3062 by marcus.d...@gmail.com: CompilerEvaluationTest >> testEvaluationOfSelfSend dependent on SmalltalkEditor http://code.google.com/p/pharo/issues/detail?id=3062 This has been fixed

1 0

Re: [Pharo-project] Issue 3109 in pharo: TextURL >> #actOnClickFor: dependent on network
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Updates: Status: Closed Labels: Milestone-1.3 Comment #1 on issue 3109 by marcus.d...@gmail.com: TextURL >> #actOnClickFor: dependent on network http://code.google.com/p/pharo/issues/detail?id=3109 #actOnClickFor: has been removed in 1.3

1 0

Re: [Pharo-project] Issue 3262 in pharo: Debugger enhancement to open in a background process when the UI process is busy
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Updates: Summary: Debugger enhancement to open in a background process when the UI process is busy Comment #2 on issue 3262 by stephane.ducasse: Debugger enhancement to open in a background process when the UI process is busy http://code.google.com/p/pharo/issues/detail?id=3262 Tried to rescue some of Eliot Miranda improvement for the debugger. Strangely enough the functions introduced by eliot got removed and not invoked in latter versions. Now invoking the debugger crash the system probably because there is an problem with the semaphore or other. I just save this to avoid to redo everything. Attachments: Debugger.1.cs 4.4 KB

1 4

Re: [Pharo-project] UIBuilder Tool
by sourav roy April 12, 2011

April 12, 2011

thanks.... Original message From:"eMko"< mm007.emko(a)gmail.com >Date: 11 Apr 11 23:53:49Subject: Re: [Pharoproject] UIBuilder ToolTo: pharoproject(a)lists.gforge.inria.frYou can download it from squeaksourcehttp://www.squeaksource.com/UIBuilder.html .If you want some practical information, watch youtubehttp://www.google.cz/search?q=uibuilder+pharo+youtube&ie=utf8&oe=utf8&aq=t&rls=org.mozilla:cs:official&client=firefoxa#q=uibuilder+pharo+youtube&hl=cs&client=firefoxa&hs=hu1&rls=org.mozilla:cs:official&prmd=ivns&source=univ&tbm=vid&tbo=u&sa=X&ei=NkajTbCiHsiBOt7LvTQ&ved=0CDkQqwQ&fp=46e891d5c7303f5eOne big drawback of Pharo smalltalk is lack of good documentation, butthings are getting better and better.View this message in context: http://forum.world.st/UIBuilderTooltp3442594p3442745.htmlSent from the Pharo Smalltalk mailing list archive at Nabble.com.Get Yourself a cool, short @in.com Email ID now!

1 0

[Pharo-project] keymapping
by Tudor Girba April 12, 2011

April 12, 2011

Hi, I would like to give it a try to integrate Keymapping into Glamour, but I see that there are two repositories where Keymapping-related packages are committed: Keymapping and ShortWays (this has the latest commit). Furthermore, there are three ConfigurationOfKeymapping (also in MetacelloRepository). Where do I get the latest and supported Keymapping from? Cheers, Doru -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter."

3 6

[Pharo-project] Please clarify which versions to report issues on
by DougEdmunds April 12, 2011

April 12, 2011

If you start to open a new issue on http://code.google.com/p/pharo/issues/list this is what appears: "We are currently working on version 1.2, so please verify your issue with the latest 1.2 Unstable version before reporting it - we improved a lot the system." But on http://www.pharo-project.org/pharo-download, the 'unstable' version is listed as Pharo 1.3 image (unstable), with a link to PharoCore 1.3 (just core). Is there another place to go to for 1.2 Unstable? Or should everything be reported against 1.3? If it is 1.3, can someone update the default text new issue info on code.google.com? -- View this message in context: http://forum.world.st/Please-clarify-which-versions-to-report-issues-on-tp3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

Re: [Pharo-project] [Seaside] [ANN] Seaside Tutorial Ready for 3.0
by Mariano Martinez Peck April 12, 2011

April 12, 2011

This was the first tutorial I read and it was really nice. Thanks a lot for this. Mariano ---------- Forwarded message ---------- From: Michael Perscheid <michaelperscheid(a)googlemail.com> Date: Tue, Apr 12, 2011 at 3:21 PM Subject: [Seaside] [ANN] Seaside Tutorial Ready for 3.0 To: seaside(a)lists.squeakfoundation.org Hi all, I would like to announce that we have updated the Seaside tutorial of the Software Architecture Group ( http://www.hpi.uni-potsdam.de/hirschfeld/seaside/tutorial) Now it can be applied with the current Seaside 3.0 version without any problems. Besides a revision of all chapters, we have especially changed the persistence chapter and added new sections about SandstoneDB, PostgreSQL, and GemStone. Most of the update was done by Lauritz Thamsen and Tobias Pape. Thank you very much. If you have any feedback, please let us know. Best regards, Michael Perscheid _______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: New Owner: ---- New issue 3992 by nicholas...@gmail.com: Proposed O2 fixes for Pharo-1.2 http://code.google.com/p/pharo/issues/detail?id=3992 Pharo Metainfo ------------- Pharo image: dev Pharo core version: Pharo1.2.1 Virtual machine used: Cog VM.r2378 Description ---------- Follow the full discussion at <http://forum.world.st/Code-Navigation-Navigation-History-in-System-Browser-…>. I completely agree with StÃ©phane Ducasse's comments about O2 being outdated and how it will be replaced soon. But since I've ported it, I might as well share it with the community in case someone else is interested. These are the fixes to make it possible to load O2 into a Pharo-1.2 Dev image. It is based off the latest version of the code from the O2 repository (http://www.squeaksource.com/O2) made by David Roethlisberger. Notable changes: * Removed all references to Preferences (deprecated in Pharo 1.2) * Removed most preferences that I could not find any references to. * Made test cases pass (mostly adapting the tests to the new TestCase hierarchy that it was testing for) Remaining problems: * Undo/redo does not work in the editor. This is probably because Pharo-1.2 changed the TextEditor components (i.e. uses EditingState). * Lots of duplication between O2 and OB. Not sure whether to merge/eliminate duplication since these browsers seem to be quite independent and I don't enough of their ecosystem to say if we should merge.

1 3