[Pharo-dev] How to include Moose-Finder in build
Hi I want to use the Moose UI tools for development and since I have a CI job for the project I thought I could just load Moose and be done with it. That doesn’t seem to work however. I tried loading #development but when I do that I get the FallbackMenu instead of the world menu and no new inspectors / browsers. Here are the conditions of my build: - I want to start my build from a fresh Pharo3 image - I only want the Moose UI tools (I don’t need any of the parsers etc.) - it would be nice if, when I open a built image, the default tools are already set to the Moose ones I know that there is a development Moose build for Pharo3, so I’m a bit surprised that I can’t just load the configuration… BTW: this is how I tried to load Moose (maybe I just screwed up the configuration): baseline02: spec version: '0.2-baseline' spec for: #common do: [ spec blessing: #baseline. spec package: 'LibGit2Bindings' with: [ spec repository: 'http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ]. spec project: 'Moose' with: [ spec className: 'ConfigurationOfMoose'; file: 'ConfigurationOfMoose'; version: #development; loads: #(Core UI); repository: 'http://smalltalkhub.com/mc/Moose/Moose/main' ]. spec package: 'Phexample' with: [ spec repository: 'http://smalltalkhub.com/mc/Phexample/Phexample/main' ]. spec repository: 'http://smalltalkhub.com/mc/StefanMarr/LibGit/main'. spec package: 'LibGit-Core' with: [ spec requires: #(Phexample LibGit2Bindings Moose); postLoadDoIt: #postLoadRecompile ] ]. I’d appreciate any help (and if nobody helps me Doru will probably kick my ass for still not using Moose :p) Cheers, Max
Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31
### Here's what I've been up to since the last WhatsUp: - reported a couple bugs for Pharo 3.0 - got one commercial deal signed with Pharo as the underlying technology - learning Roassal ### What's next, until 2014-03-31 (*): - another deal coming - proposal in the intertubes Phil
[Pharo-dev] #checkSourcesFileAvailability: gone?
Hello, In 3.0, I don't see it anymore. Found nothing in the forum either. Thanks Hilaire -- Dr. Geo http://drgeo.eu
[Pharo-dev] FileSystem-Git status update 2
- I moved all the code to the FileSystemGitDev team on Smalltalkhub - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) - we got simple fetch working yesterday (yay!) - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) Today’s program: - migrate more tests - fix initialization and setup issues - try to perform a complete fetch + merge (without conflicts) - implement clone - try to get push working Have a great day! Cheers, Max
Re: [Pharo-dev] FileSystem-Git status update 2
Good to see this progress! Thanks for your effort. Uko On 19 Mar 2014, at 08:46, Max Leske maxle...@gmail.com wrote: - I moved all the code to the FileSystemGitDev team on Smalltalkhub - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) - we got simple fetch working yesterday (yay!) - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) Today’s program: - migrate more tests - fix initialization and setup issues - try to perform a complete fetch + merge (without conflicts) - implement clone - try to get push working Have a great day! Cheers, Max
Re: [Pharo-dev] How to include Moose-Finder in build
Hi Max,
I am happy you want to give these tools a try :).
The tools do not install themselves automatically because I think it is not
a good practice to tie code loading with installation. To setup the Moose
image, we actually have a command line handler that allows you to simply
trigger this from the CI job:
./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL
You can also trigger from the image:
MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments
withArguments: {})
This installs the theme, the fonts, preferences and the GToolkit
playground, inspector and debugger.
However, for developing in Pharo, you do not need all of Moose, and almost
certainly do not need the Moose Finder. You likely only need the GToolkit.
spec project: 'GToolkit' with: [
spec
className: 'ConfigurationOfGToolkit';
version: #development;
file: 'ConfigurationOfGToolkit';
repository: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ].
To install the tools, you have to install them manually at the moment - but
I will create a command line handler for that soon:
GTPlayground registerToolsOn: Smalltalk tools.
GTInspector registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools.
GTPPDebugger registerToolsOn: Smalltalk tools. only if you need it for
PetitParser
GTGlamourDebugger registerToolsOn: Smalltalk tools.
ACGlamourDebugger registerToolsOn: Smalltalk tools.
GTSUnitDebugger registerToolsOn: Smalltalk tools.
GTMoldableDebugger enableDebuggerWindowDistinctColor: true
To install the white theme:
GLMWhitespaceTheme defaultSettings: nil; setPreferredWorldBackground;
beCurrent
To install the fonts, you can just do this:
#('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular'
'SourceSansProBold') do: [ :each |
Smalltalk globals
at: each asSymbol
ifAbsent: [
Gofer new
smalltalkhubUser: 'girba' project: 'FreeFonts';
package: each;
load ].
(Smalltalk at: each asSymbol) new install ].
FreeTypeSystemSettings loadFt2Library: true.
FreeTypeFontProvider current updateFromSystem
Let me know how it goes.
Cheers,
Doru
On Wed, Mar 19, 2014 at 8:24 AM, Max Leske maxle...@gmail.com wrote:
Hi
I want to use the Moose UI tools for development and since I have a CI job
for the project I thought I could just load Moose and be done with it. That
doesn't seem to work however.
I tried loading #development but when I do that I get the FallbackMenu
instead of the world menu and no new inspectors / browsers. Here are the
conditions of my build:
- I want to start my build from a fresh Pharo3 image
- I only want the Moose UI tools (I don't need any of the parsers etc.)
- it would be nice if, when I open a built image, the default tools are
already set to the Moose ones
I know that there is a development Moose build for Pharo3, so I'm a bit
surprised that I can't just load the configuration...
BTW: this is how I tried to load Moose (maybe I just screwed up the
configuration):
baseline02: spec
version: '0.2-baseline'
spec for: #common do: [
spec blessing: #baseline.
spec package: 'LibGit2Bindings' with: [
spec repository: '
http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ].
spec project: 'Moose' with: [
spec
className: 'ConfigurationOfMoose';
file: 'ConfigurationOfMoose';
version: #development;
loads: #(Core UI);
repository: '
http://smalltalkhub.com/mc/Moose/Moose/main' ].
spec package: 'Phexample' with: [
spec repository: '
http://smalltalkhub.com/mc/Phexample/Phexample/main' ].
spec repository: '
http://smalltalkhub.com/mc/StefanMarr/LibGit/main'.
spec package: 'LibGit-Core' with: [
spec
requires: #(Phexample LibGit2Bindings
Moose);
postLoadDoIt: #postLoadRecompile ]
].
I'd appreciate any help (and if nobody helps me Doru will probably kick my
ass for still not using Moose :p)
Cheers,
Max
--
www.tudorgirba.com
Every thing has its own flow
[Pharo-dev] SmalltalkHub troubles
Hi I'm having trouble committing to SmalltalkHub and I don't know where to go for support. When trying to commit to Seaside31 I get the following error: HTTP/1.1 403 Forbidden Date: Tue, 18 Mar 2014 20:16:45 GMT Content-Length: 512 Vary: Accept-Encoding Server: Zinc HTTP Components 1.0 Connection: close Content-Type: text/plain Unknown token type I double checked and my username and password are correct. Cheers Philippe
Re: [Pharo-dev] Removing tools
Hi Pavel, dont know if this is a good idea but why not: - put this into a ConfigurationOfNoTools with a spec postLoadDoIt: #postloadToShrinkWithLoader:package:. - put the script into a #postloadToShrinkWithLoader:package - store the project on STHub - create a CI job for loading the Config This way one can: - browse the changes to the script in Monticello as it progresses - have the CI built the image automagically - the final image can be downloaded from CI or using Pharo launcher easily If some simply unit tests will be applied (like checking for Undeclared, etc) one can control if the image will get/be/stay red or green. Bye T. Gesendet:Dienstag, 18. Mrz 2014 um 23:00 Uhr Von:Pavel Krivanek pavel.kriva...@gmail.com An:Discusses Development of Pharo pharo-dev@lists.pharo.org Betreff:[Pharo-dev] Removing tools Hi, this is an initial attempt to produce an image without development tools. Currently it leaves Workspace and Transcript in the image, has no obsolete classes and six Undeclared. The image size is still quite big, 16.1 MB. Tested on #30798. Do not forget to share your improvements ;-) Cheers, -- Pavel
Re: [Pharo-dev] Removing tools
Hi Torsten, we plan to do that in Pharo/SystemConfigurations(/Unreloader). That mail was something like a late night backup of very experimental stuff :-) Cheers, -- Pavel 2014-03-19 9:08 GMT+01:00 Torsten Bergmann asta...@gmx.de: Hi Pavel, dont know if this is a good idea but why not: - put this into a ConfigurationOfNoTools with a spec postLoadDoIt: #postloadToShrinkWithLoader:package:. - put the script into a #postloadToShrinkWithLoader:package - store the project on STHub - create a CI job for loading the Config This way one can: - browse the changes to the script in Monticello as it progresses - have the CI built the image automagically - the final image can be downloaded from CI or using Pharo launcher easily If some simply unit tests will be applied (like checking for Undeclared, etc) one can control if the image will get/be/stay red or green. Bye T. *Gesendet:* Dienstag, 18. März 2014 um 23:00 Uhr *Von:* Pavel Krivanek pavel.kriva...@gmail.com *An:* Discusses Development of Pharo pharo-dev@lists.pharo.org *Betreff:* [Pharo-dev] Removing tools Hi, this is an initial attempt to produce an image without development tools. Currently it leaves Workspace and Transcript in the image, has no obsolete classes and six Undeclared. The image size is still quite big, 16.1 MB. Tested on #30798. Do not forget to share your improvements ;-) Cheers, -- Pavel
Re: [Pharo-dev] FileSystem-Git status update 2
Le 19/03/2014 08:46, Max Leske a écrit : - I moved all the code to the FileSystemGitDev team on Smalltalkhub - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) - we got simple fetch working yesterday (yay!) - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) Today’s program: - migrate more tests - fix initialization and setup issues - try to perform a complete fetch + merge (without conflicts) - implement clone - try to get push working Have a great day! With such news, it is a great day :) Thanks for the effort, 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
Re: [Pharo-dev] FileSystem-Git status update 2
+1 On 19 Mar 2014, at 08:53, Yuriy Tymchuk yuriy.tymc...@me.com wrote: Good to see this progress! Thanks for your effort. Uko On 19 Mar 2014, at 08:46, Max Leske maxle...@gmail.com wrote: - I moved all the code to the FileSystemGitDev team on Smalltalkhub - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) - we got simple fetch working yesterday (yay!) - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) Today’s program: - migrate more tests - fix initialization and setup issues - try to perform a complete fetch + merge (without conflicts) - implement clone - try to get push working Have a great day! Cheers, Max
Re: [Pharo-dev] Just found, i can compile this:
Le 18 mars 2014 à 19:50, Eliot Miranda a écrit : On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey christophe.dema...@inria.fr wrote: Why arguments should be read only? They are just temporary variables with an initial value. Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow debugging. The assignment to block arguments is a side-effect of the old BlockContext implementation of blocks where block arguments were mapped onto temporary variables of the home context. It is an anachronism and should be forbidden also. Thank you for the explanation. I'm just curious why it is so difficult to implement a debugger if arguments are assignable? If you need to restart the execution of a method, and so you need to get the initial value of the argument, I understand you cannot find the value anymore in the method context but it is available in the caller context, no? As I never implemented a debugger, I cannot figure out the difficulties. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] SmalltalkHub troubles
Hi Philippe, Can you send me the mcz privately so I can take a look? Cheers, Nico -- Nicolas Petton http://nicolas-petton.fr
[Pharo-dev] Pharo3 release delayed!
Ladies and gentlemen, For achieving a great 3.0 release we still have some tasks that we still need to prepare. They are not many, but we (Pharo Board) think it deserves some more effort: 1) Technically, there are still some minor bugs to tackle around RPackage and Nautilus. We do not miss much and that could be done in a couple of days work (in fact, I'm working on them and trying to have it before going to Argentina next week), but in order to be sure, we better wait a bit :). It would be great to see more eyeballs focused on these issues. 2) We want to create a real marketing strategy this time, and that requires preparation time. Marketing strategy sounds probably really bombastic, but in our case it means to create pages, send mails, construct the progress log, etc. We we need some time to prepare it properly. So... Pharo3 release date has been moved to April 22. Cheers, Esteban
Re: [Pharo-dev] Image's size in pillar
Thank you. Best regards On Mar 17, 2014, at 9:08 AM, Damien Cassou damien.cas...@gmail.com wrote: Hi Natalia, On Sun, Mar 16, 2014 at 2:23 PM, Natalia Tymchuk natalia.tymc...@unikernel.net wrote: but with changing the value width I didn't get changes of my images sizes. How can I make my images take half of the page's width? I fixed this a month ago in the development version of Pillar but didn't release a stable version yet. -- 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] Pharo as a NT service
The Squeak VM had such a feature and it was/is widely used. For instance with Squeak it was/is easily able to install a Swiki as an NT Service and just run. There is a command line option -service: serviceName as you can see here: http://wiki.squeak.org/squeak/105 Pharo VM should have this too - I guess from Phillips post the code is still there. It registers the VM on the SCM (Service control manager) of Windows. Easily service registration would be really useful if provided out of the box especially for people who want to write web applications and deploy to Windows servers as one can run headless, control the service easily from the services panel or manage even clusters. Maybe it is broken, maybe related to the also broken headless support in Windows, also the stdio support of Pharo was never really finished (therefore we have a file stdout on Windows which is far from optimal) rant Even if it is not the best operating system: in IT reality Windows is still widely used as business platform. Currently Pharo does not really honor this these days - but should to get more business opportunities if it will (hopefully) provide better Window support in the future. /rant Bye T. Gesendet: Montag, 17. März 2014 um 19:12 Uhr Von: Esteban A. Maringolo emaring...@gmail.com An: Pharo Development List pharo-dev@lists.pharo.org Betreff: Re: [Pharo-dev] Pharo as a NT service To implement a 100% native service the executable must support certain functions. Which I don't think Pharo VM does. However you could use srvany.exe to run any executable file as a service (http://support.microsoft.com/kb/137890). Regards! Esteban A. Maringolo 2014-03-17 14:58 GMT-03:00 p...@highoctane.be p...@highoctane.be: I need to be able to run a Pharo VM+image as a service. I saw that in the Windows VM there are such flags. But I do not know how to make that work (or if it still works). Anyone knowing? Phil
Re: [Pharo-dev] FileSystem-Git status update 2
+1.. Keep going :) Doru On Wed, Mar 19, 2014 at 9:43 AM, Goubier Thierry thierry.goub...@cea.frwrote: Le 19/03/2014 08:46, Max Leske a écrit : - I moved all the code to the FileSystemGitDev team on Smalltalkhub - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) - we got simple fetch working yesterday (yay!) - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) Today's program: - migrate more tests - fix initialization and setup issues - try to perform a complete fetch + merge (without conflicts) - implement clone - try to get push working Have a great day! With such news, it is a great day :) Thanks for the effort, 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
Re: [Pharo-dev] How to include Moose-Finder in build
Thanks Doru.
Looks much better now. Unfortunately my image is now unusable because there’s
no memory left (even after saving and restarting it. The image with tools
loaded is 450MB).
I retried without the installation code, simply loading GToolkit. The result is
always that I have about 8MB of memory left in the image.
I have to focus my energy on Git at the moment so I’m not going to invest time
to find out what’s wrong. I still want to use GToolkit, so if you (or anybody
else) can help out, that would be great.
Cheers,
Max
On 19.03.2014, at 08:54, Tudor Girba tu...@tudorgirba.com wrote:
Hi Max,
I am happy you want to give these tools a try :).
The tools do not install themselves automatically because I think it is not a
good practice to tie code loading with installation. To setup the Moose
image, we actually have a command line handler that allows you to simply
trigger this from the CI job:
./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL
You can also trigger from the image:
MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments
withArguments: {})
This installs the theme, the fonts, preferences and the GToolkit playground,
inspector and debugger.
However, for developing in Pharo, you do not need all of Moose, and almost
certainly do not need the Moose Finder. You likely only need the GToolkit.
spec project: 'GToolkit' with: [
spec
className: 'ConfigurationOfGToolkit';
version: #development;
file: 'ConfigurationOfGToolkit';
repository:
'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ].
To install the tools, you have to install them manually at the moment - but I
will create a command line handler for that soon:
GTPlayground registerToolsOn: Smalltalk tools.
GTInspector registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools.
GTPPDebugger registerToolsOn: Smalltalk tools. only if you need it
for PetitParser
GTGlamourDebugger registerToolsOn: Smalltalk tools.
ACGlamourDebugger registerToolsOn: Smalltalk tools.
GTSUnitDebugger registerToolsOn: Smalltalk tools.
GTMoldableDebugger enableDebuggerWindowDistinctColor: true
To install the white theme:
GLMWhitespaceTheme
defaultSettings: nil;
setPreferredWorldBackground;
beCurrent
To install the fonts, you can just do this:
#('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular'
'SourceSansProBold') do: [ :each |
Smalltalk globals
at: each asSymbol
ifAbsent: [
Gofer new
smalltalkhubUser: 'girba' project:
'FreeFonts';
package: each;
load ].
(Smalltalk at: each asSymbol) new install ].
FreeTypeSystemSettings loadFt2Library: true.
FreeTypeFontProvider current updateFromSystem
Let me know how it goes.
Cheers,
Doru
On Wed, Mar 19, 2014 at 8:24 AM, Max Leske maxle...@gmail.com wrote:
Hi
I want to use the Moose UI tools for development and since I have a CI job
for the project I thought I could just load Moose and be done with it. That
doesn’t seem to work however.
I tried loading #development but when I do that I get the FallbackMenu
instead of the world menu and no new inspectors / browsers. Here are the
conditions of my build:
- I want to start my build from a fresh Pharo3 image
- I only want the Moose UI tools (I don’t need any of the parsers etc.)
- it would be nice if, when I open a built image, the default tools are
already set to the Moose ones
I know that there is a development Moose build for Pharo3, so I’m a bit
surprised that I can’t just load the configuration…
BTW: this is how I tried to load Moose (maybe I just screwed up the
configuration):
baseline02: spec
version: '0.2-baseline'
spec for: #common do: [
spec blessing: #baseline.
spec package: 'LibGit2Bindings' with: [
spec repository:
'http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ].
spec project: 'Moose' with: [
spec
className: 'ConfigurationOfMoose';
file: 'ConfigurationOfMoose';
version: #development;
loads: #(Core UI);
repository:
'http://smalltalkhub.com/mc/Moose/Moose/main' ].
Re: [Pharo-dev] How to include Moose-Finder in build
Hi,
Something is wrong with your setup or with some collision caused by
something else you are loading. The image should be in the range of 40-50
MB.
Could you give me the exact script you are using?
Cheers,
Doru
On Wed, Mar 19, 2014 at 11:10 AM, Max Leske maxle...@gmail.com wrote:
Thanks Doru.
Looks much better now. Unfortunately my image is now unusable because
there's no memory left (even after saving and restarting it. The image with
tools loaded is 450MB).
I retried without the installation code, simply loading GToolkit. The
result is always that I have about 8MB of memory left in the image.
I have to focus my energy on Git at the moment so I'm not going to invest
time to find out what's wrong. I still want to use GToolkit, so if you (or
anybody else) can help out, that would be great.
Cheers,
Max
On 19.03.2014, at 08:54, Tudor Girba tu...@tudorgirba.com wrote:
Hi Max,
I am happy you want to give these tools a try :).
The tools do not install themselves automatically because I think it is
not a good practice to tie code loading with installation. To setup the
Moose image, we actually have a command line handler that allows you to
simply trigger this from the CI job:
./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL
You can also trigger from the image:
MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments
withArguments: {})
This installs the theme, the fonts, preferences and the GToolkit
playground, inspector and debugger.
However, for developing in Pharo, you do not need all of Moose, and almost
certainly do not need the Moose Finder. You likely only need the GToolkit.
spec project: 'GToolkit' with: [
spec
className: 'ConfigurationOfGToolkit';
version: #development;
file: 'ConfigurationOfGToolkit';
repository: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ].
To install the tools, you have to install them manually at the moment -
but I will create a command line handler for that soon:
GTPlayground registerToolsOn: Smalltalk tools.
GTInspector registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools.
GTPPDebugger registerToolsOn: Smalltalk tools. only if you need it for
PetitParser
GTGlamourDebugger registerToolsOn: Smalltalk tools.
ACGlamourDebugger registerToolsOn: Smalltalk tools.
GTSUnitDebugger registerToolsOn: Smalltalk tools.
GTMoldableDebugger enableDebuggerWindowDistinctColor: true
To install the white theme:
GLMWhitespaceTheme defaultSettings: nil; setPreferredWorldBackground;
beCurrent
To install the fonts, you can just do this:
#('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular'
'SourceSansProBold') do: [ :each |
Smalltalk globals
at: each asSymbol
ifAbsent: [
Gofer new
smalltalkhubUser: 'girba' project: 'FreeFonts';
package: each;
load ].
(Smalltalk at: each asSymbol) new install ].
FreeTypeSystemSettings loadFt2Library: true.
FreeTypeFontProvider current updateFromSystem
Let me know how it goes.
Cheers,
Doru
On Wed, Mar 19, 2014 at 8:24 AM, Max Leske maxle...@gmail.com wrote:
Hi
I want to use the Moose UI tools for development and since I have a CI
job for the project I thought I could just load Moose and be done with it.
That doesn't seem to work however.
I tried loading #development but when I do that I get the FallbackMenu
instead of the world menu and no new inspectors / browsers. Here are the
conditions of my build:
- I want to start my build from a fresh Pharo3 image
- I only want the Moose UI tools (I don't need any of the parsers etc.)
- it would be nice if, when I open a built image, the default tools are
already set to the Moose ones
I know that there is a development Moose build for Pharo3, so I'm a bit
surprised that I can't just load the configuration...
BTW: this is how I tried to load Moose (maybe I just screwed up the
configuration):
baseline02: spec
version: '0.2-baseline'
spec for: #common do: [
spec blessing: #baseline.
spec package: 'LibGit2Bindings' with: [
spec repository: '
http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ].
spec project: 'Moose' with: [
spec
className: 'ConfigurationOfMoose';
file: 'ConfigurationOfMoose';
version: #development;
loads: #(Core UI);
repository: '
http://smalltalkhub.com/mc/Moose/Moose/main' ].
spec package: 'Phexample' with: [
spec repository: '
http://smalltalkhub.com/mc/Phexample/Phexample/main' ].
spec repository: '
http://smalltalkhub.com/mc/StefanMarr/LibGit/main'.
spec package: 'LibGit-Core'
Re: [Pharo-dev] How to include Moose-Finder in build
On 19.03.2014, at 11:16, Tudor Girba tu...@tudorgirba.com wrote:
Hi,
Something is wrong with your setup or with some collision caused by something
else you are loading. The image should be in the range of 40-50 MB.
You’re right. Although I don’t know why, running all of that in a fresh image
works fine. Sorry about that!
Cool! I now have Moose tools :)
Could you give me the exact script you are using?
Cheers,
Doru
On Wed, Mar 19, 2014 at 11:10 AM, Max Leske maxle...@gmail.com wrote:
Thanks Doru.
Looks much better now. Unfortunately my image is now unusable because there’s
no memory left (even after saving and restarting it. The image with tools
loaded is 450MB).
I retried without the installation code, simply loading GToolkit. The result
is always that I have about 8MB of memory left in the image.
I have to focus my energy on Git at the moment so I’m not going to invest
time to find out what’s wrong. I still want to use GToolkit, so if you (or
anybody else) can help out, that would be great.
Cheers,
Max
On 19.03.2014, at 08:54, Tudor Girba tu...@tudorgirba.com wrote:
Hi Max,
I am happy you want to give these tools a try :).
The tools do not install themselves automatically because I think it is not
a good practice to tie code loading with installation. To setup the Moose
image, we actually have a command line handler that allows you to simply
trigger this from the CI job:
./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL
You can also trigger from the image:
MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments
withArguments: {})
This installs the theme, the fonts, preferences and the GToolkit playground,
inspector and debugger.
However, for developing in Pharo, you do not need all of Moose, and almost
certainly do not need the Moose Finder. You likely only need the GToolkit.
spec project: 'GToolkit' with: [
spec
className: 'ConfigurationOfGToolkit';
version: #development;
file: 'ConfigurationOfGToolkit';
repository:
'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ].
To install the tools, you have to install them manually at the moment - but
I will create a command line handler for that soon:
GTPlayground registerToolsOn: Smalltalk tools.
GTInspector registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools.
GTPPDebugger registerToolsOn: Smalltalk tools. only if you need it
for PetitParser
GTGlamourDebugger registerToolsOn: Smalltalk tools.
ACGlamourDebugger registerToolsOn: Smalltalk tools.
GTSUnitDebugger registerToolsOn: Smalltalk tools.
GTMoldableDebugger enableDebuggerWindowDistinctColor: true
To install the white theme:
GLMWhitespaceTheme
defaultSettings: nil;
setPreferredWorldBackground;
beCurrent
To install the fonts, you can just do this:
#('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular'
'SourceSansProBold') do: [ :each |
Smalltalk globals
at: each asSymbol
ifAbsent: [
Gofer new
smalltalkhubUser: 'girba' project:
'FreeFonts';
package: each;
load ].
(Smalltalk at: each asSymbol) new install ].
FreeTypeSystemSettings loadFt2Library: true.
FreeTypeFontProvider current updateFromSystem
Let me know how it goes.
Cheers,
Doru
On Wed, Mar 19, 2014 at 8:24 AM, Max Leske maxle...@gmail.com wrote:
Hi
I want to use the Moose UI tools for development and since I have a CI job
for the project I thought I could just load Moose and be done with it. That
doesn’t seem to work however.
I tried loading #development but when I do that I get the FallbackMenu
instead of the world menu and no new inspectors / browsers. Here are the
conditions of my build:
- I want to start my build from a fresh Pharo3 image
- I only want the Moose UI tools (I don’t need any of the parsers etc.)
- it would be nice if, when I open a built image, the default tools are
already set to the Moose ones
I know that there is a development Moose build for Pharo3, so I’m a bit
surprised that I can’t just load the configuration…
BTW: this is how I tried to load Moose (maybe I just screwed up the
configuration):
baseline02: spec
version: '0.2-baseline'
spec for: #common do: [
spec blessing: #baseline.
spec package: 'LibGit2Bindings' with: [
spec
[Pharo-dev] Font problem is still there
Hi!We have had experience a problem with font when using Athens to display text.Apparently, this is due to some recent version of Athens. We have to load the following packages to not experience the problem:Name: Athens-Core-MarcusDenker.34Author: MarcusDenkerTime: 5 July 2013, 10:59:47.206954 amUUID: e844b2d4-b091-42a4-9be0-17101dcdbd30Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33Name: Athens-Cairo-MarcusDenker.51Author: MarcusDenkerTime: 26 August 2013, 4:03:06.190096 pmUUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881Ancestors: Athens-Cairo-SebastianTleye.50This is a _major_ problem to us and apparently there is no simple solution. These kind of problem may force us to move to seek for an alternative to Athens.Alexandre--_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:Alexandre Bergel http://www.bergel.eu^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-dev] Removing tools
With thoses cleaning ImageCleaner cleanUpForProduction. (MCPackage named: 'HelpSystem-Core') unload. (MCPackage named: 'ProfStef-Core') unload. (MCPackage named: 'ReleaseTests') unload. (MCPackage named: 'SUnit-UITesting') unload. (MCPackage named: 'Versionner-Tests-Core-Commands') unload. (MCPackage named: 'Versionner-Tests-Core-DependenciesModel') unload. (MCPackage named: 'Versionner-Tests-Core-Model') unload. (MCPackage named: 'Versionner-Tests-Resources') unload. (MCPackage named: 'Polymorph-Tools-Diff') unload. (MCPackage named: 'Metacello') unload. (MCPackage named: 'Metacello-FileTree') unload. (MCPackage named: 'Metacello-GitHub') unload. (MCPackage named: 'Metacello-PharoCommonPlatform') unload. (MCPackage named: 'Metacello-Platform.pharo30') unload. (MCPackage named: 'Metacello-Reference') unload. FreeTypeFontProvider unload. ScriptLoader new cleanUpForProduction. StrikeFont cleanUp. The image is just bellow 17MB. Most dev. tools are there, as Nautilus. Hilaire Le 18/03/2014 23:00, Pavel Krivanek a écrit : Hi, this is an initial attempt to produce an image without development tools. Currently it leaves Workspace and Transcript in the image, has no obsolete classes and six Undeclared. The image size is still quite big, 16.1 MB. Tested on #30798. Do not forget to share your improvements ;-) Cheers, -- Pavel -- Dr. Geo http://drgeo.eu
Re: [Pharo-dev] Pharo3 release delayed!
Esteban Lorenzano wrote: Ladies and gentlemen, For achieving a great 3.0 release we still have some tasks that we still need to prepare. They are not many, but we (Pharo Board) think it deserves some more effort: 1) Technically, there are still some minor bugs to tackle around RPackage and Nautilus. We do not miss much and that could be done in a couple of days work (in fact, I'm working on them and trying to have it before going to Argentina next week), but in order to be sure, we better wait a bit :). It would be great to see more eyeballs focused on these issues. 2) We want to create a real marketing strategy this time, and that requires preparation time. "Marketing strategy" sounds probably really bombastic, but in our case it means to create pages, send mails, construct the progress log, etc. We we need some time to prepare it properly. So... Pharo3 release date has been moved toApril 22. Cheers, Esteban I'm glad to hear this. Its good to have a target, but good also to be practical to put that final polish on it. I can understand why it might take a bit to write up the progress log...
Re: [Pharo-dev] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages
On Tue, Mar 18, 2014 at 10:40 PM, Laurent Laffont laurent.laff...@gmail.com wrote: you can now install pharo vm on Arch with: that's brilliant. Thanks. Can I reference your work in http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher ? -- 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] Font problem is still there
On 19 March 2014 13:43, Alexandre Bergel alexandre.ber...@me.com wrote: Hi! We have had experience a problem with font when using Athens to display text. Apparently, this is due to some recent version of Athens. We have to load the following packages to not experience the problem: Name: Athens-Core-MarcusDenker.34 Author: MarcusDenker Time: 5 July 2013, 10:59:47.206954 am UUID: e844b2d4-b091-42a4-9be0-17101dcdbd30 Ancestors: Athens-Core-MarcusDenker.33, Athens-Core-ErwanDouaille.33 Name: Athens-Cairo-MarcusDenker.51 Author: MarcusDenker Time: 26 August 2013, 4:03:06.190096 pm UUID: 9e1bfddb-67f7-4a36-864d-11060b8b6881 Ancestors: Athens-Cairo-SebastianTleye.50 This is a _major_ problem to us and apparently there is no simple solution. These kind of problem may force us to move to seek for an alternative to Athens. there's some kind of caching interference either in cairo or between cairo and freetype, when using identity transformation matrix and integral (integer) font sizes. and there is a simple workaround: canvas pathTransform restoreAfter: [ canvas pathTransform scaleBy: 1.1. draw text here ] this workaround was in font-rendering code, but then i removed it, because i thought problem was solved. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- Best regards, Igor Stasenko. inline: Screen Shot 2014-02-24 at 6.43.10 PM.png
[Pharo-dev] Phratch Website + version 3.0 in dev
Dear all, I am pleased to announce Phratch website: www.phratch.com Thanks to the support of ESUG, it is possible to make visible this wonderful project. For now, what is available on the site: - a presentation of Phratch (you can refer to it now) - installation files, there is a portable version for Windows, Linux, MacOS. - tutorials - block documentation: generated from a Phratch image ! - Some elements for Jetstorm (a lot of new articles will come soon) - a category with news Now about the versions, I am developing the version 3.0 Why this number ? Why a third version in one year of work ? It is clear that a lot of work is already done. Each version represents strong changes in the architecture. - version 1.0 is the port of Scratch + BYOB + Panther in Pharo. It is working but not extendable. - version 2.0 makes Phratch really extendable. We can develop our own block for everything in Pharo. I also make Phratch more modular with the use of Pragmas for some menus, declaration of blocks... It is available only in Pharo 3.0. There are some languages available, I hope more people can translate in other languages (http://www.phratch.com/archives/612). - version 3.0 is the version in development. What is new here: Before this version Phratch was really slow. I am cleaning the code, and now it begins to be fast, really fast ! We also begun to write tests. I am really happy to have the support of ESUG and Pharo. Thanks to the community to make Pharo as usable as it it, it makes our dreams possible. Cheers, -- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/
Re: [Pharo-dev] Pharo3 release delayed!
2014-03-19 5:55 GMT-03:00 Esteban Lorenzano esteba...@gmail.com: Ladies and gentlemen, For achieving a great 3.0 release we still have some tasks that we still need to prepare. They are not many, but we (Pharo Board) think it deserves some more effort: 1) Technically, there are still some minor bugs to tackle around RPackage and Nautilus. We do not miss much and that could be done in a couple of days work (in fact, I'm working on them and trying to have it before going to Argentina next week), but in order to be sure, we better wait a bit :). It would be great to see more eyeballs focused on these issues. 2) We want to create a real marketing strategy this time, and that requires preparation time. Marketing strategy sounds probably really bombastic, but in our case it means to create pages, send mails, construct the progress log, etc. We we need some time to prepare it properly. Please put energy into item #2, and postpone again until it's ready if necessary. :) Those who already use Pharo 3 know the risks of using a beta version, so they can wait until the release version is ready. :) Regards! Esteban A. Maringolo
Re: [Pharo-dev] Image's size in pillar
Hello, I have one more question. I write the subscripts like it is written: @@subscript@@ and in html file it works, but in pdf not. For example: it is written x k + 1instead of x k + 1 .Will this be fixed on pillar side, or what should I do to fix it on my side? Best wishes, Natalia
Re: [Pharo-dev] [Pharo-users] Phratch Website + version 3.0 in dev
2014-03-19 15:34 GMT+01:00 Hilaire Fernandes hilaire.fernan...@gmail.com: Great news! Le 19/03/2014 15:10, jannik laval a écrit : - version 3.0 is the version in development. What is new here: Before this version Phratch was really slow. I am cleaning the code, and now it begins to be fast, really fast ! We also begun to write tests. I am curious. What did you finally find out for speed up? Hum, some crappy things. For example, to manage the z-index of the bubble talk: - a loop to draw all the morph - a second loop that select the buuble (isKindOf: bubble !!!) and draw only the bubble. These two loops are in the same method and called on each step... for a bubble that appears only 1 or 2 times in an application Removing the second loop makes Phratch 2x faster. I am continuing to clean that. I also find the problem with click-event. Now when I click, it works fine ! Cheers, Jannik Hilaire -- Dr. Geo http://drgeo.eu -- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/
Re: [Pharo-dev] Phratch Website + version 3.0 in dev
HI Jannik, Nice, note there is a typo on the page Phrao 2.0 instead of Pharo 2.0. Would also be nice if these were real links to pharo.org Bye T. Gesendet: Mittwoch, 19. März 2014 um 15:10 Uhr Von: jannik laval jannik.la...@gmail.com An: Pharo Development List pharo-dev@lists.pharo.org, ESUG Mailing list esug-l...@lists.esug.org, Any question about pharo is welcome pharo-us...@lists.pharo.org, phra...@googlegroups.com phra...@googlegroups.com Betreff: [Pharo-dev] Phratch Website + version 3.0 in dev Dear all, I am pleased to announce Phratch website: www.phratch.com[http://www.phratch.com] Thanks to the support of ESUG, it is possible to make visible this wonderful project. For now, what is available on the site: - a presentation of Phratch (you can refer to it now) - installation files, there is a portable version for Windows, Linux, MacOS. - tutorials - block documentation: generated from a Phratch image ! - Some elements for Jetstorm (a lot of new articles will come soon) - a category with news Now about the versions, I am developing the version 3.0 Why this number ? Why a third version in one year of work ? It is clear that a lot of work is already done. Each version represents strong changes in the architecture. - version 1.0 is the port of Scratch + BYOB + Panther in Pharo. It is working but not extendable. - version 2.0 makes Phratch really extendable. We can develop our own block for everything in Pharo. I also make Phratch more modular with the use of Pragmas for some menus, declaration of blocks… It is available only in Pharo 3.0. There are some languages available, I hope more people can translate in other languages (http://www.phratch.com/archives/612[http://www.phratch.com/archives/612]). - version 3.0 is the version in development. What is new here: Before this version Phratch was really slow. I am cleaning the code, and now it begins to be fast, really fast ! We also begun to write tests. I am really happy to have the support of ESUG and Pharo. Thanks to the community to make Pharo as usable as it it, it makes our dreams possible. Cheers,-- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu[http://www.jannik-laval.eu] http://car.mines-douai.fr/
Re: [Pharo-dev] Phratch Website + version 3.0 in dev
Thank you Torsten. I changed it. Jannik 2014-03-19 15:42 GMT+01:00 Torsten Bergmann asta...@gmx.de: HI Jannik, Nice, note there is a typo on the page Phrao 2.0 instead of Pharo 2.0. Would also be nice if these were real links to pharo.org Bye T. Gesendet: Mittwoch, 19. März 2014 um 15:10 Uhr Von: jannik laval jannik.la...@gmail.com An: Pharo Development List pharo-dev@lists.pharo.org, ESUG Mailing list esug-l...@lists.esug.org, Any question about pharo is welcome pharo-us...@lists.pharo.org, phra...@googlegroups.com phra...@googlegroups.com Betreff: [Pharo-dev] Phratch Website + version 3.0 in dev Dear all, I am pleased to announce Phratch website: www.phratch.com[ http://www.phratch.com] Thanks to the support of ESUG, it is possible to make visible this wonderful project. For now, what is available on the site: - a presentation of Phratch (you can refer to it now) - installation files, there is a portable version for Windows, Linux, MacOS. - tutorials - block documentation: generated from a Phratch image ! - Some elements for Jetstorm (a lot of new articles will come soon) - a category with news Now about the versions, I am developing the version 3.0 Why this number ? Why a third version in one year of work ? It is clear that a lot of work is already done. Each version represents strong changes in the architecture. - version 1.0 is the port of Scratch + BYOB + Panther in Pharo. It is working but not extendable. - version 2.0 makes Phratch really extendable. We can develop our own block for everything in Pharo. I also make Phratch more modular with the use of Pragmas for some menus, declaration of blocks... It is available only in Pharo 3.0. There are some languages available, I hope more people can translate in other languages ( http://www.phratch.com/archives/612[http://www.phratch.com/archives/612]). - version 3.0 is the version in development. What is new here: Before this version Phratch was really slow. I am cleaning the code, and now it begins to be fast, really fast ! We also begun to write tests. I am really happy to have the support of ESUG and Pharo. Thanks to the community to make Pharo as usable as it it, it makes our dreams possible. Cheers,-- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu[http://www.jannik-laval.eu] http://car.mines-douai.fr/ -- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/
Re: [Pharo-dev] Just found, i can compile this:
Hi Christophe, On Mar 19, 2014, at 1:45 AM, Christophe Demarey christophe.dema...@inria.fr wrote: Le 18 mars 2014 à 19:50, Eliot Miranda a écrit : On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey christophe.dema...@inria.fr wrote: Why arguments should be read only? They are just temporary variables with an initial value. Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow debugging. The assignment to block arguments is a side-effect of the old BlockContext implementation of blocks where block arguments were mapped onto temporary variables of the home context. It is an anachronism and should be forbidden also. Thank you for the explanation. I'm just curious why it is so difficult to implement a debugger if arguments are assignable? If you need to restart the execution of a method, and so you need to get the initial value of the argument, I understand you cannot find the value anymore in the method context but it is available in the caller context, no? As I never implemented a debugger, I cannot figure out the difficulties. the args are no longer available; they get moved from the caller context to the callee. If you think about stack frames then what happens is that the slots containing the outgoing arguments are used as the slots for the incoming arguments. So if arguments are assigned to they are indeed lost. But look at how many methods in the system (or in any system). The proportion of methods/functions/procedures that could be written to assign their arguments is very small so the Smalltalk trade off is a good one. Eliot (phone)
[Pharo-dev] XBRL parser/processor?
Hi Smalltalkers, Sorry for the cross posting. I wonder if anyway is aware of a Smalltalk parser/processor of XBRL (http://xbrl.sec.gov/) ? I know it's XML but it seems some extra work/features are needed besides a XML parser to fully support XBRL data extraction. Thanks in advance, -- Mariano http://marianopeck.wordpress.com
[Pharo-dev] Phratch on Ubuntu
Dear Community, Thanks to Damien Cassou, Phratch can now be installed on Ubuntu using apt-get. If you are an Ubuntu user on 12.10, 13.10 or 14.04, you can very easily install Phratch. You have to add the Pharo PPA (ppa:pharo/stable) and install Phratch by issuing these commands: $ sudo add-apt-repository ppa:pharo/stable $ sudo apt-get update $ sudo apt-get install phratch Then just run $ phratch Thank you again Damien ! -- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/
Re: [Pharo-dev] EyeTreeInspector - Simple Mode?
+1 Fancy that adds unpracticality is a no no no if you care about productivity And sorry but in this case, having the class there isn’t even fancy (is consistent but in a nonsensical way) We already gave this feedback On Mar 19, 2014, at 1:20 PM, p...@highoctane.be wrote: Is there a way to get the EyeTreeInspector in Pharo3 to only display instance variables and globals and not the whole set of things that are of no interest when developing business style applications? Or put the instance vars first. I'll dig in there for my own use but for newcomers, that's a real PITA I guess. Maybe a filter icon or something would come helpful (or a SimpleEyeTreeInspector option in the drop down) Phil EYE19-03-14 17-17-58.png
Re: [Pharo-dev] EyeTreeInspector - Simple Mode?
Ah, looks like I was looking at something returning the class and not a proper object, so, of course, there are lots of things. Phil On Wed, Mar 19, 2014 at 5:20 PM, p...@highoctane.be p...@highoctane.bewrote: Is there a way to get the EyeTreeInspector in Pharo3 to only display instance variables and globals and not the whole set of things that are of no interest when developing business style applications? Or put the instance vars first. I'll dig in there for my own use but for newcomers, that's a real PITA I guess. Maybe a filter icon or something would come helpful (or a SimpleEyeTreeInspector option in the drop down) Phil
Re: [Pharo-dev] [Pharo-users] Tiling Window Manager in 3.0: working but still issues with WorldMorph
Would you mind putting the configuration in the 3.0 Metarepo? Phil On Wed, Mar 12, 2014 at 6:52 PM, Laurent Laffont laurent.laff...@gmail.comwrote: Hi Phil, with latest ConfigurationOfTilingWindow manager World management (almost) works. Still a little display issue when creating a new world (need to change back and forth, seems to be some World repaint issue). I've also merged some experiments with GrowlMorph. Laurent Le mardi 11 mars 2014, 13:27:57 Laurent Laffont a écrit : Thanks a lot Phil. I will try to have a look. Laurent Le samedi 8 mars 2014, 11:57:30 p...@highoctane.be a écrit : TWM works in 3.0 after some work on icons and updating menus. Gofer new smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; configuration; load. ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: '3.0') load You can also use ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: #development) load but this will for sure change over time. There is the World management icon which is still there and it looks like it can create worlds but switching between them just breaks havoc. Maybe should we just remove that feature from TWM as 3.0 doesn't seem to be multiworld friendly. Nothing done on tests nor themeing (which appears to be not that working well in 3.0 either due to theming changes); At least the thing is back :-) [I missed it...] Phil
Re: [Pharo-dev] EyeTreeInspector - Simple Mode?
Guys,If you want to discuss these aspects, please make sure you use the very latest image. Right now, exploring an OrderedCollection looks like this:Various aspects were simplified recently. And pretty soon, it will also open on the first level.SvenOn 19 Mar 2014, at 18:00, Sebastian Sastre sebast...@flowingconcept.com wrote:yeah… but watch this:#(a b c) asOrderedCollectionScreen Shot 2014-03-19 at 1.54.23 PM.pngand then…arrow key down, then arrow key right and you getScreen Shot 2014-03-19 at 1.54.38 PM.pngwe can do better than thatOn Mar 19, 2014, at 1:42 PM,p...@highoctane.bewrote:Ah, looks like I was looking at something returning the class and not a proper object, so, ofcourse, there are lots of things.PhilOn Wed, Mar 19, 2014 at 5:20 PM,p...@highoctane.bep...@highoctane.bewrote:Is there a way to get the EyeTreeInspector in Pharo3 to only display instance variables andglobals and not the whole set of things that are of no interest when developing businessstyle applications?Or put the instance vars first.I'll dig in there for my own use but for newcomers, that's a real PITA I guess.Maybe a filter icon or something would come helpful (or a SimpleEyeTreeInspector option inthe drop down)Phil
Re: [Pharo-dev] EyeTreeInspector - Simple Mode?
But there is something weird in there still. the card1,2,3,4 things are not on the class side in any way and still do show there. Weird. Maybe these were the temporaries. In any case, it is weird. Phil On Wed, Mar 19, 2014 at 5:42 PM, p...@highoctane.be p...@highoctane.bewrote: Ah, looks like I was looking at something returning the class and not a proper object, so, of course, there are lots of things. Phil On Wed, Mar 19, 2014 at 5:20 PM, p...@highoctane.be p...@highoctane.bewrote: Is there a way to get the EyeTreeInspector in Pharo3 to only display instance variables and globals and not the whole set of things that are of no interest when developing business style applications? Or put the instance vars first. I'll dig in there for my own use but for newcomers, that's a real PITA I guess. Maybe a filter icon or something would come helpful (or a SimpleEyeTreeInspector option in the drop down) Phil
Re: [Pharo-dev] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages
Le mercredi 19 mars 2014, 15:05:56 Damien Cassou a écrit : On Tue, Mar 18, 2014 at 10:40 PM, Laurent Laffont laurent.laff...@gmail.com wrote: you can now install pharo vm on Arch with: that's brilliant. Thanks. Can I reference your work in http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher ? Sure ! Laurent
[Pharo-dev] Class vars and inst vars of a class
Can anybody tell me what is the difference between the class variable on the instance side” definition and instance variable on the “class side” definition? Thanks in advance. Uko
Re: [Pharo-dev] Class vars and inst vars of a class
A class variable is shared between all the subclasses. A class side instance variable is like instance variable, a slot at class side: every subclass (class side) will have its own slot. 2014-03-19 23:26 GMT+01:00 Yuriy Tymchuk yuriy.tymc...@me.com: Can anybody tell me what is the difference between the class variable on the instance side definition and instance variable on the class side definition? Thanks in advance. Uko
Re: [Pharo-dev] Class vars and inst vars of a class
Yuriy Tymchuk wrote: Can anybody tell me what is the difference between the class variable on the instance side” definition and instance variable on the “class side” definition? Thanks in advance. Uko instance-variable: A variable that holds the private state of an object. In Smalltalk these can only be accessed by instance-methods. class-variable: An attribute of a class that is shared by that class, its subclasses, and all instances of those classes. Can be accessed by both instance-methods and class-methods. class-instance-variable: An attribute of a class that is not shared outside that specific class. Only the definition is inherited by subclasses, not the value . Each subclass has its own private value. Accessible only by class-methods. You will understand it best by experimenting. Here is one I made for myself... ivCounter - instance variable counter CVCounter - class variable counter CIVCounter - class instance variable counter -- Object subclass: #TestCounter instanceVariableNames: 'ivCounter iName' classVariableNames: 'CVCounter' poolDictionaries: '' category: 'MyExamples' TestCounter class accessed by clicking the Class button instanceVariableNames: 'CIVCounter' TestCounter subclass: #TestSubCounter instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'MyExamples' -- TestCountername: myInstanceName iName := myInstanceName. TestCounter next ivCounter ifNil: [ ivCounter := 0 ]. CVCounter ifNil: [ CVCounter := 0 ]. ivCounter := ivCounter + 1. CVCounter := CVCounter + 1. TestCounter printOn: aStream super printOn: aStream. aStream nextPutAll: ' ['. aStream print: iName. aStream nextPutAll: '] ( '. aStream nextPutAll: ' ivCounter='; print: ivCounter. aStream nextPutAll: ', CIVCounter=n/a'. aStream nextPutAll: ', CVCounter='; print: CVCounter. aStream nextPutAll: ' )'. -- TestCounter class next2 CIVCounter ifNil: [ CIVCounter := 0 ]. CVCounter ifNil: [ CVCounter := 0 ]. CIVCounter := CIVCounter + 1. CVCounter := CVCounter + 1. TestCounter class printOn: aStream super printOn: aStream. aStream nextPutAll: ' ( '. aStream nextPutAll: 'ivCounter=n/a'. aStream nextPutAll: ', CIVCounter='; print: CIVCounter. aStream nextPutAll: ', CVCounter='; print: CVCounter. aStream nextPutAll: ' )'. TestCounter class reset CVCounter := nil. CIVCounter := nil. - Then from Workspace evaluate these... tc1 := TestCounter new. tc2 := TestCounter new. tsc1 := TestSubCounter new. tsc2 := TestSubCounter new. TestCounter reset. TestSubCounter reset. tc1 next. tc2 next. tc1 next. tc2 next. tsc1 next. tsc2 next. tsc1 next. tsc2 next. TestCounter next2. TestCounter next2. TestCounter next2. TestSubCounter next2. TestSubCounter next2. TestSubCounter next2. cheers -ben
[Pharo-dev] An attempt to use interactive tools detected, while in non-interactive mode
Hi there, my Pharo 3.0 staging builds started to fail today and this seems to be involved. Tomorrow I’ll investigate more so pointers will be appreciated muchly what is this really about? and why the headless load isn’t ignoring the warning? Loading 1.5 of ConfigurationOfMongoTalk... Project: Grease stable [1.1.6] Fetched - Grease-Core-JohanBrichau.86 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ Fetched - Grease-Pharo30-Core-JohanBrichau.13 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ Fetched - Grease-Tests-Core-JohanBrichau.95 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ Fetched - Grease-Tests-Pharo20-Core-JohanBrichau.9 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ Fetched - Grease-Slime-JohanBrichau.25 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ Fetched - Mongo-Squeak-EstebanLorenzano.13 --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ Fetched - Mongo-BSON-EstebanLorenzano.31 --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ Fetched - Mongo-Core-DamienCassou.35 --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ Fetched - MongoQueries-NicolasPetton.6 --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ --- http://smalltalkhub.com/mc/francois/MongoTalk/main/ Loaded - Grease-Core-JohanBrichau.86 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- cache'Errors in script loaded from /var/lib/jenkins/workspace/stagingFlowingWorker/FlowingWorkerBuilder.st' [31mAn attempt to use interactive tools detected, while in non-interactive mode Interactive Request: You are about to load new versions of the following packages that have unsaved changes in the image: Grease-Pharo30-Core If you continue, you will lose these changes: [0mNonInteractiveUIManagernonInteractiveWarning: NonInteractiveUIManagernonInteractiveRequest:title: NonInteractiveUIManagernonInteractiveRequest: NonInteractiveUIManagerconfirm:trueChoice:falseChoice:cancelChoice:default: MCMergeOrLoadWarningdefaultAction UndefinedObjecthandleSignal: MethodContext(ContextPart)handleSignal: MethodContext(ContextPart)handleSignal: MethodContext(ContextPart)handleSignal: MCMergeOrLoadWarning(Exception)signal MCMergeOrLoadWarning classsignalFor: MCVersionLoaderwarnAboutLosingChangesTo:ifCancel:ifMerge: MCVersionLoadercheckForModificationsIfCancel:ifMerge: MCVersionLoaderloadWithNameLike: MCVersionLoaderload in Block: [ ... BlockClosureensure:
