Re: [Pharo-dev] Roassal Question

2013-11-27 Thread Norbert Hartl

Am 27.11.2013 um 07:06 schrieb Tudor Girba tu...@tudorgirba.com:

 Perhaps it would be more useful to have these types of discussions on the 
 moose-dev mailing list. You might be surprised by other things you might find 
 there :)
 
I disagree with the first sentence. I like to read Roassal stuff here in this 
list. I’m not subscribed in the moose mailing list (trying to reduce the mails 
I get) but I would like to be up to date with Roassal that has use case 
scenarios that exceed the bounds of moose. And I don’t like the tension that 
moose is engrossing standalone packages (like petit parser ;) )

Norbert

 In case of interest, here are the coordinates:
 http://www.moosetechnology.org/about/contact
 
 Cheers,
 Doru
 
 
 
 
 On Tue, Nov 26, 2013 at 8:59 PM, Alexandre Bergel alexandre.ber...@me.com 
 wrote:
 Excellent! Let us know for any request for enhancement or bug fixes.
 
 Cheers,
 Alexandre
 --
 _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
 Alexandre Bergel  http://www.bergel.eu
 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
 
 
 
 On Nov 26, 2013, at 4:20 PM, GOUBIER Thierry thierry.goub...@cea.fr wrote:
 
  Yes! I also found there is a ROPlatform thing I can query (not sure, the 
  code is at work and I'm home).
 
  (I'm coupling a C ast + CFG + parallel task analysis displayed with Roassal 
  with interaction with the source code under analysis on a text pane. I 
  demoed it this morning to our partner)
 
  Thierry
  
  De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Alexandre 
  Bergel [alexandre.ber...@me.com]
  Date d'envoi : mardi 26 novembre 2013 17:56
  À : Pharo Development List
  Objet : Re: [Pharo-dev] Roassal Question
 
  Does the following helps?
  -=-=-=-=-=-=-=-=-=-=-=-=
  | view  shape morph |
  view := ROView new.
  100 timesRepeat: [
 shape := ROEllipse new size: 40; color: (Color green alpha: 0.5).
 view add: shape element ].
  view elements do: [ :el | el translateTo: 500 atRandom @ 500 atRandom ].
 
 
  morph := ROAthensMorph on: view.
  morph extent: 500 @ 500.
  morph openInWindow
  -=-=-=-=-=-=-=-=-=-=-=-=
 
  If you do not use Athens, then replace “ROAthensMorph” by “ROMorph”
 
  Alexandre
 
  --
  _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
  Alexandre Bergel  http://www.bergel.eu
  ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
 
 
 
  On Nov 26, 2013, at 12:51 PM, Goubier Thierry thierry.goub...@cea.fr 
  wrote:
 
  Hi all,
 
  does anybody knows how to integrate a ROView inside a Morphic GUI ?
 
  Regards,
 
  Thierry
  --
  Thierry Goubier
  CEA list
  Laboratoire des Fondations des Systèmes Temps Réel Embarqués
  91191 Gif sur Yvette Cedex
  France
  Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
 
 
 
 
 
 
 
 
 
 -- 
 www.tudorgirba.com
 
 Every thing has its own flow



[Pharo-dev] [Review needed] fix for Pharo2 text highlighting incorrect

2013-11-27 Thread Marcus Denker
12241 text highlighting incorrect
https://pharo.fogbugz.com/f/cases/12241

What needs to be done?

- does it fix the bug?
- Is the fix plausibly ok?
- Is this a problem in Pharo3, too? 
If yes — add issue for back porting, 
- make slice for 3


[Pharo-dev] [pharo-project/pharo-core] 920f37: 30600

2013-11-27 Thread GitHub
  Branch: refs/heads/3.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 920f3782ce4ba961426d2dfcc28256d4591db771
  
https://github.com/pharo-project/pharo-core/commit/920f3782ce4ba961426d2dfcc28256d4591db771
  Author: Jenkins Build Server bo...@pharo-project.org
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M 
ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/accessing/protocols.st
A Kernel.package/Job.class/class/accessing/current.st
A Kernel.package/JobDetector.class/README.md
A Kernel.package/JobDetector.class/definition.st
A Kernel.package/JobDetector.class/instance/handling/handle_.st
M Kernel.package/JobProgress.class/README.md
A KernelTests.package/JobTest.class/instance/tests/testCurrent.st
M Morphic-Base.package/MorphTreeListManager.class/instance/keyboard 
managing/basicKeyPressed_.st
M Morphic-Base.package/MorphTreeListManager.class/instance/keyboard 
managing/keyStroke_.st
A 
Morphic-Base.package/MorphTreeListManager.class/instance/private/selectSearchedElement.st
A 
Nautilus.package/PackageTreeNodeModel.class/instance/converting/asString.st
A ScriptLoader30.package/ScriptLoader.class/instance/pharo - 
scripts/script255.st
A ScriptLoader30.package/ScriptLoader.class/instance/pharo - 
updates/update30600.st
M 
ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  30600
12248 Add Job classcurrent to know the current (running) job
https://pharo.fogbugz.com/f/cases/12248

12238 ProtocolOrganizer allProtocols vs protocols are inconsistent
https://pharo.fogbugz.com/f/cases/12238

12246 package tree does not search packages by key pressing
https://pharo.fogbugz.com/f/cases/12246

http://files.pharo.org/image/30/30600.zip





[Pharo-dev] [pharo-project/pharo-core]

2013-11-27 Thread GitHub
  Branch: refs/tags/30600
  Home:   https://github.com/pharo-project/pharo-core



Re: [Pharo-dev] [Review needed] fix for Pharo2 text highlighting incorrect

2013-11-27 Thread Goubier Thierry

That's me

the solution provided doesn't work very well either.

I would need to spend time on the code used to highlight the selection 
and reuse it for highlights, but I was on a tight schedule for a demo so 
I decided to use the selection instead (and gave up for now on 
refactoring that code with something that clearly knows how to bounds a 
subset of the text).


I'll postpone it for now. If 3.0 gets a new text editor, then that code 
will be different.


Thierry

Le 27/11/2013 09:58, Marcus Denker a écrit :

12241 text highlighting incorrect
https://pharo.fogbugz.com/f/cases/12241

What needs to be done?

- does it fix the bug?
- Is the fix plausibly ok?
- Is this a problem in Pharo3, too?
If yes — add issue for back porting,
- make slice for 3




--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95



Re: [Pharo-dev] The Second Coming of Java article

2013-11-27 Thread p...@highoctane.be
Thanks. I've read the all.
Especially when I wanted to get the iPad version running and customized
some things in there and ran into CMake bugs at the time.

Thanks for writing them, they helped!
Phil




On Wed, Nov 27, 2013 at 2:20 AM, Mariano Martinez Peck 
marianop...@gmail.com wrote:




 On Tue, Nov 26, 2013 at 5:49 PM, p...@highoctane.be p...@highoctane.bewrote:

 FWIW, I'd love to have a working Pharo bytecode interpreter that works.
 VMMaker currently doesn't have one it seems (earlier experiments didn't
 worked for me).

 I am very interested with the VM, read the blue book,


 I been writing a lot about that, at least as much as I could.


  understand the primitives,


 http://marianopeck.wordpress.com/tag/primitives/


 can somewhat read bytecode


 http://marianopeck.wordpress.com/tag/bytecodes/


  but what is needed now is the ability to run/debug a VM inside Pharo
 itself.


 Yes, the simulator does not run these days.


 GDB'ing is okay but a pain in the ass to understand what's going on.

 Ok, for debugging the VM with gdb I have:
 http://marianopeck.wordpress.com/tag/gdb/


 Also read the Tour of the OE of Tim Rowledge and Porting the VM etc.

 Also looked at the VMMaker package (Interpreter and Object Memory) +
 Slang.

 Now, getting an working interpreter would help me reach the next step. I
 am not talking about the Stack interpreter, but the plain Interpreter.


 If you want to learn, besides all those mentioned books, you can start
 with http://marianopeck.wordpress.com/2011/03/31/journey-through-the-vm/
 that is a sequence of a lots of posts related to the VM.

 Cheers,



 Any plans?

 Phil

 ---
 Philippe Back
 Dramatic Performance Improvements
  Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027
 Mail:p...@highoctane.be | Web: http://philippeback.eu
 Blog: http://philippeback.be | Twitter: @philippeback
 Youtube: http://www.youtube.com/user/philippeback/videos

 High Octane SPRL
 rue cour Boisacq 101 | 1301 Bierges | Belgium

 Pharo Consortium Member - http://consortium.pharo.org/
 Featured on the Software Process and Measurement Cast -
 http://spamcast.libsyn.com
 Sparx Systems Enterprise Architect and Ability Engineering EADocX Value
 Added Reseller




 On Tue, Nov 26, 2013 at 9:33 PM, Stéphane Ducasse 
 stephane.duca...@inria.fr wrote:


 On Nov 26, 2013, at 1:21 PM, p...@highoctane.be wrote:

 I downloaded ST/X this morning and looked around for a couple hours.

 Impressive system. And impressive clients list/activities etc.
 rant
 And wow, Claus is yet another individual with top notch computer
 chops... Seems that this community has the highest density of high perf
 brains. I feel humbled indeed.
 /rant

 What struck me was the speed.


 15 years of working improving the VM pays off.
 This is why the work of Eliot on Spur are also important. What is also
 important is that more people can work on the VM
 for cleaning it so that we get a documented and good vehicule.
 And this will take time. We are working on a prototype to get forced to
 think about VM and learn. But this prototype will
 not replace Cog in the near future. So we should be happy that cog is
 there and improving.

 Stef

 Pharo really needs a huge speedup on the UI front. I am using a top of
 the line desktop system and still Pharo sometimes feels slow (some is due
 to algorithms - like the finder tool taking ages for a lot of things, but
 some is due to the UI system).

 This is not linked to the VM, as the MVC projects in Squeak are uber
 fast.

 Is the Text rewrite going to have an impact on this?

 On the front of interoperability, I personally have chosen to go the
 RabbitMQ route, it allows me to wire all kinds of things together with some
 room for scale.

 On the Java front itself, in the TCL community, we do have tclbend and
 also a package to do the same thing as STX:LIBJAVA. Truth be told, there
 hasn't been much traction in there. It works fine but that's it.
 http://www2.tcl.tk/1313 - usage sample http://www2.tcl.tk/14919
 It also has fell behind in terms of keeping up with the latest versions
 of the environment.

 In PHP, there is the Quercus and Caucho Resin Server that allows to run
 PHP on top of the JVM and invoke Java from there. Some people run very fast
 stuff on that, and benefiting from all JEE abilities (JMS, JTA, Clustering,
 JAAS...) is really nice.
 http://www.caucho.com/resin-3.1/doc/quercus.xtp


 Phil




 On Tue, Nov 26, 2013 at 12:26 PM, Jan Vrany jan.vr...@fit.cvut.czwrote:

 On 26/11/13 10:40, Serge Stinckwich wrote:

 On Tue, Nov 26, 2013 at 10:54 AM, Jan Vrany jan.vr...@fit.cvut.cz
 wrote:

 On 26/11/13 03:28, askoh wrote:


 Bravo Jan and your collaborators. You have done it.



 Thanks.


 Anything preventing STX:LIBJAVA from being used in production
 environments?



 Good question. STX:LIBJAVA is still a research phase. However, if
 everything
 goes fine, we might have first project using it for real
 in couple months.


 What is important is also the licence. Do 

Re: [Pharo-dev] Roassal Question

2013-11-27 Thread Tudor Girba
I am glad you want to read about Roassal.

My mail was about exposing people that want to get answers to other people
that want to provide those answers. And my suggestion was based on the fact
that in the moose mailing list there are likely more people that can answer
Roassal questions than there are in the Pharo-dev mailing list.

As for PetitParser, there is not engrossment happening. It's the opposite.
The Moose team as a whole takes charge of maintaining PetitParser and makes
it even available as standalone. And I said it before that if you or
someone else wants to put the effort in maintaining packages like
PetitParser, there is no problem of moving it out of the Moose team.

Cheers,
Doru


On Wed, Nov 27, 2013 at 9:11 AM, Norbert Hartl norb...@hartl.name wrote:


 Am 27.11.2013 um 07:06 schrieb Tudor Girba tu...@tudorgirba.com:

 Perhaps it would be more useful to have these types of discussions on the
 moose-dev mailing list. You might be surprised by other things you might
 find there :)

 I disagree with the first sentence. I like to read Roassal stuff here in
 this list. I’m not subscribed in the moose mailing list (trying to reduce
 the mails I get) but I would like to be up to date with Roassal that has
 use case scenarios that exceed the bounds of moose. And I don’t like the
 tension that moose is engrossing standalone packages (like petit parser ;) )

 Norbert

 In case of interest, here are the coordinates:
 http://www.moosetechnology.org/about/contact

 Cheers,
 Doru




 On Tue, Nov 26, 2013 at 8:59 PM, Alexandre Bergel alexandre.ber...@me.com
  wrote:

 Excellent! Let us know for any request for enhancement or bug fixes.

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



 On Nov 26, 2013, at 4:20 PM, GOUBIER Thierry thierry.goub...@cea.fr
 wrote:

  Yes! I also found there is a ROPlatform thing I can query (not sure,
 the code is at work and I'm home).
 
  (I'm coupling a C ast + CFG + parallel task analysis displayed with
 Roassal with interaction with the source code under analysis on a text
 pane. I demoed it this morning to our partner)
 
  Thierry
  
  De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de
 Alexandre Bergel [alexandre.ber...@me.com]
  Date d'envoi : mardi 26 novembre 2013 17:56
  À : Pharo Development List
  Objet : Re: [Pharo-dev] Roassal Question
 
  Does the following helps?
  -=-=-=-=-=-=-=-=-=-=-=-=
  | view  shape morph |
  view := ROView new.
  100 timesRepeat: [
 shape := ROEllipse new size: 40; color: (Color green alpha: 0.5).
 view add: shape element ].
  view elements do: [ :el | el translateTo: 500 atRandom @ 500 atRandom ].
 
 
  morph := ROAthensMorph on: view.
  morph extent: 500 @ 500.
  morph openInWindow
  -=-=-=-=-=-=-=-=-=-=-=-=
 
  If you do not use Athens, then replace “ROAthensMorph” by “ROMorph”
 
  Alexandre
 
  --
  _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
  Alexandre Bergel  http://www.bergel.eu
  ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
 
 
 
  On Nov 26, 2013, at 12:51 PM, Goubier Thierry thierry.goub...@cea.fr
 wrote:
 
  Hi all,
 
  does anybody knows how to integrate a ROView inside a Morphic GUI ?
 
  Regards,
 
  Thierry
  --
  Thierry Goubier
  CEA list
  Laboratoire des Fondations des Systèmes Temps Réel Embarqués
  91191 Gif sur Yvette Cedex
  France
  Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
 
 
 
 





 --
 www.tudorgirba.com

 Every thing has its own flow





-- 
www.tudorgirba.com

Every thing has its own flow


Re: [Pharo-dev] Roassal Question

2013-11-27 Thread kilon alios
Well you can get the best of both worlds and forward the messages to both
lists. But lets say I am happy that I dont have to visit for each of my
questions a diffirent mailing list since all of them are pharo related and
pharo-dev only get a few messages per day on total.

But then I don't like mailing lists or communicating through emails with
multiple people.  I have however registered to Moose mailing list in case
one of my questions is not answered here. But Alaxander has been more than
helpful here so I am sticking around ;)


On Wed, Nov 27, 2013 at 12:34 PM, Tudor Girba tu...@tudorgirba.com wrote:

 I am glad you want to read about Roassal.

 My mail was about exposing people that want to get answers to other people
 that want to provide those answers. And my suggestion was based on the fact
 that in the moose mailing list there are likely more people that can answer
 Roassal questions than there are in the Pharo-dev mailing list.

 As for PetitParser, there is not engrossment happening. It's the opposite.
 The Moose team as a whole takes charge of maintaining PetitParser and makes
 it even available as standalone. And I said it before that if you or
 someone else wants to put the effort in maintaining packages like
 PetitParser, there is no problem of moving it out of the Moose team.

 Cheers,
 Doru


 On Wed, Nov 27, 2013 at 9:11 AM, Norbert Hartl norb...@hartl.name wrote:


 Am 27.11.2013 um 07:06 schrieb Tudor Girba tu...@tudorgirba.com:

 Perhaps it would be more useful to have these types of discussions on the
 moose-dev mailing list. You might be surprised by other things you might
 find there :)

 I disagree with the first sentence. I like to read Roassal stuff here in
 this list. I’m not subscribed in the moose mailing list (trying to reduce
 the mails I get) but I would like to be up to date with Roassal that has
 use case scenarios that exceed the bounds of moose. And I don’t like the
 tension that moose is engrossing standalone packages (like petit parser ;) )

 Norbert

 In case of interest, here are the coordinates:
 http://www.moosetechnology.org/about/contact

 Cheers,
 Doru




 On Tue, Nov 26, 2013 at 8:59 PM, Alexandre Bergel 
 alexandre.ber...@me.com wrote:

 Excellent! Let us know for any request for enhancement or bug fixes.

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



 On Nov 26, 2013, at 4:20 PM, GOUBIER Thierry thierry.goub...@cea.fr
 wrote:

  Yes! I also found there is a ROPlatform thing I can query (not sure,
 the code is at work and I'm home).
 
  (I'm coupling a C ast + CFG + parallel task analysis displayed with
 Roassal with interaction with the source code under analysis on a text
 pane. I demoed it this morning to our partner)
 
  Thierry
  
  De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de
 Alexandre Bergel [alexandre.ber...@me.com]
  Date d'envoi : mardi 26 novembre 2013 17:56
  À : Pharo Development List
  Objet : Re: [Pharo-dev] Roassal Question
 
  Does the following helps?
  -=-=-=-=-=-=-=-=-=-=-=-=
  | view  shape morph |
  view := ROView new.
  100 timesRepeat: [
 shape := ROEllipse new size: 40; color: (Color green alpha:
 0.5).
 view add: shape element ].
  view elements do: [ :el | el translateTo: 500 atRandom @ 500 atRandom
 ].
 
 
  morph := ROAthensMorph on: view.
  morph extent: 500 @ 500.
  morph openInWindow
  -=-=-=-=-=-=-=-=-=-=-=-=
 
  If you do not use Athens, then replace “ROAthensMorph” by “ROMorph”
 
  Alexandre
 
  --
  _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
  Alexandre Bergel  http://www.bergel.eu
  ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
 
 
 
  On Nov 26, 2013, at 12:51 PM, Goubier Thierry thierry.goub...@cea.fr
 wrote:
 
  Hi all,
 
  does anybody knows how to integrate a ROView inside a Morphic GUI ?
 
  Regards,
 
  Thierry
  --
  Thierry Goubier
  CEA list
  Laboratoire des Fondations des Systèmes Temps Réel Embarqués
  91191 Gif sur Yvette Cedex
  France
  Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
 
 
 
 





 --
 www.tudorgirba.com

 Every thing has its own flow





 --
 www.tudorgirba.com

 Every thing has its own flow



Re: [Pharo-dev] ConfigurationOf

2013-11-27 Thread Torsten Bergmann
 In Pharo 3.0 there is a new class ConfigurationOf
 which I can subclass for my configurations.
 
 But then my config is not loadable in Pharo 2.0.
 
 The problem is that when people migrate the configs
 often are adopted for Pharo30 and still work for Pharo20.
 
 So one can use this new shiny common superclass only for new 
 Pharo 3.0 configs onwards or is there a backport planned ...

Also the +Config button in the MetacelloBrowser of Pharo 3.0 does not
use this new ConfigurationOf class. It still generates
code 

   Object subclass: #ConfigurationOfFoo

instead of

   ConfigurationOf subclass: #ConfigurationOfFoo

Bug or by intention?

Bye
T.



Re: [Pharo-dev] ConfigurationOf

2013-11-27 Thread Tudor Girba
Thanks for raising this issue up. Indeed, we should find a solution here.
Does anyone have any thoughts about this?

Doru


On Wed, Nov 27, 2013 at 12:09 PM, Torsten Bergmann asta...@gmx.de wrote:

  In Pharo 3.0 there is a new class ConfigurationOf
  which I can subclass for my configurations.
 
  But then my config is not loadable in Pharo 2.0.
 
  The problem is that when people migrate the configs
  often are adopted for Pharo30 and still work for Pharo20.
 
  So one can use this new shiny common superclass only for new
  Pharo 3.0 configs onwards or is there a backport planned ...

 Also the +Config button in the MetacelloBrowser of Pharo 3.0 does not
 use this new ConfigurationOf class. It still generates
 code

Object subclass: #ConfigurationOfFoo

 instead of

ConfigurationOf subclass: #ConfigurationOfFoo

 Bug or by intention?

 Bye
 T.




-- 
www.tudorgirba.com

Every thing has its own flow


Re: [Pharo-dev] ConfigurationOf

2013-11-27 Thread p...@highoctane.be
Not to be speaking of MetacelloToolBox supporting that.

Does it?

---
Philippe Back
Dramatic Performance Improvements
Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027
Mail:p...@highoctane.be | Web: http://philippeback.eu
Blog: http://philippeback.be | Twitter: @philippeback
Youtube: http://www.youtube.com/user/philippeback/videos

High Octane SPRL
rue cour Boisacq 101 | 1301 Bierges | Belgium

Pharo Consortium Member - http://consortium.pharo.org/
Featured on the Software Process and Measurement Cast -
http://spamcast.libsyn.com
Sparx Systems Enterprise Architect and Ability Engineering EADocX Value
Added Reseller




On Wed, Nov 27, 2013 at 12:05 PM, Torsten Bergmann asta...@gmx.de wrote:

 In Pharo 3.0 there is a new class ConfigurationOf
 which I can subclass for my configurations.

 But then my config is not loadable in Pharo 2.0.

 The problem is that when people migrate the configs
 often are adopted for Pharo30 and still work for Pharo20.

 So one can use this new shiny common superclass only for new
 Pharo 3.0 configs onwards or is there a backport planned ...

 Thx
 T.








Re: [Pharo-dev] ConfigurationOf

2013-11-27 Thread Esteban Lorenzano
it should
we just integrated metacello2, it is not a change of ours, is Dale's... and
Dale is very concerned with backward compatibility, so anything could be
used.
In fact, you can load metacello2 into pharo2... if you want to use a
ConfigurationOf subclass.

Esteban


On Wed, Nov 27, 2013 at 12:41 PM, p...@highoctane.be p...@highoctane.bewrote:

 Not to be speaking of MetacelloToolBox supporting that.

 Does it?

 ---
 Philippe Back
 Dramatic Performance Improvements
 Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027
 Mail:p...@highoctane.be | Web: http://philippeback.eu
 Blog: http://philippeback.be | Twitter: @philippeback
 Youtube: http://www.youtube.com/user/philippeback/videos

 High Octane SPRL
 rue cour Boisacq 101 | 1301 Bierges | Belgium

 Pharo Consortium Member - http://consortium.pharo.org/
 Featured on the Software Process and Measurement Cast -
 http://spamcast.libsyn.com
 Sparx Systems Enterprise Architect and Ability Engineering EADocX Value
 Added Reseller




 On Wed, Nov 27, 2013 at 12:05 PM, Torsten Bergmann asta...@gmx.de wrote:

 In Pharo 3.0 there is a new class ConfigurationOf
 which I can subclass for my configurations.

 But then my config is not loadable in Pharo 2.0.

 The problem is that when people migrate the configs
 often are adopted for Pharo30 and still work for Pharo20.

 So one can use this new shiny common superclass only for new
 Pharo 3.0 configs onwards or is there a backport planned ...

 Thx
 T.









[Pharo-dev] Fwd: [pharo-vm] added explanations on how to build on Windows 64-bit systems. (#5)

2013-11-27 Thread Camillo Bruni


Begin forwarded message:

 From: philippeback notificati...@github.com
 Subject: [pharo-vm] added explanations on how to build on Windows 64-bit 
 systems. (#5)
 Date: 2013-11-26 23:20:51 MEZ
 To: pharo-project/pharo-vm pharo...@noreply.github.com
 Reply-To: pharo-project/pharo-vm 
 reply+i-23352593-bf4ff7842dbedf07ef58e28330c06e5bbf134a37-5640...@reply.github.com
 
 added required changes to _mingw.h to do so
 added libcrtdll.def file in order to create a libcrtdll.a library in order to 
 be able to link.
 
 You can merge this Pull Request by running
 
   git pull https://github.com/philippeback/pharo-vm master
 Or view, comment on, or merge it at:
 
   https://github.com/pharo-project/pharo-vm/pull/5
 
 Commit Summary
 
 added explanations on how to build on Windows 64-bit systems.
 File Changes
 
 M README.md (36)
 A win32support/_mingw.h (338)
 A win32support/libcrtdll.a (0)
 A win32support/libcrtdll.def (695)
 Patch Links:
 
 https://github.com/pharo-project/pharo-vm/pull/5.patch
 https://github.com/pharo-project/pharo-vm/pull/5.diff



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [Pharo-dev] ConfigurationOf

2013-11-27 Thread Torsten Bergmann
Esteban wrote:
it should
we just integrated metacello2, it is not a change of ours, is Dale's... and 
Dale is very concerned with backward compatibility, so anything could be 
used. 

Think of a config like ConfigurationOfPomodoro - I can load it in Pharo 3.0 and 
Pharo2.0
right from the config browser. 

In 3.0 I can make it a subclass of ConfigurationOf because I want to clean it 
up (that was the goal of Dale's new class)

  - but then I can only put it into MetaRepoForPharo30 so it appears in the 
Pharo30 config browser
  - I can NOT put it into MetaRepoForPharo20 for Pharo20 config browser again, 
since it will not load
since there is no such base class in Pharo20

Even a dependency to metacello2 for Pharo20 in the config itself will not help 
here - since the class is 
not loadable due to the missing superclass. Kind of chicken and egg problem...

So how can one use the new ConfigurationOf by subclassing and cleaning and
still work on Pharo20...

In fact, you can load metacello2 into pharo2... if you want to use a 
ConfigurationOf subclass.

Yes - but in a simple load it from the config browser scenario or with the 
usual simple Gofer script
this is not valid. 

Maybe only a backport of ConfigurationOf for Pharo20 will help here. 
Otherwise I doubt it will
get used in Pharo30 backward compatible configs.

Bye
T.








Re: [Pharo-dev] ConfigurationOf

2013-11-27 Thread Esteban Lorenzano
On Wed, Nov 27, 2013 at 1:04 PM, Torsten Bergmann asta...@gmx.de wrote:

 Esteban wrote:
 it should
 we just integrated metacello2, it is not a change of ours, is Dale's...
 and Dale is very concerned with backward compatibility, so anything could
 be used.

 Think of a config like ConfigurationOfPomodoro - I can load it in Pharo
 3.0 and Pharo2.0
 right from the config browser.

 In 3.0 I can make it a subclass of ConfigurationOf because I want to clean
 it up (that was the goal of Dale's new class)

   - but then I can only put it into MetaRepoForPharo30 so it appears in
 the Pharo30 config browser
   - I can NOT put it into MetaRepoForPharo20 for Pharo20 config browser
 again, since it will not load
 since there is no such base class in Pharo20

 Even a dependency to metacello2 for Pharo20 in the config itself will not
 help here - since the class is
 not loadable due to the missing superclass. Kind of chicken and egg
 problem...

 So how can one use the new ConfigurationOf by subclassing and cleaning
 and
 still work on Pharo20...


You need to install M2 into Pharo2. No other solution.
But if you still want the automatic backward compatibility, then you can
still do your configuration like before (is compatible).
Sorry, no magic here.

Esteban



 In fact, you can load metacello2 into pharo2... if you want to use a
 ConfigurationOf subclass.

 Yes - but in a simple load it from the config browser scenario or with
 the usual simple Gofer script
 this is not valid.

 Maybe only a backport of ConfigurationOf for Pharo20 will help here.
 Otherwise I doubt it will
 get used in Pharo30 backward compatible configs.

 Bye
 T.









Re: [Pharo-dev] CI configuration change

2013-11-27 Thread Damien Cassou
On Wed, Nov 27, 2013 at 11:05 AM, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
 Why does configuration change after each build?

 https://www.dropbox.com/s/iciotm799urr0aj/Screenshot%202013-11-27%2011.04.13.png


click the icon to get a diff between 2 edits of the configuration

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

Success is the ability to go from one failure to another without
losing enthusiasm.
Winston Churchill



Re: [Pharo-dev] CI configuration change

2013-11-27 Thread Yuriy Tymchuk
It says that there are no changes. That’s why this is bothering me.

Uko


On 27 Nov 2013, at 13:16, Damien Cassou damien.cas...@gmail.com wrote:

 On Wed, Nov 27, 2013 at 11:05 AM, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
 Why does configuration change after each build?
 
 https://www.dropbox.com/s/iciotm799urr0aj/Screenshot%202013-11-27%2011.04.13.png
 
 
 click the icon to get a diff between 2 edits of the configuration
 
 -- 
 Damien Cassou
 http://damiencassou.seasidehosting.st
 
 Success is the ability to go from one failure to another without
 losing enthusiasm.
 Winston Churchill
 




Re: [Pharo-dev] ConfigurationOf

2013-11-27 Thread Pavel Krivanek
Will we have a special subclass for system configurations (configurations
for the basic Pharo components)?

-- Pavel


2013/11/27 Esteban Lorenzano esteba...@gmail.com




 On Wed, Nov 27, 2013 at 1:04 PM, Torsten Bergmann asta...@gmx.de wrote:

 Esteban wrote:
 it should
 we just integrated metacello2, it is not a change of ours, is Dale's...
 and Dale is very concerned with backward compatibility, so anything could
 be used.

 Think of a config like ConfigurationOfPomodoro - I can load it in Pharo
 3.0 and Pharo2.0
 right from the config browser.

 In 3.0 I can make it a subclass of ConfigurationOf because I want to
 clean it up (that was the goal of Dale's new class)

   - but then I can only put it into MetaRepoForPharo30 so it appears in
 the Pharo30 config browser
   - I can NOT put it into MetaRepoForPharo20 for Pharo20 config browser
 again, since it will not load
 since there is no such base class in Pharo20

 Even a dependency to metacello2 for Pharo20 in the config itself will not
 help here - since the class is
 not loadable due to the missing superclass. Kind of chicken and egg
 problem...

 So how can one use the new ConfigurationOf by subclassing and cleaning
 and
 still work on Pharo20...


 You need to install M2 into Pharo2. No other solution.
 But if you still want the automatic backward compatibility, then you can
 still do your configuration like before (is compatible).
 Sorry, no magic here.

 Esteban



 In fact, you can load metacello2 into pharo2... if you want to use a
 ConfigurationOf subclass.

 Yes - but in a simple load it from the config browser scenario or with
 the usual simple Gofer script
 this is not valid.

 Maybe only a backport of ConfigurationOf for Pharo20 will help here.
 Otherwise I doubt it will
 get used in Pharo30 backward compatible configs.

 Bye
 T.










[Pharo-dev] Nautilus unload...

2013-11-27 Thread Stéphane Ducasse
Hi esteban

I'm looking for a change due to the TreePackage introduction. 
Before I could simply do something like the following to unload Nautilus


Smalltalk tools remove: #browser.
Smalltalk tools register: Browser as: #browser.
(MCWorkingCopy forPackage: (MCPackage named: 'NautilusRefactoring')) 
unload. OK

#Nautilus asClass cleanUp.
KMRepository reset.
KMPragmaKeymapBuilder release.
#NautilusUI asClass allSubInstances do: [ :inst |
SystemAnnouncer uniqueInstance unsubscribe: inst].
Smalltalk garbageCollect.
(MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload.
(MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload.

And now if does not work anymore. I get some TreePackage around.

Apparently I get a weakMessageSend on classRemoved: and this message refers to 
an obsoletePackageTreeNautilus class.

buildGroupManagerFor: anInstance

| holder |
holder := GroupHolder new.
(holder 
addADynamicClassGroupSilentlyNamed: 'Most Viewed Classes' 
block: [ anInstance recentClassesElements ]) removable: false.
(holder
addADynamicClassGroupSilentlyNamed: 'Last Modified Classes'
block: [ self lastModifiedClasses ]) removable: false.

(holder
addADynamicGroupSilentlyNamed: 'Work'
block: [ {} ]) removable: true; isFillable: true.

^ holder


Do you have any idea? A registration mechanism? from which I forgot to 
unregister.

Stef




Re: [Pharo-dev] Nautilus unload...

2013-11-27 Thread Esteban Lorenzano
hi,

I think is nothing to do with PackageTree but with the fact that now groups
are shown (and because of that created),
So, probably reseting the groups before unloading would do the trick.

{Nautilus. PackageTreeNautilus} do: #resetGroups.

Esteban


On Wed, Nov 27, 2013 at 8:05 AM, Stéphane Ducasse stephane.duca...@inria.fr
 wrote:

 Hi esteban

 I'm looking for a change due to the TreePackage introduction.
 Before I could simply do something like the following to unload Nautilus


 Smalltalk tools remove: #browser.
 Smalltalk tools register: Browser as: #browser.
 (MCWorkingCopy forPackage: (MCPackage named:
 'NautilusRefactoring')) unload. OK

 #Nautilus asClass cleanUp.
 KMRepository reset.
 KMPragmaKeymapBuilder release.
 #NautilusUI asClass allSubInstances do: [ :inst |
 SystemAnnouncer uniqueInstance unsubscribe: inst].
 Smalltalk garbageCollect.
 (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon'))
 unload.
 (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload.

 And now if does not work anymore. I get some TreePackage around.

 Apparently I get a weakMessageSend on classRemoved: and this message
 refers to an obsoletePackageTreeNautilus class.

 buildGroupManagerFor: anInstance

 | holder |
 holder := GroupHolder new.
 (holder
 addADynamicClassGroupSilentlyNamed: 'Most Viewed Classes'
 block: [ anInstance recentClassesElements ]) removable:
 false.
 (holder
 addADynamicClassGroupSilentlyNamed: 'Last Modified Classes'
 block: [ self lastModifiedClasses ]) removable: false.

 (holder
 addADynamicGroupSilentlyNamed: 'Work'
 block: [ {} ]) removable: true; isFillable: true.

 ^ holder


 Do you have any idea? A registration mechanism? from which I forgot to
 unregister.

 Stef





Re: [Pharo-dev] Bug font windows

2013-11-27 Thread Tudor Girba
Strange. I did not encounter this until now. What exactly are you doing?

Doru


On Wed, Nov 27, 2013 at 2:22 PM, Stéphane Ducasse stephane.duca...@inria.fr
 wrote:

 Hi guys

 I'm running a workshop using Moose 4.8/4.7 on windows XP with Pharo2.0
 and Moose worked and now it does not. I suspect something related to fonts
 as shown by the stack trace but I could be wrong
 I suspect that the font handle is not released and reinitialized correctly.

 Any ideas?


 Smalltalk stack dump:
   0x1e97d8 I [] in FreeTypeFace(FT2Face)newFaceFromExternalMemory:index:
  0xc2d0e0c: a(n) FreeTypeFace
   0x1e97f4 M BlockClosureon:do:  0xfc85e68: a(n) BlockClosure
   0x1e9820 I FreeTypeFace(FT2Face)newFaceFromExternalMemory:index:
  0xc2d0e0c: a(n) FreeTypeFace
   0x1e984c I FreeTypeFacenewFaceFromExternalMemory:index:  0xc2d0e0c:
 a(n) FreeTypeFace
   0x1e9874 I FreeTypeFacecreate  0xc2d0e0c: a(n) FreeTypeFace
   0x1e9894 I FreeTypeFacevalidate  0xc2d0e0c: a(n) FreeTypeFace
   0x1e98b4 I FreeTypeFontface  0xfc85bd8: a(n) FreeTypeFont
   0x1e98f0 I FreeTypeFontProviderfontFor:familyName:  0x8fc7a0c: a(n)
 FreeTypeFontProvider
   0x1e991c M [] in
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520:
 a(n) LogicalFontManager
   0x1e8f44 M OrderedCollectiondo:  0xc11852c: a(n) OrderedCollection
   0x1e8f70 I [] in
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520:
 a(n) LogicalFontManager
   0x1e8f94 M Array(SequenceableCollection)do:  0xfc84b10: a(n) Array
   0x1e8fbc I
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520:
 a(n) LogicalFontManager
   0x1e8fe4 I LogicalFontManagerbestFontFor:  0xc118520: a(n)
 LogicalFontManager
   0x1e9008 I LogicalFontfindRealFont  0xc1184e0: a(n) LogicalFont
   0x1e9028 I LogicalFontrealFont  0xc1184e0: a(n) LogicalFont
   0x1e9048 I LogicalFontinstallOn:foregroundColor:backgroundColor:
  0xc1184e0: a(n) LogicalFont
   0x1e907c I FormCanvasdrawString:from:to:in:font:color:  0xfc841bc: a(n)
 FormCanvas
   0x1e90b4 I FormCanvas(Canvas)drawString:in:font:color:  0xfc841bc: a(n)
 FormCanvas
   0x1e90e4 M StringMorphdrawOn:  0xf371814: a(n) StringMorph
   0x1e9100 M FormCanvas(Canvas)draw:  0xfc841bc: a(n) FormCanvas
   0x1e911c M FormCanvas(Canvas)drawMorph:  0xfc841bc: a(n) FormCanvas
   0x1e8790 M [] in StringMorph(Morph)fullDrawOn:  0xf371814: a(n)
 StringMorph
   0x1e87a8 M FormCanvasroundCornersOf:in:during:  0xfc841bc: a(n)
 FormCanvas
   0x1e87cc M FormCanvas(Canvas)roundCornersOf:during:  0xfc841bc: a(n)
 FormCanvas
   0x1e87f0 M [] in StringMorph(Morph)fullDrawOn:  0xf371814: a(n)
 StringMorph
   0x1e880c M BlockClosureon:do:  0xfc8448c: a(n) BlockClosure
   0x1e882c M StringMorph(Morph)fullDrawOn:  0xf371814: a(n) StringMorph
   0x1e8848 M FormCanvas(Canvas)fullDraw:  0xfc841bc: a(n) FormCanvas
   0x1e8864 M FormCanvas(Canvas)fullDrawMorph:  0xfc841bc: a(n) FormCanvas
   0x1e8884 M [] in MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e88a4 M Array(SequenceableCollection)reverseDo:  0xf3719ec: a(n)
 Array
   0x1e88c0 M [] in MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e88dc M FormCanvasclipBy:during:  0xfc82780: a(n) FormCanvas
   0x1e8900 M MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e8920 M [] in MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e7fc8 M FormCanvasroundCornersOf:in:during:  0xfc82780: a(n)
 FormCanvas
   0x1e7fec M FormCanvas(Canvas)roundCornersOf:during:  0xfc82780: a(n)
 FormCanvas
   0x1e8010 M [] in MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e802c M BlockClosureon:do:  0xfc839c4: a(n) BlockClosure
   0x1e804c M MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e8068 M FormCanvas(Canvas)fullDraw:  0xfc82780: a(n) FormCanvas
   0x1e8084 M FormCanvas(Canvas)fullDrawMorph:  0xfc82780: a(n) FormCanvas
   0x1e80a4 M [] in MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c:
 a(n) MorphTreeNodeMorph
   0x1e80c4 M Array(SequenceableCollection)reverseDo:  0xf3719f4: a(n)
 Array
   0x1e80e0 M [] in MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c:
 a(n) MorphTreeNodeMorph
   0x1e8100 M MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c: a(n)
 MorphTreeNodeMorph
   0x1e8120 M [] in MorphTreeNodeMorph(Morph)fullDrawOn:  0xf37154c: a(n)
 MorphTreeNodeMorph
   0x1e77e0 M FormCanvasroundCornersOf:in:during:  0xfc82780: a(n)
 FormCanvas
   0x1e7804 M FormCanvas(Canvas)roundCornersOf:during:  0xfc82780: a(n)
 FormCanvas
   0x1e7828 M [] in MorphTreeNodeMorph(Morph)fullDrawOn:  0xf37154c: a(n)
 MorphTreeNodeMorph
   0x1e7844 M BlockClosureon:do:  0xfc82db0: a(n) BlockClosure
   0x1e7864 M MorphTreeNodeMorph(Morph)fullDrawOn:  0xf37154c: a(n)
 MorphTreeNodeMorph
   0x1e7880 M FormCanvas(Canvas)fullDraw:  0xfc82780: a(n) FormCanvas
   0x1e789c M FormCanvas(Canvas)fullDrawMorph:  0xfc82780: a(n) FormCanvas
   0x1e78d4 I [] in MorphTreeTransformMorphdrawSubmorphsOn:  0xf370b90:
 a(n) MorphTreeTransformMorph
   0x1e7910 M FormCanvastransformBy:clippingTo:during:smoothing:
  0xfc7ffc4: a(n) 

[Pharo-dev] [pharo-project/pharo-core] cdfbe9: 30601

2013-11-27 Thread GitHub
  Branch: refs/heads/3.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: cdfbe930586f52ce749c7bbb1501ab0b8dfe43ba
  
https://github.com/pharo-project/pharo-core/commit/cdfbe930586f52ce749c7bbb1501ab0b8dfe43ba
  Author: Jenkins Build Server bo...@pharo-project.org
  Date:   2013-11-27 (Wed, 27 Nov 2013)

  Changed paths:
M Polymorph-Widgets.package/ListDialogWindow.class/instance/instance 
creation/chooseFromOwner_.st
A 
SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating/duplicateClass_withNewName_.st
A 
SUnit-Tests.package/ClassFactoryForTestCaseTest.class/instance/testing/testDuplicateClassWithNewName.st
A ScriptLoader30.package/ScriptLoader.class/instance/pharo - 
scripts/script256.st
A ScriptLoader30.package/ScriptLoader.class/instance/pharo - 
updates/update30601.st
M 
ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  30601
10160 Give a nice way to duplicate classes for test purpose
https://pharo.fogbugz.com/f/cases/10160

12256 ListDialogWindowchooseFromOwner is not well implemented
https://pharo.fogbugz.com/f/cases/12256

http://files.pharo.org/image/30/30601.zip





[Pharo-dev] [pharo-project/pharo-core]

2013-11-27 Thread GitHub
  Branch: refs/tags/30601
  Home:   https://github.com/pharo-project/pharo-core



Re: [Pharo-dev] [Review needed] fix for Pharo2 text highlighting incorrect

2013-11-27 Thread Stéphane Ducasse

 That's me
 
 the solution provided doesn't work very well either.
 
 I would need to spend time on the code used to highlight the selection and 
 reuse it for highlights, but I was on a tight schedule for a demo so I 
 decided to use the selection instead (and gave up for now on refactoring that 
 code with something that clearly knows how to bounds a subset of the text).
 
 I'll postpone it for now. If 3.0 gets a new text editor, then that code will 
 be different.

It will not.
Igor got stuck and he is sick and depressed right now.

Stef


Re: [Pharo-dev] about miniimage

2013-11-27 Thread Stéphane Ducasse
would be great.
I'm doing boring admin right now and I was trying to understand why I get a 
problem unload Nautilus.

Stef

On Nov 27, 2013, at 1:46 PM, Pavel Krivanek pavel.kriva...@gmail.com wrote:

 
 
 
 2013/11/26 Stéphane Ducasse stephane.duca...@inria.fr
 
 On Nov 26, 2013, at 3:27 PM, Pavel Krivanek pavel.kriva...@gmail.com wrote:
 
 Hi Stef,
 
 I started to play with this way of shrinking (see the attachment). At least 
 it's really faster than to use MC :-)
 
 Sure :)
 Do you have a ci job to produce an image systematically?
 
 I will setup something...
 
 -- Pavel
  
 
 Where are the configurations you are creating?
 
 I started with
a new configuration for RB
   I want
   Nautilus
   Zinc, 
   Keymapping
   Gofer
   Fuel
   Morphic
   …
 
 
 
 Cheers,
 -- Pavel
 
 
 2013/11/25 Stéphane Ducasse stephane.duca...@inria.fr
 
 On Nov 25, 2013, at 7:11 AM, Pavel Krivanek pavel.kriva...@gmail.com wrote:
 
  Hi Stef,
 
  our starting point looks like this:
  - we have a method how to produce small image without network etc.
  - we are able to load network, Monticello and Gofer in it (this job is 
  currently broken)
  - we are able to load Metacello too - this should be the basic stage for 
  normal users
 
 I would love to be able to grab an image up to the previous stage. Like that 
 I can continue to work on the configurations regeneration project I have
 
  - than we are a le to load rest od the system at once
  - we have several configurations that we are able to load and unload.
 
  Our biggest problem is the huge nonmodular step between Metacello image 
  and full Pharo. I think we shoud move forward using division. To define 
  how an image without development tools should look like and create two big 
  configurations for them. Then continue with the next splitting.
 
 Yes
 
 
  From the practical point of view, it's always faster to remove. something 
  than to load something.
 Fun since it was difficult for me to unload I thought that I should focus on 
 load :)
 
 
 
  And it's much faster to unload it without Monticello. So I would use ugly 
  removeAllButPackages: because it's fast, then fix the problems like 
  obsolete classes an Undeclared, continue with the pretty unloding part of 
  the configuration and finally loading part will be easy.
 
  -- Pavel
 
  24. 11. 2013 v 22:36, Stéphane Ducasse stephane.duca...@inria.fr:
 
  Hi pavel
 
  may be I should start from your miniimage and start to making sure that 
  the configurations can load then in a second step
  I can make sure that they can unload.
 
  What do you think?
 
  Stef
 
 
 
 
 shrink.st
 
 



[Pharo-dev] When I published the ConfigurationOfBitmapCharacterSet-StephaneDucasse.4

2013-11-27 Thread Stéphane Ducasse
Hi guys

When I published the ConfigurationOfBitmapCharacterSet-StephaneDucasse.4 it got 
fully empty
and this worries me. Not only because I lost what I did but because I have no 
idea why.

Stef


Re: [Pharo-dev] Nautilus unload...

2013-11-27 Thread Pavel Krivanek
Do you do that on an image where Nautilus was not opened? I remove Nautilus
using this script without errors.


deletePackages := [:packageNames |
  SystemNavigation default removeAllButPackages: ((MCWorkingCopy
allManagers collect: #packageName) asSortedCollection copyWithoutAll:
packageNames).
  packageNames do: [:pn |
  (ScriptLoader new workingCopyFromPackageName: pn) unregister.
  (RPackage named: pn) unregister]].

Nautilus cleanUp.
NautilusUI allInstances do: [ :inst |
 SystemAnnouncer uniqueInstance unsubscribe: inst].
Smalltalk garbageCollect.

deletePackages value: #('NautilusRefactoring' 'NautilusCommon' 'Nautilus'
   'Refactoring-Critics'  'Refactoring-Changes' 'Refactoring-Core'
   'Refactoring-Environment' 'GroupManager' 'Manifest-Core'
'Manifest-CriticBrowser').
listUnimplemented value: #Nautilus.

KMRepository reset.
KMPragmaKeymapBuilder release.
Smalltalk resetTools.
5 timesRepeat:[Smalltalk garbageCollect.].
Smalltalk fixObsoleteReferences.

SystemNavigation default obsoleteClasses.
Undeclared.


-- Pavel



2013/11/27 Stéphane Ducasse stephane.duca...@inria.fr

 Hi esteban

 I'm looking for a change due to the TreePackage introduction.
 Before I could simply do something like the following to unload Nautilus


 Smalltalk tools remove: #browser.
 Smalltalk tools register: Browser as: #browser.
 (MCWorkingCopy forPackage: (MCPackage named:
 'NautilusRefactoring')) unload. OK

 #Nautilus asClass cleanUp.
 KMRepository reset.
 KMPragmaKeymapBuilder release.
 #NautilusUI asClass allSubInstances do: [ :inst |
 SystemAnnouncer uniqueInstance unsubscribe: inst].
 Smalltalk garbageCollect.
 (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon'))
 unload.
 (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload.

 And now if does not work anymore. I get some TreePackage around.

 Apparently I get a weakMessageSend on classRemoved: and this message
 refers to an obsoletePackageTreeNautilus class.

 buildGroupManagerFor: anInstance

 | holder |
 holder := GroupHolder new.
 (holder
 addADynamicClassGroupSilentlyNamed: 'Most Viewed Classes'
 block: [ anInstance recentClassesElements ]) removable:
 false.
 (holder
 addADynamicClassGroupSilentlyNamed: 'Last Modified Classes'
 block: [ self lastModifiedClasses ]) removable: false.

 (holder
 addADynamicGroupSilentlyNamed: 'Work'
 block: [ {} ]) removable: true; isFillable: true.

 ^ holder


 Do you have any idea? A registration mechanism? from which I forgot to
 unregister.

 Stef





Re: [Pharo-dev] Bug font windows

2013-11-27 Thread Tudor Girba
That is what I wanted to ask: How you built the image. Ok. I will try to
open a Pharo image built on Mac on a Windows machine and see what happens.

Cheers,
Doru


On Wed, Nov 27, 2013 at 9:11 PM, Stéphane Ducasse stephane.duca...@inria.fr
 wrote:


 On Nov 27, 2013, at 4:44 PM, Tudor Girba tu...@tudorgirba.com wrote:

 Strange. I did not encounter this until now. What exactly are you doing?


 Students of a workshop used a moose image worked perfect.
 Then today the images where not working at all. They could not reopen them
 and I suspect
 a problem with the fonts. For example I do not know on windows how the
 fonts are resolved if the image
 is built on mac.

 Stef




 Doru


 On Wed, Nov 27, 2013 at 2:22 PM, Stéphane Ducasse 
 stephane.duca...@inria.fr wrote:

 Hi guys

 I'm running a workshop using Moose 4.8/4.7 on windows XP with Pharo2.0
 and Moose worked and now it does not. I suspect something related to fonts
 as shown by the stack trace but I could be wrong
 I suspect that the font handle is not released and reinitialized
 correctly.

 Any ideas?


 Smalltalk stack dump:
   0x1e97d8 I [] in FreeTypeFace(FT2Face)newFaceFromExternalMemory:index:
  0xc2d0e0c: a(n) FreeTypeFace
   0x1e97f4 M BlockClosureon:do:  0xfc85e68: a(n) BlockClosure
   0x1e9820 I FreeTypeFace(FT2Face)newFaceFromExternalMemory:index:
  0xc2d0e0c: a(n) FreeTypeFace
   0x1e984c I FreeTypeFacenewFaceFromExternalMemory:index:  0xc2d0e0c:
 a(n) FreeTypeFace
   0x1e9874 I FreeTypeFacecreate  0xc2d0e0c: a(n) FreeTypeFace
   0x1e9894 I FreeTypeFacevalidate  0xc2d0e0c: a(n) FreeTypeFace
   0x1e98b4 I FreeTypeFontface  0xfc85bd8: a(n) FreeTypeFont
   0x1e98f0 I FreeTypeFontProviderfontFor:familyName:  0x8fc7a0c: a(n)
 FreeTypeFontProvider
   0x1e991c M [] in
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520:
 a(n) LogicalFontManager
   0x1e8f44 M OrderedCollectiondo:  0xc11852c: a(n) OrderedCollection
   0x1e8f70 I [] in
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520:
 a(n) LogicalFontManager
   0x1e8f94 M Array(SequenceableCollection)do:  0xfc84b10: a(n) Array
   0x1e8fbc I
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520:
 a(n) LogicalFontManager
   0x1e8fe4 I LogicalFontManagerbestFontFor:  0xc118520: a(n)
 LogicalFontManager
   0x1e9008 I LogicalFontfindRealFont  0xc1184e0: a(n) LogicalFont
   0x1e9028 I LogicalFontrealFont  0xc1184e0: a(n) LogicalFont
   0x1e9048 I LogicalFontinstallOn:foregroundColor:backgroundColor:
  0xc1184e0: a(n) LogicalFont
   0x1e907c I FormCanvasdrawString:from:to:in:font:color:  0xfc841bc:
 a(n) FormCanvas
   0x1e90b4 I FormCanvas(Canvas)drawString:in:font:color:  0xfc841bc:
 a(n) FormCanvas
   0x1e90e4 M StringMorphdrawOn:  0xf371814: a(n) StringMorph
   0x1e9100 M FormCanvas(Canvas)draw:  0xfc841bc: a(n) FormCanvas
   0x1e911c M FormCanvas(Canvas)drawMorph:  0xfc841bc: a(n) FormCanvas
   0x1e8790 M [] in StringMorph(Morph)fullDrawOn:  0xf371814: a(n)
 StringMorph
   0x1e87a8 M FormCanvasroundCornersOf:in:during:  0xfc841bc: a(n)
 FormCanvas
   0x1e87cc M FormCanvas(Canvas)roundCornersOf:during:  0xfc841bc: a(n)
 FormCanvas
   0x1e87f0 M [] in StringMorph(Morph)fullDrawOn:  0xf371814: a(n)
 StringMorph
   0x1e880c M BlockClosureon:do:  0xfc8448c: a(n) BlockClosure
   0x1e882c M StringMorph(Morph)fullDrawOn:  0xf371814: a(n) StringMorph
   0x1e8848 M FormCanvas(Canvas)fullDraw:  0xfc841bc: a(n) FormCanvas
   0x1e8864 M FormCanvas(Canvas)fullDrawMorph:  0xfc841bc: a(n) FormCanvas
   0x1e8884 M [] in MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e88a4 M Array(SequenceableCollection)reverseDo:  0xf3719ec: a(n)
 Array
   0x1e88c0 M [] in MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e88dc M FormCanvasclipBy:during:  0xfc82780: a(n) FormCanvas
   0x1e8900 M MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e8920 M [] in MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e7fc8 M FormCanvasroundCornersOf:in:during:  0xfc82780: a(n)
 FormCanvas
   0x1e7fec M FormCanvas(Canvas)roundCornersOf:during:  0xfc82780: a(n)
 FormCanvas
   0x1e8010 M [] in MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e802c M BlockClosureon:do:  0xfc839c4: a(n) BlockClosure
   0x1e804c M MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e8068 M FormCanvas(Canvas)fullDraw:  0xfc82780: a(n) FormCanvas
   0x1e8084 M FormCanvas(Canvas)fullDrawMorph:  0xfc82780: a(n) FormCanvas
   0x1e80a4 M [] in MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c:
 a(n) MorphTreeNodeMorph
   0x1e80c4 M Array(SequenceableCollection)reverseDo:  0xf3719f4: a(n)
 Array
   0x1e80e0 M [] in MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c:
 a(n) MorphTreeNodeMorph
   0x1e8100 M MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c: a(n)
 MorphTreeNodeMorph
   0x1e8120 M [] in MorphTreeNodeMorph(Morph)fullDrawOn:  0xf37154c: a(n)
 MorphTreeNodeMorph
   0x1e77e0 M FormCanvasroundCornersOf:in:during:  0xfc82780: a(n)
 FormCanvas
   0x1e7804 M FormCanvas(Canvas)roundCornersOf:during: 

Re: [Pharo-dev] Bug font windows

2013-11-27 Thread Stéphane Ducasse

On Nov 27, 2013, at 9:16 PM, Tudor Girba tu...@tudorgirba.com wrote:

 That is what I wanted to ask: How you built the image. Ok. I will try to open 
 a Pharo image built on Mac on a Windows machine and see what happens.

I gave to the guys a image of moose with the lucene case study loaded and it 
opened well the first time.
After saving on windows (often they use moose from their USB) then we could not 
reopen it.

Stef

 
 Cheers,
 Doru
 
 
 On Wed, Nov 27, 2013 at 9:11 PM, Stéphane Ducasse stephane.duca...@inria.fr 
 wrote:
 
 On Nov 27, 2013, at 4:44 PM, Tudor Girba tu...@tudorgirba.com wrote:
 
 Strange. I did not encounter this until now. What exactly are you doing?
 
 Students of a workshop used a moose image worked perfect.
 Then today the images where not working at all. They could not reopen them 
 and I suspect
 a problem with the fonts. For example I do not know on windows how the fonts 
 are resolved if the image 
 is built on mac. 
 
 Stef
 
 
 
 
 Doru
 
 
 On Wed, Nov 27, 2013 at 2:22 PM, Stéphane Ducasse 
 stephane.duca...@inria.fr wrote:
 Hi guys
 
 I'm running a workshop using Moose 4.8/4.7 on windows XP with Pharo2.0
 and Moose worked and now it does not. I suspect something related to fonts
 as shown by the stack trace but I could be wrong
 I suspect that the font handle is not released and reinitialized correctly.
 
 Any ideas?
 
 
 Smalltalk stack dump:
   0x1e97d8 I [] in FreeTypeFace(FT2Face)newFaceFromExternalMemory:index:  
 0xc2d0e0c: a(n) FreeTypeFace
   0x1e97f4 M BlockClosureon:do:  0xfc85e68: a(n) BlockClosure
   0x1e9820 I FreeTypeFace(FT2Face)newFaceFromExternalMemory:index:  
 0xc2d0e0c: a(n) FreeTypeFace
   0x1e984c I FreeTypeFacenewFaceFromExternalMemory:index:  0xc2d0e0c: a(n) 
 FreeTypeFace
   0x1e9874 I FreeTypeFacecreate  0xc2d0e0c: a(n) FreeTypeFace
   0x1e9894 I FreeTypeFacevalidate  0xc2d0e0c: a(n) FreeTypeFace
   0x1e98b4 I FreeTypeFontface  0xfc85bd8: a(n) FreeTypeFont
   0x1e98f0 I FreeTypeFontProviderfontFor:familyName:  0x8fc7a0c: a(n) 
 FreeTypeFontProvider
   0x1e991c M [] in 
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520: 
 a(n) LogicalFontManager
   0x1e8f44 M OrderedCollectiondo:  0xc11852c: a(n) OrderedCollection
   0x1e8f70 I [] in 
 LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll:  0xc118520: 
 a(n) LogicalFontManager
   0x1e8f94 M Array(SequenceableCollection)do:  0xfc84b10: a(n) Array
   0x1e8fbc I LogicalFontManagerbestFontFor:whenFindingAlternativeIgnoreAll: 
  0xc118520: a(n) LogicalFontManager
   0x1e8fe4 I LogicalFontManagerbestFontFor:  0xc118520: a(n) 
 LogicalFontManager
   0x1e9008 I LogicalFontfindRealFont  0xc1184e0: a(n) LogicalFont
   0x1e9028 I LogicalFontrealFont  0xc1184e0: a(n) LogicalFont
   0x1e9048 I LogicalFontinstallOn:foregroundColor:backgroundColor:  
 0xc1184e0: a(n) LogicalFont
   0x1e907c I FormCanvasdrawString:from:to:in:font:color:  0xfc841bc: a(n) 
 FormCanvas
   0x1e90b4 I FormCanvas(Canvas)drawString:in:font:color:  0xfc841bc: a(n) 
 FormCanvas
   0x1e90e4 M StringMorphdrawOn:  0xf371814: a(n) StringMorph
   0x1e9100 M FormCanvas(Canvas)draw:  0xfc841bc: a(n) FormCanvas
   0x1e911c M FormCanvas(Canvas)drawMorph:  0xfc841bc: a(n) FormCanvas
   0x1e8790 M [] in StringMorph(Morph)fullDrawOn:  0xf371814: a(n) 
 StringMorph
   0x1e87a8 M FormCanvasroundCornersOf:in:during:  0xfc841bc: a(n) FormCanvas
   0x1e87cc M FormCanvas(Canvas)roundCornersOf:during:  0xfc841bc: a(n) 
 FormCanvas
   0x1e87f0 M [] in StringMorph(Morph)fullDrawOn:  0xf371814: a(n) 
 StringMorph
   0x1e880c M BlockClosureon:do:  0xfc8448c: a(n) BlockClosure
   0x1e882c M StringMorph(Morph)fullDrawOn:  0xf371814: a(n) StringMorph
   0x1e8848 M FormCanvas(Canvas)fullDraw:  0xfc841bc: a(n) FormCanvas
   0x1e8864 M FormCanvas(Canvas)fullDrawMorph:  0xfc841bc: a(n) FormCanvas
   0x1e8884 M [] in MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e88a4 M Array(SequenceableCollection)reverseDo:  0xf3719ec: a(n) Array
   0x1e88c0 M [] in MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e88dc M FormCanvasclipBy:during:  0xfc82780: a(n) FormCanvas
   0x1e8900 M MorphdrawSubmorphsOn:  0xf371928: a(n) Morph
   0x1e8920 M [] in MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e7fc8 M FormCanvasroundCornersOf:in:during:  0xfc82780: a(n) FormCanvas
   0x1e7fec M FormCanvas(Canvas)roundCornersOf:during:  0xfc82780: a(n) 
 FormCanvas
   0x1e8010 M [] in MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e802c M BlockClosureon:do:  0xfc839c4: a(n) BlockClosure
   0x1e804c M MorphfullDrawOn:  0xf371928: a(n) Morph
   0x1e8068 M FormCanvas(Canvas)fullDraw:  0xfc82780: a(n) FormCanvas
   0x1e8084 M FormCanvas(Canvas)fullDrawMorph:  0xfc82780: a(n) FormCanvas
   0x1e80a4 M [] in MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c: 
 a(n) MorphTreeNodeMorph
   0x1e80c4 M Array(SequenceableCollection)reverseDo:  0xf3719f4: a(n) Array
   0x1e80e0 M [] in MorphTreeNodeMorph(Morph)drawSubmorphsOn:  0xf37154c: 
 a(n) MorphTreeNodeMorph
   

Re: [Pharo-dev] New configuration for XMLWriter!

2013-11-27 Thread Tudor Girba
Hi,

The problem was that configuration of xml writer was referring to the old
repository. Stephan and Diego fixed it in the meantime.

Doru


On Mon, Nov 25, 2013 at 8:38 PM, Stéphane Ducasse stephane.duca...@inria.fr
 wrote:

 I published the package. It was probably in my package cache.
 Let me know if this is working.


 On Nov 25, 2013, at 10:41 AM, Tudor Girba tu...@tudorgirba.com wrote:

 Hi Stef,

 ConfigurationOfXMLWriter does not work. The moose build fails because
 XML-Writer-Core-monty.5 does not seem to exist:

 FAILED-XML-Writer-Core-monty.5 [31mCould not resolve: XML-Writer-Core
 [XML-Writer-Core-monty.5] in /builds/workspace/moose-5.0/package-cache
 http://smalltalkhub.com/mc/Pharo/XMLWriter/main/

 I did not have time to look into the problem. Could you take a look?

 Doru



 On Sun, Nov 24, 2013 at 6:29 PM, Stéphane Ducasse 
 stephane.duca...@inria.fr wrote:

 Hi guys

 I created a new configuration based on the work on monty for the
 XMLWriter. Please test and let us know.
 In PharoExtras/XMLWriter and available via the configurationBrowser.

 Thanks Monty

 Stef
 Working on the new configurationOfXMLParser….




 --
 www.tudorgirba.com

 Every thing has its own flow





-- 
www.tudorgirba.com

Every thing has its own flow


Re: [Pharo-dev] Nautilus unload...

2013-11-27 Thread Pavel Krivanek
2013/11/28 Hernán Morales Durand hernan.mora...@gmail.com

 Hi Pavel,

 El 27/11/2013 16:57, Pavel Krivanek escribió:

  Do you do that on an image where Nautilus was not opened? I remove
 Nautilus using this script without errors.


 deletePackages := [:packageNames |
SystemNavigation default removeAllButPackages: ((MCWorkingCopy
 allManagers collect: #packageName) asSortedCollection copyWithoutAll:
 packageNames).
packageNames do: [:pn |
(ScriptLoader new workingCopyFromPackageName: pn) unregister.
(RPackage named: pn) unregister]].

 Nautilus cleanUp.
 NautilusUI allInstances do: [ :inst |
   SystemAnnouncer uniqueInstance unsubscribe: inst].
 Smalltalk garbageCollect.

 deletePackages value: #('NautilusRefactoring' 'NautilusCommon' 'Nautilus'
 'Refactoring-Critics'  'Refactoring-Changes' 'Refactoring-Core'
 'Refactoring-Environment' 'GroupManager' 'Manifest-Core'
 'Manifest-CriticBrowser').
 listUnimplemented value: #Nautilus.


 Do you mean?

 (Undeclared at: #listUnimplemented put: #Nautilus).

 instead of

 listUnimplemented value: #Nautilus.


No, sorry, it's a part of a bigger script for this Jenkins job:
https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKernel3.0-FromTopShrink/

-- Pavel




  KMRepository reset.
 KMPragmaKeymapBuilder release.
 Smalltalk resetTools.
 5 timesRepeat:[Smalltalk garbageCollect.].
 Smalltalk fixObsoleteReferences.

 SystemNavigation default obsoleteClasses.
 Undeclared.


 -- Pavel



 2013/11/27 Stéphane Ducasse stephane.duca...@inria.fr
 mailto:stephane.duca...@inria.fr


 Hi esteban

 I'm looking for a change due to the TreePackage introduction.
 Before I could simply do something like the following to unload
 Nautilus


  Smalltalk tools remove: #browser.
  Smalltalk tools register: Browser as: #browser.
  (MCWorkingCopy forPackage: (MCPackage named:
 'NautilusRefactoring')) unload. OK

  #Nautilus asClass cleanUp.
  KMRepository reset.
  KMPragmaKeymapBuilder release.
  #NautilusUI asClass allSubInstances do: [ :inst |
  SystemAnnouncer uniqueInstance unsubscribe: inst].
  Smalltalk garbageCollect.
  (MCWorkingCopy forPackage: (MCPackage named:
 'NautilusCommon')) unload.
  (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus'))
 unload.

 And now if does not work anymore. I get some TreePackage around.

 Apparently I get a weakMessageSend on classRemoved: and this message
 refers to an obsoletePackageTreeNautilus class.

 buildGroupManagerFor: anInstance

  | holder |
  holder := GroupHolder new.
  (holder
  addADynamicClassGroupSilentlyNamed: 'Most Viewed
 Classes'
  block: [ anInstance recentClassesElements ])
 removable: false.
  (holder
  addADynamicClassGroupSilentlyNamed: 'Last Modified
 Classes'
  block: [ self lastModifiedClasses ]) removable:
 false.

  (holder
  addADynamicGroupSilentlyNamed: 'Work'
  block: [ {} ]) removable: true; isFillable: true.

  ^ holder


 Do you have any idea? A registration mechanism? from which I forgot
 to unregister.

 Stef