when I saw value:random I thought that this was just what I had been
I immediately gave it a try, expecting it to be "a random child of the
page in which the link is placed". Well it worked fine until I embedded
that page into another page, and then I discovered that it is "random
child of the current structure". Not what I expected at all.
So I investigated these value links, only to find that these links do
not appear to know their document, thus making my original idea
impossible to implement with value links.
To be honest I have hit this problem many times since I started using
pier. I never have any use for "children of the current structure", and
there are many "current structure" based features in pier. I always want
children of a specific structure. Then I can craft a menu, and embed it
somewhere else, or similar.
So I implemented a subclass of value links, implementing "page:" links,
and it works great.
Then I had a thought: the most powerful, and oft forgotten feature of
Ward Cunningham's original wiki, was the ability to click on the title
of a page, and get all of the referring pages.
So how does one get "all of the links that link to this page".
btw: the code in the comment to PRIncomingReferences is not a valid
example as far as I can see.
Hi people: I am trying to use this package I downloaded from MC. I wanted to
use it, for example, for "search". Just as it is here:
Does someone know how can I do this? I have to put lightbox class css in the
div ? is there a specific component for lightbox?
Thanks a lot in advance,
I found that MAInternalEditorComponent is doing this
super renderEditorOn: html.
html hiddenInput callback: [ self component commit ]
Am I correct in thinking that this means that the commit to the model is
occurring every time the form submits? I thought that the commit should
be to the memento, when validation etc has passed.
I hope you dont mind, I extended slideshow to provide glitzy crossfading
There is a slight problem which shows up if you try to un a slideshow
without any |<< >>| tools showing. It appears that if you render a div
with nothing in it (a), and later via an evaluator update that div,
again with nothing in it(b). In IE the div appears, where it wasnt
The code is in Pier-SlideShow
(a) PRSlideShowCrossFade-#renderSlideshowOn: html
(b) PRSlideShowCrossFade-#applyCrossFadeTo: script
Is there a way to conditionally display the contents of a command column for
certain rows of a MAReport?
Say I only wanted to be able to remove an object if it's name isn't 'b'
a edit remove
c edit remove
I wrote PRCommandLink to enable a link to a command to be inserted into
a document like so:
I remember seeing something in more recent pier's that would/may provide
this functionality, but I cant remember what it was.
I have just found PRCommandWidget (which I wrote, but was hiding in the
Pier-Seaside category) I have exported it to pieraddons, and offer it as
a potentially useful addition to Pier-Seaside.
I have long been frustrated that there is no place in squeaksource for
documenting what is in a repository, and offering feedback as to what
works where. We have several solutions on a macro-universal-scale,
namely, universes, squeakmap, and sake/packages.
I have started to use Sake/Packages as a kind of micro "universe" for my
Seaside "Client" UI & Backend Component Framework. Having seen how
useful this is I thought that this might be useful for pier, and of
course seaside and other projects.
For an example of this, have a look at squeaksource/Jetsam at the
In www.squeaksource.com/Jetsam there is a package Client-Packages.
For pier you would have a package in source.renggli.ch/pier called
For seaside29 you would have Seaside29-Packages etc etc.
This contains a class/classes which document all of the packages, and
the dependencies that are available for the project, together with
metadata, and package comments.
Some have reservations about Sake/Packages because they say it is not
declaritive. It is if you want it to be. 99% of the package declarations
already present are declarative. Exceptions are usually weird cases like
the unload script for Sake itself.
Having seen recently how useful this idea is, I will be looking at the
following improvements to the idea.
1) how best to integrate these micro-universes in to the main
2) how to declare alternative definitions for pharo and other images
3) how to make the micro universes light-weight, so that they may be
available for documentation without depending upon Sake/Packages being
loaded, (hmm, perhaps they could be published as traits!).
4) Bob support - Sake/Packages will also be able to generate load
scripts (for Bob or anyone who is interested), so that "Bob the Builder"
can build complex images without having ANY of the following loaded
monticello/sake/packages/universes/squeakmap, Installer will be the only