| the dependencies, and, of course, the versions.
|
| Any thougths about this?
|
| Cheers
|
| Mariano
|
| On Sat, Jan 9, 2010 at 1:17 AM, Dale Henrichs
| dale.henri...@gemstone.comwrote:
|
| just fine..thanks
| - Mariano Martinez Peck marianop...@gmail.com wrote:
|
| | On Sat, Jan 9, 2010 at 12:47
, 2010 at 7:11 PM, Dale Henrichs
| dale.henri...@gemstone.comwrote:
|
| Mariano,
|
| That's just fine ... make the changes that you need to make and I'll
| adapt
| that configuration for GLASS and Squeak (Gemtools).
|
|
| Thanks Dale. And regardless my intention to let you know this so
Since I'm maintaining the Seaside3.0 config, I am probably at fault on this one
although I haven't run into a problem with underscore assignment ... How do I
run a pharo image that _does not_ allow underscore assignment?
Specifically, the Seaside3.0 config is not using the Swazoo code that
Torsten,
Thanks for the feedback! It is much appreciated. I've interspersed comments
below.
- Mariano Martinez Peck marianop...@gmail.com wrote:
| On Wed, Jan 13, 2010 at 2:41 PM, Torsten Bergmann asta...@gmx.de
| wrote:
|
| Played with Metacello:
|
|
| First, there is a Metacello
- Torsten Bergmann asta...@gmx.de wrote:
| And the other thing is that you put everything under spec for:
| #common
|
| Depends on the meaning of common (only Pharo and other Squeak
| Distributions) or does it include other Smalltalks (VW, VAST) too?
| If Metacello gets ported then you are
Mariano,
The progress-bar problem is solvable.
The progress bar problem appears because the dev image doits reinitalize the
progress bar class. The first question is: Must the progress bar code be
initialized? if no, then remove the initialization code and the problem should
be solved:) If
I would like to create a ConfigurationOfGofer that would be used by
ConfigurationOfMetacello.
Currently ConfigurationOfMetacello references gofer by explicit package
versions for Gofer-core and Gofer-Tests and those versions may not match the
Gofer that is used in the Core.
If we had a
On second thought .. I don't have too... I want to push Metacello 1.0-beta.22
today...
Dale
- Dale Henrichs dale.henri...@gemstone.com wrote:
| - Mariano Martinez Peck marianop...@gmail.com wrote:
|
| | BTW...do you know who/when merges your latest gofer code into
| | PharoCore
First load the configuration:
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfSeaside';
load.
Then pick the Seaside variant you want to load:
Seaside 2.8
ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'.
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfAida';
load.
((Smalltalk at: #ConfigurationOfAida) project version: '6.0') load.
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
Unload is on the list of things for Metacello ... the very early versions of
Metacello supported unload.
As I moved things around, I stopped trying to keep unload alive focussing on
getting the loading correct.
Now that Metacello is built on top of Gofer the mechanics of Monticello unload
is
- Dale Henrichs dale.henri...@gemstone.com wrote:
| Gofer new
| squeaksource: 'MetacelloRepository';
| package: 'ConfigurationOfAida';
| load.
|
| ((Smalltalk at: #ConfigurationOfAida) project version: '6.0') load
- Mariano Martinez Peck marianop...@gmail.com wrote:
| Something like this:
|
| #(Metacello-Core Metacello-MC Metacello-Platform )
| do: [ :each | (MCPackage named: each) unload ].
|
For unloading just Metacello, this gofer script works:
| gofer |
gofer := Gofer new.
I've just committed a new version of ConfigurationOfMetacello
(ConfigurationOfMetacello-DaleHenrichs.149) with the class-side method
#unloadMetacello implemented using the aforementioned Gofer script.
The template config has the class-side method #unloadMetacello (available when
1.0-beta.23 is
-2010 a las 17:14 -0800, Dale Henrichs escribió:
| First load the configuration:
|Gofer new
| squeaksource: 'MetacelloRepository';
| package: 'ConfigurationOfSeaside';
| load.
|
| Then pick the Seaside variant you want to load:
|
|Seaside 2.8
|ConfigurationOfSeaside
- laurent laffont laurent.laff...@gmail.com wrote:
|
| Hi,
|
| isn't it quite complex ? One can do:
| 3 timesRepeat: [ProfStef next].
|
| Less to type, Smalltalkish, and maybe more fun ?
|
Laurent,
The #goto: style allows one to label a lesson ... #timesRepeat: fails if I
reorder the
- Mariano Martinez Peck marianop...@gmail.com wrote:
| On Sun, Jan 31, 2010 at 7:04 PM, Dale Henrichs
| dale.henri...@gemstone.comwrote:
|
|
| - laurent laffont laurent.laff...@gmail.com wrote:
| |
| | Hi,
| |
| | isn't it quite complex ? One can do:
| | 3 timesRepeat: [ProfStef
in an unusable state.
|
| Danny
|
|
|
| Am Montag, 1. Februar 2010 19:22:58 schrieb Dale Henrichs:
| - Mariano Martinez Peck marianop...@gmail.com wrote:
| | On Sun, Jan 31, 2010 at 7:04 PM, Dale Henrichs
| |
| | dale.henri...@gemstone.comwrote:
| | - laurent laffont laurent.laff
I think that this would be the perfect spot for a ProfStef tutorial ... handful
of steps to configure/launch Seaside 2.8 ...
The tutorial could be part of ConfigurationOfSeaside28 and when loaded would
launch the tutorial ... it would not be part of the Core group, but would be
available in
I've just published ConfigurationOfXMLSupport to the MetacelloRepository. It is
used by several Pier addons. It _is_ just one package, but since it can be used
in a lot of different projects, I thought it was worth adding as a
configuration.
It is based upon the code in
...@lists.gforge.inria.fr] On Behalf Of Dale
| Henrichs
| Sent: Sunday, February 07, 2010 3:58 PM
| To: Pharo-project@lists.gforge.inria.fr
| Cc: Pharo-project@lists.gforge.inria.fr
| Subject: Re: [Pharo-project] Metacello - the missing information??
|
| Bill,
|
| This has been discussed before
(before I get to it), then I would be willing to read and correct them.
Dale
- Henrik Sperre Johansen henrik.s.johan...@veloxit.no wrote:
| On 07.02.2010 21:57, Dale Henrichs wrote:
| Bill,
|
| This has been discussed before and there is development underway for
| Loader which is aimed
- Yanni Chiu ya...@rogers.com wrote:
| BTW, since all FFI-Examples packages were removed from the FFI
| repository, even Metacello versions would fail because the package
| is
| no longer there.
This underscores Lukas' argument that you need to create your own repository of
packages that
In the current Metacello, you can set the blessing to #broken and the version
will be ignored in certain calculations like latestVersion...
Dale
- Miguel Enrique Cobá Martinez miguel.c...@gmail.com wrote:
| El mar, 16-02-2010 a las 13:25 -0800, Dale Henrichs escribió:
| - Yanni Chiu
- Yanni Chiu ya...@rogers.com wrote:
| Dale Henrichs wrote:
| - Yanni Chiu ya...@rogers.com wrote:
|
| | BTW, since all FFI-Examples packages were removed from the FFI
| | repository, even Metacello versions would fail because the
| package
| | is
| | no longer
Gemstone uses an order list of dictionaries for global lookup. Each user can
change the order of the list or insert their own dictionaries into the list ...
makes for quite a bit of flexibility you can load code into a particular
dictionary...and the global resolution is at compile time
I will put a page up on the wiki with Torsten's message ... I agree that
Torsten did a good job!
Dale
- Fernando olivero olive...@lu.unisi.ch wrote:
| I think this scenario of usage is really great! Good work Torsten.
|
| Would be a shame that this example got lost in the emails list.
|
I like the notion of a secondary repository for packages. It is absolutely
necessary to protect us from a catastrophic failure with any one of the
SqueakSource repositories.
Perhaps Gofer can be provided with a secondary repository location in the case
when the primary repository fails.
With
- Lukas Renggli reng...@gmail.com wrote:
| Perhaps Gofer can be provided with a secondary repository location
| in the case when the primary repository fails.
|
| Yes, it can. You just specify multiple repositories and it will use
| them all. If you tell Gofer to #disableRepositoryErrors
- Torsten Bergmann asta...@gmx.de wrote:
| I'm sure I'm not able to convince one or the other to use package
| systems like Metacello but at least I hope to make them think about
| the need of a more modular system.
Torsten,
Just for the record. I truly look forward to the day when a
?
|
| Cheers,
| Doru
|
|
| On 23 Feb 2010, at 21:18, Dale Henrichs wrote:
|
|
| - Lukas Renggli reng...@gmail.com wrote:
|
| | Perhaps Gofer can be provided with a secondary repository
| location
| | in the case when the primary repository fails.
| |
| | Yes, it can. You just specify
- Alexandre Bergel alexan...@bergel.eu wrote:
| But I get an error raised by MetacelloPackageSpecinstVarNames:put:
|
| apparently some reflective operations try to access a non-existing
| variable.
|
| I know that Pharo is meant to be built from a stable core. But I would
| like to
Stef,
I really like formatters, but as the discussion has already shown, there isn't
one format that fits everyone's definition of beauty/readability.
Personally I am willing to use any formatter that saves me from having to hand
edit code for format, but I think I am in the minority.
It is obvious that a consensus will not be reached on the one and only true
format.
If my browser displays code formatted the way I want to see it and the
difference tools are format neutral (i.e., the source and target code is
formatted using the same rules) there is no need to agree on a
Alexandre,
You _can_ load Metacello without requiring OB. The current default is to _not_
include the tools (at one point in time OB was required, but with more recent
versions that is no longer the case).
I just loaded ConfigurationOfMetacello into PharoCore-1.1-11239 this morning:
Gofer
Lukas,
Doesn't this enter into the same territory that you are in with Seaside ... you
are dealing with multiple platforms 1.0 and 1.1.
The code can to be partitioned into platform-specific and common packages
or you can monkey-patch for one of the platforms (presumably 1.0 should be
monkey
- Lukas Renggli reng...@gmail.com wrote:
| Yes, an OBPlatform for each major version...
|
| Well, the problem is that ...
|
| OBPlatform
|OBMorphicPlatform
| OBShoutPlatform
|
| That doesn't really work without an explosion of classes and I don't
| feel like changing all that
gemsource is back online ... the server crashed and we had a hiccup or two on
restarting gemstone ...
Dale
- Dale Henrichs dale.henri...@gemstone.com wrote:
| We are apparently having hardware problems with the gemsource
| server... we are working on it...
|
| Dale
| - Miguel Enrique
that's
complete...
Dale
- Dale Henrichs dale.henri...@gemstone.com wrote:
| gemsource is back online ... the server crashed and we had a hiccup or
| two on restarting gemstone ...
|
| Dale
| - Dale Henrichs dale.henri...@gemstone.com wrote:
|
| | We are apparently having hardware problems
Excellent work ... very good idea to hook it into Gofer!
Dale
- Esteban Lorenzano esteba...@gmail.com wrote:
| Hi,
| I want to announce the immediate release of GoferProjectLoader, a
| Gofer
| extension to manage Metacello configurations.
| For all who want to know quickly what is this,
Alexandre,
load involves loading a project into an image in which the project does not
exist.
upgrade involves loading a project into an image in which the project already
is loaded.
Loading is straightforward ... it is what we do all of the time. Add a bunch of
classes and methods, then run
- Esteban Lorenzano esteba...@gmail.com wrote:
| - any idea about how we go to differentiate stable and unstable
|
| universes for each Pharo version? How does the user know which version
| is the one he needs for his version of Pharo? Sorry, this is not
| directly related to the
- Alexandre Bergel alexan...@bergel.eu wrote:
| load involves loading a project into an image in which the project
| does not exist.
| upgrade involves loading a project into an image in which the
| project already is loaded.
|
| Loading is straightforward ... it is what we do all
- Stéphane Ducasse stephane.duca...@inria.fr wrote:
| esteban
|
| excellent!!!
| Now how can we load code for Pharo1.0 which is different for Pharo1.1
| and soon Pharo1.2
| you see what I mean.
|
| Ideally I would like to have the MetacelloRepository structured in a
| tree with
of quality.
|
| Yes!
|
|
| Cheers,
| Adrian
|
|
| On Mar 17, 2010, at 23:41 , Miguel Enrique Cobá Martinez wrote:
|
| El mié, 17-03-2010 a las 15:20 -0700, Dale Henrichs escribió:
| - Esteban Lorenzano esteba...@gmail.com wrote:
|
| | - any idea about how we go to differentiate
image and the other
| repository in 1.1 etc.?
|
| Cheers,
| Adrian
|
| On Mar 18, 2010, at 18:14 , Dale Henrichs wrote:
|
| Okay,
|
| I think I am wrapping my brain around this discussion...Sometimes I
| can be very thick headed:)
|
| Yes that makes perfect sense ... I was thinking about
George,
The mcz files containing the Metacello configurations _are_ copied, but the
configuration itself is not modified in the scheme.
The idea of using different repositories is to indicate which of the many
different projects are _expected_ or _known_ to work in Pharo1.1 or Pharo1.0.
For
the versions of the target platform?
|
| 2010/3/20 Dale Henrichs dale.henri...@gemstone.com:
| George,
|
| The mcz files containing the Metacello configurations _are_ copied,
| but the configuration itself is not modified in the scheme.
|
| The idea of using different repositories is to indicate
configuration the differences
| between the versions of the target platform?
|
| 2010/3/20 Dale Henrichs dale.henri...@gemstone.com:
| George,
|
| The mcz files containing the Metacello configurations _are_
| copied, but the configuration itself is not modified in the scheme
:)
Dale
- Dale Henrichs dale.henri...@gemstone.com wrote:
| Miguel,
|
| Keep in mind that the conditional load code in Metacello is the moral
| equivalent of #ifdef in C. The debian package universe has the
| advantage of pushing the conditional compilaton of _source code_ down
| a level
FWIW, Gemstone returns the arg..
Dale
- stephane ducasse stephane.duca...@free.fr wrote:
| hi guys
|
| I saw that nicolas fixed all the add: ... in squeak to return the
| argument and I like the idea I created an issue.
| Now I saw that nicolas fixed also nextPut:
|
| Item was changed:
|
in synch for essentially different
projects...
Dale
- Miguel Enrique Cobá Martinez miguel.c...@gmail.com wrote:
| El sáb, 20-03-2010 a las 14:12 -0700, Dale Henrichs escribió:
| Miguel,
|
| I should emphasize that conditional load/compile in Metacello is a
| pragmatic feature. I don't
That version is copied over to SqueakSource MetacelloRepository...
I also have a comment on the release...when I bring Pharo up on my laptop
(running OpenSuse) the lower right corner of the workspace is off the screen
so I have to move the workspace to see the scroll bar...
Dale
- Miguel
Mariano,
I am seriously considering releasing 1.0-beta.25 today ... I have smacked the
heck out Metacello over the last three days without issues so I'm thinking I
can let this puppy out the door:)...Especially if it will clean up the release
process...
One other point I have noticed is that
Yep,
A metacello 1.0-beta.25 bug ... I'll fix it right now (or after breakfast:).
Dale
- Dale Henrichs dale.henri...@gemstone.com wrote:
| If that's the build process you use, I'm not sure why the repsitory
| isn't mapped correctly ... maybe it's a metacello bug then...I will do
| a build
Bill,
Looks like ConfgurationOfCitezen does need required projects added (I am
willing to help the maintainers - drop me a line).
Perhaps the configs aren't ready for prime time and that's why they have not
been added to MetacelloRepository.
You can add repositories to your own GoferProject:
-project-boun...@lists.gforge.inria.fr] On Behalf Of Dale
| Henrichs
| Sent: Monday, March 22, 2010 2:18 PM
| To: Pharo-project@lists.gforge.inria.fr
| Cc: Pharo-project@lists.gforge.inria.fr
| Subject: Re: [Pharo-project] RC3 - small stuff
|
| Bill,
|
| Looks like ConfgurationOfCitezen does need
Stef and Lukas,
The other situation that I have seen these types of errors is when the package
that I am merging into(?) does not have the repository where the common
ancestor mcz file is located.
For example if I have Seaside.gemstone-dkh.500 with
http://seaside.gemstone.com/ss/seaside in
Hilaire,
Thanks for the feedback.
I've opened http://code.google.com/p/metacello/issues/detail?id=69 to track
this issue.
This might be a shortcut worth adding, since it _is_ used very frequently.
You'd still need to revert to the #package:with: form if you wanted to set
multiple attributes
Doru,
I was just a little bit worried when RC3 was shipped with a #development
blessing for 1.0-beta.25, now I have a concrete reason to be worried.
Since 1.0-beta.25 is in #development, the latestVersion of Metacello is
1.0-beta.24.1 and thats the version that gets loaded by
Adrian,
1.0-beta.25 has been released. So it is now _stable_ . No new issues have
appeared, yet, but if any do appear I'll do a dot release.
Dale
- Adrian Lienhard a...@netstyle.ch wrote:
| Because there are a few things left that still need to be done for the
| release:
| - make all tests
Bill,
I haven't followed your trials and tribulations with libraries, but I do know
that starting with version 3.11-3 of the Squeak vm(see
'http://lists.squeakfoundation.org/pipermail/vm-dev/2009-September/003206.html'),
the naming conventions for dynamically loaded files was changed to use a
to compensate. Hopefully, you are thinking of
| plugins.
|
| Bill
|
|
|
|
| -Original Message-
| From: pharo-project-boun...@lists.gforge.inria.fr
| [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Dale
| Henrichs
| Sent: Wednesday, April 07, 2010 1:19 PM
| To: Pharo
Mariano,
The Pharo-1.0.changes file looks to be corrupted. If you edit the the changes
file and search for ConfigurationOfGofer here's what you see:
!ConfigurationOfGofer methodsFor: 'accessing' stamp: 'nk 3/5/2005 15:28'!
sNil! !
!ConfigurationOfGofer methodsFor: 'baselines'!
1 into: [:sum
Sean,
Don't know if this has already mentioned, but you can programmatically add
Directory repositories as follows:
| repo |
{'/path/to/repositories/project-1/'. '/path/to/repositories/project-2/'.
'/path/to/repositories/project-3/'. } do: [:path |
repo := MCDirectoryRepository new
Torsten,
Sorry for the late reply ... caught a nasty cold and used the opportunity to
stop reading email for a couple of days ...
It looks like the original problem was that ArchiveViewer was included in the
group names but was no longer defined in 1.1-baseline. When using a
configuration
Mariano and Alexandre,
Sorry for the late reply ... I've been off-line with a cold for the last
several days ...
I have seen the behavior that you describe while working with GLASS 1.0-beta.8
and have fixed the problem in Metacello 1.0-beta.26.1 ... 1.0-beta.26.1 is
still in development, but
again. How can I do that ? because if I
| try to
| install it normally, it won't do it as it is already installed.
|
| Thanks
|
| Mariano
|
| On Tue, Apr 20, 2010 at 6:21 PM, Dale Henrichs
| dale.henri...@gemstone.comwrote:
|
| Mariano,
|
| The Pharo-1.0.changes file looks to be corrupted
I found the missing mcz in one of my package-caches and I have copied the file
to:
http://source.lukas-renggli.ch/obsolete/OmniBrowser-DamienCassou.462.mcz
Which is probably the best home for it...
Dale
- Torsten Bergmann asta...@gmx.de wrote:
| The best solution would be to bring back
.
|
| So, the problem persists :-)
| Thanks Dale for offering your help.
|
| Cheers,
| Alexandre
|
|
| On 29 Apr 2010, at 14:08, Dale Henrichs wrote:
|
| Mariano and Alexandre,
|
| Sorry for the late reply ... I've been off-line with a cold for the
|
| last several days ...
|
| I have seen
Andreas,
I think the advantage of form B comes when you end up nesting the build
instructions:
spec for: #common do: [
spec blessing: #baseline.
spec description: 'Descriptive comment'.
spec
project: 'UI Support' with: [
spec
className: 'UIConfig';
loads:
- Alexandre Bergel alexan...@bergel.eu wrote:
| Apparently the bug remains. When I load the last version of
| 'ConfigurationOfPharo project' in a fresh and updated Core 1.1, then
|
| OB-Standard.lr.442 is loaded and initialized.
|
| So, the problem persists :-)
Alexandre,
The short
Alexandre,
I'm actually working through this scenario right now. Moving OB BEFORE
AutomaticMethodCategorizer will load the proper version of OB ... with this
load order the older version of OB shouldn't be loaded by
AutomaticMethodCategorizer (this is the area where I suspected a bug in
- Mariano Martinez Peck marianop...@gmail.com wrote:
| The nesting level for '1.1.3 [ConfigurationOfOmniBrowser]' and '1.1
| [ConfigurationOfAutomaticMethodCategorizer]' are the same which
| means that
| they are both referenced in '1.1 [ConfigurationOfPharo]'. That was
| enough to
|
- Dale Henrichs dale.henri...@gemstone.com wrote:
| Moving the specification of OmniBrowser before the spec for
| AutomaticMethodCategorizer does result in the correct mcz file for
| OB-Standard to be loaded, however, other issues are exposed:
|
| SHOUT uses the deprecated registerMenu
and lots
of proceeds:)
Dale
- Mariano Martinez Peck marianop...@gmail.com wrote:
| On Tue, May 4, 2010 at 9:23 PM, Dale Henrichs
| dale.henri...@gemstone.comwrote:
|
|
| - Mariano Martinez Peck marianop...@gmail.com wrote:
|
|
| | The nesting level for '1.1.3
Alexandre,
Using Metacello 1.0-beta.26 and PharoCore-1.1-11335-UNSTABLE (latest update), I
get the same results:
SHOUT uses the deprecated registerMenu API
Refactoring Browser AST-Core-lr.66 is loaded first and the AST-Core-lr.67 is
loaded
but this probably isn't a problem, although
I've replied to question 1) in the Squeak-dev list
(http://forum.world.st/Metacello-questions-tt2132073.html#a2133038), but will
finish/continue the discussion on the Metacello list
(http://forum.world.st/Fwd-Metacello-questions-tt2132927.html#a2132927)...
Dale
- Andreas.Raab
- Dale dale.henri...@gemstone.com wrote:
| Teleplacer wrote:
|
| On 5/6/2010 9:55 AM, Dale wrote:
| snip
| #includes is used quite extensively for Seaside30 where an
| expression
| like
| the following is used:
|
| spec for: #common do: [
| spec
|
Andreas,
You have bumped into a bug in Metacello 1.0-beta.26. I discovered the bug a
couple of weeks ago while using Metacello in GLASS so the bug is fixed in
Metacello 1.0-beta.26.1. 1.0-beta.26.1 is under development (#development
blessing) so is not loaded by #latestVersion. I am a couple
- Andreas.Raab andreas.r...@gmail.com wrote:
| 3) When exactly is HelpSystem loaded?
|
| What I'm wondering about in the above is that HelpSystem should only
| be
| loaded if WebClient-Help is being loaded. Is this implicitly part of
| specifying a 'project' instead of a 'package'? Or is
+1
With at least one exception:)
In Seaside3.0 there is a tight coupling between the Seaside3.0 packages and the
Grease packages ... to the point were (at least for the time being) a later
version of Grease is not likely to work an earlier version of Seaside3.0, so it
_is_ appropriate to
Stef,
Just thinking off the top of my head a bit.
Conceptually a separate repository makes sense ... then Gofer Project
could be
setup to to use this repository by default and the standard instructions
for
loading things would be reduced to simple expressions like:
...@gmx.de wrote:
| On 5/10/2010 10:06 AM, Dale Henrichs wrote:
| +1
|
| I'll have to admit I find this quite awkward - like designing a
| framework that has only one use case. It tends to push the wrong
| things
| into the abstraction layer. Is there anything fundamentally wrong
small
subset of the configs that I'm already involved with, so it isn't that
difficult to manage manually...
Dale
- Stéphane Ducasse stephane.duca...@inria.fr wrote:
| On May 10, 2010, at 8:14 PM, Dale Henrichs wrote:
|
| Stef,
|
| Just thinking off the top of my head a bit
, that each of the individual constructor statements for a
named spec are processed in a very specific order with each of the #add, #copy,
#merge, and #remove operations applied in order...
Hope this helps,
Dale
- Andreas Raab andreas.r...@gmx.de wrote:
| On 5/6/2010 5:26 PM, Dale Henrichs
- Andreas.Raab andreas.r...@gmail.com wrote:
| 5) Bootstrapping Metacello?
|
| I found that most of the ConfigurationsOfXXX include some code to
| 'bootstrap' Metacello in some form. There appear to be variants on
| the
| code; is there a canonical bootstrap method that should be used?
|
Lukas,
For GemStone, the split in OB was made such that the #changed messages are sent
across the wire with Morphic running on the client (local) side. The Morphic
requests for lists were then made back across the wire and so on ...
There is still a fair amount of traffic that is probably
Yes, I don't think that it is a good idea to modify the configuration
when it is published in the PharoXXMetacelloRepository.
In the end the reason for this discussion revolves around the desire to
provide a simple method for developers/users to load projects that are
known/tested to work in
Mariano,
I'm not sure I am following ... What Help package are you referring to?
Dale
From: metace...@googlegroups.com [metace...@googlegroups.com] On Behalf Of
Mariano Martinez Peck [marianop...@gmail.com]
Sent: Friday, May 21, 2010 1:36 AM
To: Pharo
Mariano,
Which Test packages to load ... The real answer to that question will depend
upon what other packages are loaded if you load 'Tests' you'll end up
loading up most of the optional packages, so if that's not a problem in the
default PharoDev then 'Tests' is the right answer,
I had suggested that they not use the ConfigurationOf prefix for the Squeak
configuration package so that cross platform configurations could continue to
be used ... I would hope that folks continue to to create cross platform
packages ... the onus on copying shouldn't be on the developer, but
Miguel Enrique Cobá Martinez wrote:
I don't dislike Squeak usage but changing a emerging technology that is
being used in a given way and that appears to be working (I've done the
Magma configuration and I tested it worked on Squeak and Pharo) but this
new Squeak usage of Metacello really
Andrei,
GemStone/S and GLASS provides a free for commercial use multi-vm
environment that provides image-based persistence. With an annual
license you can use multiple vms across multiple cores.
A number of folks using GemStone develop in Pharo and deploy in
GemStone, so that mode of
Mariano Martinez Peck wrote:
On Mon, May 24, 2010 at 11:41 PM, Torsten Bergmann
asta...@gmx.demailto:asta...@gmx.de wrote:
We should listen to Torsten but as far as I would expect, only HelpSystem,
but it is already included in both PharoCore and Squeak.
The help system is included in
Stéphane Ducasse wrote:
any idea why on pharo 1.1
| b n |
b := [:aa :ab| ].
n := 1000.
{ Time millisecondsToRun: [1 to: n do: [:i| b value: 0 value: 0]].
Time millisecondsToRun: [1 to: n do: [:i| b valueWithArguments: {0. 0}]].
Time millisecondsToRun: [1 to: n do: [:i| b
Stef,
That's exactly what GoferProjectLoader is for... see
http://www.smallworks.com.ar/en/community/GoferProjectLoader.
Although you'd type:
Gofer project load: 'Torch'
Dale
stephane ducasse wrote:
hi lukas
recently I spend a lot of time typing expression like that
Gofer new
:37 PM, Dale Henrichs wrote:
Stef,
That's exactly what GoferProjectLoader is for... see
http://www.smallworks.com.ar/en/community/GoferProjectLoader.
Although you'd type:
Gofer project load: 'Torch'
Dale
stephane ducasse wrote:
hi lukas
recently I spend a lot of time typing expression like
laurent laffont wrote:
Hi,
I've just created a ConfigurationOfScamper using
MetacelloCreateConfigurationTutorial (see http://code.google.com/p/metacello/)
in ProfStefBrowser, it's really funny.
Can MetacelloCreateConfigurationTutorial be included in Pharo (Dev) 1.1 ?
Cheers,
Laurent
ecompletion does not show up in the preferences browser so I am at a
loss to turn it off ... it is annoying enough that I've spent a fair
amount of time cruising the image looking for a way to turn off a
preference (plenty of protocol for getting the preference values...) and
I've examined the
101 - 200 of 704 matches
Mail list logo
