- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Jtalk, a Smalltalk for web developers

by Hannes Hirzel

More compilers which compile from a dynamic language to JavaScript https://github.com/jashkenas/coffee-script/wiki/List-of-languages-that-comp… Smalltalk not mentioned yet .... --Hannes On 3/21/11, Richard Durr <richard.durr(a)googlemail.com> wrote: > As far as I can see, the only way to call external Javascript is by writing > Javascript-Code directly into a method like so: > doSomethingWith: anObject > {'return SOMELIBRARY.doSomething(anObject); '} > > is this correct? > The OMETA based Smalltalk->JS translator seem to let one use st-syntax for > direct access to javascript like so: > > doSomethingWith: anObject [ > SOMELIBRARY doSomething: anObject. > ] > > and CoffeeScript can use JS seamlessly in the same way. > > Best regards, > RD > > On Mon, Mar 14, 2011 at 7:36 PM, Nicolas Petton > <petton.nicolas(a)gmail.com>wrote: > >> Hi, >> >> I would like to share a project I'm working on on my spare time: Jtalk >> Smalltalk. >> >> http://nicolaspetton.github.com/jtalk >> https://github.com/NicolasPetton/jtalk >> >> Jtalk is an implementation of the Smalltalk language that compiles into >> JavaScript. >> >> Some features: >> - it is written in itself (including the parser/compiler) >> - it is self-contained >> - it compiles into efficient JS code >> - it uses the Squeak chunk format >> - Pharo is considered as the reference implementation >> >> I think Jtalk can be compared to CoffeeScript[1], Objective-J[2] or >> Clamato[3], from which it reuses some ideas and code. >> >> Jtalk includes an IDE with a class browser, transcript and workspace, an >> HTML canvas similar to Seaside and a jQuery binding. >> >> It is still a young piece of code, and some important features are still >> missing/incomplete. >> >> Cheers, >> Nicolas Petton >> >> [1] http://jashkenas.github.com/coffee-script/ >> [2] http://cappuccino.org/ >> [3] http://clamato.net >> >> >> >

March 21, 2011

Re: [Pharo-project] Issue 2299 in pharo: Do not hardcode the color for Workspaces from UIManager

by pharo＠googlecode.com

Updates: Status: Invalid Comment #4 on issue 2299 by marcus.d...(a)gmail.com: Do not hardcode the color for Workspaces from UIManager http://code.google.com/p/pharo/issues/detail?id=2299 This is already changed to be much simpler: edit: aText label: labelString accept: anAction "Open an editor on the given string/text" ^(Workspace openLabel: labelString) acceptContents: aText; acceptAction: anAction; yourself.

March 21, 2011

Re: [Pharo-project] Issue 2594 in pharo: GoferApiTest>>#testSubdirectoryRepository fails

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 2594 by marcus.d...(a)gmail.com: GoferApiTest>>#testSubdirectoryRepository fails http://code.google.com/p/pharo/issues/detail?id=2594 All test are green in 1.2

March 21, 2011

Re: [Pharo-project] Issue 2135 in pharo: New Icons

by pharo＠googlecode.com

Updates: Status: Invalid Comment #7 on issue 2135 by marcus.d...(a)gmail.com: New Icons http://code.google.com/p/pharo/issues/detail?id=2135 I don't know if it is good to have issues like this in the Bug Tracker... We should make a Wishlist somewhere.

March 21, 2011

[Pharo-project] [ANN] SqueakNOS update released!

by Javier PimÃ¡s

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

March 21, 2011

Re: [Pharo-project] Issue 1812 in pharo: Files drag and drop

by pharo＠googlecode.com

Updates: Status: Invalid Comment #4 on issue 1812 by marcus.d...(a)gmail.com: Files drag and drop http://code.google.com/p/pharo/issues/detail?id=1812 This issue has not seen any action since Jan 13, 2010. Timeout (please resubmit for 1.3)

March 21, 2011

Re: [Pharo-project] Issue 3434 in pharo: SharedQueue Fixes

by pharo＠googlecode.com

Comment #3 on issue 3434 by siguc...(a)gmail.com: SharedQueue Fixes http://code.google.com/p/pharo/issues/detail?id=3434 it reminds me that i must finish with AtomicQueue(s), so we can integrate and use them instead.

March 21, 2011

Re: [Pharo-project] [Pharo-users] Do you have a tool that works on Pharo ?

by Dale Henrichs

Mariano, You are correct, you need 1.0-beta.28 or later for symbolic versons to work. I intend to keep Metacello running on all versions of Pharo and Squeak4.x and GemStone. For example, I load Seaside30 into a Pharo1.0 image every time a new Seaside30 version is released. ... If anyone finds a problem with Metacello on any platform or version report it (send mail to the Metacello Group or submit an issue: http://code.google.com/p/metacello/issues/entry) and I will fix the bug. Which just leaves use with "upgrade magic" and the user will have to do that ... at this point, I don't think it is a good idea to have Metacello "phone home" for automatic upgrading, so it takes a manual operation to upgrade: ConfigurationOfMetacello project updateProject. ConfigurationOfMetacello load. I am continuously fixing bugs in Metacello and I recommend that users periodically update to pick up the latest bug fixes, so it is probably worth mentioning at the beginning of the section that folks should upgrade to the latest Metacello version whether or not they plan to load additional tools. You can check for new versions on this page: http://code.google.com/p/metacello/wiki/10betaVersionDescriptions and you can tell what version you are currently running by printing this expression: ConfigurationOfMetacello project currentVersion. Dale On Mar 21, 2011, at 8:55 AM, Mariano Martinez Peck wrote: On Mon, Mar 21, 2011 at 4:50 PM, Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com>> wrote: Alexandre, I agree that symbolic versions should be used in load expressions (when defined), but that should be #'stable', with some missing parens: ((Smalltalk at: #ConfigurationOfOCompletion) project version: #'stable') load. Another problem I found is that symbolic versions where integrated AFTER Pharo 1.0 and 1.1 were released. So, if you document that people should use #stable instead....then they will raise an error in Pharo 1.0 or 1.1. A possible solution is to change your conf so that it makes sure to update Metacello. BUt this is complicated because you cannot be sure that metacello will always work there. IF metacello 28 (where symbolics are) works perfect in 1.0 and 1.1, AND IF there is a magic way to tell metacello to update only to .28 then we can add such code in #stable or some place in the conf.. but I am not sure. I prefer to document clearly. cheers mariano Dale On Mar 21, 2011, at 4:00 AM, Alexandre Bergel wrote: Shouldn't it be: (Smalltalk at: #ConfigurationOfOCompletion) project version: 'stable' load. Instead? Alexandre Le 21 mars 2011 Ã 03:13, laurent laffont <laurent.laffont(a)gmail.com<mailto:laurent.laffont@gmail.com><mailto:laurent.laffont@gmail.com<mailto:laurent.laffont@gmail.com>>> a Ã©crit : Mariano, I've added Autotest. I've seen a lot of Configuration example which won't work because of missing parenthesis: (Smalltalk at: #ConfigurationOfOCompletion) project version: '1.1.2' load. should be ((Smalltalk at: #ConfigurationOfOCompletion) project version: '1.1.2') load. I cannot fix it now - must go to work. Laurent On Sun, Mar 20, 2011 at 11:40 PM, Mariano Martinez Peck <<mailto:marianopeck@gmail.com<mailto:marianopeck@gmail.com>>marianopeck(a)gmail.com<mailto:marianopeck@gmail.com><mailto:marianopeck@gmail.com<mailto:marianopeck@gmail.com>>> wrote: I've added: - Gofer - Monticello - Metacello - Fuel If you can check and improve it..please do. It only took me 30 mins. Cheers Mariano On Sun, Mar 20, 2011 at 11:12 PM, Mariano Martinez Peck <<mailto:marianopeck@gmail.com<mailto:marianopeck@gmail.com>>marianopeck(a)gmail.com<mailto:marianopeck@gmail.com><mailto:marianopeck@gmail.com<mailto:marianopeck@gmail.com>>> wrote: I forgot...If someone answer "but you can browse the MetecelloRepository" or "XX" or "blah"....the answer is that we are not targeting the same people. Someone that knows how that he has to browse MetacelloRepository, probably knows how to install the software, what it is, etc. With this page (after, moved to the pharo website) we want to targe business and new comers. Imagine someone arriving to Pharo and asking himseld "mmmmm does Pharo have XXX that I have in YYY language? ". So the idea is to show all the available tools. Cheers Mariano On Sun, Mar 20, 2011 at 10:42 PM, StÃ©phane Ducasse <<mailto:stephane.ducasse@inria.fr<mailto:stephane.ducasse@inria.fr>>stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr><mailto:stephane.ducasse@inria.fr<mailto:stephane.ducasse@inria.fr>>> wrote: thanks mariano this is a good initiative. Stef On Mar 20, 2011, at 10:22 PM, Mariano Martinez Peck wrote: > 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/> http://book.pharo-project.org/ > > Here we have a list of tools that run on Pharo: <http://book.pharo-project.org/book/PharoTools> 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

March 21, 2011

Re: [Pharo-project] Issue 1465 in pharo: Ocomplection with Enter does not work on Mercury search bar

by pharo＠googlecode.com

Updates: Status: WontFix Comment #5 on issue 1465 by marcus.d...(a)gmail.com: Ocomplection with Enter does not work on Mercury search bar http://code.google.com/p/pharo/issues/detail?id=1465 (No comment was entered for this change.)

March 21, 2011

Re: [Pharo-project] Issue 1299 in pharo: OS Process Crash

by pharo＠googlecode.com

Updates: Status: Closed Comment #8 on issue 1299 by marcus.d...(a)gmail.com: OS Process Crash http://code.google.com/p/pharo/issues/detail?id=1299 Can you re-test in the light of the 1.2 release and new VMs?

March 21, 2011