smallwiki

smallwiki@list.inf.unibe.ch

2312 discussions

Start a nNew thread

Pier CMS site is down

by Rafael Luque

Hello all, I suppose you are managing this, but I cannot load piercms.com website since yesterday. Rafael Luque

13 years, 4 months

Approaches for i18n in pier

by Norbert Hartl

Does anybody of you use pier with a multilingual setting? If so I would be interested what approaches you take. I started simple and provided a kernel for each language where the language independent stuff is shared. But the more components I embed the more the whole thing becomes a drag. So I am very interested in any approach you tried (even if you failed) thanks, Norbert

13 years, 4 months

PierBook with non-latin characters?

by Davorin Rusevljan

Hi I would like to use PierBook to write paper in Croatian, and produce nice latex output with some non latin characters in it. Can I just use Pier2 one click from Lukas jenkins, or some tweaking is required to get a smooth run? Thanks! Davorin Rusevljan http://www.cloud208.com/

13 years, 5 months

Fwd: [Seaside] SeasideHostings with custom domain names need to update their DNS config

by Lukas Renggli

---------- Forwarded message ---------- From: Adrian Lienhard Date: Friday, 22 July 2011 Subject: [Seaside] SeasideHostings with custom domain names need to update their DNS config To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> This is relevant for SeasideHosting users with their own domain name (if you access the site other than yourname.seasidehosting.st). The SeasideHosting server is getting a new IP address. Some users have their DNS configured to point to the old address (212.103.66.207) and hence need to update. Until 1st of August 2011, please update your DNS configuration as follows. Replace the existing A record (which currently points to 212.103.66.207) with a CNAME record: CNAME seasidehosting.st If you have any questions, please get in contact directly via seasidehosting(a)netstyle.ch. Cheers, Adrian_______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- Lukas Renggli www.lukas-renggli.ch

13 years, 5 months

Pier permissions

by Nick Ager

Hi, I can understand how the current implementation of Pier security could work well in the case of a set of users each with their own sub-tree - a little like Unix's '/home/user1' '/home/user2' etc, where users can control the commands allowed to be executed on their sub-trees. However I'm looking for a more capability model, for example: * does the user have permission to see this view in wiki mode? * does the user have permission to create verbatim html? * does the user have permission to create value links? * etc Is there a sensible way to map this onto the current security implementation? I've currently mapped it with code like: > editorConfiguration allowWikiTextEditing: ((self context command: > PRWikiTextEditingCommand new) isValid). This works however the owner/group/other structure permissions mapping seems too coarse grained. I'd like to be able to have groups relating to these permissions then add groups to users, depending upon the permissions I'd like to assign to them. Am I looking at this in the wrong way? Is there a mechanism to support a capability model? Cheers Nick

13 years, 5 months

Initial release of Wysiwyg editor for Pier

by Nick Ager

Hi, I've been working on a Wysiwyg editor for Pier, (see attachment). It seems to be in a useable state and I'd love to receive some feedback The editor currently supports all the Pier markup I'm aware of, except tables. That said not all markup is possible to create in wysiwyg mode, however the editor aims to preserve all markup and allow editing of markup created in wiki mode. For example annotated paragraphs can be created in wiki mode, then edited in a Wysiwyg mode. Special Pier markup such as verbatim, embedded links etc are shown and preserved in the Wysiwyg editor, but are not editable. To give it a spin, from a Pier image execute: Gofer it renggli: 'pier2addons'; package: 'Pier-Wysiwyg'; load. Then browse to /wysiwygtest and you should see a test editor, which allows switching between wysiwyg and wiki editors with changes in either editor being reflected in both editors. The html parser walks the browser's DOM, and translates into Pier wiki format. There's a set of tests for the parser, which can be loaded with: Gofer it renggli: 'pier2addons'; package: 'ConfigurationOfPierWysiwygEditor'; load. (ConfigurationOfPierWysiwygEditor project version: #bleedingEdge) load: #('Core' 'Tests'). Then browse to /testwysiwgParser The tests are written in the Jasmine Javascript test framework [1], so run in the browser. I'm still trying to work out the best method to integrate into Pier. If you want to try the editor within Pier modify: PRDocumentDescription class>>defaultComponentClasses ^ Array with: PRWysiwygEditorComponent I've yet to find a method to integrate with Pier without modifying at least one Pier method. Any thoughts? Changing the above method also results in the editor being visible blog comments, which in it's current state probably isn't desirable. Next steps: - add support for preserving table markup - add a preview tab - support enabling/disabling depending upon user permission. Thanks Nick 1 http://pivotal.github.com/jasmine/

13 years, 5 months

Wysiwyg parser escaping markup

by Nick Ager

Hi, I added code to the Wysiwyg editor to escape markup within text nodes. To illustrate here is an example from the (javascript) test-suite: it("should escaped text containing link markup", function() { expect("To create a link, put it between <code>*</code>").shouldParseInto("To create a link, put it between ==\\*=="); }); This works fine, the problem arises with: it("should escaped text containing code markup", function() { expect("To make something <code>monospaced</code>, surround it with <code>==</code>").shouldParseInto("To make something ==monospaced==, surround it with ==\\=\\==="); }); Should text containing '==' translate into '\==' OR '\=\='. rendering ' ==\==== ' into html [1] results in: '<p> <code>=</code>= </p>' whereas rendering '==\=\=== ' into html results in: '<p> <code>==</code> </p>' The html reflects the PRDocument structure. It seems that PRDocumentParser doesn't parse ' ==\==== ' as expected. Worse the sequence: wiki text-> PRDocument -> wiki text fails: PRWikiWriter write: (PRDocumentParser parse: ' ==\=\=== ') => ' ==\==== ' However I have a fix. I've locally modified PRDocumentParser class>>#escape:using: so that any multi-character markup is multiply escaped: '@@' -> '\@\@' '--' => '\-\-' This seems to solve the ambiguous parsing problem and the round-trip problem. Great. However many tests will need rewriting to reflect that any multi-character markup is escaped with multiple slashes. Before fixing the tests, I wanted to check that people thought it made sense. Thanks Nick [1] | document renderer | document := PRDocumentParser parse: ' ==\==== '. renderer := PRViewRenderer new. ^ WAHtmlCanvas builder fullDocument: false; render: [ :r | renderer withinContentDo: [ renderer start: document in: self on: r ] ].

13 years, 5 months

magritte forms for elements in a collection

by Tudor Girba

Hi, I have the following use case that I want to solve using Magritte. I have entities that have Magritte descriptions. If I have one entity, I can nicely edit its description, and when I press Save, it changes the values from the entities. Now, I also have collections of entities that have the same descriptions I would like to use the rendering of Magritte to edit the values for all entities in the collection and when I press Save it should change the values for all entities. Is there any direct support for something like that? Cheers, Doru -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

13 years, 5 months

Some pictures of the Pier Sprint in Eindhoven...

by Adriaan van Os

... are available at http://www.a3aan.st/ps2011/index.php/list/0/01+Sprint Cheers, Adriaan. -- http://www.a3aan.st

13 years, 5 months

post Pier sprint - packages, repositories, files

by Nick Ager

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

13 years, 5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

smallwiki