Re: [Pharo-project] ZeroMQ, Mongrel2...

[Mike Hales]

I'd be really interested in zmq for pharo/squeak too. I've been playing with
it to replace mutexes and semaphores for multiprocessing in a c program, and
would love to be able to tie in some smalltalk too. Mongrel2 and seaside
could be interesting too, especially for websocket support.

Mike

Mike Hales
Engineering Manager
KnowledgeScape
www.kscape.com


On Tue, Jan 11, 2011 at 9:24 AM, Geoffroy Couprie wrote:

> Hello,
>
> What would you think of a ZeroMQ frontend to Pharo? I was playing with
> ZeroMQ, and more specifically the Mongrel2 web server, and I thought
> that would be cool to use it, but the only reference of ZeroMQ and
> Smalltalk I saw was about some code from Thomas Gagné, which is not
> available anymore.
>
> Anyhow, would you be interested in a port to Pharo? It looks like the
> protocol is not really hard to implement.
>
> Best regards,
>
> Geoffroy
>
>

Re: [Pharo-project] XML packages, CDATA and encoding

[jaayer]

Sorry, I accidentally hit reply before typing anything.

Torsten, what you are trying to do is not incorrect and should work as you 
expected it to. The reason why it didn't has less to do with XMLSupport per se 
and more to do with its reliance on Pharo's TextConverter system. The problem 
is faulty matching of the "encoding" attribute value to the appropriate 
subclass of TextConverter. The code responsible for this in XMLSupport is:
converterClass :=
(Smalltalk
at: #TextConverter
ifAbsent: [^ self])
defaultConverterClassForEncoding: 
anEncodingName asLowercase.

But as you can see, the matching is actually done by TextConverter and its 
class-side #defaultConverterClassForEncoding: method, which works by sending 
#encodingNames to all subclasses and testing the array returned to see if it 
includes the specified encoding name. If you browse Latin1TextConverter, the 
right class for the encoding you specified, and look at its #encodingNames 
message, you will see the array it returns does not include "ISO-8859-1":
^ #('latin-1' 'latin1') copy.

Change it to this  (note the lowercase):
^ #('latin-1' 'latin1' 'iso-8859-1') copy.

and everything now works.

So this is really a bug in TextConverter and its Latin1TextConverter subclass, 
not XMLSupport. Also, the #allSubclassesDo: test in 
#defaultConverterClassForEncoding: should probably be augmented with a 
Dictionary cache to speed-up lookups for known encoding-converter pairs. Can 
someone forward this message to whoever maintains TextConverter?

 On Mon, 10 Jan 2011 04:38:23 -0800 Torsten Bergmann  wrote  

>Create a file "test.xml" with the following 
>contents (german umlaut): 
> 
> 
>  
>  
> 
>After loading ConfigurationOfXML try to parse it: 
> 
> |fs| 
> fs := FileStream fileNamed: 'test.xml'. 
> XMLDOMParser parseDocumentFrom: fs. 
> 
> 
>=> gives an error: 'Invalid utf8 input detected' 
>=> it works if you remove the CDATA section 
> 
>Looks like UTF8TextConverter is used independent 
>from the encoding of the XML... 
> 
>Bye 
>T. 
>-- 
>NEU: FreePhone - kostenlos mobil telefonieren und surfen! 
>Jetzt informieren: http://www.gmx.net/de/go/freephone 
> 
> 

Re: [Pharo-project] XML packages, CDATA and encoding

[jaayer]

 On Mon, 10 Jan 2011 04:38:23 -0800 Torsten Bergmann  wrote  

>Create a file "test.xml" with the following 
>contents (german umlaut): 
> 
> 
>  
>  
> 
>After loading ConfigurationOfXML try to parse it: 
> 
> |fs| 
> fs := FileStream fileNamed: 'test.xml'. 
> XMLDOMParser parseDocumentFrom: fs. 
> 
> 
>=> gives an error: 'Invalid utf8 input detected' 
>=> it works if you remove the CDATA section 
> 
>Looks like UTF8TextConverter is used independent 
>from the encoding of the XML... 
> 
>Bye 
>T. 
>-- 
>NEU: FreePhone - kostenlos mobil telefonieren und surfen! 
>Jetzt informieren: http://www.gmx.net/de/go/freephone 
> 
>

Re: [Pharo-project] new Cog VMs

[Eliot Miranda]

Hi All,

   I've uploaded new VMs to
VM.r2348/
(SimpleStackBasedCogit)
and VM.r2349/ 
(StackToRegisterMappingCogit).
The former are simply to be up-to-date with svn & Monticello.  The latter
also fix a bad bug with the StackToRegisterMappingCogit where e.g. 16r10
bitOr: 16r20 would evaluate to 1.   I've smoke-tested the 2349 VMs on the
Squeak4.2 beta test suite and things look good.

best
Eliot

Re: [Pharo-project] [update 1.2] #12305

[Francisco Ortiz Peñaloza]

Hi, i don't like the orange theme to be the default one. IMHO it looks
like a high contrast one.

I prefer Glamour or even Watery!

Regards,
Francisco

On Sat, Jan 15, 2011 at 5:39 PM, Esteban Lorenzano  wrote:
> Hi,
> I really don't like the orange theme to become the default pharo theme... is 
> to "alien" for me, and I'm sure it will be also for newcomers. May I suggest 
> to let the standard glamour theme as the default, and keep the orange just as 
> an option?
>
> Cheers,
> Esteban
>
> El 15/01/2011, a las 4:05p.m., Stéphane Ducasse escribió:
>
>> why not :)
>> even if the orange is too orange :)
>> Stef
>>
>>> Why don't you call the GLMOrangeUITheme the PharoTheme or something in this 
>>> direction?
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On 14 Jan 2011, at 15:46, Stéphane Ducasse wrote:
>>>
 12305
 -

 - GLMOrangeUITheme beCurrent.
 - Issue 3417:       BehaviorTest>>#testAllLocalCallsOn fails.

 Stef

>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Reasonable is what we are accustomed with."
>>>
>>>
>>
>>
>
>
>

Re: [Pharo-project] [update 1.2] #12305

[Esteban Lorenzano]

Hi,
I really don't like the orange theme to become the default pharo theme... is to 
"alien" for me, and I'm sure it will be also for newcomers. May I suggest to 
let the standard glamour theme as the default, and keep the orange just as an 
option?

Cheers,
Esteban

El 15/01/2011, a las 4:05p.m., Stéphane Ducasse escribió:

> why not :)
> even if the orange is too orange :)
> Stef
> 
>> Why don't you call the GLMOrangeUITheme the PharoTheme or something in this 
>> direction?
>> 
>> Cheers,
>> Doru
>> 
>> 
>> On 14 Jan 2011, at 15:46, Stéphane Ducasse wrote:
>> 
>>> 12305
>>> -
>>> 
>>> - GLMOrangeUITheme beCurrent.
>>> - Issue 3417:   BehaviorTest>>#testAllLocalCallsOn fails.
>>> 
>>> Stef
>>> 
>> 
>> --
>> www.tudorgirba.com
>> 
>> "Reasonable is what we are accustomed with."
>> 
>> 
> 
> 

Re: [Pharo-project] [Pharo-users] Where do I find KeyedSet?

[Levente Uzonyi]

On Sat, 15 Jan 2011, Hernán Morales Durand wrote:


Hi Stef

2011/1/15 Stéphane Ducasse :


On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote:


Try PluggableSet


Note that KeyedSet has nothing to do with PluggableSet. PluggableSet is a 
set where you can specify the hash and equality of two objects with 
blocks. This gives you great flexibility without creating a subclass of 
Set.
KeyedSet is like a dictionary, but the keys of the objects are not stored 
in the data structure, because the objects know it themselves. This means 
that the data structure will have a smaller memory footprint.



Levente



http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.html

Is there a way for you guys to deprecate deleted classes or mantain a
record of deleted behaviors? (IIRC VW did this from 2.x versions)


We try but we do not have the engineers of VW.
Now find somebody that pay us just 3 engineers full time for two years and you 
will not
recognized pharo and its process.


I know we are very few, but what about this idea, instead of just
deleting a class we may adopt these simple rules:

1 - If deleting a class add the deleted class name somewhere (in a method?)
2 - If renaming a class, make the class to know its previous names
like #previousNames
(Norberto Manzanos implemented this for his own package management and
I think is a great idea)

doesn't require tools, just some consensus and maybe a modified
#deleteClass to enforce this "policy"

it sounds feasible for you? what do you think?

Hernán

Re: [Pharo-project] [update 1.2] #12305

[Stéphane Ducasse]

why not :)
even if the orange is too orange :)
Stef

> Why don't you call the GLMOrangeUITheme the PharoTheme or something in this 
> direction?
> 
> Cheers,
> Doru
> 
> 
> On 14 Jan 2011, at 15:46, Stéphane Ducasse wrote:
> 
>> 12305
>> -
>> 
>> - GLMOrangeUITheme beCurrent.
>> - Issue 3417:BehaviorTest>>#testAllLocalCallsOn fails.
>> 
>> Stef
>> 
> 
> --
> www.tudorgirba.com
> 
> "Reasonable is what we are accustomed with."
> 
> 

Re: [Pharo-project] [update 1.2] #12305

[Tudor Girba]

Why don't you call the GLMOrangeUITheme the PharoTheme or something in this 
direction?

Cheers,
Doru


On 14 Jan 2011, at 15:46, Stéphane Ducasse wrote:

> 12305
> -
> 
> - GLMOrangeUITheme beCurrent.
> - Issue 3417: BehaviorTest>>#testAllLocalCallsOn fails.
> 
> Stef
> 

--
www.tudorgirba.com

"Reasonable is what we are accustomed with."

Re: [Pharo-project] Need help about Sockets

[Levente Uzonyi]

On Sat, 15 Jan 2011, Adrien BARREAU wrote:



Hi all,

I'm trying to use the Sockets in Pharo but I don't understand some points.
I tried that piece of code:

| s c rcv |
Socket initializeNetwork.
rcv := String new: 400.
s := Socket new.
s listenOn: 12345.


The problem is here. You should use #listenOn:backlogSize: if you want to 
accept (multiple) connections. #listenOn: is a "special" method that uses 
the same socket for listening and receiveing data. See the method comments 
for details. Here's a small example how to use #listenOn:. Copy it to a 
workspace and print it:


server := Socket new.
semaphore := Semaphore new.
[ [
server listenOn: 12345.
server semaphore wait. "wait for the client to connect"
server waitForData.
data := server receiveData.
semaphore signal ]
ensure: [ server closeAndDestroy ] ] fork.
client := Socket new.
client connectTo: #[127 0 0 1] port: 12345.
client sendData: 'Hello!'.
client closeAndDestroy.
data


Levente


c := s waitForAcceptFor: 30.
c dataAvailable ifTrue: [ c receiveDataInto: rcv ] ifFalse: [ self halt ].

waitForAcceptFor: waits a connection, so I opened a telnet client on localhost:12345. It 
works, but the "accept" primitive always failed.
I tried to find some code where it's used: ConnectionQueue>>listenLoop.
I assume that method works (but it has no sender), and I don't understand what 
is different between it and my code.

Perhaps I don't try to use the Sockets the good way?

Adrien.

[Pharo-project] Need help about Sockets

[Adrien BARREAU]

Hi all,

I'm trying to use the Sockets in Pharo but I don't understand some points.
I tried that piece of code:

| s c rcv |
Socket initializeNetwork.
rcv := String new: 400.
s := Socket new.
s listenOn: 12345.
c := s waitForAcceptFor: 30.
c dataAvailable ifTrue: [ c receiveDataInto: rcv ] ifFalse: [ self halt ].

waitForAcceptFor: waits a connection, so I opened a telnet client on 
localhost:12345. It works, but the "accept" primitive always failed.
I tried to find some code where it's used: ConnectionQueue>>listenLoop.
I assume that method works (but it has no sender), and I don't understand what 
is different between it and my code.

Perhaps I don't try to use the Sockets the good way?

Adrien.
  

Re: [Pharo-project] Issue 3540 in pharo: Latest versions in DevImages Workspace

[pharo]

Updates:
Status: Accepted
Cc: guillermopolito
Labels: Milestone-1.2-DevImage

Comment #1 on issue 3540 by marianopeck: Latest versions in DevImages  
Workspace

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

thanks Janko. Indeed, that's true.

[Pharo-project] Issue 3540 in pharo: Latest versions in DevImages Workspace

[pharo]

Status: New
Owner: 

New issue 3540 by janko.mi...@gmail.com: Latest versions in DevImages  
Workspace

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

Hi,

If you open DEVImageWorkspaces openExternalProjectWorkspace in latest 1.2  
build, there are still old versions, this should be corrected at least to:


...
((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.0.3') load.  
...
((Smalltalk at: #ConfigurationOfAida) project version: '6.2') load. 

Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride

[pharo]

Updates:
Status: Fixed

Comment #5 on issue 3471 by laurent@gmail.com: [Failing Test]  
OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3522 in pharo: wiki like help contents

[pharo]

Updates:
Labels: -Milestone-1.3 Milestone-1.2

Comment #10 on issue 3522 by stephane...@gmail.com: wiki like help contents
http://code.google.com/p/pharo/issues/detail?id=3522

I want that in 1.2 :)
so in the next integration

Re: [Pharo-project] we will start 1.3 really soon

[Stéphane Ducasse]

On Jan 15, 2011, at 9:57 AM, Adrian Lienhard wrote:

> Cool :)
> 
> BTW, I have a question related to 1.2 from a user's perspective: could we 
> generate a summary to help people migrate from 1.1.1 to 1.2? In particular, 
> the question is which changes in 1.2 are not backwards compatible and may 
> break my code? I've been a bit out of the loop during the last months... so 
> at least for me this is not obvious ;). There's 
> http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo but it doesn't 
> tell the important bits.


going over the issues tagged 1.2 and generate a report will take me at least a 
couple of hours so 
I'm not sure that I have the time to do it. Now if someone starts I can help 
improving the results.
We can also take all the comments in the scriptloader methods.

Stef
> 
> Cheers,
> Adrian
> 
> On Jan 15, 2011, at 09:27 , Stéphane Ducasse wrote:
> 
>> Hi guys
>> 
>> there are some minors fixes to be addressed (like the preferences use in 
>> dev) but we will go 1.3 probably this evening and 
>> we will start to harvest a large list of pending issues. If you have seen 
>> fixes in squeak that you think are good please add a bug entry.
>> After that we will plan for the big changes in 1.3 for me
>>  I would like to see
>>  - collection enh (finishing hashed collection)
>>  - weak structure support
>>  - announcement using weak structure
>>  - file system use
>>  - new package implementation (cyrille worked and will continue 
>> to really make sure everything works)
>>  - real beta of OPAL
>> The goal is to have a release for 1.3 by June/July. 
>> 
>> Stef
>>  
> 
> 

Re: [Pharo-project] we will start 1.3 really soon

[Janko Mivšek]

Stef, you again forgot namespaces ... ;)

Janko

On 15. 01. 2011 09:27, Stéphane Ducasse wrote:
> Hi guys
> 
> there are some minors fixes to be addressed (like the preferences use in dev) 
> but we will go 1.3 probably this evening and 
> we will start to harvest a large list of pending issues. If you have seen 
> fixes in squeak that you think are good please add a bug entry.
> After that we will plan for the big changes in 1.3 for me
>   I would like to see
>   - collection enh (finishing hashed collection)
>   - weak structure support
>   - announcement using weak structure
>   - file system use
>   - new package implementation (cyrille worked and will continue 
> to really make sure everything works)
>   - real beta of OPAL
> The goal is to have a release for 1.3 by June/July. 
> 
> Stef
>   

-- 
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si

Re: [Pharo-project] [Pharo-users] Where do I find KeyedSet?

[Stéphane Ducasse]

On Jan 15, 2011, at 9:52 AM, Hernán Morales Durand wrote:

> Hi Stef
> 
> 2011/1/15 Stéphane Ducasse :
>> 
>> On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote:
>> 
>>> Try PluggableSet
>>> 
>>> http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.html
>>> 
>>> Is there a way for you guys to deprecate deleted classes or mantain a
>>> record of deleted behaviors? (IIRC VW did this from 2.x versions)
>> 
>> We try but we do not have the engineers of VW.
>> Now find somebody that pay us just 3 engineers full time for two years and 
>> you will not
>> recognized pharo and its process.
> 
> I know we are very few, but what about this idea, instead of just
> deleting a class we may adopt these simple rules:
> 
> 1 - If deleting a class add the deleted class name somewhere (in a method?)
> 2 - If renaming a class, make the class to know its previous names
> like #previousNames
> (Norberto Manzanos implemented this for his own package management and
> I think is a great idea)
> 
> doesn't require tools, just some consensus and maybe a modified
> #deleteClass to enforce this "policy"

yes this would be nice to have tool doing it for us.

> 
> it sounds feasible for you? what do you think?
> 
> Hernán
> 

Re: [Pharo-project] [Pharo-users] Where do I find KeyedSet?

[Stéphane Ducasse]

Previous names is a good idea 
We should adopt it!

Stef

On Jan 15, 2011, at 9:52 AM, Hernán Morales Durand wrote:

> Hi Stef
> 
> 2011/1/15 Stéphane Ducasse :
>> 
>> On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote:
>> 
>>> Try PluggableSet
>>> 
>>> http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.html
>>> 
>>> Is there a way for you guys to deprecate deleted classes or mantain a
>>> record of deleted behaviors? (IIRC VW did this from 2.x versions)
>> 
>> We try but we do not have the engineers of VW.
>> Now find somebody that pay us just 3 engineers full time for two years and 
>> you will not
>> recognized pharo and its process.
> 
> I know we are very few, but what about this idea, instead of just
> deleting a class we may adopt these simple rules:
> 
> 1 - If deleting a class add the deleted class name somewhere (in a method?)
> 2 - If renaming a class, make the class to know its previous names
> like #previousNames
> (Norberto Manzanos implemented this for his own package management and
> I think is a great idea)
> 
> doesn't require tools, just some consensus and maybe a modified
> #deleteClass to enforce this "policy"
> 
> it sounds feasible for you? what do you think?
> 
> Hernán
> 

Re: [Pharo-project] Issue 3236 in pharo: Cuis DateAndTime Enhancement

[pharo]

Updates:
Labels: Milestone-1.3

Comment #2 on issue 3236 by stephane...@gmail.com: Cuis DateAndTime  
Enhancement

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

(No comment was entered for this change.)

Re: [Pharo-project] DateAndTime millisecond is always 0

[Stéphane Ducasse]

so simple you see
if people wants to get that in pharo
- get a changeset out of the text
- check in cuis if there are other changes
- tests?

Stef

On Jan 15, 2011, at 9:50 AM, Adrian Lienhard wrote:

> On Jan 15, 2011, at 09:21 , Stéphane Ducasse wrote:
> 
>> 
>> On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote:
>> 
>>> Sorry,
>>> 
>>> I meen DateAndTime now millisecond and DateAndTime now nanoSecond.
>>> 
>>> As I write in last mail. I found cuis fix of this in Pharo issues
>> 
>> 
>> where?
> 
> Denis sent a link to the issue in question in a previous mail in this thread:
> 
> http://code.google.com/p/pharo/issues/detail?id=3236
> 
> Adrian
> 
> 
> __
> www.adrian-lienhard.ch
> twitter.com/adrianlienhard
> 
> 

Re: [Pharo-project] DateAndTime millisecond is always 0

[Stéphane Ducasse]

Thanks I could not see it ;/

Stef

On Jan 15, 2011, at 9:50 AM, Adrian Lienhard wrote:

> On Jan 15, 2011, at 09:21 , Stéphane Ducasse wrote:
> 
>> 
>> On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote:
>> 
>>> Sorry,
>>> 
>>> I meen DateAndTime now millisecond and DateAndTime now nanoSecond.
>>> 
>>> As I write in last mail. I found cuis fix of this in Pharo issues
>> 
>> 
>> where?
> 
> Denis sent a link to the issue in question in a previous mail in this thread:
> 
> http://code.google.com/p/pharo/issues/detail?id=3236
> 
> Adrian
> 
> 
> __
> www.adrian-lienhard.ch
> twitter.com/adrianlienhard
> 
> 

Re: [Pharo-project] we will start 1.3 really soon

[Adrian Lienhard]

Cool :)

BTW, I have a question related to 1.2 from a user's perspective: could we 
generate a summary to help people migrate from 1.1.1 to 1.2? In particular, the 
question is which changes in 1.2 are not backwards compatible and may break my 
code? I've been a bit out of the loop during the last months... so at least for 
me this is not obvious ;). There's 
http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo but it doesn't tell 
the important bits.

Cheers,
Adrian

On Jan 15, 2011, at 09:27 , Stéphane Ducasse wrote:

> Hi guys
> 
> there are some minors fixes to be addressed (like the preferences use in dev) 
> but we will go 1.3 probably this evening and 
> we will start to harvest a large list of pending issues. If you have seen 
> fixes in squeak that you think are good please add a bug entry.
> After that we will plan for the big changes in 1.3 for me
>   I would like to see
>   - collection enh (finishing hashed collection)
>   - weak structure support
>   - announcement using weak structure
>   - file system use
>   - new package implementation (cyrille worked and will continue 
> to really make sure everything works)
>   - real beta of OPAL
> The goal is to have a release for 1.3 by June/July. 
> 
> Stef
>   

Re: [Pharo-project] new Cog VMs

[Philippe Marschall]

On 10.01.2011 01:28, Eliot Miranda wrote:
> Hi All,
> 
> find new VMs in VM.r2344/
>  (SimpleStackBasedCogit)
> and VM.r2345/
>  
> (StackToRegisterMappingCogit)
> and VMMaker-oscog-45.  These fix a bug that could cause crashes when
> converting an interpreted method to a machine-code method on backward
> branch (i.e. when the Vm detects an interpreted method is looping).  
> 
> I hope there are no new issues with VM.r2344/
>  (SimpleStackBasedCogit).
>  However, Matthew Fulmer has found that on linux the VM.r2343/
>  VM.r2345/
>  
> (StackToRegisterMappingCogit)
> VMs crash immediately loading Squeak4.2-10856-beta.image.  I can
> reproduce this but haven't had time to investigate.
>  The StackToRegisterMappingCogit VMs do start up this image on Mac and
> Windows.
> 
> Agan thanks for pounding on these.  I may not be able to attend to the
> linux/StackToRegisterMappingCogit/Squeak4.2-10856-beta.image until next
> weekend. Apologies.

r2346 fixes the issues I sometimes had with when the stack would be
messed up the first time a method is executed.

Cheers
Philippe

Re: [Pharo-project] [Pharo-users] Where do I find KeyedSet?

[Hernán Morales Durand]

Hi Stef

2011/1/15 Stéphane Ducasse :
>
> On Jan 14, 2011, at 6:24 PM, Hernán Morales Durand wrote:
>
>> Try PluggableSet
>>
>> http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.html
>>
>> Is there a way for you guys to deprecate deleted classes or mantain a
>> record of deleted behaviors? (IIRC VW did this from 2.x versions)
>
> We try but we do not have the engineers of VW.
> Now find somebody that pay us just 3 engineers full time for two years and 
> you will not
> recognized pharo and its process.

I know we are very few, but what about this idea, instead of just
deleting a class we may adopt these simple rules:

1 - If deleting a class add the deleted class name somewhere (in a method?)
2 - If renaming a class, make the class to know its previous names
like #previousNames
(Norberto Manzanos implemented this for his own package management and
I think is a great idea)

doesn't require tools, just some consensus and maybe a modified
#deleteClass to enforce this "policy"

it sounds feasible for you? what do you think?

Hernán

Re: [Pharo-project] DateAndTime millisecond is always 0

[Adrian Lienhard]

On Jan 15, 2011, at 09:21 , Stéphane Ducasse wrote:

> 
> On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote:
> 
>> Sorry,
>> 
>> I meen DateAndTime now millisecond and DateAndTime now nanoSecond.
>> 
>> As I write in last mail. I found cuis fix of this in Pharo issues
> 
> 
> where?

Denis sent a link to the issue in question in a previous mail in this thread:

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

Adrian


__
www.adrian-lienhard.ch
twitter.com/adrianlienhard

[Pharo-project] we will start 1.3 really soon

[Stéphane Ducasse]

Hi guys

there are some minors fixes to be addressed (like the preferences use in dev) 
but we will go 1.3 probably this evening and 
we will start to harvest a large list of pending issues. If you have seen fixes 
in squeak that you think are good please add a bug entry.
After that we will plan for the big changes in 1.3 for me
I would like to see
- collection enh (finishing hashed collection)
- weak structure support
- announcement using weak structure
- file system use
- new package implementation (cyrille worked and will continue 
to really make sure everything works)
- real beta of OPAL
The goal is to have a release for 1.3 by June/July. 

Stef

Re: [Pharo-project] DateAndTime millisecond is always 0

[Stéphane Ducasse]

On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote:

> Sorry,
> 
> I meen DateAndTime now millisecond and DateAndTime now nanoSecond.
> 
> As I write in last mail. I found cuis fix of this in Pharo issues


where?

Denis please provide more information else we all have to spend more time to 
answer and decide the next action.

Stef

> 
> 2011/1/14 Adrian Lienhard 
> Hi Denis,
> 
> There's no method milliseconds (at least in my Pharo 1.1.1 image). Can you be 
> more specific?
> 
> I assume you want to get the milli seconds of a timestamp, rather than the 
> millisecond clock (DateAndTime millisecondClockValue).
> 
> When you create a new timestamp (TimeStamp now) the milli/nano seconds are 
> indeed 0. The reason is that the timestamp is initialized from "Time 
> totalSeconds".
> 
> So I consider this not as a bug but something that could be improved.
> 
> Cheers,
> Adrian
> 
> BTW, I remember having seen a fix on Mantis (= Squeak bug tracker) which 
> asserts that TimeStamp now < TimeStamp now.
> 
> 
> On Jan 14, 2011, at 10:20 , Denis Kudriashov wrote:
> 
> > Hello.
> >
> > How I can get current time milliseconds parameter?
> >
> > I try  DateAndTime millisecond. But it always zero.
> > And DateAndTime nanoSecond is always zero too.
> >
> > Is it bug?
> >
> > I use Pharo1.1
> 
> 
> 

Re: [Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

[Stéphane Ducasse]

Improve the infrastructure so that we can get rid of most of the subclasses.
Now the best way to make sure that this will happen is that some people see it 
right in front of their nose.

Did you notice for example that we were just some to attend the irc?
So how can we really communicate?


Stef

> 
> 
> On Thu, Jan 13, 2011 at 9:15 PM, Stéphane Ducasse  
> wrote:
> 12302
> -
> 
> - GLMOrangeUITheme. Thanks Igor Stasenko
> 
> I don't agree with this kind of changes. 
> Tomorrow I want Watery2BlackTheme and GLMYellowUITHeme and what?  we are 
> going to integrate it also?
> 
> I don't understand. The change should be to create a setting to set the color 
> and then igor runs a script in his own image that set it to orange. Me to 
> yellow. And you to pink. 
>  
> 
> - Issue 3538:   Add a "Browse test" in the TestRunner failed/error list. 
> Thanks Benjamin van Ryseghem
> 
> Stef
> 

Re: [Pharo-project] Eeekk.. Morphic-Themes are now part of Morphic package

[Stéphane Ducasse]

when you send a fix, it is better that this is well structured. I do not have a 
super brain to get exactly in your mind set 
so the duller the integrator job the better. 

We verify that there is no mess and that the system load well but I would like 
to open the process.

Stef

> I was surprised to see it part of morphic. It introducing dependency loop,
> 
> Actually the name 'Morphic-Themes' was only a suggestion how to name a
> separate package,
> but not meant to merge it with Morphic.
> 
> we should fix that now.
> 
> -- 
> Best regards,
> Igor Stasenko AKA sig.
> 

Re: [Pharo-project] "Bindable" or "Observable" collections on Pharo/Smalltalk?

[Stéphane Ducasse]

you have to implement your own container emmitting events.
Because normal collection are not done for that but to go fast.

Stef

On Jan 14, 2011, at 10:35 PM, nullPointer wrote:

> 
> Hi, excuse me for my poor english.
> 
> Exist some type of collection for bind to widgets like a listView or grid? I
> want say a special collection than allow know, externally, when a object is
> added, removed, changed the "current" etc  for represent changes on a GUI.
> 
> For example, I have a collection connected on a grid. When I add or remove a
> element on collection I have refresh the grid set again the collection like
> datasource, and select the same object of before. That is hard for the
> widget when I have very items. I want "capture", with events or others, and
> remove only the row of grid, and not refresh all again.
> 
> I don´t know if I do the question correctly.
> 
> Regards
> 
> -- 
> View this message in context: 
> http://forum.world.st/Bindable-or-Observable-collections-on-Pharo-Smalltalk-tp3218402p3218402.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
> 

Re: [Pharo-project] Congrats

[Stéphane Ducasse]

On Jan 14, 2011, at 10:37 PM, Igor Stasenko wrote:

>> The Royal Academy of Engineering recognizes a researcher at INRIA
>> 
>> Stephane Ducasse © INRIA
>> 
>> Stéphane Ducasse, Director of Research Rmod team, was awarded the
>> Distinguished Visiting Fellowship Award.
>> 
> 
>> The objective of this award is multiple:
>> 
>> * Promote joint initiatives and complementary that could form the basis for
>> future collaboration and strategic alliance research
>> * Allow the sharing of latest developments, experiences and knowledge of
>> various fields of engineering and technology
>> 
>> It is in this context of international exchanges and collaborations,
>> Stéphane Ducasse has been discerned a visitor price Emeritus, by the Royal
>> Academy of Engineering (Distinguished Visiting Fellowship Award).
>> 
>> As supported by a research team English at York University, he spent three
>> weeks with daily team of Manuel Oriol, whose research focuses on software
>> engineering and testing automated software engineering.
>> Keywords:
>> 
> 
> Still i don't get it, what the catch?  :)

exactly 
but prizes and awards are cool to have 

> Sounds like Stef will be away for 3 weeks, right?

Yes :)
no admin from lille :)

> 
> 
> 
> -- 
> Best regards,
> Igor Stasenko AKA sig.
> 

Re: [Pharo-project] Congrats

[Stéphane Ducasse]

nothing special 
I got a distinguished visited award from the royal academy for visiting a 
research group in york

Stef

On Jan 14, 2011, at 8:41 PM, Steven Baker wrote:

> I can't find an english translation. Can someone summarize this in
> english for me?
> 
> Thanks,
> -Steven
> 
> On Fri, Jan 14, 2011 at 8:17 AM, Miguel Cobá  wrote:
>> Congrats Stéph,
>> 
>> http://www.inria.fr/centre-de-recherche-inria/lille-nord-europe/actualites/un-chercheur-de-l-inria-a-la-york-university
>> 
>> Cheers
>> --
>> Miguel Cobá
>> http://twitter.com/MiguelCobaMtz
>> http://miguel.leugim.com.mx
>> 
>> 
>> 
>> 
>> 
> 

Re: [Pharo-project] Congrats

[Stéphane Ducasse]

Thanks
I fact english friends of mine told me that this is really well considered 
there. but I just sent a cv and a small proposal for working with a friend there
and learn english :)
Stef

On Jan 14, 2011, at 5:17 PM, Miguel Cobá wrote:

> Congrats Stéph,
> 
> http://www.inria.fr/centre-de-recherche-inria/lille-nord-europe/actualites/un-chercheur-de-l-inria-a-la-york-university
> 
> Cheers
> -- 
> Miguel Cobá
> http://twitter.com/MiguelCobaMtz
> http://miguel.leugim.com.mx
> 
> 
> 
> 

Re: [Pharo-project] Pharo issues on Google

[Stéphane Ducasse]

what do you mean 
not sending notification?
not sending mails?

I get the list
http://code.google.com/p/pharo/issues/list

Stef
On Jan 14, 2011, at 6:15 PM, Gary Chambers wrote:

> Is the Pharo issues google site not working?
> 
> Regards, Gary