Hi,
I am giving the new PRDocumentWidget a try on my webpage. With this
occassion, I got rid of all environments and just use the documents
instead of templates. It just took a while to figure out that I have
to select the checkbox to make the documents inherited :).
It's a very nice mechanism.
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Every thing has its own flow."
yes, encodings once again :)
My CSS has UTF8 content that gets displayed: I'm using foo:after {
contents: '»'; } (that's a french closing guillemot in there, looks
like >> )
I'm loading it in a subclass of WAFileLibrary using #addAllFilesIn:
When I use WAKom, the guillemot becomes an error character. With
WAKomEncoded it's displayed correctly. but then I can't use some
characters when editing pages.
My understanding was that WAKomEncoded converts to the squeak internal
representation, and WAKom does nothing, so WAKom should work (as long
as I have UTF in my files, which is the case), and WAKomEncoded could
fail if it tries to convert what's in the FileLibrary from squeak to
utf before serving…
Why is it the reverse in practice?
--
Damien Pollet
type less, do more [ | ] http://typo.cdlm.fasmz.org
Hi,
the latest version of Pier includes a few experimental features. I
would like to hear your opinion on these:
1. Environments
Before environments were a reference to a different page anywhere on
your page. One idea was to replace this reference with a document
(like the page has one). This allows then to edit the meta-page using
the settings and have it close to the page it is applied to. As
before, keeping it empty would inherit the environment from the
parent. Do you think that improves the usability?
2. Custom Documents
Another idea was that an environment (that is independent of the
proposal above) can add any number of document (formerly called
content widget) widgets. These widgets could then be put for example
into a side-bar or the heading to allow customization of these parts
of the page as part of the edit process of a structure. Again these
'extra' documents can have default documents and/or be inherited from
parent structures. Do you think that would be useful?
Do you think 1 is still useful if we have 2?
I appreciate any thoughts on this. Of course I already made my own
opinion (that you might read between the lines) ...
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Greetings!
One of the things I find particularly cumbersome when using magritte is
knowing the order in which my components will appear and managing their
priorities effectively. I know I am just being lazy, but I have wished
for a better way.
The new improved MACustomPrioritizedDescriptionBuilder!
If you define your description like so...
description010FirstName
description020LastName
description030Address
Then the given digits (if present) are used as the priority for that item.
enjoy
Keith
=============================
(Installer http: 'mc.lukas-renggli.ch') project:'magritteaddons';
install: 'Magriite-CustomBuilder'.
=============================
Name: Magritte-CustomBuilder-kph.6
Author: kph
Time: 18 November 2007, 12:06:52 am
UUID: 2ae04c2a-956a-11dc-9bf8-000a95edb42a
Ancestors: Magritte-CustomBuilder-kph.5
- MACustomPrioritizedDescriptionBuilder
Hi,
I am using the latest version of Pier, and I noticed that the files
get lost after playing with them. The worst part was when I wanted to
replace a picture, the complete files folder got removed (the only
thing that is left is a folder named:
files/25/wdenhhtcc8zn82to8vs8lbh4iijkxt).
I would say this is a bug. Or did I get something wronng?
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"To lead is not to demand things, it is to make them happen."
Hi,
I have a special structure and everything looks just fine, except
that when I include (+/linktomystructure+) it in another page nothing
gets rendered.
What can be the possible causes for that?
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"It's not what we do that matters most, it's how we do it."
Hello All,
I have just posted an initial release to the pieraddons repository which
provides a Tabbed and Tagged pages widget.
The "Tagged" pages widget lists those pages with a given "Tag" (or
children if no tag is specified) below either the current page or a
specific target page/structure.
The "Tabbed" pages widget presents the above list as a set of tabs, with
the selected tab rendered. This uses the kalsey css that is part of the
standard seaside style library.
To load the package:
(Installer http: 'mc.lukas-renggli.ch') project: 'pieraddons'; install:
'Pier-TabbedPagesWidgets'.
best regards
Keith
Hello all,
I just set up an image with the latest and greatest of all the
packages, Kom, Seaside, Magritte, Pier. And now when I look at the
pier site I just see the grey boxes for View, Commands and History,
nothing else shows up. I browsed the PRKernel and everything seems to
be there, it just wont render. Could this be due to the environment
changes, or should the latest version work?
Thanks,
Jason
Philippe,
I can't upload files to Pier using the out-of-the-box One Click
Exerience. Safari says:
> Internal Server Error
>
> ConnectionTimedOut: Data receive timed out.
>
> Comanche/6.2 (Mac OS) Server at 'localhost' Port 8080
I don't know if this is the best solution but I've [up | down]graded
my image to KomHttpServer-gc.30 and uploads are working fine now.
More difficult for me to solve is that since the application always
uses Seaside.image, switching to ImagePersistency doesn't produce the
expected results.
Cheers
--manuel
There appears to be some crosstalk between the Contents widget Title and
and the settings Title.
On editing the settings for the Contents widget I was expecting to see
"'%k: %t'" but instead found "Main".
regards
Keith
p.s. hows the new environment stuff going?
