16 Feb
2007
16 Feb
'07
5:54 p.m.
how come when I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier packages?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
16 Feb
16 Feb
6:03 p.m.
Brad Fuller wrote:
how come when I try to load from
http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier packages?
Actually, let me ask a better question:
what is the best/preferred way of creating a Seaside/Pier/Magma image
and bringing it up to date?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
6:52 p.m.
Brad Fuller wrote:
Brad Fuller wrote:
The preferred way to generate my version of the SMP
image at the moment
is to edit the script on this wiki. Or more importantly fix the packages
that this script loads.
http://squeak310.pbwiki.com/Seaside-Magma-Pier
Then, this image will be automatically generated whenever the
http://squeak310.pbwiki.com/Make%20Seaside-Magma-Pier page is updated or
the image upon which it depends is updated to be a new release candidate.
This final step, the triggering of a build as a dependency is in the
process of being debugged.
The output will be available in
http://squeak.warwick.st/auto-build/output/make/391/NEW_RC/ in folder SMP
Nevertheless the script is there for you to see clearly the installing
steps if not the configuring steps.
I think that you can run it manually like so
#squeak Squeak3.9-final-7067.image http://installer.pbwiki.com/f/IBS.st
Installer path=http://squeak310.pbwiki.com/ install=From39To391
Installer install=Seaside-Magma-Pier MCWorkingCopy report=workingCopies
to="*.txt" SmalltalkImage save=SMP.image +quit
but some (hopefully very minor) fixes will be needed
Keith
___________________________________________________________
Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free.
http://uk.docs.yahoo.com/trueswitch2.html
how come when I try to load from
http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier packages?
Actually, let me ask a better question:
what is the best/preferred way of creating a Seaside/Pier/Magma image
and bringing it up to date
7:29 p.m.
Keith Hodges wrote:
Brad Fuller wrote:
thanks Keith. I'll try it manually and see how it goes.
Brad Fuller wrote:
The preferred way to generate my version of the SMP
image at the moment
is to edit the script on this wiki. Or more importantly fix the packages
that this script loads.
http://squeak310.pbwiki.com/Seaside-Magma-Pier
Then, this image will be automatically generated whenever the
http://squeak310.pbwiki.com/Make%20Seaside-Magma-Pier page is updated or
the image upon which it depends is updated to be a new release candidate.
This final step, the triggering of a build as a dependency is in the
process of being debugged.
The output will be available in
http://squeak.warwick.st/auto-build/output/make/391/NEW_RC/ in folder SMP
Nevertheless the script is there for you to see clearly the installing
steps if not the configuring steps.
I think that you can run it manually like so
#squeak Squeak3.9-final-7067.image http://installer.pbwiki.com/f/IBS.st
Installer path=http://squeak310.pbwiki.com/ install=From39To391
Installer install=Seaside-Magma-Pier MCWorkingCopy report=workingCopies
to="*.txt" SmalltalkImage save=SMP.image +quit
but some (hopefully very minor) fixes will be needed how come when I try to load from
http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier packages?
Actually, let me ask a better question:
what is the best/preferred way of creating a Seaside/Pier/Magma image
and bringing it up to date 
6:38 p.m.
how come when I try to load from
http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
7:30 p.m.
Lukas Renggli wrote:
ahh... thanks Lukas!
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
how come when
I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
8:14 p.m.
Lukas Renggli wrote:
Lucas,
Syntax error when "loading" Pier-All-lr.163:
Pier-Seaside-Widgets
PRSearchWidget>>go
self items in: [ :Name already used in this class ->items |
items notEmpty ifTrue: [
self context: (self context structure: items first) ] ]
how come when
I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside Cheers,
Lukas
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
8:22 p.m.
Brad Fuller wrote:
Lukas Renggli wrote:
Lucas,
Syntax error when "loading" Pier-All-lr.163:
Pier-Seaside-Widgets
PRSearchWidget>>go
self items in: [ :Name already used in this class ->items |
items notEmpty ifTrue: [
self context: (self context structure: items first) ] ]
and why do I receive
"Error: Could not find version 'Pier-Model-lr.105'
when merging Pier-All-lr?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
how come
when I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
8:59 p.m.
and why do I receive
"Error: Could not find version 'Pier-Model-lr.105'
when merging Pier-All-lr?
Again probably a bug in Monticello, since I see this version in my
repository. Add the repository http://mc.lukas-renggli.ch/pier to all
the dependencies of Pier-All, e.g. Pier-Model, Pier-Seaside, ... so
that Monticello can find the files to merge.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
9:13 p.m.
Lukas Renggli wrote:
ok, thanks
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
and why do I
receive
"Error: Could not find version 'Pier-Model-lr.105'
when merging Pier-All-lr?
Again probably a bug in Monticello, since I see this version in my
repository. Add the repository http://mc.lukas-renggli.ch/pier to all
the dependencies of Pier-All, e.g. Pier-Model, Pier-Seaside, ... so
that Monticello can find the files to merge.
8:56 p.m.
PRSearchWidget>>go
self items in: [ :Name already used in this class ->items |
items notEmpty ifTrue: [
self context: (self context structure: items first) ] ]
Oh god, that is a long standing bug in Monticello that strikes again:
there are some cases when the load order is wrong and causes a
compile error. In this case it is the simples just to delete the
method and load the package again.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
24 Feb
24 Feb
2:05 a.m.
Lukas Renggli wrote:
I think _pretty_much_ have the latest Magritte/Pier running. Took me a
while.
However, I did come across this again while upgrading. I deleted the
method PRSearchWidget>>go and upgraded. Now, though, search doesn't
work. When I press return, it doesn't do anything.
And, when you look at the components list (when adding a component)
there are TWO search component. I tried both. The second one behaves as
I have described. The first one actual seems to do something (the
hourglass goes on like it's "working"). But, it never finds anything.
Just to add a bit more mystery: search never worked in the Pier version
that was on SqueakMap. It never found any word. Although, the text
cursor went away after hitting return.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
PRSearchWidget>>go
self items in: [ :Name already used in this class ->items |
items notEmpty ifTrue: [
self context: (self context structure: items first) ] ]
Oh god, that is a long standing bug in Monticello that strikes again:
there are some cases when the load order is wrong and causes a
compile error. In this case it is the simples just to delete the
method and load the package again.
8:57 a.m.
However, I did come across this again while upgrading.
I deleted the
method PRSearchWidget>>go and upgraded. Now, though, search doesn't
work. When I press return, it doesn't do anything.
Do you have the latest version of Pier-Seaside? I just recently fixed
this problem.
And, when you look at the components list (when adding
a component)
there are TWO search component. I tried both. The second one
behaves as
I have described. The first one actual seems to do something (the
hourglass goes on like it's "working"). But, it never finds anything.
Strange, I just have one. What about in your image? Try to display
the changes of Pier-Seaside and see if there any load-artifacts left
over by Monticello.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
6:35 p.m.
Lukas Renggli wrote:
I have: Pier-Seaside-lr.138.mcz
There is one newer version from Pierre, which I just loaded. No change.
I don't see anything strange. I put in a halt in a couple of methods so
I could trace what was happening but it never made it to the methods.
(that's when I went back to Pier and saw two components for search.) So
those are there in the changes, but those are mine.
Hmm, I don't think this is related, but when I updated Pier before I
received your instructions on PRPierFrame initialize. I replied to
create a new kernel. That gave me two piers with the same name. In the
Pier Browser, they are both there. I'd like to get rid of the first one.
How can I do that.
However, I don't see how this would be related.
Thanks for the reply and help, Lukas!
brad
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
However, I did
come across this again while upgrading. I deleted the
method PRSearchWidget>>go and upgraded. Now, though, search doesn't
work. When I press return, it doesn't do anything.
Do you have the latest version of Pier-Seaside? I just recently fixed
this problem. And, when you look at the components list (when
adding a component)
there are TWO search component. I tried both. The second one
behaves as
I have described. The first one actual seems to do something (the
hourglass goes on like it's "working"). But, it never finds anything.
Strange, I just have one. What about in your image? Try to display
the changes of Pier-Seaside and see if there any load-artifacts left
over by Monticello.
8:27 p.m.
However, I did come across this again while upgrading.
I deleted the
method PRSearchWidget>>go and upgraded. Now, though, search doesn't
work. When I press return, it doesn't do anything.
Do you have the latest version of Pier-Seaside? I just recently fixed
this problem. And, when you look at the components list (when adding
a component)
there are TWO search component. I tried both. The second one
behaves as
I have described. The first one actual seems to do something (the
hourglass goes on like it's "working"). But, it never finds
anything.
Strange, I just have one. What about in your image? Try to display
the changes of Pier-Seaside and see if there any load-artifacts left
over by Monticello. Hmm, I don't think this is related, but when I
updated Pier before I
received your instructions on PRPierFrame initialize. I replied to
create a new kernel. That gave me two piers with the same name. In the
Pier Browser, they are both there. I'd like to get rid of the first
one. How can I do that.
Evaluate
PRKernel instances inspect
and then remove the one you don't want anymore. Note that if you have
an entry point defined in Seaside using the removed kernel, it won't
disappear from the Smalltalk image.
However, I don't see how this would be related.
No, that's certainly not the problem for the two search boxes.
Note that the Search Widget is one of the Widgets with two lives, one
when you have SULibrary (Scriptaculous) in your list of libraries and
one if no AJAX support is available. Depending on the mode it behaves
different, both modes work for me.
Note that you also might want to check the settings of the Search
Widget, it might well be that you filter out some types and therefor
see no results.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
9:07 p.m.
Lukas Renggli wrote:
The expression used to calculate the list of components is the
following:
Array streamContents: [ :stream |
PRWidget allSubclassesDo: [ :each |
each isAbstract
ifFalse: [ stream nextPut: each ] ].
WAComponent allSubclassesDo: [ :each |
each canBeRoot
ifTrue: [ stream nextPut: each ] ] ]
In my image this results in:
{PRCommandsWidget . PRHeaderWidget . PRNavigationWidget .
PRPathWidget . PRReferencesWidget . PRTreeWidget . PRChildrenWidget .
PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget .
PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget .
PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser .
WAFileLibraryExample . WAAllCanvasTests . WAAllTests .
WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore .
WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame .
WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo}
I get pretty much the same thing... a list like this (a bit different)
Maybe you have some other Seaside/Magritte/Pier code loaded that
provides a different search component?
I have SULibrary loaded and when I removed it, the search worked! So,
progress. I have the latest Scriptaculous installed. Anything special
about Pier in regard to this?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
Hmm, I don't think this is related, but when
I updated Pier before I
received your instructions on PRPierFrame initialize. I replied to
create a new kernel. That gave me two piers with the same name. In the
Pier Browser, they are both there. I'd like to get rid of the first
one. How can I do that.
Evaluate
PRKernel instances inspect
and then remove the one you don't want anymore. Note that if you have
an entry point defined in Seaside using the removed kernel, it won't
disappear from the Smalltalk image.
However, I don't see how this would be
related.
No, that's certainly not the problem for the two search boxes.
Note that the Search Widget is one of the Widgets with two lives, one
when you have SULibrary (Scriptaculous) in your list of libraries and
one if no AJAX support is available. Depending on the mode it behaves
different, both modes work for me.
9:36 p.m.
{PRCommandsWidget . PRHeaderWidget . PRNavigationWidget .
PRPathWidget . PRReferencesWidget . PRTreeWidget . PRChildrenWidget .
PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget .
PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget .
PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser .
WAFileLibraryExample . WAAllCanvasTests . WAAllTests .
WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore .
WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame .
WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo}
I get pretty much the same thing... a list like this (a bit different)
10:18 p.m.
Lukas Renggli wrote:
No obsolete classes in the list?
No, just two PRSearchWidget
{PRCommandsWidget . PRHeaderWidget .
PRNavigationWidget .
PRPathWidget . PRReferencesWidget . PRTreeWidget . PRChildrenWidget .
PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget .
PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget .
PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser .
WAFileLibraryExample . WAAllCanvasTests . WAAllTests .
WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore .
WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame .
WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo}
I get pretty
much the same thing... a list like this (a bit different)
11:35 p.m.
{PRCommandsWidget . PRHeaderWidget . PRNavigationWidget .
PRPathWidget . PRReferencesWidget . PRTreeWidget .
PRChildrenWidget .
PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget .
PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget .
PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser .
WAFileLibraryExample . WAAllCanvasTests . WAAllTests .
WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore .
WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame .
WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo}
I get pretty
much the same thing... a list like this (a bit
different)
25 Feb
25 Feb
12:10 a.m.
Lukas Renggli wrote:
Then your Smalltalk class hierarchy must be corrupt. I don't know
exactly how to fix that. Maybe inspect the superclass of
PRSearchWidget and see if there is anything wrong with the subclass
declaration?
If I go up one to it's superclass (PRStructuresWidget) and 'show
hierarchy' there are two PRSearchWidget shown:
PRSearchWidget #('searchText' 'items')
PRSearchWidget #('searchText')
somehow PRSearchWidget #('searchText') got in there. I can only assume
that it's an older definition. I don't know how to un-reference it (if
that's the right term in this case.)
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
No obsolete classes in the list?
No, just two
PRSearchWidget
16 Feb
16 Feb
9:10 p.m.
Lukas Renggli wrote:
Hmm... I don't see a package named RsRss in that repo.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
how come when
I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
9:30 p.m.
Brad Fuller wrote:
Lukas Renggli wrote:
Hmm... I don't see a package named RsRss in that repo.
just got it from
http://www.squeaksource.com/rsrss
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
how come
when I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
9:37 p.m.
The Blog
package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
Hmm... I don't see a package named RsRss in that repo.
9:34 p.m.
Lukas Renggli wrote:
Looks like there is just one more package to go
Pier-Magma
but I have this problem:
This package depends on the following classes:
PRPierControlPanel
You must resolve these dependencies before you will be able to load
these definitions:
PRPierControlPanel>>deleteRepositoryKernel:
PRPierControlPanel>>renderPRMagmaPersistency:kernel:on:
I've loaded all the other pier packages. Do you know where this is?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
how come when
I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
17 Feb
17 Feb
12:39 a.m.
Brad Fuller wrote:
Lukas Renggli wrote:
Looks like there is just one more package to go
Pier-Magma
but I have this problem:
This package depends on the following classes:
PRPierControlPanel
You must resolve these dependencies before you will be able to load
these definitions:
PRPierControlPanel>>deleteRepositoryKernel:
PRPierControlPanel>>renderPRMagmaPersistency:kernel:on:
I've loaded all the other pier packages. Do you know where this is?
It is in Seaside 2.6b branch and I merged it into Seaside 2.7 as well,
however for some reason the main seaside practicioners have not got it
in their latest. So if you look for my last contribution to Seaside 2.7a
it will definitely be there. (kph)
This is what I mean by 'small' things to sort out.
Keith
___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of
use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html
how come
when I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
22 Feb
22 Feb
9:56 p.m.
Keith Hodges wrote:
Brad Fuller wrote:
Keith,
I have the latest Seaside (Seaside2.7a1-pmm.153.mcz in config, but MC
says v203... don't know why that is), but I still receive this
dependency problem
This package depends on the following classes:
PRPierControlPanel
Lukas Renggli wrote:
Looks like there is just one more package to go
Pier-Magma
but I have this problem:
This package depends on the following classes:
PRPierControlPanel
You must resolve these dependencies before you will be able to load
these definitions:
PRPierControlPanel>>deleteRepositoryKernel:
PRPierControlPanel>>renderPRMagmaPersistency:kernel:on:
I've loaded all the other pier packages. Do you know where this is?
It is in Seaside 2.6b branch and I merged it into Seaside 2.7 as well,
however for some reason the main seaside practicioners have not got it
in their latest. So if you look for my last contribution to Seaside 2.7a
it will definitely be there. (kph)
This is what I mean by 'small' things to sort out. how come
when I try to load from http://mc.lukas-renggli.ch/pier for
"blog" package I receive "This package depends on the following
classes:"
and there are many of them. Is there a better way to load Pier
packages?
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
23 Feb
23 Feb
3:24 p.m.
Brad Fuller wrote:
Keith Hodges wrote:
Pier Control Panel is in one of my versions of Pier-Seaside, I dont
think lukas accepted it into his latest.
So after talking with lukas about it I suggested reorganising things to
produce a separate Pier_Persistency manager package. I am planning to
have a go at this over the weekend.
I am very sorry that it has taken me so long to get around to sorting
the SMP image out.
Keith
___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of
use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html
Brad Fuller wrote:
Keith,
I have the latest Seaside (Seaside2.7a1-pmm.153.mcz in config, but MC
says v203... don't know why that is), but I still receive this
dependency problem
This package depends on the following classes:
PRPierControlPanel
Lukas Renggli wrote:
It is in Seaside 2.6b branch and I merged it into Seaside 2.7 as well,
however for some reason the main seaside practicioners have not got it
in their latest. So if you look for my last contribution to Seaside 2.7a
it will definitely be there. (kph)
This is what I mean by 'small' things to sort out.
> how come when I try to load from
http://mc.lukas-renggli.ch/pier for
> "blog" package I receive "This package depends on the following
> classes:"
>
> and there are many of them. Is there a better way to load Pier
> packages?
>
>
Load Pier from SqueakMap, then update Magritte and Pier using
Monticello from http://mc.lukas-renggli.ch/magritte and http://
mc.lukas-renggli.ch/pier.
The Blog package requires the package RsRss from the Seaside
repository: http://www.squeaksource.com/Seaside
Looks like there is just one more package to go
Pier-Magma
but I have this problem:
This package depends on the following classes:
PRPierControlPanel
You must resolve these dependencies before you will be able to load
these definitions:
PRPierControlPanel>>deleteRepositoryKernel:
PRPierControlPanel>>renderPRMagmaPersistency:kernel:on:
I've loaded all the other pier packages. Do you know where this is?
6510
days inactive
6518
days old
26 comments
3 participants
participants (3)
-
Brad Fuller -
Keith Hodges -
Lukas Renggli