smallwiki March 2007

smallwiki@list.inf.unibe.ch

24 participants
32 discussions

by Giuseppe Luigi Punzi

Hi, I got it a 3.9 and installed pier from squeakmap. Then, from monticello, I installed Pier plugin. I created a new bog, and when I try to open it, I get the next error: MessageNotUnderstood: WARenderedHtmlRoot>>rss * WARenderedHtmlRoot(Object)>>doesNotUnderstand: #rss self a WARenderedHtmlRoot *temps* aMessage rss *inst vars* docType ' title 'Pier: Giuseppe' htmlAttrs a WAHtmlAttributes headAttrs a WAHtmlAttributes bodyAttrs a WAHtmlAttributes headElements an OrderedCollection(a WAMetaElement a WALinkElement a WALinkElement a WALinkElement a WAScriptEleme...etc... scripts an OrderedCollection() styles an OrderedCollection('#toolbar { position: fixed; bottom: 0; left: 0; right: 0; margin-top: 40px; pa...etc... resourceBaseUrl nil context a WARenderingContext * PBBlogHtmlView(PBHtmlView)>>updateRoot: self a PBBlogHtmlView *temps* aHtmlRoot a WARenderedHtmlRoot *inst vars* decoration a WAStateHolder(a WAAnswerHandler) context a PRContext stucture: 'Giuseppe' command: 'View' blog a PBBlog name: 'Giuseppe' posts #() batcher a WABatchedList tag nil * [] in WARender>>buildDocRoot {[:each | each updateRoot: docRoot]} self a WARender *temps* docRoot a WARenderedHtmlRoot each a PBBlogHtmlView *inst vars* root a WAToolFrame context a WARenderingContext request nil url a WAUrl * PBBlogHtmlView(WAPresenter)>>withNextPresentersDo: self a PBBlogHtmlView *temps* aBlock [] in WARender>>buildDocRoot {[:each | each updateRoot: docRoot]} ea nil *inst vars* decoration a WAStateHolder(a WAAnswerHandler) context a PRContext stucture: 'Giuseppe' command: 'View' blog a PBBlog name: 'Giuseppe' posts #() batcher a WABatchedList tag nil * [] in WAAnswerHandler(WAPresenter)>>withNextPresentersDo: {[:ea | ea withNextPresentersDo: aBlock]} self a WAAnswerHandler *temps* aBlock [] in WARender>>buildDocRoot {[:each | each updateRoot: docRoot]} ea a PBBlogHtmlView *inst vars* next a WAStateHolder(a PBBlogHtmlView) block [] in PRContentsWidget>>buildComponent: {[:value | self onAnswerCommand: value]} Thanks in advance. -- Giuseppe Luigi Punzi :: ZYO :: Solutions everywhere email: glpunzi(a)zyoconsulting.com tlfno: +34 675 145 912 web: http://www.zyoconsulting.com

17 years, 11 months

[ANN] Bug Tracking on Mantis

by Lukas Renggli

Bugs of Magritte and Pier are now tracked on Mantis. To report chose the project 'Squeak Packages' and an appropriate category, e.g. 'Magritte' or 'Pier'. Of course, and this is still the preferred way, all the Monticello repositories are open for your contribution. Therefor if you have found and fixed a bug you can directly commit your changes there. They will eventually be merged into the mainstream. That's simple and generally more efficient. For all other cases there is Mantis now. Cheers, Lukas PS: There is also a category for Seaside on Mantis, in case that's the source of problems. -- Lukas Renggli http://www.lukas-renggli.ch

17 years, 11 months

Linking to a command in a Pier wiki page?

by Matthias Berth

Hello, is it possible to link to a Pier command from a Pier page? Example wiki text: !Welcome Please *log in>command:PULogin*, or *read more*. Cheers Matthias

17 years, 11 months

Commands on multiple structures / Timestamps

by Sébastien Julliand

According to how commands work in Pier, is it possible to apply a command on more than a single structure? Another question: is there something in Pier to retrieve the date and time of creation/modification of each page (or do I need to add some descriptions to PRStructure?) Cheers, -- Sébastien JULLIAND

17 years, 11 months

Adaptative (to user's role) edition of objects with many "properties"

by Sebastian Sastre

Hi there, for applications sometimes the user want to edit an object that has many instvars to edit or it's composed. I guess that this could lead to forms too large to be practical for the end user's daily use. One solution to this is could be the partition of the form into smaller forms with tabs. The problem is that one should describe once and let the description prepared to be capable of build several composed forms to each model. This could be archieved by different form building policies. A concrete form build's policy should define the look of the component. To give a simple example of this policy: if the component to build is no bigger than 6 "fields" it should be like "the normal ones" (actual default) but if it has more than 6 "fields", put the first 6 in a tab and the next 6 in another tab (or more, until the total ammount of fields are reached). The policies should be extensible but generic enough to maintain economy in the design. Is also desirable collaboration with user's role to gain additional customization of the observation. A smarter policy could take advantage of grouping info set in the descriptions. As an example some fields could belong to the #'admin.indetification' or #'operator.identification' group/role to keep grouped the right fields of the editor's form for the object/model. I'd like to hear opinions about this or to know about better approachs to solve this problem. cheers, Sebastian Sastre PD: as a side note I'm evaluating to use Magritte with Glorp mapping (like Ramon Leon suggest) so, if I'm undesrtanding this right, the descriptions to map the persistance of the model objects should be "like" another role observating them but describing the persistance wanted.

17 years, 11 months

No free space in set

by Keith Hodges

(sorry wrong thread) Error: There is no free space in this set! I got this error when attempting to add a page any ideas? Keith ___________________________________________________________ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html

17 years, 11 months

User's role based observation of the model

by Sebastian Sastre

Hi there, I was reading the Lukas thesis about Magritte. By the way... congratulations for that nice document Lukas. I have questions about Magritte beign useful for generating views of the model. Note I said views and not view of the model because I think is interesting to generate more than one unique view for it. I have several examples in wich this feature is desirable. Most are user based. With user based I mean the user's role should determinate the observation. An organization's anOperator should see something of aDocumentModel but aManager should see diferent and probably more details of the same aDocumentModel and aDirector should see just metrics about that (aDocumentModel). I see that one could manipulate the design to "force" aDocumentModel to be of different species for each observer but the cost is undesirable complication, reality-virtuality mismatch and identity mess (made worst with and RDBMS mapping in the middle). I don't like the dark side. I think is possible a better approach but until now I was unable to see a clear way on how Magritte could help with multiple description request. The descriptions for the objects are deducted from class side #descriptionXX of the objects wich collaborates with MADescriptionBuilder but it's cache seems to be designed to store only one description per object. Do you think that to extend Magritte to support several descriptions per object should be the best approach to this problem? thanks, Sebastian Sastre

17 years, 11 months

Newbie question about Pier

by Diego Fernandez

Hi! I want to use Pier as a wiki at work, so I'm evaluating if it meets my needs. (side note: It's very complicated to get information about Pier from the main Squeak site, the Pier wiki or the Seaside site. I don't known how the Ruby guys get the resources to make their web sites... but we -I mean the squeak community- need to learn a lot from them in this area) After running the image provided by Keith, I've tried to use Magma and I got the same error about "objects" file mentioned early in the list :(. So before digging more into the problem, I have a couple of questions: - What is the recommended mechanism for persistence: plain files, Magma, image? - If I want to change the persistence method, how hard is to do the migration? (I think that I should execute a script that loads all the wiki in the image using the source persistence method, then write all those objects using the target persistence method... there is an easy way to do that?) - How can I make Pier components? (I'm new to Seaside too) - It's possible to use LDAP for Pier authentication? If not, how hard is to use another authentication method? (I have experience developing LDAP authentication libraries for gemstone... so I can help in this area) - I want to change the stylesheet how I can do that? - I want to change the view component, so certain options like editing or configuring the environment are invisible if the user is not logged in... any clue on how to start? - It's possible so show or hide a component according to the user role? I want to show the tree component only if the user is the administrator of the wiki That are a lot of questions for a single mail! So many thanks in advance! Diego.-

17 years, 11 months

Javascript in pier page

by Brad Fuller

Is it possible to place javascript in a pier page? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124

17 years, 11 months

Breadcrumbs List

by Koji Yokokawa

Hi all, I made a breadcrumbs list for Pier. It displays the trail of the user in the Pier site. Detailes: http://yengawa-wiki.webhop.org/YengawaWiki/55 Demo site: http://yengawapier.webhop.org/ Have fun! -- ! Koji Yokokawa <koubo2006(a)yengawa.jpn.org> http://www.yengawa.com/ ^self new!

17 years, 12 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

smallwiki March 2007