Hi,
I was trying out the Blog component and it doesn't seem to work for me. After adding the Blog component, I get this error:
WARenderedHtmlRoot(Object)>>doesNotUnderstand: #rss
Surely enough I can't find any implementors of #rss in Seaside or Pier. The following method is the one that's sending #rss to a WARenderedHtmlRoot object.
PRRecentView(PRBlogView)>>updateRoot: aHtmlRoot
super updateRoot: aHtmlRoot.
aHtmlRoot rss
title: self blog feedTitle;
url: self subscriptionUrl
Since the Blog component works in your screencast, I guess you might be missing an update to the to repository (Seaside?) somewhere.
I am using Pier-All-lr.151, Pier-Blog-lr.29, and Seaside2.7a1-lr.166.
-Bill
____________________________________________________________________________________
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get started.
http://mobile.yahoo.com/mail
> (PRCompatibility confirm: 'Would you like to create a Seaside
> application for Pier?')
> ifTrue: [^ self].
>
> This seems to cause the application to not create a Pier
> application if you say yes, so I clicked no and sure enough, it
> built everything. I could fix it, but I thought I would check with
> you first.
Ohh yeah, this is a bug. I just recently re-factored this method and
introduced this error. The latest version fixes this issue.
Lukas
>
> Thanks,
> Jason
>
>
>> From: Lukas Renggli <renggli(a)iam.unibe.ch>
>> Reply-To: "Magritte, Pier and Related Tools ..."
>> <smallwiki(a)iam.unibe.ch>
>> To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
>> Subject: Re: Status of Pier
>> Date: Tue, 30 Jan 2007 23:27:30 +0100
>>
>> > First, in my image, if you go to a page and then go to lunch, come
>> > back and hour later and click a link you get dropped back to the
>> > front page because your session has expired. But I thought Pier
>> > used the URL to be able bookmark, surf the side via URL etc. In
>> > fact, I thought it even worked this way before I put the security
>> > package in.
>>
>> Yes, it should work and remember the page even if the session
>> expired.
>>
>> > Has this been fixed? It seems like if you click on a link that has
>> > a URL, but an old session Pier could just make a new session and
>> > apply that to the page the user is trying to go to. If the user is
>> > not allowed to see that resource with the blank session then kick
>> > them back to the front like now, but if the page is not restricted
>> > they should see it.
>>
>> This is a bug in Seaside. I fixed it, and the scenario you describe
>> works when you load the latest version:
>>
>> Name: Seaside2.7a1-lr.162
>> Author: lr
>> Time: 30 January 2007, 11:23:44 pm
>> UUID: b22fe0c4-77c1-4e3d-99f7-331a368c4337
>> Ancestors: Seaside2.7a1-pmm.161
>>
>> > Second, is there any plan to expand on the RESTfulness of Pier? I
>> > mean, I'm not a die-hard REST person or anything, but there are
>> > times it would be nice to use URL's. I think the above suggested
>> > handling would probably be enough.
>>
>> Yep, that's a requirement. Thanks that you reported this, I probably
>> wouldn't have noticed it myself.
>>
>> > One thing that makes me want this is the difficulty of pointing to
>> > another page in your Pier site from a custom component. I know you
>> > have the #goto: message on anchor, but (1) I need it anywhere a URL
>> > could be used, since I am using "html tag:" to do some tags not in
>> > seaside (an HTML image map to be specific). And (2) the #goto:
>> > message expects a structure that can be tough to get a hold of
>> > sometimes. The easiest thing for me would be if I could simply
>> > point my image map at the URL as a string, since that part is
>> > public and I don't care if the user is logged in or not.
>>
>> Glad that you ask. For the blog component I also felt the need to
>> have just the url and not only an anchor. I think I will need to add
>> that sooner or later. Shouldn't be too difficult though.
>>
>> > And lastly, I have had some users complain about the ugly URL's. I
>> > know you can say that they shouldn't look at the URL, etc. etc.,
>> > but if we can make this better why not?
>> >
>> > What I was thinking was, how hard would it be to change Pier so
>> > that the URL part stays, but at least the session (and maybe the
>> > command and view fields as well) could optionally be cookies. And
>> > this could even be something configured in the /seaside/config/pier
>> > page.
>>
>> Go to the Seaside configuration page and enable 'Use Session
>> Cookies'. This will put the session key into a cookie, if possible.
>>
>> > Thanks in advance. You may have ways to do all these things by
>> > now, but I thought I would check.
>>
>> Cheers,
>> Lukas
>>
>> --
>> Lukas Renggli
>> http://www.lukas-renggli.ch
>>
>>
>>
>> _______________________________________________
>> SmallWiki, Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> _________________________________________________________________
> Talk now to your Hotmail contacts with Windows Live Messenger.
> http://get.live.com/messenger/overview
>
--
Lukas Renggli
http://www.lukas-renggli.ch
I just installed magritte into a 3.8 image that already had seaside.
It was tricky as it kept freezing post installation in WeakArray
finalization code. Several tries and some playing with the process
browser allowed me to suspend/lower the priority, and kill the errant
process. So I have it. Nifty.
I'm working through the tutorial and the very first item - add a text
area called 'comment' to person is a puzzler. I hunt down the
MATextAreaComponent thinking I'll use a StringDescription but give
it a componentClass of MATextAreaComponent.
But then I read the comment:
I display an html text area for the magritte MATextAreaDescription.
So I go looking for that and the class does not exist. I found
MAMemoDescription because of the exception I got about lineCount not
being implemented on MAStringDescription.
So you should probably fix that comment or change the name of the
class back or something.
Otherwise, I think I like what I see so far.
-Todd Blanchard
I find having to provide the label for every attribute tedious. In
the application I am considering porting to Magritte, I infer the
label from the selector nearly all of the time. The code I use for
this is:
selector asString withSpacesBeforeCapitalLetters capitalized
works pretty well.
-Todd Blanchard
> Lukas, I've run into a minor anomaly in MAReport from Magritte lr.
> 187. Have a look at this method:
>
> renderTableCaptionOn: html
> self description caption ifNotNilDo: [ :value |
> html
> tag: 'caption'
> do: self description caption ]
>
> The problem is that #caption isn't implemented in any object that
> would conceivably used in this context. I leave it to you to sort
> this one out.
That's odd. The code in my image looks completely different:
MAReport>>renderTableCaptionOn: html
(html tag: 'caption') with: self tableCaption
Are you talking about Magritte-All.lr.187?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
I was going to send an email about Pier and I couldn't come up with any
example sites. Can anyone reply with some links that I can use?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
