Hi,
It looks like Pier does not take into account the changes made to the
CSS using the Edit Design command. You can reproduce the error by just:
- Edit Design
- add: body { background: yellow;}
- save and nothing happens.
The strange thing is that the changes are stored, they just do not
affect the rendering.
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"What we can governs what we wish."
I am a bit stuck in a pre-Blueprint world. So I was having a look at it.
I loaded up the current, release of pier, and it is very clean and ready
to be styled. I miss the tree view, has it gone because it doesnt fit in
the layout?
Blueprint looks cool for some applications. I have one site which has a
fairly fixed layout, so blueprint appears to me to be an ideal solution
for that, but not, I fear for pier in general.
This appears to me to be a better fit, for general blogish/corporate sites.
http://www.contentwithstyle.co.uk/Articles/17/a-css-framework/
best regards
Keith
Pier Experts,
At my work, we've been running a smallwiki (the origininal version of
pier) for about 3 years, and have accumulated around 3k pages. While
looking into upgrading to pier, I noticed that the newest images on
** site resolve the missing slash problem (backslashes disappear in
preformatted text if they don't preceed a *), however there's a new
problem. Suppose I have images intermingled with text, such as:
text1
<IMG ALT="Picture1" src="http://apache/resources/images/
pic1.png" />
text2
<IMG ALT="Picture2" src="http://apache/resources/images/
pic2.png" />
text3
Assuming that the apache server is down, it would appear as:
text1
Picture1
text2
Picture2
text3
With the new version of pier, it is displaying as:
text1
Picture1 text2
Picture2 text3
Does anyone know a way to fix this? Is it in the CSS or in the ST code?
Thanks in advance,
John Borden
I have written a tutorial on "theming", and changing the way Pier looks, and
I would like some people to read it and give me feedback. The majority of
the document is about setting up Apache to host static content for Pier to
use. Any sugestion are welcome, I hope I didn't mess to much up. the
tutorial is at http://w337.uni.cc/PierDocs/customizingLook.pdf
--
David Zmick
/dz0004455\
http://dz0004455.googlepages.comhttp://dz0004455.blogspot.com
Greetings,
I am just starting to poke around Pier and I am trying to figure out how
to hide the "Views" menu from a non-admin user.
I can change the permissions for "Other" so that there are no menu
choices under the "Views" menu but the box with the word "Views" still
appears. I would like this to not be shown. How can this be done?
Just to clarify, what I mean by the "Views" menu is the menu on the left
hand side. There are three menus on the lhs: Views, Commands and
Navigation. I want the Views menu to not appear at all.
Thanks,
Frank
Hi,
I am experimenting with Pier and I would like to create a link to an
image (jpg) file. The Pier documentation on syntax says:
The contents of some links, e.g. links pointing to image-files, can be
embedded into the current document by using +s: +reference+. However not
all types of links support embedding and will quietly ignore it.
I don't understand the "+s: +reference+" syntax, can someone provide a
real example that shows how this works?
Thanks,
Frank
Hi All,
I have write seaside component and register it with specific application link.
Now i'm interested to integrate this component on Pier site.
I have do it with the 'component' of Pier, and all work fine.
My question is:
how i can define se the call to on specific seaside component is direct or from pier .
I'm interested to define it because when rendering component from pier the header section of the component isn't required.
Any pointers would be greatly appreciated!
Thanks!
Hi All,
i work with some model descripted with MAgritte.
Some model have 20 or more description and when display it, for the user isn't simple.
I begin to write component for rendering description with SUTabPanel.
The idea is to group description based on it priority for example:
the description with priority from 1000 to 1999 go in the first tab,
from 2000 to 2999 go in the descon tab,
and so on.
The second idea is to renderign on the single tab div with:
description from x100 x199 on the first line of the tab.
description from x200 x299 on the second line of the tab.
and so on.
My question are:
anyone solve, work around this problem ?
do you have any consideration about it ?
Any pointers would be greatly appreciated!
Thanks!
Dario
Hi,
I'm using pier in a project who needs execute certain operations after
a command is executed (journal/persistence stuff) and I added a method
PRCommand, who is executed after doExecute... so... what is the
problem? well, I have to mark an object as "persistent", in
PRAddCommand, and then I do: self child bePersistent... but, as #child
answer a ew instance of #type, the operation is lost...
I changed #child to use an instVar and just instantiate once....
everything seems to be working now, but I want to know if there is a
possible problem with this change...
what do you think? the change works?
Thanks,
Esteban