Hi,
All the work in the Eindhoven sprint repository is now checked into the
pier2, pier2addons or Seaside30Addons repositories. In the process I
performed a little refactoring on some of our work.
Admin interface
============
Found in pier2addons, Pier-Admin
PRAdminFrame class contains various helpers for loading and configuring; see
#loadDependentPackages, #register, #configureFileLibrary
I've put Thomas's files into PRAdminFileLibrary, as it seems to be the
easiest way to distribute the files. However for Thomas to continue to work
on the design it probably makes sense to export the files then use an
external file library to serve them. To export the files:
PRAdminFileLibrary deployFiles.
...which will result in a folder PRAdminFileLibrary containing the files in
the same directory as the running image. As WAFileLibrary currently (I
think) doesn't support paths, I've put removed the img folder and moved the
images into the same folder as the css file. I've also renamed pier.css to
pieradmin.css as it's the css associated with the admin interface.
Maarten's #browseCssClass I've refactored so that #cssClass now allows a
specific css class to be specified for a structure. I think that makes sense
to expand #cssClass rather than having the potential confusion of two
methods which providing similar functionality.
I've removed PRAdminDistribution as it largely replicated PRDistribution. I
took the register changes into PRAdminFrame class >> #register. I guess we
either need to modify PRDistribution to come up with a pier show-case
distribution or create a new distribution. Ideally the admin interface will
allow these distributions to be browsed and installed - it currently allows
switching between different pier kernels.
Pier-Ace
======
Pier-Ace - copied directly into pier2addons - I'm afraid I missed Bart's
demo - perhaps Bart could explain more...
Simple external file support.
====================
Adriaan's WAExternalFileLibrary has been renamed WAFileSystemFileLibrary
(from WAExternalFileLibrary to avoid a name collision) and I've checked it
into the repository: 'http://www.squeaksource.com/Seaside30Addons' package
'Seaside-FileSystemLibrary'. Maybe it should become part of Seaside-Core in
the future
Security changes
=============
I've copied Reza's security changes directly into PRDistribution. I think
there are more to come - though this also has to do with our Pier kernel
boot-strapping approach from the admin interface.
Pier-Wysiwyg
==========
The Wysiwyg editor work Norbert and I started on Sunday afternoon is
in pier2addons - package Pier-Wysiwyg. Again I've put the external
Javascript library into a WAFileLibrary for ease of distribution. The
approach looks promising though this is a very early version.
still to come
=========
Bart's JQuery tree widget which we can then integrate into the admin
interface.
Hope this makes sense. Shout if I missed something or you violently disagree
with the "tidying" I've performed prior to check-in.
Thanks all for a great weekend
Nick
Hi,
Over the weekend in Eindhoven we focused our efforts on building a friendly
admin interface for Pier. The concept was that rather than having the admin
features within site's environment (~template), we wrap a pier site in an
admin interface which would be available from a different url (eg
www.mysite.com/admin or admin.mysite.com). See attached screen grab. This is
very much still a WIP. The reasons for this approach were:
1) Focus the site's environment on the contents of the site and not to be
worried about the administration interface.
2) Simplify the site's environment by removing the administration tools.
3) Remove the concern that editing the site's environment could break the
admin interface.
4) Provide a consistent admin interface across all Pier sites.
5) Ensure that the admin url is secure.
That said it's probably not as black-and-white as I've implied; there are
some admin or editorial tasks which would probably make sense to keep within
the site, for example add a new blog post, edit a page.
The WIP admin interface is available in repository: '
http://source.lukas-renggli.ch/pier2addons', package: 'Pier-Admin'. Until we
update a Metacello configuration there are some class site installation
helpers:
PRAdminFrame class >> #loadDependentPackages
PRAdminFrame class >> #register
Hope this makes sense
Nick
The attendees where:
Adriaan van Os
Louis Andriese
thomas noordzij
Julian Fitzell
Maarten Daalder
Norbert Hartl
Bart Veenstra
Nick Ager
Reza Razavi
Stephan Eggermont
Friso Geerlings
hope I haven't missed anyone
