January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3523 in pharo: Nested comments

by pharo＠googlecode.com

Comment #2 on issue 3523 by stephane.ducasse: Nested comments http://code.google.com/p/pharo/issues/detail?id=3523 Would love but not enough time - we want opal, FS.... + better tools.

Jan. 10, 2011

Re: [Pharo-project] Issue 3523 in pharo: Nested comments

by pharo＠googlecode.com

Updates: Cc: renggli Comment #1 on issue 3523 by aplantec: Nested comments http://code.google.com/p/pharo/issues/detail?id=3523 Why don't we integrate petitparser in the core ? Its small and very powerful. I should make it possible such improvements no ?

Jan. 10, 2011

[Pharo-project] Issue 3523 in pharo: Nested comments

by pharo＠googlecode.com

Status: Accepted Owner: aplantec New issue 3523 by aplantec: Nested comments http://code.google.com/p/pharo/issues/detail?id=3523 Now let me open a big can of worms but we truly need it. When you write documentation (I did several experiments with Soup) the documentation in class comment is cool because you to not have to have " and " and '' ' ' '' '" everytimes you manipulate a string or a comment. Now you do not want to have huge class comments I would prefer to have a couple of methods and it does not work: you put back the crappy unnestable " ugly boring.... better not putting comments. So I would really like to have */ this is a nice nestable comment "hkjkhhkjh " 'hkjjkh' 1 + 2 */yet another comment: increbile this is a nested ones: yes you know Smalltalkers are discovering the world/* /* As you see stealing the C comment syntax is a plus because everybody knows it. I remember a discussion on VW about possible syntax to support that. Before replying to this point thing hard because we need that support.

Jan. 10, 2011

[Pharo-project] Issue 3522 in pharo: wiki like help contents

by pharo＠googlecode.com

Status: Accepted Owner: aplantec CC: Torsten....(a)astares.de Labels: Milestone-1.2 New issue 3522 by aplantec: wiki like help contents http://code.google.com/p/pharo/issues/detail?id=3522 The help system will provide a way to integrate contents with wiki markup.

Jan. 10, 2011

Re: [Pharo-project] How to display an image from an external PNG/JPG file in a Morph?

by Alain Plantec

(ImageReadWriter formFromFileNamed: 'pharoLogo.jpg') asMorph openInWorld works also Le 10/01/2011 05:33, Dimitry Golubovsky a Ã©crit : > Hi, > > Maybe a silly question, but is there an example of displaying an image > from an external file in a Morph? > > A sample package/class source, or a wiki page would be fine. Or just a > step-by-step description of the process. > > I am guessing that I have to create a Form first (that is, from the > picture file), but could not find which method to use. > > Thanks for any suggestions. >

Jan. 10, 2011

Re: [Pharo-project] How to display an image from an external PNG/JPG file in a Morph?

by Alain Plantec

Hi Dimitry, (ImageMorph withForm: (ImageReadWriter formFromFileNamed: 'pharoLogo.jpg')) openInWorld Cheers Alain Le 10/01/2011 05:33, Dimitry Golubovsky a Ã©crit : > Hi, > > Maybe a silly question, but is there an example of displaying an image > from an external file in a Morph? > > A sample package/class source, or a wiki page would be fine. Or just a > step-by-step description of the process. > > I am guessing that I have to create a Form first (that is, from the > picture file), but could not find which method to use. > > Thanks for any suggestions. >

Jan. 10, 2011

[Pharo-project] bootstrapping Order ...

by James Ladd

Hi All, I'm wondering where I can find information or if anyone knows off hand what the order of bootstrapping would be if the image had to be created from scratch? As I see it, there are dependencies between Object -> Class and so forth. Rgs, James.

Jan. 10, 2011

[Pharo-project] How to display an image from an external PNG/JPG file in a Morph?

by Dimitry Golubovsky

Hi, Maybe a silly question, but is there an example of displaying an image from an external file in a Morph? A sample package/class source, or a wiki page would be fine. Or just a step-by-step description of the process. I am guessing that I have to create a Form first (that is, from the picture file), but could not find which method to use. Thanks for any suggestions. -- Dimitry Golubovsky Anywhere on the Web

Jan. 10, 2011

[Pharo-project] Using Open Sound Control with Pharo 1.1.1 one click

by Andy Burnett

Hello I am trying to create some simple controls for an OSX Quartz Composer application. The app supports Open Sound Control - basically UDP multicast commands. I managed to load the OSC package from squeak source using Pharo 1.0. But I couldn't get UDP to work - the system report a Prim Failure. I updated to 1.1.1 and OSC now fails to load, due to a syntax error. Before I dig into this any further, I need to know whether UDP is actually working under Pharo - searching the list archive showed messages saying it was broken, but the bug tracker doesn't show it as a bug. Can anyone enlighten me? Cheers Andy

Jan. 10, 2011

Re: [Pharo-project] new Cog VMs

by Eliot Miranda

Hi All, find new VMs in VM.r2344/<http://www.mirandabanda.org/files/Cog/VM/VM.r2344/> (SimpleStackBasedCogit) and VM.r2345/ <http://www.mirandabanda.org/files/Cog/VM/VM.r2345/> (StackToRegisterMappingCogit) and VMMaker-oscog-45. These fix a bug that could cause crashes when converting an interpreted method to a machine-code method on backward branch (i.e. when the Vm detects an interpreted method is looping). I hope there are no new issues with VM.r2344/<http://www.mirandabanda.org/files/Cog/VM/VM.r2344/> (SimpleStackBasedCogit). However, Matthew Fulmer has found that on linux the VM.r2343/<http://www.mirandabanda.org/files/Cog/VM/VM.r2343/> VM.r2345/ <http://www.mirandabanda.org/files/Cog/VM/VM.r2345/> (StackToRegisterMappingCogit) VMs crash immediately loading Squeak4.2-10856-beta.image. I can reproduce this but haven't had time to investigate. The StackToRegisterMappingCogit VMs do start up this image on Mac and Windows. Agan thanks for pounding on these. I may not be able to attend to the linux/StackToRegisterMappingCogit/Squeak4.2-10856-beta.image until next weekend. Apologies. best Eliot On Thu, Dec 30, 2010 at 6:02 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi All, > > I've released a new version of Cog that has a substantially improved > code generator along the lines of Peter Deutsch's HPS (VisualWorks) and > various of Ian Piumarta's VMs. These all use a simple tecnique to identify > constant references in bytecode and to support a register-based calling > convention. While this does produce faster code it tends to accelerate > low-level code much more than high-level code as you can see by the > following benchmarks: > > SimpleStackBasedCogit: [1 to: 100000000 do: [:i|]] timeToRun 691 > StackToRegisterMappingCogit: [1 to: 100000000 do: [:i|]] timeToRun 192 > 192 - 691 / 6.91 -72% > > SimpleStackBasedCogit: 0 tinyBenchmarks '753495217 bytecodes/sec; 64769127 > sends/sec' > StackToRegisterMappingCogit: 0 tinyBenchmarks '931756141 bytecodes/sec; > 128157989 sends/sec' > 931756141 - 753495217 / 7534952.17 -24% > 128157989 - 64769127 / 647691.27 -98% > > SimpleStackBasedCogit: [Compiler recompileAll] timeToRun 47013 (no > transcript > StackToRegisterMappingCogit: [Compiler recompileAll] timeToRun 43406 (no > transcript) > 43406 - 47013 / 470.13 -7.67234594686576 > > The status of this code is essentially beta. The test suite runs the same > on the new code generator as on the old, but I think there are still bugs > because I get the occasional transient error. I am therefore very > interested in any reproducible errors you can find. > > The VMs (http://www.mirandabanda.org/files/Cog/VM/VM.r2334/) contain a few > other important changes: > > - a bug fix to bytecode<->native pc mappng that produced incorrect results > for methods containing blocks with ^-returns in them. One symptom is > incorrect highlighting of the pc in the debugger, althoguh symptoms could be > much serious. > > - jitting interpreted methods on backward branches. Currently any > interpreted method that performs more than 20 backward branches will be > considered for JIT compilation and if it is suitable (default, <= 60 > literals) will be compiled to native code. > > - new callback support. I need to commit some changes to the Alien package > to provide access to this but essentially the VM's callback support is now > able to be ported to architectures with register-based calling conventions > (ARM, PowerPC, SPARC etc). I'll try and get the Alien code released soon, > and to back-port the changes to the standard VM before the end of the > holiday. > > One thing that is still /not/ fixed is the lack of a SoundPlugin on win32. > Apologies. I'll try and get a fix for this before the end of the holidays > too, but time might be too tight. There are other priorities such as > harmonising the standard and Cog VMs for the 4.2 release. > > best > Eliot > >

Jan. 10, 2011