I found that pasting a 'long dash' character into a pier page results in
the contents being rendered like so
—
<���?���x���m���l���
���v���e���r���s���i���o���n���=���"���1���.���0���"���
���e���n���c���o���d���i���n���g���=���"���U���T���F���-���8���"���?���>���<���!���D���O���C���T���Y���P���E���
���h���t���m���l��� ���P���U���B���L���I���C���
���"���-���/���/���W���3���C���/���/���D���T���D��� ���X���H���T���M���L���
I am using the standard WAKom.
best regards
Keith
==
fyi: using pier-beta in 3.10 dev image
Yes, the code I gave you at that time won't work in Seaside 2.8.
WARenderLoop has been completely rewritten to avoid the need to store
many unnecessary continuations. This greatly reduces the memory
requirements per session.
What I suggest to do is that you implement a decoration that you can
add around your component. Inside this decoration you store the
context-holder and wrap the rendering and callback processing into
PRCurrentContext use: contextHolder during: [ ... ]
HTH,
Lukas
On 02.08.2007, at 22:20, Keith Hodges wrote:
> Hello Lukas,
>
> a while ago you gave me this code. Now I am using the latest
> seaisde 2.8 it doesnt work as I would like. The widgit works but
> its callbacks fail. Any thoughts on what may have changed?
>
> cheers
>
> Keith
>
>
> From: Keith Hodges <keith_hodges(a)yahoo.co.uk>
> Date: 27. Juli 2007 04:30:25 GMT+02:00
> To: "small >> \"SmallWiki, Magritte, Pier and Related Tools ...\""
> <smallwiki(a)iam.unibe.ch>
> Subject: Help needed to run widgets in other contexts
> Reply-To: "Magritte, Pier and Related Tools ..."
> <smallwiki(a)iam.unibe.ch>
>
>
> Help!
>
> Hi All,
>
> A while ago Lukas gave me the following code for opening a pier widget
> so that it would be able to access its context even though we are not
> even in a pier application!
>
> self - is my control panel which runs in the WADispatcherEditor's
> session.
> widget is PUUsers or PUGroups
>
> ControlPanel-callWidget: widget titled: title
>
> PRCurrentContext use: self during: [
> WARenderLoop new call: (widget
> addDecoration: (WAWindowDecoration new
> title: title;
> yourself);
> yourself) ]
>
>
> This works to the extent that the widget displays correctly,
> however the
> buttons do not work due to PRCurrentContext value being nil.
>
> I am using the latest everything in the development universes.
>
> Does anyone have any ideas?
>
> thanks in advance
>
> Keith
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
>
>
--
Lukas Renggli
http://www.lukas-renggli.ch
Hello,
I was updating my Pier installation (using Pier-Seaside-lr.182 and
others), it stumbled at
PRPieronfiguration>>ancestors
^ Array with: WARenderConfiguration new
not knowing the class WARenderConfiguration. Replacing this with
WARenderLoopConfiguration works OK so far.
I am running seaside 2.7b1. Looks like the ancestors method comes from
Pier-Seaside-lr.182. Maybe WARenderLoopConfiguration got renamed to
WARenderConfiguration in Seaside 2.8?
Is it OK to use WARenderLoopConfiguration here? If not, where can I
get WARenderConfiguration ?
best regards
Matthias
Hi,
I'm a user of seaside testing. SeasideTesting provides two
methods for accessing form elements. It's by index and by
element id. Requesting by index is too error prone as the
change of the order of form elements breaks the test.
Requesting by id is rendered impossible by using Magritte.
The ajaxId: stuff includes the hash of an object and is not
predictable when used inside a test.
I changed ajaxId: in MAComponent to use the following:
ajaxId: aSymbol
| accessor |
^ String streamContents: [
:stream|
accessor := self description accessor.
[ accessor respondsTo: #next ] whileTrue: [
stream nextPutAll: accessor accessor readSelector.
stream nextPut: $..
accessor := accessor next
].
stream nextPutAll: accessor readSelector.
].
This gives you the name of the selector as id and for nested
descriptions you get nestedObjectSelector.selector. Therefor
the ids per object are unique and are easily used in SeasideTesting.
But my colleague reminded me that this only works if I have a
single form on the page. He said the id has to be unique across
the whole page. So my approach is bit critical.
Is there anybody who uses SeasideTesting for testing magritte
components? And if yes how do you do that?
thanks,
Norbert
I have an existing seaside application that I would like to port into
the Pier framework, and need some pointers :)
1. I store some things on session; what is the Pier equivalent?
2. Do I have to move my renderContentOn: methods to renderWidgetOn:?
3. Should I subclass MAComponent or PRViewComponent or something
entirely different?
Thanks!
Brian
(I've looked on the pier Wiki and read the FAQ and have got a minimal
grasp of Magritte (and am using it in a non Pier context), but I
haven't found any developer getting started type documentation)
At some point I thought I saw a video demonstrating how to create
the birthday forms used in "Creating Custom Forms" video using the
web interface. The "Creating Custom Forms" video shows how to copy
one and modify it, but not how they got there in the first place. Is
that still around some where?
Thanks,
Brian
Hi,
OrderedCollection>>copyWithAll: does not work.
(OrderedCollection with: 1 with: 2) copyWithAll: {3 . 4 . 5 }
throws an error. It uses replaceFrom:to:with: which tries
to operate on non-existing indexes. copyWithAll: is just
used at two places
MADistribution>>addPostscript:
and
MADistribution>>addPreamble:
These make use of Collection>>copyWithAll: which works for
String objects. OrderedCollection>>copyWithAll: is never
used.
So it isn't that important and might be better removed
regards,
Norbert
