Doru,
When 3.0.5 was released Pharo1.2 support was just added and AFAIK Pharo1.3 was not ... there has been work on Seaside since then and talk of 3.0.6 ... I was planning on doing some configuration maintenance as part of the Seaside sprint after ESUG ... no time to spare before:) Dale ----- Original Message ----- | From: "Tudor Girba" <[email protected]> | To: [email protected] | Sent: Tuesday, August 16, 2011 11:34:54 AM | Subject: Re: [Pharo-project] [Seaside] seaside #stable on pharo.13? | | Hi, | | Dale, as the main maintainer of the configuration, would you be | available to give a hand with this? | | Cheers, | Doru | | | On 16 Aug 2011, at 13:10, Lukas Renggli wrote: | | > All the latest packages work well in Pharo 1.3, especially in | > combination with Zinc (so the dependency to Kom could be removed). | > | > Lukas | > | > On Tuesday, 16 August 2011, Marcus Denker <[email protected]> | > wrote: | > > | > > On Aug 16, 2011, at 12:18 PM, Tudor Girba wrote: | > > | > >> Hi, | > >> | > >> The ConfiguraitonOfSeaside does not define any #stable version | > >> for Pharo 1.3. | > >> | > >> Is it intentional or is it simply because the configuration is | > >> not up to date? | > > | > > | > > The configuration is not up to date... would be nice to fix it. | > > And it would be good | > > to have a version that loads a minimal seaside (no OB, which I | > > think this does). | > > | > > -- | > > Marcus Denker -- http://marcusdenker.de | > > | > > | > > | > | > -- | > Lukas Renggli | > www.lukas-renggli.ch | | -- | www.tudorgirba.com | | "Problem solving should be focused on describing | the problem in a way that makes the solution obvious." | | | | | |
