Hi,<div><br></div><div>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.</div><div>
<br></div><div>Admin interface</div><div>============</div><div>Found in pier2addons, Pier-Admin</div><div><br></div><div>PRAdminFrame class contains various helpers for loading and configuring; see #loadDependentPackages, #register, #configureFileLibrary</div>
<div><br></div><div>I&#39;ve put Thomas&#39;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:</div>
<div><br></div><div>PRAdminFileLibrary deployFiles.</div><div><br></div><div>...which will result in a folder PRAdminFileLibrary containing the files in the same directory as the running image. As WAFileLibrary currently (I think) doesn&#39;t support paths, I&#39;ve put removed the img folder and moved the images into the same folder as the css file. I&#39;ve also renamed pier.css to pieradmin.css as it&#39;s the css associated with the admin interface. </div>
<div><br></div><div><br></div><div>Maarten&#39;s #browseCssClass I&#39;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.</div>
<div><br></div><div>I&#39;ve removed PRAdminDistribution as it largely replicated PRDistribution. I took the register changes into PRAdminFrame class &gt;&gt; #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.</div>
<div><br></div><div><div>Pier-Ace</div><div>======</div><div>Pier-Ace - copied directly into pier2addons - I&#39;m afraid I missed Bart&#39;s demo - perhaps Bart could explain more...</div><div><br></div><div>Simple external file support.</div>
<div>====================</div><div>Adriaan&#39;s WAExternalFileLibrary has been renamed WAFileSystemFileLibrary (from WAExternalFileLibrary to avoid a name collision) and I&#39;ve checked it into the repository: &#39;<a href="http://www.squeaksource.com/Seaside30Addons">http://www.squeaksource.com/Seaside30Addons</a>&#39; package &#39;Seaside-FileSystemLibrary&#39;. Maybe it should become part of Seaside-Core in the future </div>
</div><div><br></div><div><br></div><div>Security changes</div><div>=============</div><div>I&#39;ve copied <span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">Reza&#39;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.</span></div>
<div><br></div><div><br></div><div>Pier-Wysiwyg </div><div>==========</div><div>The Wysiwyg editor work Norbert and I started on Sunday afternoon is in pier2addons - package Pier-Wysiwyg. Again I&#39;ve put the external Javascript library into a WAFileLibrary for ease of distribution. The approach looks promising though this is a very early version.</div>
<div><br></div><div>still to come</div><div>=========</div><div>Bart&#39;s JQuery tree widget which we can then integrate into the admin interface.</div><div><br></div><div>Hope this makes sense. Shout if I missed something or you violently disagree with the &quot;tidying&quot; I&#39;ve performed prior to check-in.</div>
<div><br></div><div>Thanks all for a great weekend</div><div><br></div><div>Nick</div>