is there any photo gallery available for Pier? I mean a widget where I
could upload pictures and they are rendered in a nice way. I started
one 4 years ago but I abandoned it.
I wonder how can I add a css who references an image to a page in Pier.
For example, I have this style:
so... I upload the style to /system/components/css/style.css, and I change my page to use that css.
So... how can I add the image file? I tried by creating a /system/components/css/background.png file, but it does not works :(
Also... I would like to add some meta information (a couple of <link> rels), and no idea how to do it... any idea?
I would like someone to verify this..
I want to create a plugin that would be part of the enviroment of a number
the plugin wants to know the user that is logged in, the owner of the page
that is viewing and the absolute path of the page.
So to get this i ll put in my component these lines right?
PRContext structure owner
PRContext structure absolutePath
I guess that the absolute path is the only way to identfy a page.
Another problem i have is with persistency..
I googled and found that lots of people have already talked about it.
For me and i think every new programmer, it is the biggest obstacle for
Pier is very powerfull , easy to use and programm due to its smalltalk
foundation. The code is so easily understood and the reusability of the code
So If this persistency problem is solved with the new programmer in mind,
the one that just wants its objects to save, no questions asked, Pier would
So to use Pier, the only option for me is to go for a non-free DB like
gemstoneS. All i have to do is tell Pier to save objects and gemstone will
do it automatically without me changing any of the code, right?
Unfortunately at the time of writing i have access to a 32bit CPU so i cant
check for myself..
I know there are other options like magma, but from what i understand you
have to understand the underlying structure and i dont want to.
I would like to ask you if there is any documentation on creating new addons
for the pier systems, apart from the code.
Also if there is documentation for the already existant addons, for all the
Is the list http://source.lukas-renggli.ch/pieraddons/ complete or are there
If there is no documentation what are the differences in creating components
for pier than for a general seaside web site.
Do i have to learn magritte?
This message and any attachments (the "message") are confidential,
intended solely for the addressee(s), and may contain legally
Any unauthorised use or dissemination is prohibited. E-mails are
susceptible to alteration.
I shall not be liable for the message if altered, changed or
I load Seaside, Pier and addons with the script below. Most things (at least
those I've tried) works, but Import/Export widget. It simply ignores all
clicks on Import and Export buttons. What's wrong (how is it possible?!) and
how can I resolve this issue? BTW: Grease, Seaside, Magritte, Pier tests are
(Smalltalk at: #ConfigurationOfSeaside30) load.
(Smalltalk at: #ConfigurationOfPier2) load.
project := ConfigurationOfPier2 project.
(project version: '2.0.7') load.
(Smalltalk at: #ConfigurationOfPier2) project latestVersion load:
(Smalltalk at: #ConfigurationOfSeaside30) project latestVersion
load: #('Magritte2 Tests' 'Pier2 Tests').
(Smalltalk at: #ConfigurationOfPierAddOns2) project latestVersion load:
I remember seeing a demo of a halo view for editing Pier components
that I think Lukas and Tudor worked on. Can anyone point me at a
repository containing the code?
I'm interested in building UIs where the user can edit in-place rather
than editing in a form which then flips to the resulting screen. I'm
considering using something like JQWidgetBox-JEditable-* in
http://www.squeaksource.com/JQueryWidgetBox. Anyone with experience of
doing this kind of thing?
I've logged a bug: http://code.google.com/p/pier/issues/detail?id=132
The text of the bug is:
Steps to recreate the bug:
1) Download the recent build of Pier 2 -
http://hudson.lukas-renggli.ch/job/Pier%202/ - this bug is not present
in Pier with Seaside 2.8
2) In a workspace execute the following:
WAAdmin defaultDispatcher defaultHandler preferenceAt: #useCookies put: true.
(PRPathLookup start: (PRKernel instances anyOne) root path: '/call')
contents: 'In Firefox, try clicking on the counter
(PRPathLookup start: (PRKernel instances anyOne) root path: '/call') addChild: (
(PRComponent named: 'counter') componentClass: WACounter; yourself)
3) Within Firefox (I'm using 3.16.13) browse to
http://localhost:8080/pier/call - you should be on the "Call for
Contributions" page into which the above script embeds the standard
Seaside counter component in the page.
4) Try clicking on the "++" or "--" links a couple of times and you'll
find yourself taken to http://localhost:8080/pier/dates and rather
than modifying the counter value.
Here's my understanding of the bug:
1) Amongst other metadata Pier adds the following to the header: <link
2) In Firefox when cookies are enabled, the <link rel="next"> causes
firefox to issue at least two requests for each page; the first
request for the url specified, the second for the url specified in the
href of the <link rel="next">. Note this second request is not visible
in firebug (I added request logging to WAComancheRequestConverter). In
Safari or Chrome, I haven't seen any additional requests and so the
problem does not appear.
3) The second request confuses the callback hander
Unfortunately my understanding of how the callback handler should work
is limiting my ability to fix the bug. Any thoughts?
i have some descriptions and one based on MAStringDescription for manage the e-mail reference.
Now i'm interested to create a MAReport with fields for management email.
Where for management i think a link to open new email directly from report :
html anchor attributeAt: 'href' put: 'mailto:', anObject emailBase.
How i can do it ?
Anyone create a specific MADescription for define e management email reference ?