Re: [Pharo-project] Pharo-project Digest, Vol 29, Issue 84

2010/9/12 Michael Roberts > > Sort of like > > Progressor progressDuring:[:bar | > ... > Progressor progressDuring:[:bar | > ... > Progressor progressDuring:[:bar | > > at different levels in the stack rather than letting the exception find the > notifier each time you would do it

Re: [Pharo-project] Pharo-project Digest, Vol 29, Issue 84

Sort of like Progressor progressDuring:[:bar | ... Progressor progressDuring:[:bar | ... Progressor progressDuring:[:bar | at different levels in the stack rather than letting the exception find the notifier each time you would do it explicitly. Perhaps there is a reason why

Re: [Pharo-project] Pharo-project Digest, Vol 29, Issue 84

When I looked through the code I imagined one could implement the nesting by just maintaining a stack on the progress initiator sort of like ... On 11 Sep 2010, at 16:45, Eliot Miranda wrote: Hi Ralph, On Sat, Sep 11, 2010 at 1:05 AM, Ralph Boland wrote: > Hi, i don't know why thing

[Pharo-project] Updated http://isqueak.org/PlatformVMAPI

I spent a few hours this morning and updated the VM Platform API documentation at http://isqueak.org/PlatformVMAPI To capture the details of the OS-X Cocoa work. (Squeak macintosh VM 5.x) For the most part the iPhone & OS-X implementation share a common Objective-C code base because Apple uses

Re: [Pharo-project] update to OCompletion

On Sun, Sep 12, 2010 at 5:08 AM, Alexandre Bergel wrote: >> This is because when you have a line split into multiple lines, I want Enter >> to mean new line, not complete. This is particularly the case when you have >> pseudo-domain specific languages like in Glamour or Mondrian. > > A bit hard

[Pharo-project] Improving generate accessors for refactoring browser

Dear list, I've noticed that when I'm using the generate accessors refactoring, I'm always adapting the generated code for the mutator: number: anObject number := anObject to: number: aNumber number := aNumber So I've adapted the refactoring code a bit so that it automatically generates

Re: [Pharo-project] Compiling the VM for MacOSX

> > > The instructions seems to target building a VM from April of 2009. Lots has > changed since then to make the > process of building a Cocoa OS-X VM to match a distributed pre-built VM > version more of a one-step process. > > Otherwise it's just too hard to mesh the pieces together bet

Re: [Pharo-project] Alien and multi-threading

2010/9/12 Eliot Miranda > Hi Noury, > > likely there will be, as I'm currently working on threading Cog for > callouts, callbacks et al. But currently I believe there is no > multi-threading of Alien. > Wasen't that the work of the GSoC project? > > best, > Eliot > > On Sun, Sep 12, 2010

[Pharo-project] [ANN] Seaside 3.0 released

The Seaside core developers are pleased to announce the release of Seaside 3.0 - see http://seaside.st/seaside30 for more information. The changes in 3.0 are intended to make using and extending Seaside faster and easier. Useful Links: Full Release Announcement http://seaside.st/seaside30 Seasi

Re: [Pharo-project] Alien and multi-threading

Hi Noury, likely there will be, as I'm currently working on threading Cog for callouts, callbacks et al. But currently I believe there is no multi-threading of Alien. best, Eliot On Sun, Sep 12, 2010 at 9:31 AM, Noury Bouraqadi wrote: > Hi, > > Is there any possibility for multi-threading

[Pharo-project] Alien and multi-threading

Hi, Is there any possibility for multi-threading with Alien? Noury @ ESUG 2010 - Barcelona :-) --- 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. http://www.esug.org/Conferences/2010 ___ Pharo-project mailing

[Pharo-project] [update 1.2] #12140

12140 - Issue 2735: Null Styler for PluggableTextMorph Issue 2960: Fix size for the OverRowMorph in the Browser -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. ___ Pharo-project mailing list Pharo-pr

Re: [Pharo-project] Mark and space parity

Thanks to all who replied. I will try reprogramming the reader to 8n1 and see if that sticks. I still think there is room for the vm to be less aggressive in failing over valid parity values, certainly on Windows now and perhaps on Linux either now or in the future (once support for mark and s

[Pharo-project] [update 1.2] #12139

12139 - Issue 2953: Fixing bug with select in paragraphEditor Issue 2956: remvove #bigDisplay and collapsewinInPlace Issue 2950: ChangeList errors Issue 2954: Accepting method with undefined variable -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. T

Re: [Pharo-project] pharo tests

Welcome linus > Pharo dev's, > > I'm lurking around the Pharo project for a while now. As I wanted to get some > hands-on experience with Pharo I thought it was a good idea to fix an easy > bug and see how it goes. The wiki page on how to contribute, and the two > screen casts are a great help

[Pharo-project] [ANN 1.1] Pre-built core 1.1.1

https://gforge.inria.fr/frs/download.php/27479/PharoCore-1.1.1.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.in

[Pharo-project] [update 1.1] #11414

11414 - - Call releaseClean - Set version number to 1.1.1 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bi

[Pharo-project] pharo tests

Pharo dev's, I'm lurking around the Pharo project for a while now. As I wanted to get some hands-on experience with Pharo I thought it was a good idea to fix an easy bug and see how it goes. The wiki page on how to contribute, and the two screen casts are a great help for newbies like me. Neverthe

Re: [Pharo-project] WebClient License Update

Bonjour cher andreas >>> For string concatenation on the other hand, we're basically talking about >>> dispersing a whole load of FUD about all the things that "may" go wrong. >>> Fact is, nothing actually *does* go wrong with the change, but the change >>> does fix situations that are *very* d

[Pharo-project] [update 1.2] #12138

12138 - Issue 2948: Removing code annotation from source code Issue 2944: fix for systemtemdictionary Issue 2930: Modifiable World menu -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. ___ Pharo-pr

[Pharo-project] [ANN 1.2] pre-built core #12137

https://gforge.inria.fr/frs/download.php/27474/PharoCore-1.2-12137.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.

Re: [Pharo-project] Mark and space parity

Generally, settings are stored in flash and changes should be permanent. Though we have had the odd Datalogic unit that tends to suffer from amnesia! Regards, Gary Sent from my iPad On 11 Sep 2010, at 19:25, "Schwab,Wilhelm K" wrote: > Tony, I *almost* understand that, and greatly appreciate

Re: [Pharo-project] update to OCompletion

> This is because when you have a line split into multiple lines, I want Enter > to mean new line, not complete. This is particularly the case when you have > pseudo-domain specific languages like in Glamour or Mondrian. A bit hard to get used to it, but I agree. > Nevertheless, I would say tha