-----Original Message-----
From:
pharo-project-bounces@lists.gforge.inria.fr [mailto:
pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of
Matthias Berth
Sent: Saturday, January 09, 2010 6:09 PM
To:
Pharo-project@lists.gforge.inria.frSubject: Re:
[Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
Hi
Bill,
this one works for me with the current pharo core 1.0 rc1,
update upto 10505
"execute this:"
Gofer new
� �
� squeaksource: 'Loader';
� � � package:
'Loader';
� � � load.
"then this"
Loader new load:
'Pharo' version: '1.0-rc2.10505'.
"then this"
Loader new
�
� � load: 'Seaside28' version: '2.8.4.2'
The "Loader new
load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo
packages. I guess you won't need that just to get seaside
working.
Ask Esteban Lorenzano for details about hw this works
:)
Cheers
Matthias
2010/1/9 Schwab,Wilhelm K <
bschwab@anest.ufl.edu>:
> Two can be tired of
this.� I could just use the official Seaside
> images, but I
thought it might be nice to help with testing the
> monthly
images.� I won't get very far with that if Seaside won't
load.
>
>
> ________________________________
> From:
pharo-project-bounces@lists.gforge.inria.fr>
[mailto:
pharo-project-bounces@lists.gforge.inria.fr] On Behalf
Of
> Mariano Martinez Peck
> Sent: Saturday, January 09, 2010
4:38 PM
> To:
Pharo-project@lists.gforge.inria.fr> Subject: Re:
[Pharo-project] [BetaTesting] [ANN]
>
Pharo1.0-10505-rc1dev10.01.1
>
>
>
> 2010/1/9
Schwab,Wilhelm K <
bschwab@anest.ufl.edu>
>>
>>
Mariano,
>>
>> The reason I objected (and continue to do
so) to clobbering the web
>> image is that complete chaos of how to
install things comes into
>> play.� Assuming that I know what
YOU said on the subject is a stretch
>> to say the least: try a
search engine on the subject.
>>
>
> I am a bit tired
of this. I will answer for the last time and I hope
> you
>
understand: Do you want seaside ?
>
> 1) Volunteer yourself to
build Web images. It is easy to ask, but what
> about
doing?
>
> 2) Take the Web Image before, analize how seaside was
installed and do
> it by yourself. I cannot take it more than half an
hour.
>
> 3) Use official seaside image
>
> 4)
Report what doesn't work with the ConfigurationOfSeaside in
>
Metacello mailing list so that everybody can collaborate and fix it.
>
If you see that mailing list, I did exactly that. Just saying "doesn't
work"� does not help.
>
> Cheers
>
>
Mariano
>
>>
>> BTW, it does not work.� There
is very little I can do until Seaside loads.
>>
>>
Bill
>>
>> ________________________________
>>
From:
pharo-project-bounces@lists.gforge.inria.fr>>
[mailto:
pharo-project-bounces@lists.gforge.inria.fr] On Behalf
Of
>> Mariano Martinez Peck
>> Sent: Saturday, January 09,
2010 4:08 PM
>> To:
Pharo-project@lists.gforge.inria.fr>> Subject:
Re: [Pharo-project] [BetaTesting] [ANN]
>>
Pharo1.0-10505-rc1dev10.01.1
>>
>>
>>
>>
2010/1/9 Schwab,Wilhelm K <
bschwab@anest.ufl.edu>
>>>
>>>
Gofer seaside28 load
>>>
>>
>> I didn't say
that. I said:
>>
>> Gofer new
>>
��� squeaksource: 'MetacelloRepository';
>>
��� package: 'ConfigurationOfSeaside28';
>>
��� load.
>>
>> (Smalltalk at:
#ConfigurationOfSeaside28) load
>>
>> And I also said I
was not sure of this is working.
>>
>>
Cheers
>>
>>
Mariano
>>
>>>
>>> does not work.�
What is the correct way to install Seaside - I can't
>>> do much
w/o it.
>>>
>>>
________________________________
>>> From:
pharo-project-bounces@lists.gforge.inria.fr>>>
[mailto:
pharo-project-bounces@lists.gforge.inria.fr] On Behalf
Of
>>> Mariano Martinez Peck
>>> Sent: Saturday,
January 09, 2010 3:01 PM
>>> To:
Pharo-project@lists.gforge.inria.fr>>>
Subject: Re: [Pharo-project] [BetaTesting] [ANN]
>>>
Pharo1.0-10505-rc1dev10.01.1
>>>
>>>
>>>
>>>
2010/1/9 Miguel Enrique Cob� Martinez <
miguel.coba@gmail.com>
>>>>
>>>>
Hi Mariano,
>>>>
>>>> good job. Some
feedback.
>>>>
>>>> The installScript has
unused variables and your proxy settings exposed.
>>>> Maybe
this should be deleted from the final
build.
>>>>
>>>
>>> hahahahah I knew
I was going to forget about that :( Thanks. Some
>>> bash guru
that help me to automatize this? I would like something
>>> that
automatically removes that from the file if it is found.
>>> Can
you help me Miguel ?
>>>
>>>>
>>>>
Shouldn't be this a RC 2? because there is a new build process
and
>>>> has nothing to do with the
RC1?
>>>>
>>>
>>> I thought about
putting it RC2, actually, I was going to do that.
>>> But as the
PharoCore was named rc1, I din't want to name it rc2
>>> because
maybe it was confusing.
>>> I am not sure, thus. What do you
think ?
>>>
>>>>
>>>> Also, the
changes files, shouldn't be compressed for each RC and
>>>>
for the final release?
>>>
>>> Excellent point. Do
you rather to Smalltalk >> condenseChanges ?� It
>>>
can be perfectly added. Right now, we are doing all
this:
>>>
>>>
>>> ���
MCFileBasedRepository flushAllCaches.
>>> ���
MCDefinition clearInstances.
>>> ��� Smalltalk
removeEmptyMessageCategories.
>>> ��� Utilities
cleanseOtherworldlySteppers.
>>> ��� Undeclared
removeUnreferencedKeys.
>>> ��� Categorizer
sortAllCategories.
>>> ��� Symbol
compactSymbolTable.
>>> ��� Smalltalk at:
#ReleaseBuilderDeveloper ifPresent: [:builder |
>>> builder new
fixObsoleteReferences].
>>> ��� RequiredSelectors
initialize.
>>> ��� ProvidedSelectors
initialize.
>>> ��� LocalSends
initialize.
>>> ��� Smalltalk organization
removeEmptyCategories.
>>> ��� SystemBrowser
removeObsolete.
>>> ��� TheWorldMenu
removeObsolete.
>>> ��� AppRegistry
removeObsolete.
>>> ��� Set
rehashAllSets.
>>> ��� Smalltalk
cleanOutUndeclared.
>>> ��� Smalltalk
garbageCollect.
>>>
>>>
>>> Do you think
something else should be addded?�� Maybe we can
reuse
>>> ScriptLoader cleanings
?
>>>
>>>
>>>>
>>>>
Also, the packages.txt file talks about PharoCore1.0 (#10505).
Has
>>>> someone thought about the name shown in
System->About:
>>>>
>>>>
PharoCore1.0rc1
>>>> Latest update:
#10505
>>>>
>>>> Because this is not a
PharoCore image. Shouldn't this read
>>>> something
like
>>>>
>>>> Pharo 1.0 Dev
image.
>>>> Based on PharoCore1.0rc1
>>>>
Latest update: #10505
>>>>
>>>
>>>
Yes, that's true. I agree. At least it was not "my falt" as it
was
>>> already like that. But I am agree we should change that.
However, I
>>> don't know how to do it.
>>> Maybe
something related to SystemVersion? Any help
?
>>>
>>>
>>>>
>>>>
What about the disabling of software updates in the Pharo
dev/web
>>>> images? Will this be implemented or a careful
update stream will be
>>>> made in order to not break a dev
image with overrides (real
>>>> difficult I
think).
>>>>
>>>
>>> Maybe. But in
addition, sometimes there are bugs that updating just
>>> fix
them. I am not sure if I want to disable. I rather warn people about
it.
>>> Do you know if we break some overrrides doing an
update?
>>>
>>>>
>>>> Maybe all
this setup can be put in a post-script in the
>>>>
ConfigurationOfPharo class.
>>>
>>> It is. We have
pre and post do its. So, no problem
:)
>>>
>>>>
>>>> That's all for
now. I'm going to use this image to work the
>>>> following
days.
>>>>
>>>>
>>>> Cheers and
keep the good work.
>>>>
>>>
>>>
Thanks Miguel for the excellent feedback. Let's hope to build
better
>>> images!
>>>
>>>
Mariano
>>>
>>>
>>>>
>>>>
--
>>>> Miguel Cob�
>>>>
http://miguel.leugim.com.mx>>>>
>>>>
>>>>
_______________________________________________
>>>>
Pharo-project mailing list
>>>>
Pharo-project@lists.gforge.inria.fr>>>>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
_______________________________________________
>>>
Pharo-project mailing list
>>>
Pharo-project@lists.gforge.inria.fr>>>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>>
_______________________________________________
>> Pharo-project
mailing list
>>
Pharo-project@lists.gforge.inria.fr>>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
_______________________________________________
> Pharo-project
mailing list
>
Pharo-project@lists.gforge.inria.fr>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project
mailing list
Pharo-project@lists.gforge.inria.frhttp://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project
mailing list
Pharo-project@lists.gforge.inria.frhttp://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project