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
First (alpha!) release of Pier running with Magma Persistency.
Image available from ftp.seasidehosting.st
User: preloaded Password: squeak
enjoy
Keith
------
Image Use Instructions
In pier configuration click on 'Magma Control Panel', which will inform
you that the repository does not exist. If you have placed this image on
seasidehosting then you will have to manually create the repository
directory. Given the list of options as to what repository to create,
click the 'create' button (and wait). The existing pier kernel should
appear in the list with a 'persist' button next to it, click 'persist'.
Then try it and see!
------
------
Detailed Log of Image Creation Steps (alternative title: "monticello
tutorial")
This image was prepared as follows:
Beginning with Squeak3.8-6555full
Initial start asks for updates: select "do not ask again" - this is
important should you wish to deploy. Headless servers (e.g.
seasidehosting) cannot handle user interaction and will stop at this point.
From "world menu > open.... > Monticello Browser"
Browser opens with (Monticello....)
Click the "+Repository Button", select "HTTP" as the repository type,
and enter
MCHttpRepository
location: 'http://www.squeaksource.com/Seaside'
user: ''
password: ''
as the repository info (if you have a login on Squeaksource then you can
enter your initials
as the 'user' above.)
Add the following repository for Monticello.
MCHttpRepository
location: 'http://www.squeaksource.com/Monticello'
user: ''
password: ''
Add the following repository for Magma.
MCHttpRepository
location: 'http://www.squeaksource.com/MagmaTester'
user: ''
password: ''
and the following two repositories for Magritte and Pier
MCHttpRepository
location: 'http://mc.lukas-renggli.ch/magritte'
user: ''
password: ''
MCHttpRepository
location: 'http://mc.lukas-renggli.ch/pier'
user: ''
password: ''
also:
MCHttpRepository
location: 'http://www.squeaksource.com/OmniBrowser'
user: ''
password: ''
(to edit this information:
click the menu button in the right hand pane of the Monticello Browser)
----
Loading Latest Monticello.
More recent versions of Monticello provide better feedback as to which
packages are currently loaded.
Select the http://www.squeaksource.com/Monticello repository, click
"open", select the latest package (Monticello-avi.279) from the main
"Monticello" branch, and click "load".
Select the Monticello package on the left hand pane, and the
squeaksource/Monticello repository in the right hand pane. Click 'open'.
In the repository browser, click on the latest version
(Monticello-avi.279.mcz) and click 'Load'.
----
Loading Seaside
Select "world menu > open... SqueakMap"... and a dialog will ask if you
wish to upgrade SqueakMap. Which you do. Notice that SMBase, SMLoader
packages appeaer in the Monticello browser, since the upgrade is
performed by loading Monticello packages.
In SqueakMap, select the ever so convenient "Seaside Installer" which
should load in the whole of seaside with its dependencies in one go. To
do this select the left had pane menu button, "install". (Part way
through the install you will be prompted to enter an admin username
(seaside) and password (admin))
(if SqueakMap doesnt work it is being knobbled by a more recent
package-cache, remove it and try again)
Select the seaside repositoryClick the "open" and the repository browser
will open.
Select Seaside2.6b1 which is the current latest. In the right hand pane
are the releases. Releases may be made by anyone and they may be small
branches off from the main stream. Periodically an effort will be made
to ensure that all changes are merged. Click the history button in order
to browse the history of this package to get some idea of what is going
on. Look at the ancestors of a package to see if one version is being
sequentially built on the next, or whether any branching is occurring.
Seaside is fairly mature and changes infrequent, therefore it is likely
to be safe to grab the latest version.
Loaded Seaside2.6b1-mb.79
Loaded Scriptaculous-lr.137
To start Seaside doit:
WAKom startOn: 8080.
( Or use the "beach flags" SeasideMorph
available from: http://minnow.cc.gatech.edu/squeak/5862 )
To test if everything is running, check the following url in your normal
web browser.
http://localhost:8080/seaside/config
you should be prompted for you username and password (as given earlier).
----
Loading Magma
Back to the Monticello Browser. Deselect the selected package by
clicking on it once. This should re-reveal all of the registered
repositories.
(It is worth saving this. In the right hand side pane menu button there
is a menu item: "Save Repositories", which writes a simple configuration
script to the working directory.)
Select the http://www.squeaksource.com/MagmaTester repository, and click
"open".
Select MagmaServerLoader, and click "load". (it takes a while!)
loaded MagmaServerLoader-cmm.21
loaded Ma client server-cmm.123
loaded Ma exception handling-cmm.22
loaded Ma time objects-cmm.37
----
Load Magma Seaside Integration Package
Select "Magma Seaside" (lhs) and the latest package and click "load",
loaded Magma Seaside-kph.18
----
Load Magma Seaside Sushi Store Demo fixes
loaded Seaside-Examples-Store-Magma.kph-11
----
Before using Magma may need to execute the following.
MagmaSession initialize.
MagmaRepositoryController initialize.
useful snippets
MagmaSession allInstances cleanUp.
MagmaSession disconnectAndCloseAllConnectedSessions.
----
Load Magritte
loaded Magritte-All-lr.171
Load Pier
loaded Pier-All-lr.109
Load OmniBrowser
loaded OmniBrowser-avi.258
loaded Pier-OmniBrowser-lr.19
----
Latest Pier-Magma code
loaded Pier-Model-kph.80
loaded Pier-Seaside-kph.80
loaded Pier-Magma-kph.1
----
Pre-upload actions:
Monticello Browser - "flush cached versions".
----
Release Preloaded Image as Sqk3.8f-smp.image
___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
Hi all
I would like to know, is thedefault persistency mechanism of pier on
when we start the plain default seaside image?
Stef
PS: I found the PierImagePersistency but there is not even a single
comment. :(
When i add a PostArchive component to my page , the component renderes as
"(no blog found)" even thought is a Blog present. How do you specify the
blog for a PostArchive component ?
thanks
--
View this message in context: http://www.nabble.com/Pier-Blog%2C-PostArchive-component-tp18031433p1803143…
Sent from the SmallWiki mailing list archive at Nabble.com.
stupidly I created an admin page in the blog and I wanted to move it
elsewehere.
So I clicked on move and I tried
/ but I'm not allowed
/AnotherPage
and I always get Move: 'PAD' can not be a child of 'Passes'
So what is the solution?
Doru lukas I can tell you that I can really be a guinea pig about
usability
because I just crash in everything.
Stef
Greetings,
I have built a component called "VeComponent", with an embedded
Magritte component. The code for rendering looks like:
VeComponent>>renderContentOn: html
html render: self model asComponent addValidatedForm; yourself.
html submitButton callback: [self answer: someValue];
text: 'Done'
To test this code I call it from aWATask like this:
go>>
returnValue := self call: aVeComponent.
self halt.
This works, I get to the halt.
If I embed aVeComponent in another component then it appears that the
"self answer: someValue" in VeComponent>>renderContentOn: does not work.
What I observe is that clicking on the 'Done' button results in the
re-displaying of aVeComponent.
How is it that the code works when called from aWATask but it does not
work if it is contained in another component?
Can anyone explain what I am doing wrong?
Many Thanks,
Frank
Hello All,
Pier-Jetsam-Environment moves all configuration and initialization of a
pier kernel to subclasses of PRPierFrame.
1. Just switch your seaside application's PRPierFrame component to
switch to a different style and layout (even switch to a different style
framework).
2. Set up a second entry point to your Pier instance with a different
style. e.g. http://admin.mypier.example
this allows a simple way to support admin users without needing
Pier-Security.
3. Embed your pier instance in another seaside app, with a specialised
style for that app as provided by the root frame component that you
choose to embed.
4. The standard scheme of user editable environments still works as
before except that new environments get auto initialized.
enjoy
Keith
p.s. feedback invited
===========
PRPierFrameStandardBP
==================
The same policies and layout as the current pier release, except that no
'environment' is initially needed. If you provide 'environment' with
empty contents it will be initialized automatically.
PRPierFrameNewBP
================
As above except that the layout is obtained/initialized in
$environment/layout
PRPierFrameCWS and subclasses
========================
As above except that the style framework is based upon "Content With
Style" css framework.
The framework uses a single layout definition, but provides a number of
common layouts via CSS variants.
The options are
"#layout1colCss
" #layoutnavtopsubrightCss
"#layoutnavtop3colCss
"" #layoutnavtop1colCss
"" #layoutnavleft1colCss
"" #layoutnavleft2colCss
"" #layoutnavtoplocalleftCss
"
see: http://www.contentwithstyle.co.uk/Articles/17/a-css-framework
PRPierFrameAdminBP - Themeable classic pier 1.0.0 ui
========================================
The old classic pier admin UI (including the tree navigation widget)
All colors in css are referenced to method selectors for easy theming.
(Subclass and override #colorMethods)
Updated to use "Nifty Corners" so that rounded corners show in Internet
Explorer.
Updated to use transparent png, so that the color of the banner and the
logo can be changed in a single method.
There is still a little bit of work to get the css working cross browser
feedback as always appreciated
Keith
Dear Lukas,
your rewrite of MAChainAccessor provoked some panic here!
Just to let you know that I had written a couple of chaining and
unchaining operaterations, which I use for mapping a flat db query into
a magritte model. It allows me to treat a chain accessor as a kind of
stack as the model is traversed.
These are
#last
#chainTo:
#chainUnlinkLast:
I thought that you might be interested in adopting these (now they are
fixed for the latest) as utilities into MA-Model. If you are interested
then you will find them in the latest Magritte-RDB package in magritte
addons.
best regards
Keith
