Re: [Pharo-project] getting rid of Symbol >> new: ?

[Martin McClure]

Sheridan Mahoney wrote:

> Martin and I had been working towards the idea that ImageSegments should
> never create non-Canonical symbols, and the user should not have to use
> manual techniques to preserve symbols they are interested in keeping alive.
> 
> I ended up getting stuck however, in trying to discover what process
> ImageSegment
> goes through while it is installing objects - ImageSegment #install  has a
> call to an
> unimplemented method   #readFromFileWithSymbols  which it seems it should be
> using, but isn't(wha' the?)
> 
> 
> install
>   "This operation retrieves the segment if necessary from file storage,
> installs it in memory, and replaces (using become:) all the root stubs with
> the reconstructed roots of the segment."
> 
>   | newRoots |
>   state = #onFile ifTrue: [self readFromFile].
>   state = #onFileWithSymbols ifTrue: [self readFromFileWithSymbols.

My guess (and only a guess) is that #onFileWithSymbols never becomes a 
state in the test case that's failing.

And my opinion is that it's suspicious to require something different 
for a image segment that contains symbols as opposed to one that 
doesn't; the ideal would be to have image segments just transparently 
handle Symbols correctly. Users just shouldn't have to deal with details 
at that level; the correct semantics are extremely clear.

Regards,

-Martin

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] ClassTree new openOn: Collection :)

[Schwab,Wilhelm K]

Doru, all,

That's good news on a couple of fronts: I had missed/forgotten about gofer's 
availability in RC1.

One snag though: the fonts look weird in the tree and list, so I tried the 
squeakvm.org vm, and am getting seriously ugly fonts.  What do I have to do to 
fix that?  When is the Pharo-specific VM going to "come back?"

Bill



-Original Message-
From: pharo-project-boun...@lists.gforge.inria.fr 
[mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Tudor Girba
Sent: Wednesday, December 09, 2009 4:38 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] ClassTree new openOn: Collection :)

We are already using the MorphTreeMorph in Glamour in a 1.0 image.  
It's pretty cool.

You can get it at: Gofer new squeaksource: 'Momo'; addPackage:  
'Morphic-MorphTreeWidget'; load.

Cheers,
Doru


On 8 Dec 2009, at 21:36, Stéphane Ducasse wrote:

> 1.1 of course :)
> I'm riding the wafe :)
>
>
> On Dec 8, 2009, at 9:05 PM, Schwab,Wilhelm K wrote:
>
>> Stef,
>>
>> Where does this work?  My RC1 image either does not contain the 
>> classes, or I'm being too dense to see the corrected thing in the 
>> list of choices.  Interested, if only as examples to help me with a 
>> couple of tasks...
>>
>> Bill
>>
>>
>> -Original Message-
>> From: pharo-project-boun...@lists.gforge.inria.fr 
>> [mailto:pharo-project-boun...@lists.gforge.inria.fr
>> ] On Behalf Of Stéphane Ducasse
>> Sent: Tuesday, December 08, 2009 11:08 AM
>> To: Pharo-project@lists.gforge.inria.fr Development
>> Cc: notre liste
>> Subject: [Pharo-project] ClassTree new openOn: Collection :)
>>
>> I started to understand MorphTreeMorph to build a class documentation 
>> browsing browser and I discovered that
>>
>>  ClassTree new openOn: Collection
>>
>>  ClassList new openOn: Collection
>>
>> This is really a good start.
>> We could have it for package
>> and displaying methods
>>
>> Stef
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"Be rather willing to give than demanding to get."




___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] getting rid of Symbol >> new: ?

[Sheridan Mahoney]

Adrian Lienhard wrote:
> 
> 
> On Dec 8, 2009, at 12:08 , Mariano Martinez Peck wrote:
> 
>> On Fri, Dec 4, 2009 at 12:05 PM, Adrian Lienhard   
>> wrote:
> 
>> When you are creating your root of objects and you put symbols  
>> inside, they
>> are not put in ourPointers but in ByteArray.
>> This is due to the fact that the only object who is pointing to that  
>> symbol
>> is inside the segment ?
> 
> To be precise, the symbols are also pointed to by the symbol table,  
> but only by weak references. Since image segments use the GC mark  
> logic, these pointers are not considered.
> 
> 

Martin and I had been working towards the idea that ImageSegments should
never create non-Canonical symbols, and the user should not have to use
manual techniques to preserve symbols they are interested in keeping alive.

I ended up getting stuck however, in trying to discover what process
ImageSegment
goes through while it is installing objects - ImageSegment #install  has a
call to an
unimplemented method   #readFromFileWithSymbols  which it seems it should be
using, but isn't(wha' the?)


install
"This operation retrieves the segment if necessary from file storage,
installs it in memory, and replaces (using become:) all the root stubs with
the reconstructed roots of the segment."

| newRoots |
state = #onFile ifTrue: [self readFromFile].
state = #onFileWithSymbols ifTrue: [self readFromFileWithSymbols.
endMarker := segment nextObject."for enumeration of 
objects"
endMarker == 0 ifTrue: [endMarker := 'End' clone]].
(state = #active) | (state = #imported) ifFalse: [self errorWrongState].
newRoots := self loadSegmentFrom: segment outPointers: outPointers.
state = #imported 
ifTrue: ["just came in from exported file"
arrayOfRoots := newRoots]
ifFalse: [
arrayOfRoots elementsForwardIdentityTo: newRoots].
state := #inactive.
Beeper beepPrimitive


I think the next step in this trajectory is to trace is how the state is
getting
set - right now it is kind of a mystery...

Does this seem reasonable?

Thanks, 

Sheri


-- 
View this message in context: 
http://n2.nabble.com/Re-getting-rid-of-Symbol-new-tp4109230p4143090.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Problems with updates 1.0 & 1.1 on XP ...

[Guido Stepken]

Hi folks!

I installed recent Pharo 1.0 and downloaded also the 1.1 alpha Image.

Updating both fails finally. 1.1 stops updating at a certain point, 1.0 
updates, but classbrowser finally doesn't work.

Any ideas?

tnx, Guido

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] package documentation viewer

[Simon Denier]

On 9 déc. 2009, at 19:11, csra...@bol.com.br wrote:

> I also vote for having it running at Pharo website.
> 
> However it gives another opportunity to my canvassing: it is imperative that 
> the comments written (class and methods) be accurate and uptodate!!


Can someone quickly run some query to see how bad it is? That is, how many 
classes without comment or with the generic template?


> 
> --
> Cesar Rabak
> 
> 
> Em 09/12/2009 11:06, Alexandre Bergel < alexan...@bergel.eu > escreveu:
> 
> 
> Looks good. Maybe this could be part of the Pharo website no ?
> 
> Alexandre
> 
> 
> On 9 Dec 2009, at 07:49, laurent laffont wrote:
> 
>> Hi,
>> 
>> for fun and *for me*, I've made a small Seaside app to quickly  
>> browse all documentation in a Pharo image.
>> It's package oriented, all  classes and selectors comment on a  
>> single page, so I can use search and print functions of my web  
>> browser.
>> 
>> Someone might have a use of it.  It's here: 
>> http://www.squeaksource.com/SimpleWebDoc.html
>> Screenshots: http://picasaweb.google.fr/laurent.laffont/Simplewebdoc
>> 
>> Laurent
>> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
> 
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
 Simon




___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] getting rid of Symbol >> new: ?

[Mariano Martinez Peck]

On Wed, Dec 9, 2009 at 9:40 AM, Adrian Lienhard  wrote:

> I don't have the VMMaker code at hand right now (or rather, don't have
> time to look at it ;)), but I guess that after that piece of code you
> pasted below there is a loop from the first field (BaseHeader+4) to
> the last non-weak field (lastFieldOffset) in which the non-weak fields
> are traced. Note, that if an object both fixed and indexable weak
> fields the latter are always located after the former. You can see the
> memory layout and object formats on the pages 9 and 10 of the slides
> [1] (from a lecture about VMs I gave recently).
>
>
Thanks for the explanation Adrian and the link Adrian...now, being a bit
off-topic, I have the following situation about ImageSegment. I tried to
reproduce it in a unit test, but I couldn't yet :(

Suppose I create a segment with a tree of objects. Suppose inside of that
tree I have an object that refers to an external object called XXX, thus it
is put in the outPointers.
Then I extract the segment, I write it to disk, and I put a nil to the
segment variable.
After that, for some reason, my object XXX is garbage collected from my
image.
Then I want to load again my segment (reading the file and installling it).
What happens ? it fails? If true, suppose I have already "installed" some
other objects, what happen with those objects? is this atomic ?

Thanks a lot for anyone that can give me a hint.

Mariano



> Cheers,
> Adrian
>
> [1] http://www.adrian-lienhard.ch/presentations
>
> On Dec 8, 2009, at 22:57 , Mariano Martinez Peck wrote:
>
> > On Tue, Dec 8, 2009 at 10:54 PM, Mariano Martinez Peck <
> > marianop...@gmail.com> wrote:
> >
> >>
> >>
> >> On Tue, Dec 8, 2009 at 5:07 PM, Adrian Lienhard 
> >> wrote:
> >>
> >>>
> >>> On Dec 8, 2009, at 12:08 , Mariano Martinez Peck wrote:
> >>>
>  On Fri, Dec 4, 2009 at 12:05 PM, Adrian Lienhard 
>  wrote:
> >>>
>  When you are creating your root of objects and you put symbols
>  inside, they
>  are not put in ourPointers but in ByteArray.
>  This is due to the fact that the only object who is pointing to
>  that
>  symbol
>  is inside the segment ?
> >>>
> >>> To be precise, the symbols are also pointed to by the symbol table,
> >>> but only by weak references. Since image segments use the GC mark
> >>> logic, these pointers are not considered.
> >>>
> >>
> >> Ahhh ok. Now I see Symbol class >> rehashwhere it sets to
> >> SymbolTable
> >> := WeakSet
> >>
> >> Now...my finally question is, where in the code you can see the GC
> >> only
> >> mark "normal" objects and that week objects are not being taken into
> >> account. Do you know ?   I tried to search it but I didn't find it.
> >>
> >>
> > Sorry, I forgot to said I found this in ObjectMemory >> markAndTrace:
> >
> >(self isWeakNonInt: oop) ifTrue: [
> >"Set lastFieldOffset before the weak fields in the receiver"
> >lastFieldOffset := (self nonWeakFieldsOf: oop) << ShiftForWord.
> >"And remember as weak root"
> >weakRootCount := weakRootCount + 1.
> >weakRoots at: weakRootCount put: oop.
> >] ifFalse: [
> >"Do it the usual way"
> >lastFieldOffset := self lastPointerOf: oop.
> >].
> >
> >
> > But I don't know if this make sense or not.
> >
> > Thanks!!
> >
> > Mariano
> >
> >
>  What you do with this piece of code:
> 
>    symbolHolder := Symbol allSymbols.
> 
>  is to hold those symbols there. So, when ImageSegment uses the GC
>  techniques
>  to detect which objects are ONLY pointed from inside of the
>  segment,
>  the
>  symbols is not found (because it is accessible trough that test)
>  and
>  thus,
>  it goes to outPointers instead of ByteArray.
> 
>  And of course, if it is in outPointers instead of ByteArray when
>  the
>  segment
>  is loaded again, yo don't create a symbol again but use the same
>  object (the
>  one of the oop).
> 
>  I am correct? or I understood anything ?
> >>>
> >>> yes.
> >>>
> >>> Cheers,
> >>> Adrian
> >>>
> >>> ___
> >>> Pharo-project mailing list
> >>> Pharo-project@lists.gforge.inria.fr
> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >>>
> >>
> >>
> > ___
> > Pharo-project mailing list
> > Pharo-project@lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] EventInterceptor and MessageSendTree

[Stéphane Ducasse]

hernan

this sounds cool.
Keep pushing that. We need better tools to analyseour living system.

stef

On Dec 7, 2009, at 10:25 PM, Hernán Morales Durand wrote:

> Hi Alex,
>  Of course, I'm using it to observe what's the best place to hook an
> interceptor (like a method wrapper) for a wayfinder tool I'm
> developing, i.e. modeling conceptual route knowledge and then
> replaying landmarked routes for learning purposes. Implementing a
> keylogger could be another interesting place to start using this tool
> as you may see all the possible methods to intercept a keystroke.
>  Concerning debugging I didn't experimented, but maybe a situation
> where a click freezes the image...IIRC there was a bug in Pharo trying
> to grab the world and then releasing the attached world... now is
> somewhat closed but is a possible scenario to see the stack trace.
> Cheers,
> 
> Hernán
> 
> 2009/12/6 Alexandre Bergel :
>> Hi Hernán,
>> 
>> Can you describe a situation when you needed this?
>> 
>> Alexandre
>> 
>> 
>> On 6 Dec 2009, at 04:25, Hernán Morales Durand wrote:
>> 
>>> Dear all,
>>>  I've attached a little cool tool for intercepting Morphic events I
>>> just resurrected today, from the class comments:
>>> 
>>> This morph is a button which, when pressed, begins listening to the
>>> hand's event stream.  When an even of the appropriate type is
>>> encountered, this morph intercepts it and traces the dispatch of the
>>> event using MessageSendTree, and opens a SendTreeExplorer on the
>>> results.  This is useful for debugging parts of the UI process which
>>> are otherwise difficult to trace. The eventType can be any of the
>>> Morphic event types, but #mouseUp, #mouseDown, and #keystroke are by
>>> far the most useful because they are the triggers for the majority of
>>> actual UI activity.
>>> 
>>> This is a list of morphic events to try:
>>> 
>>> #mouseDown
>>> #mouseMove
>>> #mouseUp
>>> #mouseOver
>>> #mouseEnter
>>> #mouseLeave
>>> #mouseLeaveDragging
>>> 
>>> #keystroke
>>> #keyDown
>>> #keyUp
>>> 
>>> #unknown
>>> #click
>>> 
>>> To install it load first MessageSendTree. The original author is Jesse
>>> Welton http://jwelton.v-space.org/squeak/
>>> 
>>> Cheers,
>>> 
>>> Hernán
>>> >> 1.mcz>___
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] gofer is cooooool

[Stéphane Ducasse]

now with the pull I could dl all the petitParser...coral and work in the 
library without net.
My gut feeling is that you will soon do Sync :)

Here is what I do rigth now.
I imagine that soon or later somebody will do a simple interface or add button 
to MCBrowser to 
do that with one menu.


sync
"to sync local and remote repositories"
"self sync"
Gofer new
squeaksource: 'Coral';
addVersion: 'Coral';
addVersion: 'LoadCoral';
push.
Gofer new
squeaksource: 'Coral';
addVersion: 'Coral';
addVersion: 'LoadCoral';
pull.

Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] New configurations in MetacelloRepository

[Dale Henrichs]

I've added the following configurations to the MetacelloRepository:
  ConfigurationOfKomHttpServer
  ConfigurationOfSPort2
  ConfigurationOfSwazoo2

and updated ConfigurationOfSeaside30 updated to use the above configurations.

Dale

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] package documentation viewer

[Alexandre Bergel]

> However it gives another opportunity to my canvassing: it is  
> imperative that the comments written (class and methods) be accurate  
> and uptodate!!


Indeed

Alexandre

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






___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] How to report a bug ? [WAS] lukas-renggli.ch down, mirrors exists ?

[Michael Roberts]

Hi, I like the template!

However, we are mixing our brand up a bit.  I thought we agreed we
would not call the pharo image a dev image?  or did I miss something?
So we are in this state where some things (e.g the installers, the
pharo images) have dev in their name/filename, and sometimes we just
call it Pharo in our documentation and conversation.  We should try
and be consistent, or rethink the branding. It's caused by us having
one artifact without a suffix, whereas the rest do. (pharo,
pharo-core, pharo-web).

thanks,
Mike

On Thu, Dec 3, 2009 at 12:55 PM, Adrian Lienhard  wrote:
> Thanks, I updated the template.
>
> Adrian
>
> On Dec 3, 2009, at 11:26 , laurent laffont wrote:
>
>> A first template:
>>
>>
>> If you fill an issue for the first time, please read "How to report
>> bugs"
>> at http://www.pharo-project.org/community/issue-tracking
>>
>> Pharo image: 
>> Pharo core version: 
>> Virtual machine used: 
>> Class browser used if applicable: > you don't
>> know, print "SystemBrowser default">
>>
>> Steps to reproduce:
>> 1.
>> 2.
>> 3.
>>
>>
>> Paste or attach stack trace if applicable (look at the file
>> PharoDebug.log
>> located in the same directory as your image):
>>
>> Thank you !
>>
>> Laurent
>>
>> 2009/12/3 Mariano Martinez Peck 
>>
>>> Adrian: Thanks for your changes! It looks much better :)
>>>
>>> Laufert: yes, that's a cool idea. I wasn't aware neither.
>>>
>>> Could someone write a template? Then we just add the link to the
>>> new page.
>>>
>>> Cheers
>>>
>>> Mariano
>>>
>>>
>>> On Thu, Dec 3, 2009 at 10:44 AM, Adrian Lienhard 
>>> wrote:
>>>
 ah, I didn't know that is possible. Good idea!

 Adrian

 On Dec 3, 2009, at 10:34 , laurent laffont wrote:

> May be you should fill the issue templates on google code issue
> tracker.
> Like this: http://code.google.com/p/chromium/issues/entry
>
> Laurent
>
>
> On Thu, Dec 3, 2009 at 10:18 AM, Adrian Lienhard 
> wrote:
>
>> Thanks Mariano. I have condensed your text a bit and put it
>> online at
>> http://www.pharo-project.org/community/issue-tracking
>>
>> Cheers,
>> Adrian
>>
>> BTW, I also added the milestones for version 1.1 on the home page.
>>
>> On Dec 2, 2009, at 18:43 , Mariano Martinez Peck wrote:
>>
>>> I think it is really a good idea to create a page in the Pharo
>>> website about
>>> how to report a bug. I think that only the link to the google
>>> page
>>> is not
>>> enough. Maybe it is a good idea to explain it a bit more, and in
>>> addition,
>>> give some tips. I would write something like the text above in
>>> that
>>> page. I
>>> would replace everywhere where it is a link to
>>> http://code.google.com/p/pharo/issues/list   to this new page.
>>> I saw
>>> there
>>> are these
>>>
>>> http://www.pharo-project.org/home    (on the right)
>>> http://www.pharo-project.org/documentation/faq  (in the question
>>> "Where do I
>>> report Pharo bugs?")
>>>
>>> My English is not the best at all, so any feedback is more than
>>> welcome. In
>>> addition, maybe you don't agree with me.
>>>
>>> My main purpose is to help newcomers to submit issues.
>>>
>>> Sohere it is
>>>
>>>
>>> "
>>> An issue, also known as ticket,  represents many things. It can
>>> be a
>>> bug, a
>>> enchantment,  packages, projects or commits to check, etc.
>>> For the Pharo project, we use the Google Code issue tracker
>>> which is
>>> in
>>> http://code.google.com/p/pharo/issues/list.
>>>
>>> - Before submitting you may take into account the following tips:
>>>
>>> 1) Search in the existent issue list if there is something
>>> similar.
>>> In the
>>> issue tracker you will find a "search" button to do that. Be
>>> aware
>>> that
>>> there is a list of options and the default one is "Open
>>> ticket". It
>>> is very
>>> common you need to search in "All issues".
>>>
>>> 2) If the ticket is a bug, and there is a problem with certain
>>> method,
>>> search for that method or even for that class. It is very
>>> common to
>>> have
>>> "MessageNotUnderstood". So, in this case you can search for that
>>> method. For
>>> example, if you evaluate:
>>>
>>> TestCase nonExistentMethod: something other: another
>>>
>>> You will get "MessageNotUnderstood: TestCase
>>> class>>nonExistentMethod:other:"
>>>
>>> So, here you can search for "nonExistentMethod:other:" for
>>> exampe.
>>>
>>> 3) Do the same of 1) and 2) but on the mailing list. If you are
>>> new
>>> or even
>>> if you are not subscribed, you can see and search in the mailing
>>> list here:
>>> http://n2.nabble.com/Pharo-Smalltalk-f2305563.html
>>>
>>> Sometimes some tickets are reported only in m

Re: [Pharo-project] New User Experience Suggestion for 1.0

[csrabak]

Adrian,

I understand there is some reluctance in adding a "long text" (for the 
arbitrary definition of 'long').

As a counter argument, I would say that Squeak images are less laconic and two 
other Smalltalks I'm aware of (VW and ST/X) also carry a more thorough 
introduction for people who are trying first time.

As some others that report working in trains or other places with limited (or 
none conectivity), it would be nice if we could have an image where the initial 
tour could be done without need to web access.  More often than not, we 
download a lot of stuff to try it while waiting in some glass doors, airports, 
etc.!

In retrospect, I think the way as Squeak had a welcome.txt or readme.txt that 
could even be read before launching the application would be a fine addition to 
our tools to make Pharo more (new) user friendly.

my 0.01999...

--
Cesar Rabak  

Em 08/12/2009 06:39, Adrian Lienhard  escreveu:


Please note that there is an issue in the tracker that discusses this.  
I've suggested to add a workspace but do not add a long text and code  
but link to the pages on the web that contain it so that we can more  
easily make updates.

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

Tim, would that be helpful for new users of Pharo?

Cheers,
Adrian

On Dec 8, 2009, at 09:23 , Damien Cassou wrote:

> Hi Tim,
>
> On Tue, Dec 8, 2009 at 12:51 AM, Tim Mackinnon  
>  wrote:
>> Guys - do you think you might consider bringing back the little  
>> Readme Workspace in the final 1.0 image (or maybe 1.1)?
>
> there is no technical difficulty. Could you please provide a text? I
> will take care of putting it in a workspace. There may be something in
> the Pharo wiki already.
>
> Thank you
>
> -- 
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Lambdas are relegated to relative obscurity until Java makes them
> popular by not having them." James Iry
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] macintosh cocoa 32/64bit & 64/64bit VM goes BETA

[Michael Roberts]

ok that's useful to know.  it's a poor test case, i could not recreate it!

would be good to add the fixes to the tracker.

cheers,
Mike

On Wed, Dec 9, 2009 at 1:05 PM, Marcus Denker  wrote:
> Hi,
>
> This "image need a while after update" is normal.

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] package documentation viewer

[csrabak]

I also vote for having it running at Pharo website.

However it gives another opportunity to my canvassing: it is imperative that 
the comments written (class and methods) be accurate and uptodate!!

--
Cesar Rabak


Em 09/12/2009 11:06, Alexandre Bergel < alexan...@bergel.eu > escreveu:


Looks good. Maybe this could be part of the Pharo website no ?

Alexandre


On 9 Dec 2009, at 07:49, laurent laffont wrote:

> Hi,
>
> for fun and *for me*, I've made a small Seaside app to quickly  
> browse all documentation in a Pharo image.
> It's package oriented, all  classes and selectors comment on a  
> single page, so I can use search and print functions of my web  
> browser.
>
> Someone might have a use of it.  It's here: 
> http://www.squeaksource.com/SimpleWebDoc.html
> Screenshots: http://picasaweb.google.fr/laurent.laffont/Simplewebdoc
>
> Laurent
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

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






___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Gofer git

[Lukas Renggli]

> I do not know if you noticed that with the latest version of Gofer you can 
> get a full git behavior

Not full, but at least it mimics that Git syncs the local and remote
repositories.

> Gofer new
>        squeaksource: 'PharoTaskForces';
>        addPackage: 'RPackage';
>        pull

This operation is called #fetch in the latest Gofer, I renamed it
recently. This is how it is called originally in Git and it downloads
all versions to the local package cache.

> to pull all the packages pubslihed and fill up your local cache
>
> Gofer new
>        squeaksource: 'PharoTaskForces';
>        addPackage: 'RPackage';
>        push
>
> to push your local saved versions to the repository

There is updated documentation in the class comment and on my blog
article at .

> Of course it means that you can build a database and when you run your script
> the cache is checked first so yes you can work in the train :)

The reason why I didn't announce this, is because the current
implementation has serious problems that need to be fixed.

For example, reading from a remote repository that is not available
silently fails. Furthermore, to determine the latest version all
available versions from all repositories are merged, that is often not
desired.

I probably need to introduce some kind of a repository object where
the user can specify these things (consider cache or not, fail
silently or not, ...). Also there are no tests for any of this, so use
it at your own risk.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Gofer git

[Sean Allen]

On Wed, Dec 9, 2009 at 7:28 AM, Stéphane Ducasse
wrote:

> Hi guys
>
> I do not know if you noticed that with the latest version of Gofer you can
> get a full git behavior
>
> Gofer new
>squeaksource: 'PharoTaskForces';
>addPackage: 'RPackage';
>pull
>
> to pull all the packages pubslihed and fill up your local cache
>
> Gofer new
>squeaksource: 'PharoTaskForces';
>addPackage: 'RPackage';
>push
>
> to push your local saved versions to the repository
>
> Of course it means that you can build a database and when you run your
> script
> the cache is checked first so yes you can work in the train :)
>
> Tx lukas
>
>
That is awesome.
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] can I debug a primitive?

[Alexandre Bergel]

> now, the question is, should I be able to put a self halt there and  
> debug it?   I tried but I did nothing. Is this possible ? I thought  
> it was :(

I do not know for now, for few years ago you could. Simply adding a  
'self halt' in the VM code or pressing Cmd-. while executing would  
popup a debugger.

Alexandre


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






___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [Fwd: Re: DeprecationHistory]

[Alain Plantec]

--- Begin Message ---

Henrik Johansen a écrit :
From the standpoint of wanting to fix them, I really don't see the point in expanding the  tree past the first level, but sure. 
As long as you have a right-click menu-item on each to open a browser on the method for easy fixing of the deprecated call site ;)


Personally, I'd prefer a tree like in the picture attached, to me at least 
that's more intuitive.

Cheers,
Henry
  

I agree, I will make a try.
thanks a lot
Alain


--- End Message ---
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] EventInterceptor and MessageSendTree

[Alexandre Bergel]

Looks good! Do you visualize those landmarked routes?

Cheers,
Alexandre


On 7 Dec 2009, at 18:25, Hernán Morales Durand wrote:

> Hi Alex,
>  Of course, I'm using it to observe what's the best place to hook an
> interceptor (like a method wrapper) for a wayfinder tool I'm
> developing, i.e. modeling conceptual route knowledge and then
> replaying landmarked routes for learning purposes. Implementing a
> keylogger could be another interesting place to start using this tool
> as you may see all the possible methods to intercept a keystroke.
>  Concerning debugging I didn't experimented, but maybe a situation
> where a click freezes the image...IIRC there was a bug in Pharo trying
> to grab the world and then releasing the attached world... now is
> somewhat closed but is a possible scenario to see the stack trace.
> Cheers,
>
> Hernán
>
> 2009/12/6 Alexandre Bergel :
>> Hi Hernán,
>>
>> Can you describe a situation when you needed this?
>>
>> Alexandre
>>
>>
>> On 6 Dec 2009, at 04:25, Hernán Morales Durand wrote:
>>
>>> Dear all,
>>>  I've attached a little cool tool for intercepting Morphic events I
>>> just resurrected today, from the class comments:
>>>
>>> This morph is a button which, when pressed, begins listening to the
>>> hand's event stream.  When an even of the appropriate type is
>>> encountered, this morph intercepts it and traces the dispatch of the
>>> event using MessageSendTree, and opens a SendTreeExplorer on the
>>> results.  This is useful for debugging parts of the UI process which
>>> are otherwise difficult to trace. The eventType can be any of the
>>> Morphic event types, but #mouseUp, #mouseDown, and #keystroke are by
>>> far the most useful because they are the triggers for the majority  
>>> of
>>> actual UI activity.
>>>
>>> This is a list of morphic events to try:
>>>
>>> #mouseDown
>>> #mouseMove
>>> #mouseUp
>>> #mouseOver
>>> #mouseEnter
>>> #mouseLeave
>>> #mouseLeaveDragging
>>>
>>> #keystroke
>>> #keyDown
>>> #keyUp
>>>
>>> #unknown
>>> #click
>>>
>>> To install it load first MessageSendTree. The original author is  
>>> Jesse
>>> Welton http://jwelton.v-space.org/squeak/
>>>
>>> Cheers,
>>>
>>> Hernán
>>> >> 1.mcz>___
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>>
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

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






___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] package documentation viewer

[Alexandre Bergel]

Looks good. Maybe this could be part of the Pharo website no ?

Alexandre


On 9 Dec 2009, at 07:49, laurent laffont wrote:

> Hi,
>
> for fun and *for me*, I've made a small Seaside app to quickly  
> browse all documentation in a Pharo image.
> It's package oriented, all  classes and selectors comment on a  
> single page, so I can use search and print functions of my web  
> browser.
>
> Someone might have a use of it.  It's here: 
> http://www.squeaksource.com/SimpleWebDoc.html
> Screenshots: http://picasaweb.google.fr/laurent.laffont/Simplewebdoc
>
> Laurent
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

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






___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [ANN] Win32 Installers for 1.0 and 1.1alpha

[Stéphane Ducasse]

thanks

On Dec 9, 2009, at 1:37 PM, asta...@gmx.de wrote:

> The download page now includes TWO new setups for Win32
> 
> - Windows Installer 1.0-10500-rc1dev09.12.1 (Pharo 1.0 RC1)
> - Windows Installer 1.1-11073-alphadev09.12.1 (Pharo 1.1 Alpha)
> 
> similar to the ones release by Damien.
> 
> The splash now also shows if it is the release candidate or the alpha.
> Now also successfully tested on a Windows7 machine.
> 
> Bye
> T.
> 
> 
> 
> -- 
> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] macintosh cocoa 32/64bit & 64/64bit VM goes BETA

[Marcus Denker]

Hi,

This "image need a while after update" is normal.

I think it has to do with the really bad Weak* stuff... We should look at the 
fixes
that Martin von Loewis did back in end of 2007 when he visited SCG.

Marcus

On Dec 8, 2009, at 8:46 PM, Michael Roberts wrote:

> Hi John, it was not the pharo image, but the pharo core image.  You
> can get them direct from the inria download area. This is linked off
> the pharo-project site.  11049 was an internal update so start from
> 
> http://gforge.inria.fr/frs/download.php/24763/PharoCore-1.1-11043-alpha.zip
> 
> I will do this myself just to check the test case.
> 
> thanks,
> Mike
> 
> On Monday, December 7, 2009, John M McIntosh
>  wrote:
>> Ah, if someone can describe the test case:
>> 
>> which I think is take a pharo 1.1 core 11049 then do update?
>> I'll see where it's hung.
>> 
>> would that be the
>> pharo1.1-11073-alphadev09.12.1.zip
>> or
>> pharo1.1-11073-alphaweb09.12.1.zip
>> 
>> from the 1.1 alpha links on the main pharo web page?
>> 
>> 
>> On 2009-12-07, at 1:33 PM, Henrik Sperre Johansen wrote:
>> 
>>> That's pretty normal, it's happened to me a lot of times, at least.
>>> If you leave if for a while, it'll starts responding again.
>>> No idea why it happens though, I glanced at the code one time it
>>> happened, but no neurons fired :/
>>> 
>>> Cheers,
>>> Henry
>>> 
>>> On 07.12.2009 21:49, Michael Roberts wrote:
 Hi, I did a quick test on the 32bit version on 10.5.8.  I took a pharo
 1.1 core 11049 and told it to update from the network.  It processed
 all the updates (took some time) and drew the "ok" dialog.  However it
 then hung. I am not sure if that is related to the VM or not.  in a
 spare moment I will dig deeper.
 
 thanks,
 Mike
 
 On Fri, Dec 4, 2009 at 7:33 PM, John M McIntosh
   wrote:
 
> On 2009-12-04, at 4:30 AM, Stéphane Ducasse wrote:
> 
> 
>>> john needs beta testersDo not forget
>>> I know that we are all terribly busy.
>>> 
>>> 
> 
> Yes , *cough* feedback and response has been zero...
> Maybe I should push the self-destruct button on the 3.x, 4.x VM series.
> Where is that red button? Must be here somewhere in the office clutter...
> 
> --
> ===
> John M. McIntosh Twitter:  
> squeaker68882
> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
> ===
> 
> 
> 
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> 
 ___
 Pharo-project mailing list
 Pharo-project@lists.gforge.inria.fr
 http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
 
 
 
>>> 
>>> 
>>> ___
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> --
>> ===
>> John M. McIntoshTwitter:  squeaker68882
>> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
>> ===
>> 
>> 
>> 
>> 
>> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [Policital] skip if not interested

[Stéphane Ducasse]

http://www.anoncontest.org/
against scientology

Stef (I support this action because I hate brainwashers)

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [ANN] Win32 Installers for 1.0 and 1.1alpha

[astares]

The download page now includes TWO new setups for Win32

 - Windows Installer 1.0-10500-rc1dev09.12.1 (Pharo 1.0 RC1)
 - Windows Installer 1.1-11073-alphadev09.12.1 (Pharo 1.1 Alpha)

similar to the ones release by Damien.

The splash now also shows if it is the release candidate or the alpha.
Now also successfully tested on a Windows7 machine.

Bye
T.



-- 
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Gofer git

[Stéphane Ducasse]

Hi guys

I do not know if you noticed that with the latest version of Gofer you can get 
a full git behavior

Gofer new 
squeaksource: 'PharoTaskForces';
addPackage: 'RPackage';
pull

to pull all the packages pubslihed and fill up your local cache

Gofer new 
squeaksource: 'PharoTaskForces';
addPackage: 'RPackage';
push

to push your local saved versions to the repository

Of course it means that you can build a database and when you run your script 
the cache is checked first so yes you can work in the train :)

Tx lukas 



___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [update 1.1] #11083

[Marcus Denker]

11083
-

Issue 420:  Grabbing point and moving windows aroung
Issue 1152: HTTPSocket>>#getResponseUpTo: and 
HTTPSocket>>#getResponseUpTo:ignoring: are ugly and misleading
Issue 1381: ClassTestCase relies on some undocumented naming conventions
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] DeprecationHistory

[Romain Robbes]

That's a great idea!

Romain

On Dec 8, 2009, at 11:18 PM, Alain Plantec wrote:

> Hi all,
> One of my recents slice for preferences migration has made pharo  
> nearly
> unusable
> because a lot of  deprecation dialogs was opened for a single browser.
> Then, the user had to forbid the deprecation warnings in order to  
> avoid
> these popups.
>
> Now, what about a non blocking window which is opened automatically  
> when
> a deprecated method is run,
> but showing the list of recents deprecations ?
> A double click on a list item, et hop!,  a browser is opened on the
> deprecated method.
> I've tried it on the last pharo image and it seems ok. With it, it is
> still always possible to let deprecation warning
> without having to close any dialog window.
> What do you think ?
>
> A screenshot is attached.
> Cheers
> Alain
>
>
> 

--
Romain Robbes
http://www.inf.unisi.ch/phd/robbes


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] DeprecationHistory

[Stéphane Ducasse]

alain

this is cool. :)
I want to reuse the code to enhance the classBrowser 
to see the documentation of the class in a file based view
this is relate to what laurent is doing in seaside.


On Dec 9, 2009, at 12:19 PM, Alain Plantec wrote:

> Henrik Sperre Johansen a écrit :
>> +2
>> Even better if there's a button in each row to open a list of the methods 
>> that have been recorded as calling the deprecated version :D
>> 
>> Henry
>>  
> Hi Henry,
> Maybe something like that (see screenshot):
> 
> Each root shows a deprecated method call.
> Here, 3 calls to the same deprecated method but from different paths.
> The occurence show how many time the deprecated method has been called with 
> the same caller chain.
> 23 times for Try1>>call -> Try2>>call
> 2 times for Try2>>call
> 3 times for Try3>>call -> Try1>>call -> Try2>>call
> 
> So, you see exactly which deprecated methods were called, from where and how 
> many times.
> 
> Alain
> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>>  
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] package documentation viewer

[laurent laffont]

Hi,

for fun and *for me*, I've made a small Seaside app to quickly browse all
documentation in a Pharo image.
It's package oriented, all  classes and selectors comment on a single page,
so I can use search and print functions of my web browser.

Someone might have a use of it.  It's here:
http://www.squeaksource.com/SimpleWebDoc.html
Screenshots: http://picasaweb.google.fr/laurent.laffont/Simplewebdoc

Laurent
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [update] #10502

[Marcus Denker]

Hi,

Two more fixes for 1.0... 

10502
-

Issue 889:  MouseOverHandler send messages to nil
Issue 1136: DejaVu strinkeFonts render ascii character in WideStrings as 
black boxes
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] ClassTree new openOn: Collection :)

[Tudor Girba]

We are already using the MorphTreeMorph in Glamour in a 1.0 image.  
It's pretty cool.

You can get it at: Gofer new squeaksource: 'Momo'; addPackage:  
'Morphic-MorphTreeWidget'; load.

Cheers,
Doru


On 8 Dec 2009, at 21:36, Stéphane Ducasse wrote:

> 1.1 of course :)
> I'm riding the wafe :)
>
>
> On Dec 8, 2009, at 9:05 PM, Schwab,Wilhelm K wrote:
>
>> Stef,
>>
>> Where does this work?  My RC1 image either does not contain the  
>> classes, or I'm being too dense to see the corrected thing in the  
>> list of choices.  Interested, if only as examples to help me with a  
>> couple of tasks...
>>
>> Bill
>>
>>
>> -Original Message-
>> From: pharo-project-boun...@lists.gforge.inria.fr 
>> [mailto:pharo-project-boun...@lists.gforge.inria.fr 
>> ] On Behalf Of Stéphane Ducasse
>> Sent: Tuesday, December 08, 2009 11:08 AM
>> To: Pharo-project@lists.gforge.inria.fr Development
>> Cc: notre liste
>> Subject: [Pharo-project] ClassTree new openOn: Collection :)
>>
>> I started to understand MorphTreeMorph to build a class  
>> documentation browsing browser and I discovered that
>>
>>  ClassTree new openOn: Collection
>>
>>  ClassList new openOn: Collection
>>
>> This is really a good start.
>> We could have it for package
>> and displaying methods
>>
>> Stef
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"Be rather willing to give than demanding to get."




___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [ANN] new pre-build 1.0rc1#10501

[Marcus Denker]

http://gforge.inria.fr/frs/download.php/24991/PharoCore-1.0-10501rc1.zip

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [update] #10501

[Marcus Denker]

10501
-

Issue 1562: Font browser button "Update" does load fonts but font list is 
not updated
Issue 1559: BUG: "Error: Instances of UndefinedObject are not indexable" 
with Interpreter
Issue 1475: Cancelling from the Unknown Variable prompt, gives error
Issue 1478: ScriptLoader loadFFI fails with a dependency error


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [update 1.1] #11082

[Marcus Denker]

11082
-

Issue 1562: Font browser button "Update" does load fonts but font list is 
not updated
Issue 1559: BUG: "Error: Instances of UndefinedObject are not indexable" 
with Interpreter
Issue 1475: Cancelling from the Unknown Variable prompt, gives error

I will do an update for 1.0 with these now, too


Marcus
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] getting rid of Symbol >> new: ?

[Adrian Lienhard]

I don't have the VMMaker code at hand right now (or rather, don't have  
time to look at it ;)), but I guess that after that piece of code you  
pasted below there is a loop from the first field (BaseHeader+4) to  
the last non-weak field (lastFieldOffset) in which the non-weak fields  
are traced. Note, that if an object both fixed and indexable weak  
fields the latter are always located after the former. You can see the  
memory layout and object formats on the pages 9 and 10 of the slides  
[1] (from a lecture about VMs I gave recently).

Cheers,
Adrian

[1] http://www.adrian-lienhard.ch/presentations

On Dec 8, 2009, at 22:57 , Mariano Martinez Peck wrote:

> On Tue, Dec 8, 2009 at 10:54 PM, Mariano Martinez Peck <
> marianop...@gmail.com> wrote:
>
>>
>>
>> On Tue, Dec 8, 2009 at 5:07 PM, Adrian Lienhard   
>> wrote:
>>
>>>
>>> On Dec 8, 2009, at 12:08 , Mariano Martinez Peck wrote:
>>>
 On Fri, Dec 4, 2009 at 12:05 PM, Adrian Lienhard 
 wrote:
>>>
 When you are creating your root of objects and you put symbols
 inside, they
 are not put in ourPointers but in ByteArray.
 This is due to the fact that the only object who is pointing to  
 that
 symbol
 is inside the segment ?
>>>
>>> To be precise, the symbols are also pointed to by the symbol table,
>>> but only by weak references. Since image segments use the GC mark
>>> logic, these pointers are not considered.
>>>
>>
>> Ahhh ok. Now I see Symbol class >> rehashwhere it sets to  
>> SymbolTable
>> := WeakSet
>>
>> Now...my finally question is, where in the code you can see the GC  
>> only
>> mark "normal" objects and that week objects are not being taken into
>> account. Do you know ?   I tried to search it but I didn't find it.
>>
>>
> Sorry, I forgot to said I found this in ObjectMemory >> markAndTrace:
>
>(self isWeakNonInt: oop) ifTrue: [
>"Set lastFieldOffset before the weak fields in the receiver"
>lastFieldOffset := (self nonWeakFieldsOf: oop) << ShiftForWord.
>"And remember as weak root"
>weakRootCount := weakRootCount + 1.
>weakRoots at: weakRootCount put: oop.
>] ifFalse: [
>"Do it the usual way"
>lastFieldOffset := self lastPointerOf: oop.
>].
>
>
> But I don't know if this make sense or not.
>
> Thanks!!
>
> Mariano
>
>
 What you do with this piece of code:

   symbolHolder := Symbol allSymbols.

 is to hold those symbols there. So, when ImageSegment uses the GC
 techniques
 to detect which objects are ONLY pointed from inside of the  
 segment,
 the
 symbols is not found (because it is accessible trough that test)  
 and
 thus,
 it goes to outPointers instead of ByteArray.

 And of course, if it is in outPointers instead of ByteArray when  
 the
 segment
 is loaded again, yo don't create a symbol again but use the same
 object (the
 one of the oop).

 I am correct? or I understood anything ?
>>>
>>> yes.
>>>
>>> Cheers,
>>> Adrian
>>>
>>> ___
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] DeprecationHistory

[Hernán Morales Durand]

Hi Alain,
  It looks a pretty nice way to keep the developer informed, I like it.
Cheers,

Hernán

2009/12/8 Alain Plantec :
> Hi all,
> One of my recents slice for preferences migration has made pharo nearly
> unusable
> because a lot of  deprecation dialogs was opened for a single browser.
> Then, the user had to forbid the deprecation warnings in order to avoid
> these popups.
>
> Now, what about a non blocking window which is opened automatically when a
> deprecated method is run,
> but showing the list of recents deprecations ?
> A double click on a list item, et hop!,  a browser is opened on the
> deprecated method.
> I've tried it on the last pharo image and it seems ok. With it, it is still
> always possible to let deprecation warning
> without having to close any dialog window.
> What do you think ?
>
> A screenshot is attached.
> Cheers
> Alain
>
>
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project