- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3339 in pharo: WeakOrderedCollection
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3339 by stephane.ducasse: WeakOrderedCollection http://code.google.com/p/pharo/issues/detail?id=3339 Squeak got weak ordered collection and we could want to have that too.

2 2

[Pharo-project] Do you have a tool that works on Pharo ?
by Mariano Martinez Peck March 22, 2011

March 22, 2011

ifTrue: [ self writeOnPharoBook: aTool] We need to improve our documentation. Right now, we have a collaborative book where everyone can join and write: http://book.pharo-project.org/ Here we have a list of tools that run on Pharo: http://book.pharo-project.org/book/PharoTools and it is REALLY important to have such list updated and maintained. So, if you have a tool that works in pharo and it is not there, please add it. If you don't have a user, I can create one for you. If you are TOO lazy, you can send by email the text to me and I write it. Thanks Mariano

7 12

[Pharo-project] Inspector in 1.2
by AxiNat March 22, 2011

March 22, 2011

Hi list, First of all, I'd like to apologise just in case this is already a known issue; I checked and couldn't find it around. I've started working with 1.2 RC a couple days ago, and I noticed the inspector went back to (IIRC) several releases ago. In 1.1 we had tree navigation and were able to run code in context, now you must open a new inspector for each node and the code is always executed from the scope of the root object. I've also noticed you can't remove items from a collection straight from the UI anymore. Thanks! Bernat Romagosa.

3 5

Re: [Pharo-project] test crashing the cog vm
by Marcus Denker March 22, 2011

March 22, 2011

On Mar 22, 2011, at 4:10 PM, Alexandre Bergel wrote: > I see your point and I suspected you spoke according to your experience. I am just trying to make people innovate, in my own way. > But talking is easy. Doing is hard. > Another thing. Keeping the VM small will definitely help when moving to a different executing platform. It would be amazing to have the Pharo running on Javascript VM. > I don't know... Gilad sounds really depressed: http://gbracha.blogspot.com/2011/03/truthiness-is-out-there.html I did not waste the last years fighting about not doing research in Java to now do it on top of another crap. And the things I wan to do are, I think, not possible on top of JavaScript anyway. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] test crashing the cog vm
by Marcus Denker March 22, 2011

March 22, 2011

On Mar 22, 2011, at 3:53 PM, Alexandre Bergel wrote: >>> I am not saying that this is feasible with the current VM. But I am doubtful that the bytecode verification can only be done in the VM. If something get wrong, why not to raise a primitiveFailed, as 1/0 will do? >>> >> Because checking all these things at runtime will make interpretation slow. > > But could not it be at compile time? > Yes. That is called a "bytecode verifier". Now if that would be in the image, you would not gain anything as what you verify is changable. (and the verifier itself, too). > I am not expert in VM. But something that I learnt from all over these years, is that if we copy what other people do, then we will just have a pale copy. Innovation begins by doing what other think it is impossible to do. Smalltalk has classes as object, whereas Java and C++ took a different stance. Smalltalk has the debugger and the profiler in the image; again, java people have a different opinion. Now, if someone say that bytecode verification can only be done in the VM, I am skeptic. > It can only be done in the VM if what you have is a standard smalltalk system. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] We are preparing to this year Google Summer of Code (GSoC)
by Janko MivÅ¡ek March 22, 2011

March 22, 2011

Dear Smalltalkers, I'd like to inform you that we are preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects. Please start thinking about ideas what projects would be nice to have. Also start looking around for students. How to approach the universitites near by you, do you know who to contact there, etc. To see last year ideas and accepted/done projects, visit last year http://gsoc2010.esug.org. More on our already open special Smalltalk GSoC 2011 website: http://gsoc2011.esug.org I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC: http://groups.google.com/group/smalltalk-gsoc-mentors Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

4 5

Re: [Pharo-project] Issue 1909 in pharo: Rectangle In place merging for Morphic
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Comment #5 on issue 1909 by fernando...(a)gmail.com: Rectangle In place merging for Morphic http://code.google.com/p/pharo/issues/detail?id=1909 Could this issue be closed? Given the that Juan's significative speedup in GUI in CUIS is somehow related to this, without changing anything.

1 0

[Pharo-project] Issue 3753 in pharo: SimpleMorphic Layout Code missing
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: New Owner: ---- New issue 3753 by Ken.Dic...(a)whidbey.com: SimpleMorphic Layout Code missing http://code.google.com/p/pharo/issues/detail?id=3753 Cuis code for layouts is missing & I am unable to port a solitaire card game without them. Pharo image: Pharo-core 2.1 rc2 Pharo core version: 12366 Virtual machine used: VM in Pharo-1.1-OneClick.app Steps to reproduce: 1. Open a file browser and file in SimpleMorphicSolitaire.1.cs Attachments: SimpleMorphSolitaire.1.cs 276 KB

1 6

Re: [Pharo-project] Issue 1836 in pharo: Adding dedicated accessors for VM parameters
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Updates: Status: Started Labels: Milestone-1.2 Comment #9 on issue 1836 by jbaptist...(a)gmail.com: Adding dedicated accessors for VM parameters http://code.google.com/p/pharo/issues/detail?id=1836 (No comment was entered for this change.)

1 6

[Pharo-project] [ANN] SqueakNOS update released!
by Javier PimÃ¡s March 22, 2011

March 22, 2011

For all those who may be intrested, we are glad to announce that we have just uploaded an updated version of SqueakNOS to our site. You can find the updated download links here <http://squeaknos.blogspot.com/p/download.html>. This release adds the following items to the previous version: (99.9% modeled with objects) - Improved support for ATA devices access - Implementation of a model of files and directories - Implementation of FAT32 filesystem - Support for reading sources from the hard disk - Support for X86 paging setup and handling of page faults - Implementation of a model of free and used memory - Implementation of image snapshotting (based on the paging mechanism) - Based on Pharo, but also supporting Squeak and Cuis - Added some primitives for communicating between VM and image - Support for Alien and FFI - Added basic support for writing to serial via VM so that it's possiblo to out debug info to the outside world. - Added pretty basic ATA benchmarks - Added some scripts to automatize work done from the outside world - Many code cleanups Future directions are: - Support for Cog VM - Investigate replacing SqueakNOS plugin with NativeBoost so that we do more on the image - Offloading memory pages to disk - More tests - Benchmarks For the brave ones, remember that you can always generate a SqueakNOS image by using the ConfigurationOfSqueakNOS (which is a bit outdated now), or by manually loading the packages from monticello. Also to generate a SqueakNOS VM download its code from GIT (hosted on sourceforge.net) Don't forget to visit squeaknos.blogspot.com for news and instructions. We hope to be able to write more soon. Many thank's t all the people who made it possible to understand the code and to develop all this. SqueakNOS' Team -- Javier PimÃ¡s Ciudad de Buenos Aires

7 10