Conf for seaside 3.0 is loading OB in a Core image :(

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Conf for seaside 3.0 is loading OB in a Core image :(

Mariano Martinez Peck
Hi Dale. I took a PharoCore-1.1-11355-UNSTABLE.1  image and I evaluated:

ConfigurationOfSeaside project latestVersion load: #( 'Seaside 3.0' 'Seaside 3.0 Tests' ).

In this core image, of course, I don't have OB installed. I remember that Seaside - OB was installed ONLY if OB was present in the image. However, this is loading OB :(

Any quotes ?

In addition (and a bit offtopic), Lukas and Alexandre made OB to work on Pharo 1.1. The ConfigurationOfOmnibroswer version 1.1.4
So, it would be cool if we can define a new version of ConfigurationOfSeaside so that to be able to load Seaside 2.8 and 3.0 in Pharo 1.1. Of course, you should use OB 1.1.4.
I know you also use Conf of OB in GALSS...

Thanks a lot.

Mariano
 
Reply | Threaded
Open this post in threaded view
|

Re: Conf for seaside 3.0 is loading OB in a Core image :(

Dale

----- "Mariano Martinez Peck" <[hidden email]> wrote:

| Hi Dale. I took a PharoCore-1.1-11355-UNSTABLE.1  image and I
| evaluated:
|
| ConfigurationOfSeaside project latestVersion load: #( 'Seaside 3.0'
| 'Seaside
| 3.0 Tests' ).
|
| In this core image, of course, I don't have OB installed. I remember
| that
| Seaside - OB was installed ONLY if OB was present in the image.
| However,
| this is loading OB :(

I believe that Lukas and Julian decided that they wanted everything loaded by default in Seaside3.0 including the parts that require OB, so I changed the config...

|
| Any quotes ?
|
| In addition (and a bit offtopic), Lukas and Alexandre made OB to work
| on
| Pharo 1.1. The ConfigurationOfOmnibroswer version 1.1.4
| So, it would be cool if we can define a new version of
| ConfigurationOfSeaside so that to be able to load Seaside 2.8 and 3.0
| in
| Pharo 1.1. Of course, you should use OB 1.1.4.
| I know you also use Conf of OB in GALSS...

I'm trying to push a GLASS release out (Metacello 1.0-beta.26.1 was the first step:), but if the release drags too long, I'll push out a new Seaside3.0 version...

Dale
Reply | Threaded
Open this post in threaded view
|

Re: Conf for seaside 3.0 is loading OB in a Core image :(

Mariano Martinez Peck


On Wed, May 12, 2010 at 11:52 PM, Dale Henrichs <[hidden email]> wrote:

----- "Mariano Martinez Peck" <[hidden email]> wrote:

| Hi Dale. I took a PharoCore-1.1-11355-UNSTABLE.1  image and I
| evaluated:
|
| ConfigurationOfSeaside project latestVersion load: #( 'Seaside 3.0'
| 'Seaside
| 3.0 Tests' ).
|
| In this core image, of course, I don't have OB installed. I remember
| that
| Seaside - OB was installed ONLY if OB was present in the image.
| However,
| this is loading OB :(

I believe that Lukas and Julian decided that they wanted everything loaded by default in Seaside3.0 including the parts that require OB, so I changed the config...


OK...

 

|
| Any quotes ?
|
| In addition (and a bit offtopic), Lukas and Alexandre made OB to work
| on
| Pharo 1.1. The ConfigurationOfOmnibroswer version 1.1.4
| So, it would be cool if we can define a new version of
| ConfigurationOfSeaside so that to be able to load Seaside 2.8 and 3.0
| in
| Pharo 1.1. Of course, you should use OB 1.1.4.
| I know you also use Conf of OB in GALSS...

I'm trying to push a GLASS release out (Metacello 1.0-beta.26.1 was the first step:), but if the release drags too long, I'll push out a new Seaside3.0 version...


Ok...but that new Seaside 3.0 version will use 1.1.4 of OB ?   Otherwhise, don't worry. I can create a new version of Seside 3.0 for us (Pharo 1.1) that uses OB 1.1.4. I just asked it can it was also useful for you. Just let me know.

Cheers

Mariano
 
Reply | Threaded
Open this post in threaded view
|

Re: Conf for seaside 3.0 is loading OB in a Core image :(

Dale
Mariano,

For GLASS I use the same ConfigurationOfSeaside30 as Pharo/Squeak...I don't want to diverge. I am in the process of updating things for Pharo 1.0 as we speak and once I get that working/passing tests I'll test it on Pharo1.1 ...


BTW, does OB 1.1.4 work on both Pharo1.0 and Pharo1.1?

Dale

----- "Mariano Martinez Peck" <[hidden email]> wrote:

| On Wed, May 12, 2010 at 11:52 PM, Dale Henrichs
| <[hidden email]>wrote:
|
| >
| > ----- "Mariano Martinez Peck" <[hidden email]> wrote:
| >
| > | Hi Dale. I took a PharoCore-1.1-11355-UNSTABLE.1  image and I
| > | evaluated:
| > |
| > | ConfigurationOfSeaside project latestVersion load: #( 'Seaside
| 3.0'
| > | 'Seaside
| > | 3.0 Tests' ).
| > |
| > | In this core image, of course, I don't have OB installed. I
| remember
| > | that
| > | Seaside - OB was installed ONLY if OB was present in the image.
| > | However,
| > | this is loading OB :(
| >
| > I believe that Lukas and Julian decided that they wanted everything
| loaded
| > by default in Seaside3.0 including the parts that require OB, so I
| changed
| > the config...
| >
|
|
| OK...
|
|
|
| >
| > |
| > | Any quotes ?
| > |
| > | In addition (and a bit offtopic), Lukas and Alexandre made OB to
| work
| > | on
| > | Pharo 1.1. The ConfigurationOfOmnibroswer version 1.1.4
| > | So, it would be cool if we can define a new version of
| > | ConfigurationOfSeaside so that to be able to load Seaside 2.8 and
| 3.0
| > | in
| > | Pharo 1.1. Of course, you should use OB 1.1.4.
| > | I know you also use Conf of OB in GALSS...
| >
| > I'm trying to push a GLASS release out (Metacello 1.0-beta.26.1 was
| the
| > first step:), but if the release drags too long, I'll push out a
| new
| > Seaside3.0 version...
| >
| >
| Ok...but that new Seaside 3.0 version will use 1.1.4 of OB ?  
| Otherwhise,
| don't worry. I can create a new version of Seside 3.0 for us (Pharo
| 1.1)
| that uses OB 1.1.4. I just asked it can it was also useful for you.
| Just let
| me know.
|
| Cheers
|
| Mariano
Reply | Threaded
Open this post in threaded view
|

Re: Conf for seaside 3.0 is loading OB in a Core image :(

Mariano Martinez Peck


On Thu, May 13, 2010 at 1:27 AM, Dale Henrichs <[hidden email]> wrote:
Mariano,

For GLASS I use the same ConfigurationOfSeaside30 as Pharo/Squeak...I don't want to diverge. I am in the process of updating things for Pharo 1.0 as we speak and once I get that working/passing tests I'll test it on Pharo1.1 ...


BTW, does OB 1.1.4 work on both Pharo1.0 and Pharo1.1?

Hi Dale. I have just testes and not only seems to work but also all tests are green :)

 

Dale

----- "Mariano Martinez Peck" <[hidden email]> wrote:

| On Wed, May 12, 2010 at 11:52 PM, Dale Henrichs
| <[hidden email]>wrote:
|
| >
| > ----- "Mariano Martinez Peck" <[hidden email]> wrote:
| >
| > | Hi Dale. I took a PharoCore-1.1-11355-UNSTABLE.1  image and I
| > | evaluated:
| > |
| > | ConfigurationOfSeaside project latestVersion load: #( 'Seaside
| 3.0'
| > | 'Seaside
| > | 3.0 Tests' ).
| > |
| > | In this core image, of course, I don't have OB installed. I
| remember
| > | that
| > | Seaside - OB was installed ONLY if OB was present in the image.
| > | However,
| > | this is loading OB :(
| >
| > I believe that Lukas and Julian decided that they wanted everything
| loaded
| > by default in Seaside3.0 including the parts that require OB, so I
| changed
| > the config...
| >
|
|
| OK...
|
|
|
| >
| > |
| > | Any quotes ?
| > |
| > | In addition (and a bit offtopic), Lukas and Alexandre made OB to
| work
| > | on
| > | Pharo 1.1. The ConfigurationOfOmnibroswer version 1.1.4
| > | So, it would be cool if we can define a new version of
| > | ConfigurationOfSeaside so that to be able to load Seaside 2.8 and
| 3.0
| > | in
| > | Pharo 1.1. Of course, you should use OB 1.1.4.
| > | I know you also use Conf of OB in GALSS...
| >
| > I'm trying to push a GLASS release out (Metacello 1.0-beta.26.1 was
| the
| > first step:), but if the release drags too long, I'll push out a
| new
| > Seaside3.0 version...
| >
| >
| Ok...but that new Seaside 3.0 version will use 1.1.4 of OB ?
| Otherwhise,
| don't worry. I can create a new version of Seside 3.0 for us (Pharo
| 1.1)
| that uses OB 1.1.4. I just asked it can it was also useful for you.
| Just let
| me know.
|
| Cheers
|
| Mariano

Reply | Threaded
Open this post in threaded view
|

Re: Conf for seaside 3.0 is loading OB in a Core image :(

Lukas Renggli
>> BTW, does OB 1.1.4 work on both Pharo1.0 and Pharo1.1?

I don't know what OB 1.1.4 is, but the very latest code work in Pharo
1.0 and the latest Pharo 1.1.

Lukas

>
> Hi Dale. I have just testes and not only seems to work but also all tests
> are green :)
>
>
>>
>> Dale
>>
>> ----- "Mariano Martinez Peck" <[hidden email]> wrote:
>>
>> | On Wed, May 12, 2010 at 11:52 PM, Dale Henrichs
>> | <[hidden email]>wrote:
>> |
>> | >
>> | > ----- "Mariano Martinez Peck" <[hidden email]> wrote:
>> | >
>> | > | Hi Dale. I took a PharoCore-1.1-11355-UNSTABLE.1  image and I
>> | > | evaluated:
>> | > |
>> | > | ConfigurationOfSeaside project latestVersion load: #( 'Seaside
>> | 3.0'
>> | > | 'Seaside
>> | > | 3.0 Tests' ).
>> | > |
>> | > | In this core image, of course, I don't have OB installed. I
>> | remember
>> | > | that
>> | > | Seaside - OB was installed ONLY if OB was present in the image.
>> | > | However,
>> | > | this is loading OB :(
>> | >
>> | > I believe that Lukas and Julian decided that they wanted everything
>> | loaded
>> | > by default in Seaside3.0 including the parts that require OB, so I
>> | changed
>> | > the config...
>> | >
>> |
>> |
>> | OK...
>> |
>> |
>> |
>> | >
>> | > |
>> | > | Any quotes ?
>> | > |
>> | > | In addition (and a bit offtopic), Lukas and Alexandre made OB to
>> | work
>> | > | on
>> | > | Pharo 1.1. The ConfigurationOfOmnibroswer version 1.1.4
>> | > | So, it would be cool if we can define a new version of
>> | > | ConfigurationOfSeaside so that to be able to load Seaside 2.8 and
>> | 3.0
>> | > | in
>> | > | Pharo 1.1. Of course, you should use OB 1.1.4.
>> | > | I know you also use Conf of OB in GALSS...
>> | >
>> | > I'm trying to push a GLASS release out (Metacello 1.0-beta.26.1 was
>> | the
>> | > first step:), but if the release drags too long, I'll push out a
>> | new
>> | > Seaside3.0 version...
>> | >
>> | >
>> | Ok...but that new Seaside 3.0 version will use 1.1.4 of OB ?
>> | Otherwhise,
>> | don't worry. I can create a new version of Seside 3.0 for us (Pharo
>> | 1.1)
>> | that uses OB 1.1.4. I just asked it can it was also useful for you.
>> | Just let
>> | me know.
>> |
>> | Cheers
>> |
>> | Mariano
>
>



--
Lukas Renggli
www.lukas-renggli.ch
Reply | Threaded
Open this post in threaded view
|

Re: Conf for seaside 3.0 is loading OB in a Core image :(

Dale
Sorry about the question ... I was hitting errors in OB-Metacello code in Pharo1.1 that wasn't producing errors in Pharo1.0, but the difference turned out to be that there was an incorrect specification in my code that was probably not even used in the older version of OB...I'll be releasing a newer version of OB-Metacello with the Pharo1.1 (actually OB 1.1.4 compat) fixes...

Dale
----- "Lukas Renggli" <[hidden email]> wrote:

| >> BTW, does OB 1.1.4 work on both Pharo1.0 and Pharo1.1?
|
| I don't know what OB 1.1.4 is, but the very latest code work in Pharo
| 1.0 and the latest Pharo 1.1.
|
| Lukas
|
| >
| > Hi Dale. I have just testes and not only seems to work but also all
| tests
| > are green :)
| >
| >
| >>
| >> Dale
| >>
| >> ----- "Mariano Martinez Peck" <[hidden email]> wrote:
| >>
| >> | On Wed, May 12, 2010 at 11:52 PM, Dale Henrichs
| >> | <[hidden email]>wrote:
| >> |
| >> | >
| >> | > ----- "Mariano Martinez Peck" <[hidden email]> wrote:
| >> | >
| >> | > | Hi Dale. I took a PharoCore-1.1-11355-UNSTABLE.1  image and
| I
| >> | > | evaluated:
| >> | > |
| >> | > | ConfigurationOfSeaside project latestVersion load: #(
| 'Seaside
| >> | 3.0'
| >> | > | 'Seaside
| >> | > | 3.0 Tests' ).
| >> | > |
| >> | > | In this core image, of course, I don't have OB installed. I
| >> | remember
| >> | > | that
| >> | > | Seaside - OB was installed ONLY if OB was present in the
| image.
| >> | > | However,
| >> | > | this is loading OB :(
| >> | >
| >> | > I believe that Lukas and Julian decided that they wanted
| everything
| >> | loaded
| >> | > by default in Seaside3.0 including the parts that require OB,
| so I
| >> | changed
| >> | > the config...
| >> | >
| >> |
| >> |
| >> | OK...
| >> |
| >> |
| >> |
| >> | >
| >> | > |
| >> | > | Any quotes ?
| >> | > |
| >> | > | In addition (and a bit offtopic), Lukas and Alexandre made OB
| to
| >> | work
| >> | > | on
| >> | > | Pharo 1.1. The ConfigurationOfOmnibroswer version 1.1.4
| >> | > | So, it would be cool if we can define a new version of
| >> | > | ConfigurationOfSeaside so that to be able to load Seaside 2.8
| and
| >> | 3.0
| >> | > | in
| >> | > | Pharo 1.1. Of course, you should use OB 1.1.4.
| >> | > | I know you also use Conf of OB in GALSS...
| >> | >
| >> | > I'm trying to push a GLASS release out (Metacello 1.0-beta.26.1
| was
| >> | the
| >> | > first step:), but if the release drags too long, I'll push out
| a
| >> | new
| >> | > Seaside3.0 version...
| >> | >
| >> | >
| >> | Ok...but that new Seaside 3.0 version will use 1.1.4 of OB ?
| >> | Otherwhise,
| >> | don't worry. I can create a new version of Seside 3.0 for us
| (Pharo
| >> | 1.1)
| >> | that uses OB 1.1.4. I just asked it can it was also useful for
| you.
| >> | Just let
| >> | me know.
| >> |
| >> | Cheers
| >> |
| >> | Mariano
| >
| >
|
|
|
| --
| Lukas Renggli
| www.lukas-renggli.ch