Le 26 juin 2014 à 14:49, Roberto Minelli a écrit :
Hi Christophe,
Thanks for the answer. I managed to do that!
Am I interpreting something wrong or the CoolBrowser-Platform itself is an
empty package?
Some kind of.
It is just a name you define that will then be bound to a real package.
Hi,
I have my project with my Configuration and I am using spec groups to load
different sets of packages (e.g., development and user groups).
With the porting to Pharo 4.0 I discovered that there are some functionalities
specific to Pharo 3.0 and others to Pharo 4.0, for example the fact that
Hi,
You can find useful information into the 'Deep into Pharo' book, chapter 9
(Managing projects with Metacello), section 9.12 (platform specific package).
Example:
ConfigurationOfCoolBrowserbaseline09: spec
version: '0.9-baseline'
spec for: #common do: [
spec blessing: #baseline.
Hi Christophe,
Thanks for the answer. I managed to do that!
Am I interpreting something wrong or the CoolBrowser-Platform itself is an
empty package?
Cheers,
R
On Jun 26, 2014, at 2:08 PM, Christophe Demarey christophe.dema...@inria.fr
wrote:
Hi,
You can find useful information into
