You can download the lastest 1.4 here for testing:
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo-1.4.zip
And a first version of the one-click here:
https://ci.lille.inria.fr/pharo/job/Pharo%20One%20Click%20image/lastSucces
Looks like the script manager gone from the world menu.
As is the script manager.
Normal?
2012/3/30 Marcus Denker
>
>
> You can download the lastest 1.4 here for testing:
>
>
> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo-1.4.zip
>
> And a
The browser is looking weird.
Which one is it? No OB package view anymore?
2012/3/30 Marcus Denker
>
>
> You can download the lastest 1.4 here for testing:
>
>
> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo-1.4.zip
>
> And a first version of
I am trying the one-click and it works fine.
It took me a while to understand where the images are saved:
pharo-1.4.app/Contents/Resources
That wouldn't very intuitive for newcomers -- I'd expect the images to be
saved in the Documents folder.
I know... we are all short of time.
- Francisco
On
On Mar 30, 2012, at 10:23 AM, Francisco Garau wrote:
> I am trying the one-click and it works fine.
>
> It took me a while to understand where the images are saved:
> pharo-1.4.app/Contents/Resources
>
> That wouldn't very intuitive for newcomers -- I'd expect the images to be
> saved in the
On Fri, Mar 30, 2012 at 9:53 AM, p...@highoctane.be wrote:
> Looks like the script manager gone from the world menu.
> As is the script manager.
>
> Normal?
>
Hmm, script manager was removed from the build long ago :). (like from
pharo 1.3)
Try using the ConfigurationOfScriptManager from Metacel
On Fri, Mar 30, 2012 at 10:15 AM, p...@highoctane.be wrote:
> The browser is looking weird.
> Which one is it? No OB package view anymore?
>
It is the default System Browser, no OB. You can donwload OB by yourself
using the ConfigurationOfOmniBrowser from MetacelloRepository.
Ask if you need he
It is in my 1.3 OneClick.
It is useful to me :-)
2012/3/30 Guillermo Polito
>
>
> On Fri, Mar 30, 2012 at 9:53 AM, p...@highoctane.be wrote:
>
>> Looks like the script manager gone from the world menu.
>> As is the script manager.
>>
>> Normal?
>>
>
> Hmm, script manager was removed from the bu
No, no problem. Just that my 1.3 OneClick defaulted to OB.
OB is way better for working with code when compared to the default thing.
What should I look for? Nautilus? OB? All this looks like a tad confusing.
2012/3/30 Guillermo Polito
>
>
> On Fri, Mar 30, 2012 at 10:15 AM, p...@highoctane.be
For OB, there is an stable version published with the metacello
configuration. But it is not receiving a constant manteinance.
For Nautilus, you will also find an stable metacello configuration, and
currently there is work on it to enhance it and make it work in the current
pharo images.
On Fri,
The Moose build is green on the latest Pharo 1.4.
Cheers,
Doru
On Fri, Mar 30, 2012 at 11:10 AM, Guillermo Polito
wrote:
> For OB, there is an stable version published with the metacello
> configuration. But it is not receiving a constant manteinance.
>
> For Nautilus, you will also find an sta
I am not sure of the plans for syntax highlighting in version 1.4 but when I go
to Settings for Shout: Syntax Highlighting I am not given any controls to
adjust the values. When I change try to make the changes programmatically (as
in 1.3) I am given the error AnObsoleteSHStyleSetting. Is this
Trying the soon to be released 3.0.7:
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfSeaside30';
load.
(ConfigurationOfSeaside30 project version: '3.0.7') load: 'OneClick'.
I see the following issues during loading:
RBAddMethodChange>>printOn: (RBPlatf
On Mar 30, 2012, at 4:19 PM, Nick Ager wrote:
> Trying the soon to be released 3.0.7:
>
> Gofer new
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfSeaside30';
> load.
>
> (ConfigurationOfSeaside30 project version: '3.0.7') load: 'OneClick'.
>
> I see the fo
On Mar 30, 2012, at 4:09 PM, Scott Gibson wrote:
> I am not sure of the plans for syntax highlighting in version 1.4 but when I
> go to Settings for Shout: Syntax Highlighting I am not given any controls to
> adjust the values. When I change try to make the changes programmatically
> (as in 1
Guillermo Polito wrote
>
> For OB, there is an stable version published with the metacello
> configuration. But it is not receiving a constant manteinance.
>
That's good news. Where can i find it?
--
View this message in context:
http://forum.world.st/Pharo-1-4-Please-test-tp4518277p4519342
You can try
Gofer it
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfOmniBrowser';
load.
And then
(ConfigurationOfOmniBrowser project version: #stable) load: #( 'Core Tests'
'OCompletion Tests' ) , #( 'Core' 'OB-SUnitIntegration' 'OB-Shout'
'OCForOB').
or maybe
(ConfigurationOfOm
Hi, I just tried the one-click in windows and it doesn't open the
pharo-1.4.image by default, which is inconvenient since a newcomer wouldn't
know where to look for. I also see a .bat file that does the right thing,
but that's now what windows users usually do.
So I think the CogVM.exe should be re
On Mar 30, 2012, at 4:08 PM, Scott Gibson wrote:
> I am not sure of the plans for syntax highlighting in version 1.4 but when I
> go to Settings for Shout: Syntax Highlighting I am not given any controls to
> adjust the values. When I change try to make the changes programmatically
> (as in 1
On Mar 30, 2012, at 9:01 PM, Ricardo Moran wrote:
> Hi, I just tried the one-click in windows and it doesn't open the
> pharo-1.4.image by default, which is inconvenient since a newcomer wouldn't
> know where to look for. I also see a .bat file that does the right thing, but
> that's now what
+1
On Mar 30, 2012, at 4:32 PM, Marcus Denker wrote:
>
> On Mar 30, 2012, at 4:09 PM, Scott Gibson wrote:
>
>> I am not sure of the plans for syntax highlighting in version 1.4 but when I
>> go to Settings for Shout: Syntax Highlighting I am not given any controls to
>> adjust the values. Wh
On Mar 30, 2012, at 3:50 PM, Stéphane Ducasse wrote:
>
> On Mar 30, 2012, at 4:08 PM, Scott Gibson wrote:
>
>> I am not sure of the plans for syntax highlighting in version 1.4 but when I
>> go to Settings for Shout: Syntax Highlighting I am not given any controls to
>> adjust the values. Wh
BTW, here are two things to care about:
- Shout is not loaded in the image by default (maybe that's the reason for
the non appearing settings).
You can try loading Shout by yourself using the metacello configuration.
- the Obsolete thingy is obviously a bug :).
Guille
On Mon, Apr 2, 2012 at 3:3
On Apr 2, 2012, at 3:38 PM, Guillermo Polito wrote:
> BTW, here are two things to care about:
>
> - Shout is not loaded in the image by default (maybe that's the reason for
> the non appearing settings).
> You can try loading Shout by yourself using the metacello configuration.
>
No, Shout is
Hi,
ProfStef and TWM load successfully, all tests green.
Laurent
On Fri, Mar 30, 2012 at 9:26 AM, Marcus Denker wrote:
>
>
> You can download the lastest 1.4 here for testing:
>
>
> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo-1.4.zip
>
> A
Strange, an install of DrGeo then clean up, make this:
(1 to: 1000) do: [:i |] displayingProgress: 'hello'
with a remnant SystemProgressMoprh on the display.
Was not occurring with previous version 1.3.
I don't override anything there.
Also clean up is not as good as before, cleaned image i
On Apr 4, 2012, at 5:23 PM, Hilaire Fernandes wrote:
>
>
> Also clean up is not as good as before, cleaned image is still 22MB (in
> contrast to about 10MB with 1.3)
>
This is strange...
ScriptLoader new cleanUpForProduction
generates a 8.4 MB Image...
What you should check is that
Le 04/04/2012 17:30, Marcus Denker a écrit :
> This is strange...
>
> ScriptLoader new cleanUpForProduction
>
> generates a 8.4 MB Image...
>
Great.
Hilaire
--
Dr. Geo -- http://www.drgeo.eu
But still I have to hand delete SystemProgressMorph after each use:
World submorphs
select: [:m | m class == (Smalltalk at: #SystemProgressMorph)]
thenDo: [:morph | morph delete].
Strange.
It only occure after my installation of DrGeo and clean up.
I will track the problem
Here
On Apr 5, 2012, at 11:07 AM, Hilaire Fernandes wrote:
> But still I have to hand delete SystemProgressMorph after each use:
>
> World submorphs
> select: [:m | m class == (Smalltalk at: #SystemProgressMorph)]
> thenDo: [:morph | morph delete].
>
> Strange.
Yes this is strange.
>
You may want to add these clean-up as well.
Strangely, 'FileSystem-Tests-Disk' and 'FileSystem-Tests-Memory' are not
cleaned up. Although there is instance class in memory. May be order
matter in cleaning and those need to be cleaned first.
(MCPackage named: 'Announcements-Help') unload.
On Apr 5, 2012, at 5:42 PM, Hilaire Fernandes wrote:
> You may want to add these clean-up as well.
> Strangely, 'FileSystem-Tests-Disk' and 'FileSystem-Tests-Memory' are not
> cleaned up. Although there is instance class in memory. May be order
> matter in cleaning and those need to be cleaned fi
On Apr 6, 2012, at 10:16 AM, Marcus Denker wrote:
>
> On Apr 5, 2012, at 5:42 PM, Hilaire Fernandes wrote:
>
>> You may want to add these clean-up as well.
>> Strangely, 'FileSystem-Tests-Disk' and 'FileSystem-Tests-Memory' are not
>> cleaned up. Although there is instance class in memory. May
33 matches
Mail list logo
