[ANN] Seaside 3.0.3 release

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

Re: [ANN] Seaside 3.0.3 release

sebastianconcept@gmail.co
Fritz,

that's why periodical fresh starts are the way to go (and why being too much conservative about old images hurts).

All,

frustrations shouldn't be "a feature" (and they are the most sad way to "learn" and provide "education" (note the quotes)). 

As long as we (here with seaside but this happen to any project) can consistently provide sweet fresh experiences, we're fine (and as long as we start to shooting our own foots we're screwed)

duh right? 

let the practical results tell you if duh or not duh


suggestions? two entries in the FAQ:
1. how to load seaside in pharo (chose only one best way to do it, not two, one; stick to it and don't distract the reader, if you can't help it then add it as references to other posts but don't distract the newcomer (or the veteran in a hurry) with "higher nerdisms" that are irrelevant at that poin)
2. how to upgrade seaside in pharo (same criteria as 1)
3. don't be afraid of being freaking sued if you're trying to freaking help




On Dec 20, 2010, at 10:42 PM, Fritz Schenk wrote:

Indeed, when I close the old browser and open a new one, the new one works.
I wish there was some warning of this 'feature'.

Thanks

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Seaside 3.0.3 release

Dale Henrichs
In reply to this post by mozillanerd
Fritz,

I was probably being a little too aggressive in "requiring" the latest
version of OmniBrowser when I updated the ConfigurationOfSeaside30 (I
don't remember specifically), so I'll take the blame on this one:)

Pharo, Metacello, and Seaside30 are all changing at different rates over
time so I tend to go with what works for me (which is usually later
versions of the packages) rather than testing the large number of
potential package versions ...

While there is no tool support at the moment, you _can_ find out what
Metacello will load _before_ actually doing the load (and you can look
at what was actually loaded ... without having to scan through the
Transcrtip), but without being familiar with which packages go with
which projects, it may not be that useful..

Dale

On 12/20/2010 04:42 PM, Fritz Schenk wrote:
> Indeed, when I close the old browser and open a new one, the new one works.
> I wish there was some warning of this 'feature'.
>
> Thanks
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Seaside 3.0.3 release

mozillanerd
Thanks for the explanation. I kind of assumed that when '3.0.3' was mentioned,
the configuration would say 3.0.3. So what goes on here is that
ConfigurationOfSeaside30 is some sort of pseudonym for the latest.
Confusing,
and then the IDE simply is not letting me know that a refresh is needed. \


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Seaside 3.0.3 release

Dale Henrichs
Fritz,

The ConfigurationOfSeaside30 class is contains the "version
specifications" for all Seaside3.0 versions. The
ConfigurationOfSeaside30 mcz file manages the version of the "version
specifications".

So you need to latest ConfigurationOfSeaside30 mcz file to get the
specification of the latest version and then you need to load the latest
specified version in the ConfigurationOfSeaside30 class.

Providing better tool support for Metacello is definitely in the plans
... it's just a matter of time for the development tools to evolve to
include Metacello support...

Dale

On 12/21/2010 08:15 PM, Fritz Schenk wrote:

> Thanks for the explanation. I kind of assumed that when '3.0.3' was mentioned,
> the configuration would say 3.0.3. So what goes on here is that
> ConfigurationOfSeaside30 is some sort of pseudonym for the latest.
> Confusing,
> and then the IDE simply is not letting me know that a refresh is needed. \
>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Seaside 3.0.3 release

Tudor Girba
In reply to this post by Dale Henrichs
Hi Dale,

Why does Seaside need to load OB?

Cheers,
Doru


On 21 Dec 2010, at 02:22, Dale Henrichs wrote:

> Fritz,
>
> I was probably being a little too aggressive in "requiring" the latest version of OmniBrowser when I updated the ConfigurationOfSeaside30 (I don't remember specifically), so I'll take the blame on this one:)
>
> Pharo, Metacello, and Seaside30 are all changing at different rates over time so I tend to go with what works for me (which is usually later versions of the packages) rather than testing the large number of potential package versions ...
>
> While there is no tool support at the moment, you _can_ find out what Metacello will load _before_ actually doing the load (and you can look at what was actually loaded ... without having to scan through the Transcrtip), but without being familiar with which packages go with which projects, it may not be that useful..
>
> Dale
>
> On 12/20/2010 04:42 PM, Fritz Schenk wrote:
>> Indeed, when I close the old browser and open a new one, the new one works.
>> I wish there was some warning of this 'feature'.
>>
>> Thanks
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

--
www.tudorgirba.com

"Obvious things are difficult to teach."



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Seaside 3.0.3 release

Julian Fitzell-2
The Seaside-Tools-OmniBrowser package needs OB. You don't *have* to
load that of course but it is loaded by the default configuration.

Julian

On Fri, Dec 24, 2010 at 2:24 PM, Tudor Girba <[hidden email]> wrote:

> Hi Dale,
>
> Why does Seaside need to load OB?
>
> Cheers,
> Doru
>
>
> On 21 Dec 2010, at 02:22, Dale Henrichs wrote:
>
>> Fritz,
>>
>> I was probably being a little too aggressive in "requiring" the latest version of OmniBrowser when I updated the ConfigurationOfSeaside30 (I don't remember specifically), so I'll take the blame on this one:)
>>
>> Pharo, Metacello, and Seaside30 are all changing at different rates over time so I tend to go with what works for me (which is usually later versions of the packages) rather than testing the large number of potential package versions ...
>>
>> While there is no tool support at the moment, you _can_ find out what Metacello will load _before_ actually doing the load (and you can look at what was actually loaded ... without having to scan through the Transcrtip), but without being familiar with which packages go with which projects, it may not be that useful..
>>
>> Dale
>>
>> On 12/20/2010 04:42 PM, Fritz Schenk wrote:
>>> Indeed, when I close the old browser and open a new one, the new one works.
>>> I wish there was some warning of this 'feature'.
>>>
>>> Thanks
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> --
> www.tudorgirba.com
>
> "Obvious things are difficult to teach."
>
>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Seaside 3.0.3 release

Tudor Girba
I see.

I took a look at the configuration, and as I understand, I can load the Core group to get the basic functionality. I will give it a try.

Cheers,
Doru


On 24 Dec 2010, at 23:28, Julian Fitzell wrote:

> The Seaside-Tools-OmniBrowser package needs OB. You don't *have* to
> load that of course but it is loaded by the default configuration.
>
> Julian
>
> On Fri, Dec 24, 2010 at 2:24 PM, Tudor Girba <[hidden email]> wrote:
>> Hi Dale,
>>
>> Why does Seaside need to load OB?
>>
>> Cheers,
>> Doru
>>
>>
>> On 21 Dec 2010, at 02:22, Dale Henrichs wrote:
>>
>>> Fritz,
>>>
>>> I was probably being a little too aggressive in "requiring" the latest version of OmniBrowser when I updated the ConfigurationOfSeaside30 (I don't remember specifically), so I'll take the blame on this one:)
>>>
>>> Pharo, Metacello, and Seaside30 are all changing at different rates over time so I tend to go with what works for me (which is usually later versions of the packages) rather than testing the large number of potential package versions ...
>>>
>>> While there is no tool support at the moment, you _can_ find out what Metacello will load _before_ actually doing the load (and you can look at what was actually loaded ... without having to scan through the Transcrtip), but without being familiar with which packages go with which projects, it may not be that useful..
>>>
>>> Dale
>>>
>>> On 12/20/2010 04:42 PM, Fritz Schenk wrote:
>>>> Indeed, when I close the old browser and open a new one, the new one works.
>>>> I wish there was some warning of this 'feature'.
>>>>
>>>> Thanks
>>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> [hidden email]
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>> --
>> www.tudorgirba.com
>>
>> "Obvious things are difficult to teach."
>>
>>
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

--
www.tudorgirba.com

"Live like you mean it."

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
12