Hi people, I am triying Pier 2, but I found this issue: If I try to put : "<div style="clear: both"></div>" under an image, I not work as in Pier 1.2. Can some body help me. Thanks _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Hi Pablo,
Hi people, I am triying Pier 2, but I found this issue:
If I try to put :
"<div style="clear: both"></div>"
under an image, I not work as in Pier 1.2.
Can some body help me.
Thanks
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
How do I format text output from my custom link? I can embed raw HTML by doing: ^PRVerbatim content: '<p>',myString1,'</p>', '<p>',myString2,'</p>'. and so on. How can I use the renderContentOn: syntax so I can take advantage of seaside's internal formatting methods... Or can I, or is there something more pier-oriented I should do instead? e.g. +values:awgvalues|factorialval=300+ goes right of the edge of the webpage currently. Thanks, Lawson _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Typically you return a PRDocument composite, as in your example with
PRVerbatim. Also you can return a string, or a collection of strings
or PRDocument items. If you return anything else, the default
#printOn: representation will be displayed.
If you are sure you only want to use the value link in the context of
Seaside you can even return a rendering block, something along ...
^ [ :html | html anchor callback: [ ... ]; with: 'some link' ]
Keep in mind that this will break if you try to convert your page to
Text, LaTeX, etc.
Lukas
On 2 October 2010 21:11, Lawson English <lenglish5 <at> cox.net> wrote:
> How do I format text output from my custom link?
>
> I can embed raw HTML by doing:
>
> ^PRVerbatim content: '<p>',myString1,'</p>', '<p>',myString2,'</p>'.
>
> and so on. How can I use the renderContentOn: syntax so I can take
> advantage of seaside's internal formatting methods... Or can I, or is there
> something more pier-oriented I should do instead?
>
> e.g. +values:awgvalues|factorialval=300+ goes right of the edge of the
> webpage currently.
>
> Thanks,
>
> Lawson
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
--
--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Thanks very much. Pier is amazingly powerful. Lawson On 10/2/10 12:22 PM, Lukas Renggli wrote: > Typically you return a PRDocument composite, as in your example with > PRVerbatim. Also you can return a string, or a collection of strings > or PRDocument items. If you return anything else, the default > #printOn: representation will be displayed. > > If you are sure you only want to use the value link in the context of > Seaside you can even return a rendering block, something along ... > > ^ [ :html | html anchor callback: [ ... ]; with: 'some link' ] > > Keep in mind that this will break if you try to convert your page to > Text, LaTeX, etc. > > Lukas > > On 2 October 2010 21:11, Lawson English<lenglish5 <at> cox.net> wrote: >> How do I format text output from my custom link? >> >> I can embed raw HTML by doing: >> >> ^PRVerbatim content: '<p>',myString1,'</p>','<p>',myString2,'</p>'. >> >> and so on. How can I use the renderContentOn: syntax so I can take >> advantage of seaside's internal formatting methods... Or can I, or is there >> something more pier-oriented I should do instead? >> >> e.g. +values:awgvalues|factorialval=300+ goes right of the edge of the >> webpage currently. >> >> Thanks, >> >> Lawson >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Hi John, You need to revert the Pharo 1.1 collection packages, because Magritte accidentally overrode the implementation in Pharo. Lukas On Oct 3, 2010, at 18:26 , John McKeon wrote: > Hello Lukas, > I updated to the latest Magritte-Model last night and found things fairly broken with the removal of these extension methods. Pier still uses reduce: in several places and MAOptionDescription uses lines in MAOptionDescription >>optionsTextual: > > Regards > John > > -- > http://john-mckeon.us -- -- Lukas Renggli, Software Composition Group (SCG) Schützenmattstrasse 14, 3012 Bern, Switzerland Room: 203, Phone: +41 31 631 8643 www.lukas-renggli.ch _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Yeah, presumably this should go into the Squeak specific packages of Grease. On Oct 3, 2010, at 20:12 , John McKeon wrote: > I see. > I have been using Squeak 4.1 =) > What are my options in that case? A squeak compatibility layer? > > > On Sun, Oct 3, 2010 at 1:48 PM, Lukas Renggli <renggli <at> me.com> wrote: > Hi John, > > You need to revert the Pharo 1.1 collection packages, because Magritte accidentally overrode the implementation in Pharo. > > Lukas > > On Oct 3, 2010, at 18:26 , John McKeon wrote: > > > Hello Lukas, > > I updated to the latest Magritte-Model last night and found things fairly broken with the removal of these extension methods. Pier still uses reduce: in several places and MAOptionDescription uses lines in MAOptionDescription >>optionsTextual: > > > > Regards > > John > > > > -- > > http://john-mckeon.us > > -- > Lukas Renggli, Software Composition Group (SCG) > Schützenmattstrasse 14, 3012 Bern, Switzerland > Room: 203, Phone: +41 31 631 8643 > www.lukas-renggli.ch > > > > > > > > > > > -- > http://john-mckeon.us -- -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Squeak's had Collection>>reduce: since 2010/04/05, if that helps. So that was probably just AFTER 4.1 was released? frank On 2010/10/03 20:15, Lukas Renggli wrote: > Yeah, presumably this should go into the Squeak specific packages of Grease. > > On Oct 3, 2010, at 20:12 , John McKeon wrote: > >> I see. >> I have been using Squeak 4.1 =) >> What are my options in that case? A squeak compatibility layer? >> >> >> On Sun, Oct 3, 2010 at 1:48 PM, Lukas Renggli<renggli <at> me.com> wrote: >> Hi John, >> >> You need to revert the Pharo 1.1 collection packages, because Magritte accidentally overrode the implementation in Pharo. >> >> Lukas >> >> On Oct 3, 2010, at 18:26 , John McKeon wrote: >> >>> Hello Lukas, >>> I updated to the latest Magritte-Model last night and found things fairly broken with the removal of these extension methods. Pier still uses reduce: in several places and MAOptionDescription uses lines in MAOptionDescription>>optionsTextual: >>> >>> Regards >>> John >>> >>> -- >>> http://john-mckeon.us >> >> -- >> Lukas Renggli, Software Composition Group (SCG) >> Schützenmattstrasse 14, 3012 Bern, Switzerland >> Room: 203, Phone: +41 31 631 8643 >> www.lukas-renggli.ch >> >> >> >> >> >> >> >> >> >> >> -- >> http://john-mckeon.us > _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Has anyone ever used Pier for collaborative documentation? I realize a wiki is sorta that already, but I'm part of an IETF group that is exploring options at the moment and I wonder if there were any existing examples of Pier being used that way? Thanks.. Lawson _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> Has anyone ever used Pier for collaborative documentation? Yes, for example books are being written using Pier. > I realize a wiki is sorta that already, but I'm part of an IETF group that > is exploring options at the moment and I wonder if there were any existing > examples of Pier being used that way? Probably more, but these are the ones that come to my mind: http://book.seaside.st/ http://book.pharo-project.org/ http://www.themoosebook.org/book/ Lukas -- -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki
RSS Feed31 | |
|---|---|
11 | |
15 | |
8 | |
26 | |
3 | |
3 | |
36 | |
33 | |
14 | |
1 | |
2 | |
20 | |
7 | |
49 | |
111 | |
28 | |
14 | |
13 | |
51 | |
56 | |
42 | |
27 | |
35 | |
31 | |
26 | |
35 | |
97 | |
58 | |
124 | |
120 | |
54 | |
55 | |
56 | |
58 | |
57 | |
103 | |
52 | |
167 | |
158 | |
10 | |
23 | |
30 | |
83 | |
32 | |
228 | |
94 | |
185 | |
213 | |
201 | |
89 | |
38 | |
33 | |
97 | |
39 | |
59 | |
153 | |
50 | |
58 | |
24 | |
69 | |
28 | |
32 | |
69 | |
44 | |
121 | |
95 | |
108 | |
124 | |
63 | |
41 | |
88 | |
116 | |
5 | |
1 | |
2 | |
1 | |
72 | |
53 | |
25 | |
69 | |
52 | |
88 | |
46 | |
75 | |
57 | |
27 | |
79 | |
33 | |
63 | |
27 | |
56 | |
30 | |
29 |
