Hi,
I vaguely remember some work was undertaken making a mobile view for Pier.
Is it still available? How did/does it work? Custom templates, views?
Did/does it select the view based on user agent?
I was wondering about using jQueryMobile to create a mobile view - though
as I write this perhaps a mobile rss reader and using Pier's rss support
would fulfil a similar purpose? Thoughts?
Cheers
Nick
Hi,
Since my initial post about Pier Admin I've fixed numerous bugs, added
documentation and simplified the configuration. The WYSIWYG parser now
parses tables, embedded lists, book index and reference links. To the best
of my knowledge it should either understand or preserve all Pier markup.
Let me know if not.
I've also created a new book view - BOAggregatedView. From it's comment:
I display my own structure and all my child structures if I answer true to
> #isPublication. I format publication numbers as the default book template.
> I provide an edit link for each child structure.
The view allows you to view all the contents of a chapter or section at
once. I'm couldn't find anything similar already in Pier, is there?
I've discovered some cool Pier-EditorEnh functionality that I didn't know
existed. If you click on a link button (in the enhanced wiki editor)
without any text highlighted a popup window displays the site map and the
available value links. Very cool. There was a small bug which prevented it
working in Pier2, which should now be fixed.
As ever Pier admin can be installed with:
Gofer it
> renggli: 'pier2addons';
> package: 'ConfigurationOfPierAdmin';
> load.
> ConfigurationOfPierAdmin loadBleedingEdge.
Let me know how you get along - feedback always appreciated.
Nick
Hi,
For all the Pier distribution I've checked I've noticed that for each
request the stylesheet was being served from a new Url. The relevant
implementation is:
MAFileModel>>url
"Answer a link to a request handler for the given file."
| handler |
handler := MAFileModelHandler on: self.
^ WACurrentRequestContext value registry
register: handler;
urlFor: handler
Which means that for every request for a file model's url, a
new MAFileModelHandler is being created and registered.
The result is:
* The browser never caches the stylesheet
* Each page request unnecessarily adds to the application's collection of
handlers.
Note: This is a generic Pier issue for PRFile requests, unless the url
includes the query ?view=PRDownloadView OR MAExternalFileModel class
baseUrl: has been defined).
One solution would be to add ?view=PRDownloadView to the url for stylesheet
requests or possibly for all file requests (modify MAExternalFileModel>>url
to add ?view=PRDownloadView).
However pondering the problem I've prototyped a solution in which PRFile
have a custom view component "PRFileView" which responds with it's
associated PRFile file directly, rather than delegating
to MAFileModelHandler. The logic is that, by default, PRFile>>#url responds
with a fully qualified path to itself within the pier structure
e.g. /pier/template/style.css then PRFileView>>#initialRequest checks the
request to see if it matches the mime-type of it's associated PRFile's
mime-type, if so it will respond true to PRFileView>#isFullResponse and
serve the file directly in PRFileView>#respondUsing:
MAExternalFileModel class>>#baseUrl still works as intended and
MAFileModel>>#url (and friends) remains unchanged.
The result appears to be a neater solution
than modify MAExternalFileModel>>url to add ?view=PRDownloadView, but I
might be suffering from implementors bias :-)
I thought I should check that:
1) people think it looks like a sensible fix and improvement
2) if (1) then whether I should delete MAFileModel>>#url (and friends),
deprecate them, or leave them as is.
Thanks
Nick
I love the demo. Would be nice to have an image built automatically with it.
Thank you Nick
---------- Forwarded message ----------
From: Nick Ager <nick.ager(a)gmail.com>
Date: Sun, Nov 27, 2011 at 10:43 PM
Subject: [Seaside] Pier Admin
To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org>
Hi,
Pier Admin - a new administration UI for Pier - has progressed enough
to be given a wider audience.
I've put a demo site up on seasidehosting.st -
http://pieradmin.seasidehosting.st
(be gentle it's a shared resource - any edits you make will be seen be
all others).
I've also recorded a short demo, illustrating some of it's features -
http://vimeo.com/32749535.
Install with:
Gofer it
renggli: 'pier2addons';
package: 'ConfigurationOfPierAdmin';
load.
ConfigurationOfPierAdmin loadBleedingEdge.
Hope it's of interest
Nick
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry
Hi guys. Pier-Shout does not put colors. SyntaxHighlighter doesn't have
Smalltalk. So...how can I have Smalltalk SyntaxHighlighter for Pier?
Thanks,
--
Mariano
http://marianopeck.wordpress.com
Hi,
Me and a group of friends in a local hackerspace[1] want to intervene
the interface of this Cynin site using the technologies of Diazo[2],
Xdv[3] or Deliverance[4]. Seeing the way that views are wrote in Seaside
I wondder if there is someway to make a similar intervention/integration
of interface without touching directly the code a la
Diazo/XDV/Deliverance but using Seaside/Zinc or some similar combination.
[1] http://hackbo.co/
[2] http://diazo.org/index.html
[3] http://www.enfoldsystems.com/software/proxy/docs/6.0/xdvtutorial.html
[4] http://packages.python.org/Deliverance/
Any pointer will be appreciated.
Cheers,
Offray
Hi all,
I'm getting random "504 gateway error" answers from several sites (using
Zope and Rails) that are served by Cherokee using a reverse proxy setup.
This error is an open issue in Cherokee and has been reported and not
properly patched since 2009:
https://code.google.com/p/cherokee/issues/detail?id=504
I did choose Cherokee because of its easiness to setup and newbie
friendly interface and character, but with this problem I'm thinking in
testing another server, may be a Smalltalk based one that have similar
characteristics and can serve sites in Zope or Rails also. I know about
Comanche, Swazoo and Zinc, but I don't know which of them is better
(making load balance and stuff like that) and have proper documentation
about using it in combination with other software (Zope and Rails in my
case).
Any advice on this matter is greatly appreciated,
Offray
I've made a pass throughout he piercms.com website to make it
up-to-date. I removed all the contents referring to Pier 1.0 and
updated the contents where possible. Also I changed the download link
to point to the latest stable build. Please let me know if I missed
something.
Lukas
--
Lukas Renggli
www.lukas-renggli.ch
I have the latest Pier One-Click working well with no problems. But I
wanted to upload a Pier image to SeasideHosting and I assumed the
One-Click version wouldn't work there. So I obtained a new Pharo1.3
image and loaded the latest configurations of Seaside, Magritte and Pier
into it. When I stared Comanche, Seaside came up up OK in my browser and
Magritte was included in the Applications list but not Pier.
I tried PRPierFrame registerAsApplication: 'pier' kernel:(PRKernel
instanceNamed: 'pier') and it does add a pier application to the Seaside
application list but it appears to be an older version of Pier without
the enhancements of the sample Pier page in the One-Click Pier.
Is the Pier One-Click sample webpage included in Pier2.0? If so, can
someone please advise how best to register Pier as an application in
Seaside so that it comes up the same as in One-Click Pier?