I haven't found a better way to load Mondrian in the last Pharo than
this incantation:
-=-=-=-=-=-=-=-=-=-=-=-=
[Gofer new renggli: 'gofer'; version: 'Gofer-lr.86'; load] on: Error
do: [].
Gofer new
squeaksource: 'Mondrian';
addPackage: 'ConfigurationOfMondrian';
load.
I've been able to address the problems with Metacello and
pharo1.0-10502-rc1dev09.12.2. Version 1.0-beta.18 (just released see:
http://groups.google.com/group/metacello/msg/a12918b4bd11c0ef for the
announcement) has been tested with both:
- pharo1.0-10493-rc1dev09.11.2
-
On Dec 27, 2009, at 11:38 PM, Dale Henrichs wrote:
Gofer-dkh.105 or whichever later version predates the move of the instance
variable would get Metacello back into a bootable form for all versions of
Pharo.
I agree that for 1.0 a stable version of Gofer be chosen ... I'm trying to
Stef,
The moving sands are one of the costs of advancement ... I'm more upset that
_I_ don't have time to solve the dang problems than I am that the problems are
appearing ... all of the changes have been for good reasons and over time I
have been removing code from Metacello as Gofer has
Yes
I'm losing my time trying to rescue a proposal we should sent and I wonder what
I'm doing because the acceptance rate are null.
Stef
On Dec 28, 2009, at 4:20 PM, Dale Henrichs wrote:
Stef,
The moving sands are one of the costs of advancement ... I'm more upset that
_I_ don't have
Hi!
Last week, the following expression was used to load Mondrian.
Gofer new squeaksource: 'Mondrian'; addPackage:
'ConfigurationOfMondrian'; load. (Smalltalk at:
#ConfigurationOfMondrian) perform: #loadLastStable.
With the last version of Pharo (10502), I get few deprecation warnings
Alexandre Bergel wrote:
With the last version of Pharo (10502), I get few deprecation warnings
(package: should be used instead of addPackage: and version: instead
of addVersion:).
Similar issues when trying to load Moose with the last version of Pharo
(addPackage, data was late?,
Hi Lukas,
In a fresh 10502 I evaluated:
-=-=-=-=-=-=-=-=-=
[ Gofer gofer load ]
on: Error
do: [ :err | err retry ].
Gofer gofer recompile.
Gofer new
squeaksource: 'Mondrian';
addPackage: 'ConfigurationOfMondrian';
load.
(Smalltalk at:
Hi,
The problem is that Metacello is not quite working with the latest
Gofer.
Cheers,
Doru
On 27 Dec 2009, at 17:39, Alexandre Bergel wrote:
Hi Lukas,
In a fresh 10502 I evaluated:
-=-=-=-=-=-=-=-=-=
[ Gofer gofer load ]
on: Error
do: [ :err | err retry ].
Gofer gofer
I get problems trying to load Seaside30 using
[Gofer new
squeaksource: 'Seaside30';
package: 'LoadOrderTests';
load]
valueSupplyingAnswers: {
{'Load Seaside'. true}.
{'SqueakSource User Name'. ''}.
Version 1.0-beta.18 (development) should have fixes for the latest Gofer.
1.0-beta.18 is currently in #development so it is automatically loaded. When I
get the chance to test the Metacello fixes with 10502, I'll #release
1.0-beta.18 (and will be automatically loaded).
Dale
- Alexandre
I get problems trying to load Seaside30 using
[Gofer new
squeaksource: 'Seaside30';
package: 'LoadOrderTests';
load]
valueSupplyingAnswers: {
{'Load Seaside'. true}.
{'SqueakSource User Name'. ''}.
Ok. Thanks,
Alexandre
On 27 Dec 2009, at 20:14, Dale Henrichs wrote:
Version 1.0-beta.18 (development) should have fixes for the latest
Gofer. 1.0-beta.18 is currently in #development so it is
automatically loaded. When I get the chance to test the Metacello
fixes with 10502, I'll
Is there a script to migrate underscore assignment to := ?
rule := RBUnderscoreAssignmentRule new.
environment := BrowserEnvironment new forPackageNames: #('PackageA'
'PackageB' ...).
SmalllintChecker runRule: rule onEnvironment: environment.
rule open
--
Lukas Renggli
Thanks for both replies.
Cheers
r
On Sun, Dec 27, 2009 at 7:25 PM, Lukas Renggli reng...@gmail.com wrote:
Is there a script to migrate underscore assignment to := ?
rule := RBUnderscoreAssignmentRule new.
environment := BrowserEnvironment new forPackageNames: #('PackageA'
'PackageB'
It is a shame :)
I really wanted to use Pharo 1.1, at least for development. The UI is so
much faster.
On Sun, Dec 27, 2009 at 7:23 PM, Lukas Renggli reng...@gmail.com wrote:
I get problems trying to load Seaside30 using
[Gofer new
squeaksource: 'Seaside30';
package:
It is a shame :)
I agree, but we do not have the resources to maintain two branches.
I really wanted to use Pharo 1.1, at least for development. The UI is so
much faster.
It would be cool if that could be back-ported to 1.0.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
On Dec 27, 2009, at 8:33 PM, Lukas Renggli wrote:
It is a shame :)
I agree, but we do not have the resources to maintain two branches.
I really wanted to use Pharo 1.1, at least for development. The UI is so
much faster.
It would be cool if that could be back-ported to 1.0.
no :)
we
| | After proceeding these warnings, I have a rollback: MNU
| | GoferPackageReference classname:repository:
| |
| | Can you evaluate
| |
| | [ Gofer gofer load ]
| | on: Error
| | do: [ :err | err retry ].
| | Gofer gofer recompile.
| |
| | ? I don't have any
Gofer-dkh.105 or whichever later version predates the move of the instance
variable would get Metacello back into a bootable form for all versions of
Pharo.
I agree that for 1.0 a stable version of Gofer be chosen ... I'm trying to
restrict the current Metacello changes to avoid significant
20 matches
Mail list logo
