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

[Pharo-project] Issue 3333 in pharo: [Kernel Dependencies] Integer>>#asColorOfDepth
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo Labels: Type-Seed Importance-High New issue 3333 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Integer>>#asColorOfDepth http://code.google.com/p/pharo/issues/detail?id=3333 Strange dependence to Graphics-Primitives

1 3

[Pharo-project] Issue 3334 in pharo: [Kernel Dependencies] Model>>#patchworkUIThemeColor
by pharo＠googlecode.com Jan. 28, 2011

Jan. 28, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo Labels: Type-Seed Importance-High New issue 3334 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Model>>#patchworkUIThemeColor http://code.google.com/p/pharo/issues/detail?id=3334 Strange dependence to Graphics-Primitives

1 2

[Pharo-project] Issue 3335 in pharo: [Kernel Dependencies] Number>>@
by pharo＠googlecode.com Jan. 25, 2011

Jan. 25, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3335 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Number>>@ http://code.google.com/p/pharo/issues/detail?id=3335 If you fill an issue for the first time, please read "How to report bugs" at http://www.pharo-project.org/community/issue-tracking Pharo image: <core, dev or web> Pharo core version: <copy from World/System/About> Virtual machine used: <ex: pharo-vm-0.15.2f-linux> Class browser used if applicable: <ex: O2PackageBrowserAdaptor. If you don't know, print "SystemBrowser default"> Steps to reproduce: 1. 2. 3. Paste or attach stack trace if applicable (look at the file PharoDebug.log located in the same directory as your image):

1 3

Re: [Pharo-project] Issue 3172 in pharo: NewInspector really really slow while parsing XMLNode
by pharo＠googlecode.com Jan. 22, 2011

Jan. 22, 2011

Updates: Cc: jaa...(a)zoho.com Comment #2 on issue 3172 by laurent.laffont: NewInspector really really slow while parsing XMLNode http://code.google.com/p/pharo/issues/detail?id=3172 From jaayer: Hi Laurent. First, thank you for your screencasts. I am writing to you concerning this issue: http://code.google.com/p/pharo/issues/detail?id=3172&q=xml&colspec=ID%20Typ… I only discovered the above last night, as I am not a Pharo core developer and only check the issue tracker occasionally. I am a maintainer of XML-Support, however, so feel free to mail me directly with any issues you have in the future, or at the very least, please post them to the Pharo-Project, Squeak-dev or Moose-dev lists. Now, in your video, which was made back in August, you used version .74 of XML-Parser. If you look at the changelogs of XML-Parser, it is clear that much has changed since that time. It would not be unreasonable to assume that one or more of those changes is responsible for the difficulties you experienced inspecting that XML document. However, if you load version .74, the same version used in your screencast, into a Pharo 1.1 image, the problem is still there (and is in fact much worse), meaning that whatever has changed since August to bring this about, I can say with some confidence that it is not in XML-Parser. Using the latest version of XML-Parser and ignoring the question of causality for a moment, the bottleneck we're observing is in XMLNode>>printOn:. The proof is that disabling XMLNode>>printOn: makes our problem go away. Why then is XML generation suddenly such a bottleneck? The main reason appears to be that the document being inspected is, when printed, roughly 40K in size, and by inspecting it you are causing it to be printed over and over again. I tracked sends of #printOn: and found that inspecting the document and navigating to the "title" element results in #printOn: being sent 300-400 times. The recipients were the document object and the root "feed" element ~350 times. By the time you've navigated to the "feed" element and clicked the "Elements" entry to display its children, #printOn: has already been sent ~150 times. That means the remaining 150-250 sends come when you click on the "title" element or some other child element of the root, and that single additional click results in the generation of roughly 6-10 MBs of XML (150 * 40K to 250 * 40K). *That* is why it's so slow. Now, why does NewInspector cause #printOn: to be sent so much? I honestly don't know. I will forward this to the maintainers of NewInspector to get their input. Maybe NewInspector can be changed to not print inspected objects so often, or to provide them with some way to suppress its printing behavior. It must be pointed out that Pharo also comes with an object explorer that is designed specifically for this usecase of browsing deep object hierarchies. I tried exploring the document with cmd-I (capital i) and encountered no trouble.

1 2

[Pharo-project] Issue 3361 in pharo: CompiledMethod's copy
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: gbarbuto New issue 3361 by gbarbuto: CompiledMethod's copy http://code.google.com/p/pharo/issues/detail?id=3361 Pharo image: core Pharo core version: Pharo1.2a Latest update: #12264 Virtual machine used: <any Steps to reproduce: 1. Try to completely copy a CompiledMethod and the copy still have references to the original CompiledMethod.

1 4

[Pharo-project] Waste of CPU Power by polling events?
by Guido Stepken Jan. 11, 2011

Jan. 11, 2011

I am just porting squeak/Etoys to Samsung-PAD and i noticed some strange things: In Pharo 1.1 network connections seemed to be limited to 4 connections: In the listenLoop backlogSize is set to 4. Means - Pharo is limited to max. of four simultaneous TCP Connections? But: Some MacIntel VM seem to run Squeak with additional worker thread for event processing. Maybe this limitation may not occur here? Carbon ports of Pharo use ioPeekKeystroke, ioGetKeystroke, ioMousePoint, ioGetButtonState instead of kEventRawKeyModifiersChanged and kEventMouseMoved event Found in Pharo so far: isDraggingEvent isDropEvent isEditEvent isKbdEvent isMorphicEvent isNoteEvent isTempoEvent isWindowEvent Hmmm ... quite a lot of events being polled: Need additional: isOnMouseOverEvent isMouseGestureEvent isTouchGestureEvent isNetworkEvent isUSBEvent isSerialEvent isParallelPortEvents isCtrl-C-Event ... I fear, that this costs a lot of wasted VM Power by polling. UNIX, especially Linux is changing towards a event machine, driven by interrupts. So - Interpreters should also migrated from polling to interrupt driven event-machines. I am missing that in Pharo. Pharo still has too much polling code/algorithm running, that slows down Pharo/Squeak/Etoys ... unneccessarily. Any ideas appreciated ... tnx, regards Guido Stepken

7 11

[Pharo-project] Alien + Cog VM
by Ken Treis Jan. 11, 2011

Jan. 11, 2011

What's the status of Alien in the new Cog VM? I was able to load Alien into Pharo 1.1.1 running Cog, and some simple callouts worked (e.g. `CRLibrary libraryVersionString` in CairoGraphics. But every callout with arguments failed in primFFICallResult:. Alien works perfectly for me in Pharo 1.1 using JMM's VMs when I load the Pharo 1.1 version from ConfigurationOfAlien, but I admit I haven't tried 1.1.1 in this arrangement. Is there something that's changed in Cog's Alien primitive implementation? -- Ken Treis Miriam Technologies, Inc.

6 8

[Pharo-project] Best way for change a window style
by nullPointer Jan. 5, 2011

Jan. 5, 2011

For a TIP example I want implement in Pharo the steps for build a GUI like that: http://forum.world.st/file/n3032341/eBox.png The main problem for me is the window style. I understand one way for change the style of windows is create my own UITheme subclass; but exists some alternative way for generate a new style for windows? a generic window: I only want a one panel with the three buttons for close, minimize and maximize, and the rounded corners, much more rebranded in top corners than bottom, with the default behavior of window: draggable for the Desktop. Perhaps the best way for implement it is know if is possible change a few properties of a panel for have the same behavior of a window. Many thanks for the help. -- View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3032341.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

8 21

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?
by Simon Denier Dec. 30, 2010

Dec. 30, 2010

Uhuh, that's indeed the old theme, but as said before I now prefer the current theme with some adaptations: it's less aggressive to the eye. To apply, call SHTextStylerST80 initialize after changing the style table SHTextStylerST80 styleTable: #( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default ( black ) ) (invalid ( red ) ) (excessCode ( red ) ) (comment ( green muchDarker ) ) (unfinishedComment ( green muchDarker ) ) (#'$' ( magenta muchDarker) ) (character ( magenta muchDarker) ) (integer ( magenta muchDarker) ) (number ( magenta muchDarker) ) (#- ( magenta muchDarker) ) (symbol ( magenta muchDarker) ) (stringSymbol ( magenta muchDarker) ) (literalArray ( magenta muchDarker) ) (string ( magenta muchDarker) ) (unfinishedString ( magenta muchDarker) ) (assignment ( black ) ) (ansiAssignment ( black ) ) (literal ( black ) ) (keyword ( black ) ) (binary ( black ) ) (unary ( black ) ) (incompleteKeyword ( red ) ) (incompleteBinary ( red ) ) (incompleteUnary ( red ) ) (undefinedKeyword ( red ) ) (undefinedBinary ( red ) ) (undefinedUnary ( red ) ) (patternKeyword ( black ) bold ) (patternBinary ( black ) bold ) (patternUnary ( black ) bold ) (#self ( cyan muchDarker ) ) (#super ( cyan muchDarker ) ) (#true ( cyan muchDarker ) ) (#false ( cyan muchDarker ) ) (#nil ( cyan muchDarker ) ) (#thisContext ( cyan muchDarker ) ) (#return ( black ) ) (patternArg ( blue muchDarker ) ) (methodArg ( blue muchDarker ) ) (blockPatternArg ( blue muchDarker ) ) (blockArg ( blue muchDarker ) ) (argument ( blue muchDarker ) ) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 black ) (rightParenthesis1 black ) (leftParenthesis2 black ) (rightParenthesis2 black ) (leftParenthesis3 black ) (rightParenthesis3 black ) (leftParenthesis4 black ) (rightParenthesis4 black ) (leftParenthesis5 black ) (rightParenthesis5 black ) (leftParenthesis6 black ) (rightParenthesis6 black ) (leftParenthesis7 black ) (rightParenthesis7 black ) (blockStart black ) (blockEnd black ) (blockStart1 black ) (blockEnd1 black ) (blockStart2 black ) (blockEnd2 black ) (blockStart3 black ) (blockEnd3 black ) (blockStart4 black ) (blockEnd4 black ) (blockStart5 black ) (blockEnd5 black ) (blockStart6 black ) (blockEnd6 black ) (blockStart7 black ) (blockEnd7 black ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (byteArrayStart black ) (byteArrayEnd black ) (byteArrayStart1 black ) (byteArrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black ) (primitiveOrExternalCallEnd black ) (methodTempBar black ) (blockTempBar black ) (blockArgsBar black ) (primitive gray ) (externalFunctionCallingConvention gray ) (module gray ) (blockTempVar ( blue muchDarker ) ) (blockPatternTempVar ( blue muchDarker ) ) (instVar ( brown darker) ) (workspaceVar ( blue muchDarker ) ) (undefinedIdentifier ( red ) ) (incompleteIdentifier ( red ) ) (tempVar ( blue muchDarker ) ) (patternTempVar ( blue muchDarker ) ) (poolConstant ( black ) bold ) (classVar ( brown darker ) ) (globalVar ( black ) bold ) ) On 25 oct. 2010, at 19:36, Mariano Martinez Peck wrote: > Thanks Ramon. So, we have to options. > > 1) We commit this change to Shout repository > 2) We add this method in ConfigurationOfPharo and we call it while building the dev image. > > opinions? > > cheers > > mariano > > On Mon, Oct 25, 2010 at 7:12 PM, Ramon Leon <ramon.leon(a)allresnet.com> wrote: > On 10/23/2010 10:11 AM, Mariano Martinez Peck wrote: > Exactly. > > Can you or Simon provide a script to set back the original colors?? So > that we can apply this for next PharoDev images? (or at least for my > own images) > > Thanks > > Mariano > > I just went back in the package history and found the point where Damien changed the colors and grabbed the previous version. I have a ConfigurationOfDevelopment class that loads all my local packages, so I just added a method to it to reload the old colors. Here it is... > > -- Simon

5 11

Dec. 26, 2010

does anybody ported neopus to squeak/pharo? Stef

4 7