Re: [Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

[pharo]

Updates:
Status: Closed

Comment #6 on issue 3960 by marcus.d...@gmail.com: Catch all: Remove  
experimental + ancient backward compatibility code

http://code.google.com/p/pharo/issues/detail?id=3960

in 14143

Re: [Pharo-project] Issue 3990 in pharo: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

[pharo]

Updates:
Status: Started

Comment #2 on issue 3990 by marcus.d...@gmail.com: 2 dependencies removed  
from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

http://code.google.com/p/pharo/issues/detail?id=3990

Nope. needs testing. (I had problems with the world menu after)

Re: [Pharo-project] Issue 3800 in pharo: StaticForm can be removed

[pharo]

Updates:
Status: Closed

Comment #5 on issue 3800 by marcus.d...@gmail.com: StaticForm can be removed
http://code.google.com/p/pharo/issues/detail?id=3800

in 14143

Re: [Pharo-project] Issue 3989 in pharo: Fix the scrollToView method

[pharo]

Updates:
Status: Closed

Comment #1 on issue 3989 by marcus.d...@gmail.com: Fix the scrollToView  
method

http://code.google.com/p/pharo/issues/detail?id=3989

in 14143

Re: [Pharo-project] Issue 3990 in pharo: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

[pharo]

Updates:
Status: Closed

Comment #1 on issue 3990 by marcus.d...@gmail.com: 2 dependencies removed  
from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

http://code.google.com/p/pharo/issues/detail?id=3990

in 14143

Re: [Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2

[pharo]

Updates:
Cc: roeth...@iam.unibe.ch
Labels: Type-O2

Comment #2 on issue 3992 by marcus.d...@gmail.com: Proposed O2 fixes for  
Pharo-1.2

http://code.google.com/p/pharo/issues/detail?id=3992

(No comment was entered for this change.)

Re: [Pharo-project] Using SMark

[Stefan Marr]

Hi Javier:


On 12 Apr 2011, at 04:52, Javier Pimás wrote:

> Hi, I need to do some benchmarking on SqueakNOS and I'm exploring SMark. I 
> downloaded the SMark and PBenchmarks packages from monticello, but now I 
> don't know what to do to use it. The tests pass mostly OK, but, how do you 
> run the existing benchs?

To execute a benchmark suite, you can just send it the #run, or 
#run:withAnIntForTheNumberOfIterations messages.
This will return the runner, that also has the results.
The results are then processed or reported by one of the reporters, but there 
aren't many yet.

Depending on your needs, you might also want to use another runner then the 
standard one.
How to use them is currently probably documented best in the tests.
But there are also some class comments here and there.

> Is there any tool for visualizing the results?

There is nothing fancy like the test runner UI.

But the following should work:

| runner |
runner := SMarkLoops run: 10.
SMarkSimpleStatisticsReporter reportFor: runner on: Transcript.  

Best regards
Stefan




> 
> Thanks,
>   Javier.
> 
> -- 
> Javier Pimás
> Ciudad de Buenos Aires

-- 
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax:   +32 2 629 3525

Re: [Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2

[pharo]

Comment #1 on issue 3992 by nicholas...@gmail.com: Proposed O2 fixes for  
Pharo-1.2

http://code.google.com/p/pharo/issues/detail?id=3992

Since this is the first time I am doing this following the instructions at  
 I expect that I might  
have missed some steps. In that case please let me know and I can fix them.


I've also attached the SLICE here just in case.

Attachments:
SLICE-Issue-3992-Proposed-O2-fixes-for-Pharo-12-NC.1.mcz  23.4 KB

[Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2

[pharo]

Status: New
Owner: 

New issue 3992 by nicholas...@gmail.com: Proposed O2 fixes for Pharo-1.2
http://code.google.com/p/pharo/issues/detail?id=3992

Pharo Metainfo
-

Pharo image: dev
Pharo core version: Pharo1.2.1
Virtual machine used: Cog VM.r2378

Description
--

Follow the full discussion at  
.


I completely agree with Stéphane Ducasse's comments about O2 being outdated  
and how it will be replaced soon. But since I've ported it, I might as well  
share it with the community in case someone else is interested.


These are the fixes to make it possible to load O2 into a Pharo-1.2 Dev  
image. It is based off the latest version of the code from the O2  
repository (http://www.squeaksource.com/O2) made by David Roethlisberger.


Notable changes:

* Removed all references to Preferences (deprecated in Pharo 1.2)
* Removed most preferences that I could not find any references to.
* Made test cases pass (mostly adapting the tests to the new TestCase  
hierarchy that it was testing for)


Remaining problems:

* Undo/redo does not work in the editor. This is probably because Pharo-1.2  
changed the TextEditor components (i.e. uses EditingState).
* Lots of duplication between O2 and OB. Not sure whether to  
merge/eliminate duplication since these browsers seem to be quite  
independent and I don't enough of their ecosystem to say if we should merge.

[Pharo-project] Using SMark

[Javier Pimás]

Hi, I need to do some benchmarking on SqueakNOS and I'm exploring SMark. I
downloaded the SMark and PBenchmarks packages from monticello, but now I
don't know what to do to use it. The tests pass mostly OK, but, how do you
run the existing benchs? Is there any tool for visualizing the results?

Thanks,
  Javier.

-- 
Javier Pimás
Ciudad de Buenos Aires

Re: [Pharo-project] UIBuilder Tool

[nullPointer]

The development of UIBuilder is closed from time ago, but perhaps I could
write a little doc with basic concepts.

Anyway I recommend the fantastic new MorphicDesigner:

http://www.youtube.com/watch?v=rx67fjK39Qg
http://www.youtube.com/watch?v=v7PTQcN_8Go
http://www.youtube.com/watch?v=WTMSFt5vYfo

Regards.

--
View this message in context: 
http://forum.world.st/UIBuilder-Tool-tp3442594p3443571.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

[Pharo-project] [Guillermo Polito, Benjamin Van Ryseghem] Issue 3088: MNU Text>>withBlanksTrimmed

[Bernardo Ezequiel Contreras]

Guillermo Polito and Benjamin Van Ryseghem,

Could you check your changes made to ProtocolBrowser>>initListFrom:
selectorCollection highlighting: aClass ?
It's related to http://code.google.com/p/pharo/issues/detail?id=3088

Basically,
Guillermo added the line

stringVersion: item asString

and then Benjamin replaced it with

stringVersion: item

So, now the Protocol Browser is creating SourceMethodReferences with Texts
as stringVersion.
you can view those instances if you follow the steps and then execute

SourcedMethodReference allInstances
  select: [:each | each stringVersion class == Text ]

And it leads to http://code.google.com/p/pharo/issues/detail?id=3088

For what i saw, the fix will be to add Guillermo's line again but im not
sure. its confusing.

What do you think?

Thanks

Re: [Pharo-project] Brussels Sprint: gathering number of attendes

[Camillo Bruni]

I'll come as well ;)

On 2011-04-11, at 17:39, Stefan Marr wrote:
> On 11 Apr 2011, at 17:33, Veronica Isabel Uquillas Gomez wrote:
>> On 11 Apr 2011, at 11:23, Johan Brichau wrote:
>>> - Steph
>>> - Marcus
>>> - Sven
>>> - Mariano
>>> - Craig Latta
>>> - Thomas Holzer
>>> - Andy
>>> - Johan
>> 
>> -> Veronica
> -> Stefan
-> Camillo

[Pharo-project] Issue 3991 in pharo: use them instead of UITheme current

[pharo]

Status: Accepted
Owner: stephane...@gmail.com
Labels: Milestone-1.3

New issue 3991 by stephane...@gmail.com: use them instead of UITheme current
http://code.google.com/p/pharo/issues/detail?id=3991

I found

theme
"Answer the current theme for the receiver."

(self valueOfProperty: #theme) ifNotNil: [:t | ^ t].
^(self window ifNil: [self class]) theme

in Morph

theme: aUITheme
"Set the current theme for the receiver."

self theme = aUITheme ifFalse: [
self setProperty: #theme toValue: aUITheme.
self themeChanged]

and theme is defined on the Morph class so this means that we can change  
the UITheme current by self theme :)



Stef

[Pharo-project] [update 1.3] #13142

[Stéphane Ducasse]

13142
-

- continued to merged ploymoprh overrides
- Repackaged SUnit
- Use new Glamour refactored code but to avoid problems to Doru renamed it into 
BluePharo - should remove the PharoUITheme. We should migrate the orange look 
to be a subclass of BlueUITheme

Stef

Re: [Pharo-project] A question about UIManager

[Stéphane Ducasse]

I found 

theme
"Answer the current theme for the receiver."

(self valueOfProperty: #theme) ifNotNil: [:t | ^ t].
^(self window ifNil: [self class]) theme

in Morph

theme: aUITheme
"Set the current theme for the receiver."

self theme = aUITheme ifFalse: [
self setProperty: #theme toValue: aUITheme.
self themeChanged]

and theme is defined on the Morph class so this means that we can change the 
UITheme current by self theme :)


Stef

Re: [Pharo-project] Issue 3984 in pharo: Announcements announced when a test is runned

[pharo]

Comment #2 on issue 3984 by ryd...@gmail.com: Announcements announced when  
a test is runned

http://code.google.com/p/pharo/issues/detail?id=3984

Also, should this be done by an announcer of a TestRunner, or is  
SystemAnnouncer ok?


To me, that seems a bit strange of a place to be announcing them :)

Re: [Pharo-project] Issue 3984 in pharo: Announcements announced when a test is runned

[pharo]

Comment #1 on issue 3984 by ryd...@gmail.com: Announcements announced when  
a test is runned

http://code.google.com/p/pharo/issues/detail?id=3984

Please... no Announcement at the end of class name :)
Announcements are action notifications, and their names should indicate  
that.


Also, Runned is not English, either Ran, or Finished, or Completed, etc.

Re: [Pharo-project] A question about UIManager

[Stéphane Ducasse]

I was reading code on UITheme current everywhere and I was thinking:
either we can add a method in Morph or we could add a trait for 
ThemeAndInteraction: uimanager, uitheme

I think that using a trait would be good because we could have Morph that is 
the underlying layer and the tools and widgets that need to be theme managed
using the trait.
What do you think?
There is already TEasyTheme but to me it looks too large.

Stef

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

[pharo]

Comment #6 on issue 3982 by ryd...@gmail.com: Error: can''t find EOCD  
position

http://code.google.com/p/pharo/issues/detail?id=3982

This is what you see when squeaksource returns an error- I'm down page, and  
monticello tries to read that page as a zip file.


If you encounter it again, wait a bit, then try upgrading again.

Re: [Pharo-project] fonts on Pharo website

[Stéphane Ducasse]

It does not work on my safari :)
Please revert ;D

On Apr 11, 2011, at 1:55 PM, Adrian Lienhard wrote:

> hehe, I wondered how long it takes to notice the new fonts ;)
> 
> We can revert to the old font if the web font is not an improvement... Geert 
> also noted that the font we embedded does not look the same on all 
> browsers/platforms.
> 
> Cheers,
> Adrian
> 
> 
> On Apr 11, 2011, at 13:47 , laurent laffont wrote:
> 
>> Hi,
>> 
>> For me the new fonts used on www.pharo-project.org are hard to read. The
>> rendering on Firefox / Windows is not nice too.
>> 
>> What do you think ?
>> 
>> Laurent Laffont
> 
> 

Re: [Pharo-project] A question about UIManager

[Stéphane Ducasse]

>>> the class in a single uiManager method in Morph is a good idea. So i
>>> vote in favor of  Morph>>uiManager ^ MorphicUIManager default.

But it should not be 
MorphicUIManager default.

because else we cannot use the DummyUIManager.
So it should be UIManager default.

In general referencing to subclasses defeat the purpose of UIManager


On Apr 11, 2011, at 8:57 AM, Fernando Olivero wrote:

> Actually i havent uploaded the fix yet, so this is good because now i
> can modify the changeset to adopt Morph>>uiManager.
> 
> Stef, what do you think about the class vars of SystemWindow, should
> they also be moved to UIManager: for example TopWindow and associated
> protocol.

I do not know.

> In Issue 3917:Make all uses of SystemWindow go thru UIManger, i
> provided an initial implementation. I've replaced the refs of
> SystemWindow to UIManager>>newWindowLabelled: aString,

yes it looks good.

> and eliminated the class vars in favor of ivars of the MorphiUIManager.

I do not know for this one.

Sytef

> 
> Fernando
> 
> On Mon, Apr 11, 2011 at 7:37 AM, Stéphane Ducasse
>  wrote:
>> thanks!
>> 
>> Stef
>> 
>> On Apr 10, 2011, at 10:31 PM, Fernando Olivero wrote:
>> 
>>> I believe that any UI element, should answer uiManager. And hardcoding
>>> the class in a single uiManager method in Morph is a good idea. So i
>>> vote in favor of  Morph>>uiManager ^ MorphicUIManager default.


>>> 
>>> Following the same line of thought we should do the same for the
>>> globals World, ActiveWorld, ActiveEvent and ActiveHand.
>>> I've provided with the code in  Issue 3903:   Removing the Globals
>>> World, ActiveHand and ActiveEvent. As well as direct references to
>>> WorldState.
>>> 
>>> Fernando
>>> 
>>> On Sun, Apr 10, 2011 at 9:21 PM, Stéphane Ducasse
>>>  wrote:
 Hi pharoers
 
 I was trying to change MenuMorph direct reference to use UIManager because 
 I was thinking
 that a popup menu should not open alone but this is the responsibility of 
 the UIManager and I was not happy.
 why because we have these
UIManager default
 
 and I started to think about them (ok I'm dead nearly sleeping at 9 in the 
 evening because I took too much sun
 and walk today). My gut feeling is that at least for UI code, any UI 
 element could have an access to the current UIManager
 via an instance variable or a message.
self uiManager.
 Now may be the UI World should point to the UIMAnager and each graphical 
 element should access it like that.
 For non UI class then this is a different story.
 
 But I would like to get your point of view on that point.
 
 Tx
 
 stef
 
>>> 
>> 
>> 
> 

Re: [Pharo-project] Improving Pharo's Exception Hierarchy

[Stéphane Ducasse]

this is a good idea.
Now pay attention that we should restart to work on integrating FS and that the 
file exception may change.

Stef

On Apr 11, 2011, at 4:10 PM, Sven Van Caekenberghe wrote:

> Hi All,
> 
> I have this idea that I would like to discuss on the next Pharo sprint and 
> maybe start to implement if there is some consensus on it.
> 
> It has been mentioned many times before on this list that Object>>#error: 
> should be replaced by signalling specific Exceptions in as many cases as 
> possible (or where it makes sense). Even today, there was 
> http://code.google.com/p/pharo/issues/detail?id=3987 !
> 
> I think the core system should set the example here, by defining a number of 
> general purpose exceptions and by using them. Going over #error: senders will 
> be a lot of work but can be done in incremental/Pharo steps.
> 
> So I went over the current hierarchy, scanned quickly through their 
> references and some #error: senders by fundamental classes and looked at some 
> other Smalltalks. I came up with the following very rough draft of an 
> extended hierarchy (** marks new exceptions). In between brackets are the 
> instance variables. Of course, we have to discuss about naming, instance 
> variables and opportunities for reuse and inheritance (could be fun). 
> 
> I am no expert on exceptions and would certainly like to learn more. I am 
> probably overlooking some aspects. We have to keep this Smalltalk like, 
> flexible, dynamic, not start mimicing other languages. 
> 
> Any step in this direction will be an improvement over the current situation. 
> Really using them correctly throughout the system will take some time. 
> Defining the hierarchy could be done rather quickly. Refactoring is always 
> possible later on.
> 
> Exception (messageText)
>  Abort
>  Error
>ArithemticError
>  ZeroDivide (dividend)
>  FloatingPointException
>  RangeError ** (from, to)
>  NaNError **
>FileStreamException (fileName)
>  FileDoesNotExistException (readOnly)
>  FileExistsException (fileClass)
>  CannotDeleteFileException
>  FileWriteError
>  FileReadError **
>  FileClosedException **
>  CannotAccessFileException **
>  ReadonlyFileException **
>MessageNotUnderstood (message, receiver)
>NonBooleanReceiver (object)
>OutOfMemory
>Halt
>  AssertionFailure
>  BreakPoint
>SyntaxError ** !exists! (input, position)
>  NumberFormatException **
>HeadlessError **
>TimedOut ** (object, operation, timeout)
>VerificationException
>IllegalOperation ** (operation, object)
>SizeMismatch (objects)
>LowMemory ** (percentageFree)
>SubclassResponsibility ** (message, receiver)
>NotYetImplemented ** (message, receiver)
>CannotInstanciate ** (class)
>ReadOnlyObject ** (object)
>OutOfFreeSpace ** (object, size)
>InvalidArgument ** (message, receiver, argument)
>NotIndexable ** (object)
>NoKeyedAccess ** (object)
>NonIntegerIndex ** (receiver, index)
>SubscriptOutOfBounds ** (receiver, index, from, to)
>NotFoundException ** (receiver, object)
>  KeyNotFound **
>  ValueNotFound **
>  ElementNotFound **
>StreamException (stream)
>  PositionError ** (index, from, to) 
>  EndOfStream **
>  BeginOfStream ** 
> 
> All feedback is welcome.
> 
> Regards,
> 
> Sven
> 
> 
> 

Re: [Pharo-project] [COTDC] 46 - SUnitUnloader

[Sven Van Caekenberghe]

I am SUnitUnloader, a little tool to unload SUnit and a fixed set of Tests from 
the current image.

Usage: SUnitUnloader new unloadAll

Caveat: #unloadTestPackages uses a fixed and probably ill maintained list of 
what packages hold unit tests.


On 11 Apr 2011, at 20:21, laurent laffont wrote:

> Today:  SUnitUnloader
> 
> 
> Comment Of The Day Contest - One Day One Comment
> Rules: 
> #1: Each day a not commented class is elected. Each day the best comment will 
> be integrated with name of the author(s).
> #2: If you cannot comment it, deprecate it.
> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest
> 
> Laurent

Re: [Pharo-project] UIBuilder Tool

[eMko]

You can download it from squeaksource
http://www.squeaksource.com/UIBuilder.html .

If you want some practical information, watch youtube

http://www.google.cz/search?q=uibuilder+pharo+youtube&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:cs:official&client=firefox-a#q=uibuilder+pharo+youtube&hl=cs&client=firefox-a&hs=hu1&rls=org.mozilla:cs:official&prmd=ivns&source=univ&tbm=vid&tbo=u&sa=X&ei=NkajTbCiHsiBOt7LvTQ&ved=0CDkQqwQ&fp=46e891d5c7303f5e

One big drawback of Pharo smalltalk is lack of good documentation, but
things are getting better and better.

--
View this message in context: 
http://forum.world.st/UIBuilder-Tool-tp3442594p3442745.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

[Pharo-project] [COTDC] 46 - SUnitUnloader

[laurent laffont]

 Today:  SUnitUnloader


Comment Of The Day Contest - One Day One Comment
Rules:
#1: Each day a not commented class is elected. Each day the best comment
will be integrated with name of the author(s).
#2: If you cannot comment it, deprecate it.
Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest

Laurent

Re: [Pharo-project] [COTDC] 45 - TestCoverage

[laurent laffont]

On Fri, Apr 8, 2011 at 5:59 PM, Alexandre Bergel wrote:

> Is this class work with Cog?
>

yes

Laurent.


>
> Alexandre
>
>
> On 8 Apr 2011, at 10:53, laurent laffont wrote:
>
> > Today:  TestCoverage
> >
> >
> > Comment Of The Day Contest - One Day One Comment
> > Rules:
> > #1: Each day a not commented class is elected. Each day the best comment
> will be integrated with name of the author(s).
> > #2: If you cannot comment it, deprecate it.
> > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest
> >
> > Laurent
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
>

Re: [Pharo-project] [COTDC] 45 - TestCoverage

[laurent laffont]

I wrap a method in order to detect whether it has been called or not. Then I
can be used to calculate test coverage for SUnit.

Laurent.

On Fri, Apr 8, 2011 at 4:53 PM, laurent laffont
wrote:

> Today:  TestCoverage
>
>
> Comment Of The Day Contest - One Day One Comment
> Rules:
> #1: Each day a not commented class is elected. Each day the best comment
> will be integrated with name of the author(s).
> #2: If you cannot comment it, deprecate it.
> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest
>
> Laurent
>

Re: [Pharo-project] FAQ migration

[Benoit St-Jean]

Perhaps, to make sure we don't forget anything and that we cover everything a 
newbie could ask himself, I think we should take a close look at all the 
examples included in Dave N. Smith' FAQ and do something similar (or at least 
get some inspiration from his FAQ) :

http://udos.users.dolphinmap.net/archive/DavesSmalltalkFAQ.pdf 

 -
Benoit St-Jean
Yahoo! Messenger: bstjean
A standpoint is an intellectual horizon of radius zero.
(Albert Einstein)

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

[pharo]

Comment #15 on issue 3088 by vonbecm...@gmail.com: MNU  
Text>>withBlanksTrimmed

http://code.google.com/p/pharo/issues/detail?id=3088

if you try several times with classes from Announcements-Core,
then the query will return more elements each time you follow the steps.

an Array(Announcement >> #asAnnouncement Announcement >> #open Announcer >>  
#announce: Announcer >> #basicSubscribe: Announcer >> #initialize Announcer  
#numberOfSubscriptions Announcer >> #on:do: Announcer >> #on:send:to:  
Announcer >> #open Announcer >> #removeSubscription: Announcer >>  
#replace:with: Announcer >> #subscribe:do: Announcer >> #subscribe:send:to:  
Announcer >> #unsubscribe: Announcer >> #weak Announcer >> #when:do:  
Announcer >> #announce: Announcer >> #basicSubscribe: Announcer >>  
#initialize Announcer >> #numberOfSubscriptions Announcer >> #on:do:  
Announcer >> #on:send:to: Announcer >> #open Announcer >>  
#removeSubscription: Announcer >> #replace:with: Announcer >>  
#subscribe:do: Announcer >> #subscribe:send:to: Announcer >> #unsubscribe:  
Announcer >> #weak Announcer >> #when:do:)

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

[pharo]

Updates:
Status: Started

Comment #14 on issue 3088 by marcus.d...@gmail.com: MNU  
Text>>withBlanksTrimmed

http://code.google.com/p/pharo/issues/detail?id=3088

(No comment was entered for this change.)

[Pharo-project] Issue 3990 in pharo: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

[pharo]

Status: FixProposed
Owner: benjamin...@gmail.com
Labels: Milestone-1.3

New issue 3990 by benjamin...@gmail.com: 2 dependencies removed from  
ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

http://code.google.com/p/pharo/issues/detail?id=3990

We removed 2 dependencies to ToolBuilder when creating menus.
We've decided to keep PluggableMenuSpec & PluggableMenuItemSpec from  
ToolBuilder.


Attachments:
LittleCleanInToolBuilderHierarchy.2.cs  2.6 KB

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

[pharo]

Comment #13 on issue 3088 by vonbecm...@gmail.com: MNU  
Text>>withBlanksTrimmed

http://code.google.com/p/pharo/issues/detail?id=3088

Pharo image: Pharo1.3a#13140
Virtual machine used: Squeak4.1 of 17 April 2010 [latest update: #9957]
Platform Name: unix
Class browser used (if applicable): Browser

did you follow the steps? because i did and it does not work.

steps to reproduce
1. follow the steps to reproduce at the beginning.
2. this MNU
3. execute the query
SourcedMethodReference allInstances
  select: [:each | each stringVersion class == Text ]

you will get two methods



Attachments:
PharoDebug.log  29.9 KB

[Pharo-project] UIBuilder Tool

[sourav roy]

HiI am new to smalltalk and have got fascinated by itsconcepts Can i get 
any information about how to get the UIBuilder Tool integrated with my Pharo 
1.1.1What is the link to download the patch if any.Please help me 
ASAP.Thanks®ards,Sourav RoyGet Yourself a cool, short @in.com Email ID now!

Re: [Pharo-project] Improving Pharo's Exception Hierarchy

[Alexandre Bergel]

Hi Sven,

+1
The exception hierarchy needs some work, indeed. 
If you make all your new exception a subclass of Error, you should not have a 
problem with the existing handler I imagine.

Alexandre



On 11 Apr 2011, at 10:10, Sven Van Caekenberghe wrote:

> Hi All,
> 
> I have this idea that I would like to discuss on the next Pharo sprint and 
> maybe start to implement if there is some consensus on it.
> 
> It has been mentioned many times before on this list that Object>>#error: 
> should be replaced by signalling specific Exceptions in as many cases as 
> possible (or where it makes sense). Even today, there was 
> http://code.google.com/p/pharo/issues/detail?id=3987 !
> 
> I think the core system should set the example here, by defining a number of 
> general purpose exceptions and by using them. Going over #error: senders will 
> be a lot of work but can be done in incremental/Pharo steps.
> 
> So I went over the current hierarchy, scanned quickly through their 
> references and some #error: senders by fundamental classes and looked at some 
> other Smalltalks. I came up with the following very rough draft of an 
> extended hierarchy (** marks new exceptions). In between brackets are the 
> instance variables. Of course, we have to discuss about naming, instance 
> variables and opportunities for reuse and inheritance (could be fun). 
> 
> I am no expert on exceptions and would certainly like to learn more. I am 
> probably overlooking some aspects. We have to keep this Smalltalk like, 
> flexible, dynamic, not start mimicing other languages. 
> 
> Any step in this direction will be an improvement over the current situation. 
> Really using them correctly throughout the system will take some time. 
> Defining the hierarchy could be done rather quickly. Refactoring is always 
> possible later on.
> 
> Exception (messageText)
>  Abort
>  Error
>ArithemticError
>  ZeroDivide (dividend)
>  FloatingPointException
>  RangeError ** (from, to)
>  NaNError **
>FileStreamException (fileName)
>  FileDoesNotExistException (readOnly)
>  FileExistsException (fileClass)
>  CannotDeleteFileException
>  FileWriteError
>  FileReadError **
>  FileClosedException **
>  CannotAccessFileException **
>  ReadonlyFileException **
>MessageNotUnderstood (message, receiver)
>NonBooleanReceiver (object)
>OutOfMemory
>Halt
>  AssertionFailure
>  BreakPoint
>SyntaxError ** !exists! (input, position)
>  NumberFormatException **
>HeadlessError **
>TimedOut ** (object, operation, timeout)
>VerificationException
>IllegalOperation ** (operation, object)
>SizeMismatch (objects)
>LowMemory ** (percentageFree)
>SubclassResponsibility ** (message, receiver)
>NotYetImplemented ** (message, receiver)
>CannotInstanciate ** (class)
>ReadOnlyObject ** (object)
>OutOfFreeSpace ** (object, size)
>InvalidArgument ** (message, receiver, argument)
>NotIndexable ** (object)
>NoKeyedAccess ** (object)
>NonIntegerIndex ** (receiver, index)
>SubscriptOutOfBounds ** (receiver, index, from, to)
>NotFoundException ** (receiver, object)
>  KeyNotFound **
>  ValueNotFound **
>  ElementNotFound **
>StreamException (stream)
>  PositionError ** (index, from, to) 
>  EndOfStream **
>  BeginOfStream ** 
> 
> All feedback is welcome.
> 
> Regards,
> 
> Sven
> 
> 
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-project] Issue 2703 in pharo: Unicode experiments of nicolas cellier on squeak

[pharo]

Updates:
Status: Closed

Comment #7 on issue 2703 by marcus.d...@gmail.com: Unicode experiments of  
nicolas cellier on squeak

http://code.google.com/p/pharo/issues/detail?id=2703

in 13141

Re: [Pharo-project] Issue 3987 in pharo: Use specific KeyNotFoundError in Dictionaries

[pharo]

Updates:
Status: Closed

Comment #2 on issue 3987 by marcus.d...@gmail.com: Use specific  
KeyNotFoundError in Dictionaries

http://code.google.com/p/pharo/issues/detail?id=3987

in 13141

[Pharo-project] [update 1.3] #13141

[Marcus Denker]

13141
-

Issue 3988: Debugger cannot open because of Decompiler assertion failure
Issue 3980: TestResource fails to makeAvailable an never recovers
Issue 3987: Use specific KeyNotFoundError in Dictionaries
Issue 2703: Unicode experiments of nicolas cellier on squeak


--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

[pharo]

Comment #3 on issue 3980 by marcus.d...@gmail.com: TestResource fails to  
makeAvailable an never recovers

http://code.google.com/p/pharo/issues/detail?id=3980

in 13141

TODO: 1.2

Re: [Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

[pharo]

Updates:
Status: Closed

Comment #3 on issue 3988 by marcus.d...@gmail.com: Debugger cannot open  
because of Decompiler assertion failure

http://code.google.com/p/pharo/issues/detail?id=3988

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

[pharo]

Updates:
Labels: Milestone-1.3

Comment #2 on issue 3988 by marcus.d...@gmail.com: Debugger cannot open  
because of Decompiler assertion failure

http://code.google.com/p/pharo/issues/detail?id=3988

in 13141

Re: [Pharo-project] Brussels Sprint: gathering number of attendes

[Stefan Marr]

On 11 Apr 2011, at 17:33, Veronica Isabel Uquillas Gomez wrote:
> On 11 Apr 2011, at 11:23, Johan Brichau wrote:
>> - Steph
>> - Marcus
>> - Sven
>> - Mariano
>> - Craig Latta
>> - Thomas Holzer
>> - Andy
>> - Johan
> 
> -> Veronica
-> Stefan


-- 
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax:   +32 2 629 3525

Re: [Pharo-project] Brussels Sprint: gathering number of attendes

[Veronica Isabel Uquillas Gomez]

On 11 Apr 2011, at 11:23, Johan Brichau wrote:

> Hi everyone.
> 
> To make sure we have enough food and drinks for everyone. Please make sure to 
> let us know you are coming.
> From previous emails, I have understood the following people are attending:
> 
> - Steph
> - Marcus
> - Sven
> - Mariano
> - Craig Latta
> - Thomas Holzer
> - Andy
> - Johan

-> Veronica

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

[pharo]

Updates:
Status: Closed

Comment #5 on issue 3982 by marcus.d...@gmail.com: Error: can''t find EOCD  
position

http://code.google.com/p/pharo/issues/detail?id=3982

(No comment was entered for this change.)

[Pharo-project] Issue 3989 in pharo: Fix the scrollToView method

[pharo]

Status: FixProposed
Owner: benjamin...@gmail.com
Labels: Nautilus

New issue 3989 by benjamin...@gmail.com: Fix the scrollToView method
http://code.google.com/p/pharo/issues/detail?id=3989

Like that, even if the method has been chooser without using the  
keyboard/mouse, the selection is shown "properly"


Because it's hard to reproduce, I'm not sure it fix totally the issue, but  
I'm testing it right now, and if some of you want to test it, you're welcome


Attachments:
MorphTreeMorph.BenjaminVanRyseghem.2.cs  424 bytes

[Pharo-project] Improving Pharo's Exception Hierarchy

[Sven Van Caekenberghe]

Hi All,

I have this idea that I would like to discuss on the next Pharo sprint and 
maybe start to implement if there is some consensus on it.

It has been mentioned many times before on this list that Object>>#error: 
should be replaced by signalling specific Exceptions in as many cases as 
possible (or where it makes sense). Even today, there was 
http://code.google.com/p/pharo/issues/detail?id=3987 !

I think the core system should set the example here, by defining a number of 
general purpose exceptions and by using them. Going over #error: senders will 
be a lot of work but can be done in incremental/Pharo steps.

So I went over the current hierarchy, scanned quickly through their references 
and some #error: senders by fundamental classes and looked at some other 
Smalltalks. I came up with the following very rough draft of an extended 
hierarchy (** marks new exceptions). In between brackets are the instance 
variables. Of course, we have to discuss about naming, instance variables and 
opportunities for reuse and inheritance (could be fun). 

I am no expert on exceptions and would certainly like to learn more. I am 
probably overlooking some aspects. We have to keep this Smalltalk like, 
flexible, dynamic, not start mimicing other languages. 

Any step in this direction will be an improvement over the current situation. 
Really using them correctly throughout the system will take some time. Defining 
the hierarchy could be done rather quickly. Refactoring is always possible 
later on.

Exception (messageText)
  Abort
  Error
ArithemticError
  ZeroDivide (dividend) 
  FloatingPointException
  RangeError ** (from, to)
  NaNError **
FileStreamException (fileName)
  FileDoesNotExistException (readOnly)
  FileExistsException (fileClass)
  CannotDeleteFileException
  FileWriteError
  FileReadError **
  FileClosedException **
  CannotAccessFileException **
  ReadonlyFileException **
MessageNotUnderstood (message, receiver)
NonBooleanReceiver (object)
OutOfMemory
Halt
  AssertionFailure
  BreakPoint
SyntaxError ** !exists! (input, position)
  NumberFormatException **
HeadlessError **
TimedOut ** (object, operation, timeout)
VerificationException
IllegalOperation ** (operation, object)
SizeMismatch (objects)
LowMemory ** (percentageFree)
SubclassResponsibility ** (message, receiver)
NotYetImplemented ** (message, receiver)
CannotInstanciate ** (class)
ReadOnlyObject ** (object)
OutOfFreeSpace ** (object, size)
InvalidArgument ** (message, receiver, argument)
NotIndexable ** (object)
NoKeyedAccess ** (object)
NonIntegerIndex ** (receiver, index)
SubscriptOutOfBounds ** (receiver, index, from, to)
NotFoundException ** (receiver, object)
  KeyNotFound **
  ValueNotFound **
  ElementNotFound **
StreamException (stream)
  PositionError ** (index, from, to) 
  EndOfStream **
  BeginOfStream ** 

All feedback is welcome.

Regards,

Sven


 

Re: [Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

[pharo]

Updates:
Status: FixProposed

Comment #1 on issue 3988 by nicolas@gmail.com: Debugger cannot open  
because of Decompiler assertion failure

http://code.google.com/p/pharo/issues/detail?id=3988

Name:  
SLICE-Issue-3988-DebuggerCannotOpenBecauseOfDecompilerAssertionFailure-nice.1

Dependencies: Compiler-nice.282

This is the fix from squeak (Compiler.nice.130)

[Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

[pharo]

Status: Accepted
Owner: nicolas@gmail.com
Labels: Type-Squeak

New issue 3988 by nicolas@gmail.com: Debugger cannot open because of  
Decompiler assertion failure

http://code.google.com/p/pharo/issues/detail?id=3988

This was reported at http://bugs.squeak.org/view.php?id=7467
If you try to debug this, then your image might hang:

'1 0' readStream in: [ :input |
| i |
[
input skipSeparators.
i := Integer readFrom: input.
i = 0 ] whileFalse: [
| k count digits |
k := 1.
count := 0.
digits := Array new: 10 withAll: 0.
[ count < i ] whileTrue: [
| index1 ps |
ps := k printString.
((index1 := ps indexOf: $1) = 0 or: [ (ps indexOf: $3  
startingAt: index1) = 0 ]) ifTrue: [

count := count + 1.
ps do: [ :each | digits at: each asciiValue - 47 put:  
(digits at: each asciiValue - 47) + 1 ] ].

k := k + 1 ].
self halt ] ]

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

[pharo]

Comment #4 on issue 3982 by vonbecm...@gmail.com: Error: can''t find EOCD  
position

http://code.google.com/p/pharo/issues/detail?id=3982

i tried again several times, and now it works.
Sorry, i cannot reproduce it anymore.
you can close it.

Re: [Pharo-project] Issue 3818 in pharo: CommandLine Manager

[pharo]

Updates:
Cc: -tristan@gmail.com

Comment #5 on issue 3818 by stephane...@gmail.com: CommandLine Manager
http://code.google.com/p/pharo/issues/detail?id=3818

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3818 in pharo: CommandLine Manager

[pharo]

Updates:
Status: Started

Comment #4 on issue 3818 by marcus.d...@gmail.com: CommandLine Manager
http://code.google.com/p/pharo/issues/detail?id=3818

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3818 in pharo: CommandLine Manager

[pharo]

Comment #3 on issue 3818 by marcus.d...@gmail.com: CommandLine Manager
http://code.google.com/p/pharo/issues/detail?id=3818


So I am checking this. For testing, I made a tt.st that just  
does "Smalltalk quitPrimitive!". I tested it, works:


 ./Squeak\ 4.2.5beta1U.app/Contents/MacOS/Squeak\ VM\ Opt  
PharoCore-1.3.image tt.st


Now I load the SLICE. Result: script is *not* executed anymore.

So there is something not working.

Re: [Pharo-project] Issue 2703 in pharo: Unicode experiments of nicolas cellier on squeak

[pharo]

Updates:
Labels: Milestone-1.3

Comment #6 on issue 2703 by marcus.d...@gmail.com: Unicode experiments of  
nicolas cellier on squeak

http://code.google.com/p/pharo/issues/detail?id=2703

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

[pharo]

Updates:
Status: Closed

Comment #12 on issue 3088 by marcus.d...@gmail.com: MNU  
Text>>withBlanksTrimmed

http://code.google.com/p/pharo/issues/detail?id=3088

In 13140 this expression:

SourcedMethodReference allInstances
  select: [:each | each stringVersion class == Text ]

now returns an epmpty array.

I think the image recompile fixed it.

Re: [Pharo-project] Issue 2986 in pharo: DemoMode should not change Fonts only sizes

[pharo]

Updates:
Status: FixToInclude

Comment #8 on issue 2986 by marcus.d...@gmail.com: DemoMode should not  
change Fonts only sizes

http://code.google.com/p/pharo/issues/detail?id=2986

(No comment was entered for this change.)

Re: [Pharo-project] Brussels Sprint: gathering number of attendes

[Marcus Denker]

On Apr 11, 2011, at 11:23 AM, Johan Brichau wrote:

> Hi everyone.
> 
> To make sure we have enough food and drinks for everyone. Please make sure to 
> let us know you are coming.
> From previous emails, I have understood the following people are attending:
> 
> - Steph
> - Marcus
> - Sven
> - Mariano
> - Craig Latta
> - Thomas Holzer
> - Andy
> - Johan
> 
-> Igor.

Marcus


--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

[pharo]

Updates:
Labels: Milestone-1.2.2 Milestone-1.3

Comment #2 on issue 3980 by marcus.d...@gmail.com: TestResource fails to  
makeAvailable an never recovers

http://code.google.com/p/pharo/issues/detail?id=3980

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3986 in pharo: Bug with Delay during clock rollover

[pharo]

Updates:
Labels: Milestone-1.2.2 Milestone-1.3

Comment #2 on issue 3986 by marcus.d...@gmail.com: Bug with Delay during  
clock rollover

http://code.google.com/p/pharo/issues/detail?id=3986

(No comment was entered for this change.)

Re: [Pharo-project] fonts on Pharo website

[Adrian Lienhard]

hehe, I wondered how long it takes to notice the new fonts ;)

We can revert to the old font if the web font is not an improvement... Geert 
also noted that the font we embedded does not look the same on all 
browsers/platforms.

Cheers,
Adrian


On Apr 11, 2011, at 13:47 , laurent laffont wrote:

> Hi,
> 
> For me the new fonts used on www.pharo-project.org are hard to read. The
> rendering on Firefox / Windows is not nice too.
> 
> What do you think ?
> 
> Laurent Laffont

Re: [Pharo-project] fonts on Pharo website

[Max Leske]

They're good to read in Safari on MacOS but I must say I found myself wondering 
if I had accidentally set strange preferences to narrow the fonts :) It's 
just... I'm not used to seeing such a font on the web


On 11.04.2011, at 13:47, laurent laffont wrote:

> Hi,
> 
> For me the new fonts used on www.pharo-project.org are hard to read. The 
> rendering on Firefox / Windows is not nice too.
> 
> What do you think ?
> 
> Laurent Laffont 

Re: [Pharo-project] Issue 3987 in pharo: Use specific KeyNotFoundError in Dictionaries

[pharo]

Updates:
Status: FixProposed
Labels: Milestone-1.3

Comment #1 on issue 3987 by marcus.d...@gmail.com: Use specific  
KeyNotFoundError in Dictionaries

http://code.google.com/p/pharo/issues/detail?id=3987

(No comment was entered for this change.)

[Pharo-project] Issue 3987 in pharo: Use specific KeyNotFoundError in Dictionaries

[pharo]

Status: New
Owner: 

New issue 3987 by camillob...@gmail.com: Use specific KeyNotFoundError in  
Dictionaries

http://code.google.com/p/pharo/issues/detail?id=3987

Pharo Inbox:
Polymorph-Widgets-CamilloBruni.423
Collections-Unordered-CamilloBruni.108

[Pharo-project] fonts on Pharo website

[laurent laffont]

Hi,

For me the new fonts used on www.pharo-project.org are hard to read. The
rendering on Firefox / Windows is not nice too.

What do you think ?

Laurent Laffont

[Pharo-project] [update 1.3] #13140

[Marcus Denker]

13140
-

Issue 3977: Undeclared vars in MorphTreeMorp
Issue 3931: Move all Exceptions-Kernel to Kernel-Exceptions
--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

[Pharo-project] Fwd: Company using Pharo [was: Have started an independent developer activity]

[laurent laffont]

Thanks Thierry !

-- Forwarded message --
From: Gmail perso 
Date: Mon, Apr 11, 2011 at 10:38 AM
Subject: Re: [Pharo-project] Have started an independent developer activity
- Thank you
To: laurent laffont 


 Of course! You can add Alsim (http://ww.alsim.com/) to the list of company
using Pharo. For the details, we are still in early stage of adoption, but
it is really promising.

As the best way to learn is to practice, we have started the development of
a tool for our stock management, as the model is quite simple. The aim is to
learn, and to validate some concepts too, like the use of a web interface.
So we use:
* Pharo
* Seaside for the web part
* Magma for the data persistence.

For the moment, it is still in early stage of development, but it is growing
quite fast. I think I will be able to give you more feed back soon.

-- 
Thierry

On lundi 11 avril 2011 at 09:52, laurent laffont wrote:

On Sun, Apr 10, 2011 at 10:01 PM, ZeBourk  wrote:

 Congratulations Laurent!

And thank you for having given me the motivation to dive into
smalltalk. Now I have introduced it in the company I work for, and
it's really fun.


Cool !

Can we add it to http://www.pharo-project.org/about/success-stories ?

Laurent




I wish you success, too.

Thierry

2011/4/9 laurent laffont :
> Hi,
> I discovered Smalltalk and Pharo almost three years ago and just after
read
> Chad Fowler book "Passionate Programmer" (1st edition title was "My job
went
> to India"). These have changed my developer life, how I perceive software
> and that great technology is fun, people doing it more. You're a cool
> community and I'm proud to be there.
> Now I've started an aside (paid :) independent developer activity thanks
to
> a cool guy. That would not be possible without all the stuff I learn every
> day from the community and the urge to continue you give me.
> Each time I've made a step forward (open a blog, write ProfStef, fix bugs,
> create PharoCasts) I've been amazed that the generated effects were those
> described in Passionate Programmer (go read it !) The last chapter is "Go
> independent" so now I need the sequel ;)
> Special big thank you to Stéphane Ducasse - you're crazy :) Long live
Pharo
> !
>
> PS: nice piece of Passionate Programmer:
> When I was in India weeding through hundreds of candidates for only
> tens of jobs, the interview team was exhausting itself and running out
> of time because of a poor interview-to-hire hit rate. Heads hurting and
> eyes red, we held a late-night meeting to discuss a strategic change in
the
> way we would go through the candidates. We had to either optimize the
> process so we could interview more people or somehow interview better
> people (or both). With what little was left of my voice after twelve
> straight
> hours of trying to drag answers out of dumbstruck programmers, I argued
> for adding Smalltalk to the list of keywords our headhunters were using
> to search their résumé database. But, nobody knows Smalltalk in India,
cried
> the human resources director. That was my point. Nobody knew it, and
> programming in Smalltalk was a fundamentally different experience than
> programming in Java. The varying experience would give candidates a
> different level of expectations, and the dynamic nature of the Smalltalk
> environment would reshape the way a Java programmer would approach
> a problem. My hope was that these factors would encourage a level of
> technical maturity that I hadn’t been seeing from the candidates I’d met
so
> far.
> The addition of Smalltalk to the requirements list yielded a candidate
pool
> that was tiny in contrast to our previous list. These people were diamonds
> in the rough. They really understood object-oriented programming. They
> were aware that Java isn’t the idealistic panacea it’s sometimes made out
> to be. Many of them loved to program! Where have you been for the past two
> weeks? we thought.
> Unfortunately, our ability to attract these developers for the salaries we
> were able to pay was limited. They were calling the shots, and most of
> them chose to stay where they were or to keep looking for a new job.
> Though we failed to recruit many of them, we learned a valuable recruit-
> ing lesson: we were more likely to extend offers to candidates with
diverse
> (and even unorthodox) experience than to those whose experiences were
> homogenous. My explanation is that either the good people seek out
> diversity, because they love to learn new things, or being forced into
alien
> experiences and environments created more mature, well-rounded soft-
> ware developers. I suspect it’s a little of both, but regardless of why it
> works, we learned that it works. I still use this technique when looking
> for developers.
>
> Laurent Laffont - @lolgzs
>
> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> Blog: http://magaloma.blogspot.com/
> Developer group: http://cara74.seasidehosting.st
>
>

Re: [Pharo-project] Issue 3931 in pharo: Move all Exceptions-Kernel to Kernel-Exceptions

[pharo]

Updates:
Status: Closed
Labels: Milestone-1.3

Comment #2 on issue 3931 by marcus.d...@gmail.com: Move all 	 
Exceptions-Kernel to Kernel-Exceptions

http://code.google.com/p/pharo/issues/detail?id=3931

in 13140

Re: [Pharo-project] Issue 3977 in pharo: Undeclared vars in MorphTreeMorph

[pharo]

Updates:
Status: Closed

Comment #4 on issue 3977 by marcus.d...@gmail.com: Undeclared vars in  
MorphTreeMorph

http://code.google.com/p/pharo/issues/detail?id=3977

in 13140

[Pharo-project] Fwd: [Metacello] [ANN] MetacelloBrowser 1.59.1 ready for feedback

[Alexandre Bergel]

Début du message transféré :

> Expéditeur: Dale Henrichs 
> Date: 11 avril 2011 00:54:01 UTC-04:00
> Destinataire: "metace...@googlegroups.com" 
> Objet: [Metacello] [ANN] MetacelloBrowser 1.59.1 ready for feedback
> Répondre à: metace...@googlegroups.com
> 

> I've been using the MetacelloBrowser pretty heavily in my day to day 
> development and I feel that it has reached a relatively stable point in terms 
> of reliability and functionality, so now is a good time to get feedback from 
> a wider audience of users. 
> 
> The MetacelloBrowser pretty much supports the development cycle as described 
> in my blog post[1], with menu items or buttons to support the major 
> operations. For the most part you shouldn't have to open the Monticello 
> Browser when using the Metacello Browser ... if you find you have to use it 
> let us know:). To submit bug reports, visit [2] and set the Product label to 
> Product-Browser.
> 
> Please use the 'documentation' menu item in the configuration list to look at 
> the help text for a configuration (Metacello and MetacelloBrowser entries 
> have been customized) and let me know what you think.
> 
> The 'Load Configuration' button should let you load a configuration and then 
> you can use the browser to load a specific version.
> 
> There are still times when you have to 'browse' a configuration or version to 
> had edit things, but over time I hope that we can build ui's for doing that 
> as well.
> 
> Press the 'Help' button to take a look at the Help available and feel free to 
> suggest improvements.
> 
> When you load the MetacelloBrowser, you'll get version 1.0-beta.29 of 
> Metacello which is still under development ...there are a number of 
> performance improvements and bugfixes in 1.0-beta.29 along with the 
> Configuration Help System entries so don't forget to open a Help Browser and 
> look at the 'Metacello Configruations' topic (related to the MetacelloBrowser 
> 'documentation' menu item). 
> 
> To load do the following:
> 
>  Gofer new
>squeaksource: 'MetacelloBrowser';
>package: 'ConfigurationOfMetacelloBrowser';
>load.
> 
> then:
> 
>  (ConfigurationOfMetacelloBrowser project version: #stable) load.
> 
> then either:
> 
>  MetacelloBrowser open.
> 
> or
> 
>  MBOBConfigurationBrowser open.
> 
> In Pharo, the MetacelloBrowser shows up in the Tools menu.
> 
> I expect the MetacelloBrowser to work in:
> 
>  - Pharo1.1 and Pharo1.2 (OB or Morphic)
>  - Squeak 4.2 (OB)
>  - GLASS 1.0-beta.8.7 (OB)
> 
> The MetacelloBrowser is still a work in progress, but your feedback now will 
> make it possible for Alexandre and I to focus on the things that need to be 
> addressed before we can announce general availability.
> 
> Dale
> 
> [1] http://gemstonesoup.wordpress.com/#walkthrough
> [2] http://code.google.com/p/metacello/issues/entry

Re: [Pharo-project] Issue 3986 in pharo: Bug with Delay during clock rollover

[pharo]

Comment #1 on issue 3986 by gazzagu...@googlemail.com: Bug with Delay  
during clock rollover

http://code.google.com/p/pharo/issues/detail?id=3986

(file attached, failed first time!)

Attachments:
DelayRolloverFix.1.cs  1.3 KB

Re: [Pharo-project] Delay bug

[Gary Chambers]

Issue http://code.google.com/p/pharo/issues/detail?id=3986

Regards, Gary

- Original Message - 
From: "Adrian Lienhard" 

To: 
Sent: Wednesday, April 06, 2011 5:41 PM
Subject: Re: [Pharo-project] Delay bug


We managed to resolve our initial problem with the process scheduling [1]. 
All Cmsbox customers have been migrated to Pharo and it works very reliably 
now.


Gary, maybe you could open a ticket already now and post what you know at 
this time to get early feedback.


[1] http://code.google.com/p/pharo/issues/detail?id=3498

Cheers
Adrian


On Apr 6, 2011, at 18:24 , Stéphane Ducasse wrote:


thanks gary.
Yes adrian got a problem on his server after two weeks of load. I do not 
know how we can improve them.


Stef

On Apr 6, 2011, at 6:02 PM, Gary Chambers wrote:

Well, we have been having problems with applications appearing to hang 
every 6 days or so (sound familiar?).


I have identified a bug in the Delay implementation, rather obscure, but 
highlighted by our applications that make HEAVY use of processes/(tight, 
a few tens of milliseconds)delays/semaphores etc.

Naturally due to an edge case on millisecond clock rollover...

Affects all Squeak/Pharo versions, as far as I can tell. (It is separate 
from the OSProcess issues I have posted about a few weeks ago).


I've developed a potential fix, though I'll have to let you all know 
whether (hopefully) successful in a week or two... fingers crossed!


I hope it is fixable, last hurdle for business applications, from our 
point of view.


I'll post details when fix confirmed or failed then.

Regards, Gary

[Pharo-project] Issue 3986 in pharo: Bug with Delay during clock rollover

[pharo]

Status: FixProposed
Owner: gazzagu...@googlemail.com
CC: adrian.l...@gmail.com,  marcus.d...@gmail.com
Labels: Type-ReportDefect

New issue 3986 by gazzagu...@googlemail.com: Bug with Delay during clock  
rollover

http://code.google.com/p/pharo/issues/detail?id=3986

I have identified a bug with Delays that are scheduled close to the  
millisecond clock rollover that can occur when other delays expire around  
the same time.


The issue appears to be that when scheduling a delay, the resumption time  
gets set and, before the AccessProtect critical block can be entered, the  
TimingSemaphore gets signalled, causing the timer process to handle an  
expired delay.


If the clock rolls over before the resumption of the process that was  
scheduling the original delay, that delay gets scheduled with the  
resumption time that was determined prior to the clock rollover, hence a  
delay of around 6 days.


A fix is proposed in the attached change set, tested empirically during a  
rollover with the result of no "rogue" delays - not conclusive but in our  
production code it appears the problem is resolved.


Regards, Gary

[Pharo-project] Brussels Sprint: gathering number of attendes

[Johan Brichau]

Hi everyone.

To make sure we have enough food and drinks for everyone. Please make sure to 
let us know you are coming.
From previous emails, I have understood the following people are attending:

- Steph
- Marcus
- Sven
- Mariano
- Craig Latta
- Thomas Holzer
- Andy
- Johan

Someone on here who is not attending? 
Someone not attending who is listed above?

The parking access code will follow shortly.

ps: I will bring some Faro beer this time then ;-)

Johan

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

[pharo]

Comment #3 on issue 3982 by marianopeck: Error: can''t find EOCD position
http://code.google.com/p/pharo/issues/detail?id=3982

Yes, that would be nice. We have already seen this problem FAR so many  
times.

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

[pharo]

Comment #2 on issue 3982 by nicolas@gmail.com: Error: can''t find EOCD  
position

http://code.google.com/p/pharo/issues/detail?id=3982

Couldn't the exception be handled with an automated or manual action via a  
more appropriated dialog like:


Error can't find EOCD blah blah
The package appear to be corrupted, maybe due to a communication error
What would you like to do ?
- flush the cache and retry
- abort operation

[Pharo-project] Issue 3985 in pharo: Create temporary in debugger does not work for new keyword method

[pharo]

Status: Accepted
Owner: laurent@gmail.com

New issue 3985 by laurent@gmail.com: Create temporary in debugger does  
not work for new keyword method

http://code.google.com/p/pharo/issues/detail?id=3985

Reproductible in Pharo 1.2 (Full) - looks ok in PharoCore 1.3

Create a class in the browser like

Foo >> bar
   self doSomethingWith: 2.


save and evaluate

Foo new bar.

Debugger pops up. Click create method doSomethingWith:

Foo>>doSomethingWith: aSmallInteger
  a := aSmallInteger
  ^ a.

Accept. Dialog popus up, select declare temp => does not work.

[Pharo-project] GitFS and Pharogenesis

[Max Leske]

Hi folks

I promised a while ago that I would keep you up to date with GitFS and 
Pharogenesis. Well, now that I've handed in my thesis you can read it if you 
like:
http://scg.unibe.ch/archive/projects/Lesk11a.pdf

I also wrote a short How-To on Filesystem (alas, the "old" version) and GitFS:
http://scg.unibe.ch/archive/projects/Lesk11b.pdf

You can find a summary of important information (loading the code etc.) on this 
page: http://scg.unibe.ch/research/Pharogenesis

Although I'm sort of "releasing" the code for both now, please note that Pharo 
has progressed a bit too fast lately for me to keep up. GitFS was built on the 
original implementation of Filesystem and I will have to put some work into 
updating the implementation. I'm even thinking of starting over from scratch.
Pharogenesis also depends on the old version of Filesystem. The Metacello 
configurations load the old Filesystem version into the image, just so you know.

If you don't know what this is all about, here's the abstract of my thesis:

In the Smalltalk dialects Squeak and Pharo it is difficult to view changes to 
source code that occurred accross major releases. This poses a problem for 
development as well as for code analysis: Developers often need to be able to 
revert code to a previous version and for code analysis there should ideally be 
a single source of information. We solve the problem by building a Git 
repository with the complete source code history of Pharo.

To build the repository we propose two tools: GitFS and Pharogenesis. GitFS is 
an implementation of Git written entirely in Smalltalk. With GitFS we can 
create, read and manipulate Git repositories. Pharogenesis uses GitFS to build 
a Git repository from the source code that Pharogenesis extracts from the 
source files.

We also show how Git can be used to provide a single point of access for all 
source code from Squeak 1 through Squeak 4 and Pharo 1 using GitFS. The source 
code database we built with Pharogenesis is available on github 
(http://www.github. com/pharogenesis/pharogenesis.git).

If you have any questions, feel free to ask.

Cheers,
Max

[Pharo-project] Issue 3984 in pharo: Announcements announced when a test is runned

[pharo]

Status: FixProposed
Owner: benjamin...@gmail.com
Labels: Milestone-1.3 Nautilus

New issue 3984 by benjamin...@gmail.com: Announcements announced when a  
test is runned

http://code.google.com/p/pharo/issues/detail?id=3984

More precisely, when the history of the test case is updated

Attachments:
AnnouncementsInTestCase.1.cs  2.8 KB

[Pharo-project] Issue 3983 in pharo: TestCase assertions are in accessing protocol

[pharo]

Status: Accepted
Owner: laurent@gmail.com
Labels: Type-RequestForEnhancement Difficulty-Easy

New issue 3983 by laurent@gmail.com: TestCase assertions are in  
accessing protocol

http://code.google.com/p/pharo/issues/detail?id=3983

Pharo 1.2 & 1.3

Put them in asserting protocol like TestAsserter

Re: [Pharo-project] Issue 3977 in pharo: Undeclared vars in MorphTreeMorph

[pharo]

Updates:
Status: FixProposed

Comment #3 on issue 3977 by benjamin...@gmail.com: Undeclared vars in  
MorphTreeMorph

http://code.google.com/p/pharo/issues/detail?id=3977

It should fix the issue :)

Attachments:
MorphTreeMorph.BenjaminVanRyseghem.1.cs  5.5 KB

Re: [Pharo-project] FAQ migration

[Max Leske]

Yeah, should probably better contain the TOC to the FAQ entries. 

Max

On 11.04.2011, at 09:40, Adrian Lienhard wrote:

> 
> On Apr 10, 2011, at 13:16 , Mariano Martinez Peck wrote:
> 
>> Thanks Max, I am reading it now :)
>> For those who doesn't know the link: http://book.pharo-project.org/book/FAQ/
> 
> Hm, this page is pretty empty...
> 
> Adrian
> 
> BTW, there's another FAQ, which I had written over some time: 
> http://www.pharo-project.org/documentation/faq. Does it make sense to keep 
> both (a technical and a non-technical FAQ)? Or should we merge this one also 
> into the book? 
> 
> 

Re: [Pharo-project] Issue 3977 in pharo: Undeclared vars in MorphTreeMorph

[pharo]

Comment #2 on issue 3977 by benjamin...@gmail.com: Undeclared vars in  
MorphTreeMorph

http://code.google.com/p/pharo/issues/detail?id=3977

I think it's a fix based on an out dated version because the Issue  
3955introduce those variables ...


The problem comes from the fix Issue 3969 attachment: TreePart2.cs (8.0  
KB) :)


Those fixes should be merged using a clean image ^^

Re: [Pharo-project] Have started an independent developer activity - Thank you

[laurent laffont]

On Sun, Apr 10, 2011 at 10:01 PM, ZeBourk  wrote:

> Congratulations Laurent!
>
> And thank you for having given me the motivation to dive into
> smalltalk. Now I have introduced it in the company I work for, and
> it's really fun.
>

Cool !

Can we add it to http://www.pharo-project.org/about/success-stories ?

Laurent



>
> I wish you success, too.
>
> Thierry
>
> 2011/4/9 laurent laffont :
> > Hi,
> > I discovered Smalltalk and Pharo almost three years ago and just after
> read
> > Chad Fowler book "Passionate Programmer" (1st edition title was "My job
> went
> > to India"). These have changed my developer life, how I perceive software
> > and that great technology is fun, people doing it more. You're a cool
> > community and I'm proud to be there.
> > Now I've started an aside (paid :) independent developer activity thanks
> to
> > a cool guy. That would not be possible without all the stuff I learn
> every
> > day from the community and the urge to continue you give me.
> > Each time I've made a step forward (open a blog, write ProfStef, fix
> bugs,
> > create PharoCasts) I've been amazed that the generated effects were those
> > described in Passionate Programmer (go read it !) The last chapter is "Go
> > independent" so now I need the sequel ;)
> > Special big thank you to Stéphane Ducasse - you're crazy :) Long live
> Pharo
> > !
> >
> > PS: nice piece of Passionate Programmer:
> > When I was in India weeding through hundreds of candidates for only
> > tens of jobs, the interview team was exhausting itself and running out
> > of time because of a poor interview-to-hire hit rate. Heads hurting and
> > eyes red, we held a late-night meeting to discuss a strategic change in
> the
> > way we would go through the candidates. We had to either optimize the
> > process so we could interview more people or somehow interview better
> > people (or both). With what little was left of my voice after twelve
> > straight
> > hours of trying to drag answers out of dumbstruck programmers, I argued
> > for adding Smalltalk to the list of keywords our headhunters were using
> > to search their résumé database. But, nobody knows Smalltalk in India,
> cried
> > the human resources director. That was my point. Nobody knew it, and
> > programming in Smalltalk was a fundamentally different experience than
> > programming in Java. The varying experience would give candidates a
> > different level of expectations, and the dynamic nature of the Smalltalk
> > environment would reshape the way a Java programmer would approach
> > a problem. My hope was that these factors would encourage a level of
> > technical maturity that I hadn’t been seeing from the candidates I’d met
> so
> > far.
> > The addition of Smalltalk to the requirements list yielded a candidate
> pool
> > that was tiny in contrast to our previous list. These people were
> diamonds
> > in the rough. They really understood object-oriented programming. They
> > were aware that Java isn’t the idealistic panacea it’s sometimes made out
> > to be. Many of them loved to program! Where have you been for the past
> two
> > weeks? we thought.
> > Unfortunately, our ability to attract these developers for the salaries
> we
> > were able to pay was limited. They were calling the shots, and most of
> > them chose to stay where they were or to keep looking for a new job.
> > Though we failed to recruit many of them, we learned a valuable recruit-
> > ing lesson: we were more likely to extend offers to candidates with
> diverse
> > (and even unorthodox) experience than to those whose experiences were
> > homogenous. My explanation is that either the good people seek out
> > diversity, because they love to learn new things, or being forced into
> alien
> > experiences and environments created more mature, well-rounded soft-
> > ware developers. I suspect it’s a little of both, but regardless of why
> it
> > works, we learned that it works. I still use this technique when looking
> > for developers.
> >
> > Laurent Laffont - @lolgzs
> >
> > Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> > Blog: http://magaloma.blogspot.com/
> > Developer group: http://cara74.seasidehosting.st
> >
> >
>
>

Re: [Pharo-project] Download choices :) or :(?

[Adrian Lienhard]

On Apr 11, 2011, at 04:43 , Serge Stinckwich wrote:

> There should be i guess just one download page.
> On the first page, there is some downloads links in the three columns.
> If you look at the python language website, there is only one download
> page, the same for Ruby.

Yep!

> Adrian take care of the website if i remember. I know from experience
> this a really boring task.
> If we want to scale to a small team of volunteers, what could be done
> to simplify the modification of pages ?
> I know that the website currently used is based on Cmsbox and this is
> great showcase for Pharo&Smalltalk, but
> maybe an automatically generated html website with the help of tools
> like webgen or something similar with the pages on a git repository
> somewhere could help the management.

I don't think we have a tool issue here. We already have several people that 
help with managing the website and that works pretty well. I think the 
confusion about what to download can be addressed by providing less options. 
Maybe we just have too many of them... The initial idea was that in particular 
newcomers would just download the one-click image. In the meantime we got a 
one-click image with and without COG. Then people asked for direct shortcuts on 
the home page for the stable core, the unstable core, and the stable full 
image. Of course this makes everything very complicated for people who don't 
know what they want/need. So we should think again about what images we want to 
provide for download and how to link them.

Cheers,
Adrian

Re: [Pharo-project] FAQ migration

[Adrian Lienhard]

On Apr 10, 2011, at 13:16 , Mariano Martinez Peck wrote:

> Thanks Max, I am reading it now :)
> For those who doesn't know the link: http://book.pharo-project.org/book/FAQ/

Hm, this page is pretty empty...

Adrian

BTW, there's another FAQ, which I had written over some time: 
http://www.pharo-project.org/documentation/faq. Does it make sense to keep both 
(a technical and a non-technical FAQ)? Or should we merge this one also into 
the book? 

Re: [Pharo-project] [SPAM] Nice post about files ....

[Sven Van Caekenberghe]

On 11 Apr 2011, at 08:57, Geert Claes wrote:

> http://gbracha.blogspot.com/2010/02/nail-files.html

Indeed, it's very well put.

Re: [Pharo-project] Issue 2986 in pharo: DemoMode should not change Fonts only sizes

[pharo]

Comment #7 on issue 2986 by aplan...@gmail.com: DemoMode should not change  
Fonts only sizes

http://code.google.com/p/pharo/issues/detail?id=2986

Here is a new version

Attachments:
moreDejaVuAndRemoveAccunyFor1.3.st  675 bytes