- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3395 in pharo: Capitalization of Author

by pharo＠googlecode.com

Updates: Status: Fixed Owner: renggli Comment #1 on issue 3395 by renggli: Capitalization of Author http://code.google.com/p/pharo/issues/detail?id=3395 Name: System-Support-LukasRenggli.418 Author: lr Time: 9 December 2010, 5:37:10 pm UUID: 762cf0e3-e188-44f3-b675-0e22ced6f3a5 Ancestors: System-Support-StephaneDucasse.417 - do not enforce camel case on author name: - some people have lowercase words in their name (X van Y) - some projects have othe conventions

Dec. 9, 2010

Re: [Pharo-project] Creating temporary classes for testing

by Noury Bouraqadi

Hi Sean, For testing you can have two approaches: -You need a mock object, and then you use a Mock library -You want to test something related to classes, and in this case you can use the SUnit extension I introduced a while ago ClassFactoryForTestCase. It's part of the core image. It supports the creation and the deletion of classes. To ensure keeping the system clean. Noury On 9 dÃ©c. 2010, at 17:00, Sean P. DeNigris wrote: > > I was playing with creating temporary classes for testing in a separate > SystemDictionary, so I don't have to worry about removing them. But I'm a > little beyond the boundary of my knowledge (although I stepped through it in > the debugger and it seemed pretty straight forward). Are there any hidden > side-effects/implications of the following? Specifically, after the > SystemDictionary is garbage collected, is the system exactly the same as it > was before the code was run? It seems like a better approach than creating > them in the global namespace and cleaning up. > > testingEnvironment := SystemDictionary withOrganizer: SystemOrganizer new. > > ClassBuilder new > name: #AClassForTesting > inEnvironment: testingEnvironment > subclassOf: Object > type: Object typeOfClass > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'TemporaryTesting'. > > newClass := (testingEnvironment at: #AClassForTesting). > newClass > compile: 'greeting > ^ ''hello there''' > classified: 'greeting'. > > newClass new greeting. "Returns 'hello there'" > > Thanks. > Sean > -- > View this message in context: http://forum.world.st/Creating-temporary-classes-for-testing-tp3080408p3080… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Dec. 9, 2010

[Pharo-project] Issue 3396 in pharo: Change Notification in Monticello Browser is broken

by pharo＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-ReportDefect Milestone-1.2 Importance-High New issue 3396 by renggli: Change Notification in Monticello Browser is broken http://code.google.com/p/pharo/issues/detail?id=3396 Packages are not marked as dirty anymore

Dec. 9, 2010

Re: [Pharo-project] Issue 3394 in pharo: Adopt disappeared from Monticello Browser

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3394 by renggli: Adopt disappeared from Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3394 Sorry, I was confused. The adopt button is still there. The change in the inbox fixes other issues with the buttons and menus: Name: MonticelloGUI-LukasRenggli.83 Author: Lr Time: 9 December 2010, 5:27:10 pm UUID: 5ba0e157-bf35-4b90-b273-4f65e6fafb4e Ancestors: MonticelloGUI-LukasRenggli.82 - fixed buttons and rearranged menu in Repository Browser - fixed some accidental changes on the default window size

Dec. 9, 2010

Re: [Pharo-project] [squeak-dev] Cog+NativeBoost @ Mac OS

by Michael Haupt

Hi Igor, here are some details. On 9 December 2010 16:29, Michael Haupt <mhaupt(a)gmail.com> wrote: > I installed the examples (which appear to be working) and tests as > well, but the tests crash the VM. I have not yet tried to nail the > problem down; is this expected behaviour on the Mac? most tests are green, but there are some issues: 1. NBUnixHeapManagerTests - 2 errors ("unable to map to virtual memory") 2. NBCallbackTests - assertion failure in NBInterpreterProxy >> #callInterpreter I installed NB in a clean up-to-date Squeak trunk image and use the Cog/NB VM from the NB Google code page. Best, Michael

Dec. 9, 2010

[Pharo-project] Creating temporary classes for testing

by Sean P. DeNigris

I was playing with creating temporary classes for testing in a separate SystemDictionary, so I don't have to worry about removing them. But I'm a little beyond the boundary of my knowledge (although I stepped through it in the debugger and it seemed pretty straight forward). Are there any hidden side-effects/implications of the following? Specifically, after the SystemDictionary is garbage collected, is the system exactly the same as it was before the code was run? It seems like a better approach than creating them in the global namespace and cleaning up. testingEnvironment := SystemDictionary withOrganizer: SystemOrganizer new. ClassBuilder new name: #AClassForTesting inEnvironment: testingEnvironment subclassOf: Object type: Object typeOfClass instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'TemporaryTesting'. newClass := (testingEnvironment at: #AClassForTesting). newClass compile: 'greeting ^ ''hello there''' classified: 'greeting'. newClass new greeting. "Returns 'hello there'" Thanks. Sean -- View this message in context: http://forum.world.st/Creating-temporary-classes-for-testing-tp3080408p3080… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 9, 2010

[Pharo-project] Issue 3395 in pharo: Capitalization of Author

by pharo＠googlecode.com

Status: Accepted Owner: ---- Labels: Difficulty-Easy Type-ToDo Milestone-1.2 New issue 3395 by renggli: Capitalization of Author http://code.google.com/p/pharo/issues/detail?id=3395 The author initials are automatically capitalized, this is extremely annoying! Not everybody is following the PharoCore people conventions.

Dec. 9, 2010

[Pharo-project] Issue 3394 in pharo: Adopt disappeared from Monticello Browser

by pharo＠googlecode.com

Status: Accepted Owner: ---- Labels: Milestone-1.2 Difficulty-Easy New issue 3394 by renggli: Adopt disappeared from Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3394 The adopt button disappeared, which is a sensible change. The adopt functionality should still be available from the menu, because it is a common operation when integrating.

Dec. 9, 2010

Re: [Pharo-project] Just another struggling newbie

by Henrik Johansen

Den 09.12.2010 15:52, skrev Chip Nowacek: > > To the matter: I don't understand why I can't accept a change to my > comment in one of my classes. When I try to accept in the OB Package > Browser, about a dozen calls in, #Utility is being sent #changeStamp > and doesn't understand it. I am in the midst of sorting through the > stack trying to figure out what happened. As you might imagine, it's a > little discouraging for such a basic function to blow up. What makes > it worse, I'm probably the cause of the problem - I just don't know > what I screwed up. I am working in Pharo 1.1.1 and have loaded Magma > and O2 per: > It seems the O2 tools have not been entirely updated to reflect 1.1 "deprecations" (in quotes since they were moved without leaving stubs pointing to their new location). Change Utilities changeStamp to Author changeStamp in the debugger that pops up, and hit proceed :) Cheers, Henry ps. in such cases, the simplest way to find a solution is usually to highlight the message (changeStamp in this instance), then either use alt-m shortcut or right click -> extended search -> implementors of it, and see which one fits what you attempt to do. Alternatively ask on the list if none seem to fit :)

Dec. 9, 2010

Re: [Pharo-project] Just another struggling newbie

by Marcus Denker

On Dec 9, 2010, at 3:53 PM, Chip Nowacek wrote: > Hello everyone, > > While I should have introduced myself before I ran into trouble, it is trouble that has brought me here. I guess I'm glad something provided the excuse to meet you. > > First, a short introduction... > > I'm really new to Smalltalk. Kent Beck said it's a good choice for my project. Technically, I come from the database architecture world - though I am more entrepreneur now than techie. I'm starting up a new company and Kent suggested building a prototype myself instead of bringing someone else in - so here I am. I'm trying to move from Squeak because Pharo feels a little more developer oriented. We'll see how it goes. > > To the matter: I don't understand why I can't accept a change to my comment in one of my classes. When I try to accept in the OB Package Browser, about a dozen calls in, #Utility is being sent #changeStamp and doesn't understand it. I am in the midst of sorting through the stack trying to figure out what happened. As you might imagine, it's a little discouraging for such a basic function to blow up. What makes it worse, I'm probably the cause of the problem - I just don't know what I screwed up. I am working in Pharo 1.1.1 and have loaded Magma and O2 per: > Hello, We did not include O2 in the release precisely because it it not yet mature enough... it has lots of nice features and I understand that people want to use it. But man-power was not there to bring it to a state where all these bugs are fixed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 9, 2010