Hi Frank,
> I've tryed to install pier from your squeakmap
> repository. First I take a fresh Seaside-image from
> Seaside-website and after this a load the packages
> Margrit and Pier with monticello. After restart the image
> I tryed to start Seaside-pier in the webbrowswer. There
> an error comes up with a message not understood of
> an class from Seaside. So I think it is an version-problem
> with seaside. What package versiion (mcz) you use for
> the actual version of pier?
just load the Pier package from SqueakMap into a fresh 3.8 image. It
will automatically load all required prerequisites such as Kom,
Seaside, Magritte, etc.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Hi folks,
I have this ugly walback a pair of times in a Pier wiki. I've quit
saving, then restarted the wiki, and after a couple of times of doing this
it not happen again.
I'm using the default persistent mechanism. I supouse it's image based
because no files are added to the base path of that squeak image and I have
to save the image to persist changes.
Is the persistent mechanism envolved with this scenario or not? if so,
wich alternative do you recomend? how can I make it file based?
thanks,
Sebastian
Hi, so I was playing around with the wiki a bit, started to paste in
some text from another web page, which contained the following...
“Head Start”
When I save it, the squeak VM blow chunks and dies, I think on the
illegal characters. I'm not sure how to tackle this, I'm assuming it's
really a seaside problem accepting the form upload without properly
forcing some encoding on it or something. Anyone have any ideas here,
someone's had to ran into this already, pasting text into Pier being
fatal. Suggestions?
>
> > "Head Start"
> >
> > When I save it, the squeak VM blow chunks and dies, I think on the
> > illegal characters. I'm not sure how to tackle this, I'm assuming
> > it's really a seaside problem accepting the form upload without
> > properly forcing some encoding on it or something. Anyone have any
> > ideas here, someone's had to ran into this already, pasting
> text into
> > Pier being fatal. Suggestions?
>
> Mhh, it works in my 3.8 image and vm. Can you reproduce this
> with a simpler application? Maybe even without the web? Do
> you get a stack- trace in the console?
>
> Cheers,
> Lukas
>
Hmm.. I don't have it handy at the moment, but I do recall seeing
something in the stack trace about fonts, I have Win32 fonts installed,
let me try it tonight when I get home on a clean VM and see. BTW, can
you review my notes on the latest Pier check in, I was working on
PRFilePersistency and could use a little input.
Hi
I was triing to use scriptaculous with component generated by
Magritte... and it's not working.
I used the same code as the select-list example in a subclass of
MASelectListComponent.
When used alone, it works fine (registeredAsApplication +
SUScriptLibrary)... but if I use it as the componentClass of a
MASingleOptionDescription in renderEditorOn: it doesn't work... (I
added the SUScriptLibrary in the main component that call it ).
Do you have an idea ?
Thanks
Cédrick
Hi
>So, I need a documentation of the meta-model 'Magritte'.
>
>
you should post on this list for Magritte related questions ;)
smallwiki(a)iam.unibe.ch
and go to:
www.lukas-renggli.ch and then Magritte for documentation and exercices ;)
See you
Cédrick
ps: Steph, are all questions valid for the + one point ? ;)
Hi
>So, I need a documentation of the meta-model 'Magritte'.
>
>
you should post on this list for Magritte related questions ;)
smallwiki(a)iam.unibe.ch
and go to:
www.lukas-renggli.ch and then Magritte for documentation and exercices ;)
See you
Cédrick
Hi,
It seems that the log feature works for both PRFilePersistency and
PRImagePersistency, but the History and Change reports always
generate a backtrace.
I have tried to figure out what is happening, but it looks like that
the history feature is just not there.
Any idea when it will be available?
Dominique
Hi,
when trying:
PRLatexBuilder build
the first error comes because there is no 'docs' directory in the
default directory.
the second one arrives because there is no #methodsInCategory:ofClass:
method in PackageInfo (used in PRLatexBuilder>>buildClass:category:on:)
Bye
--
Damien Cassou
Hi
Shriram Krisnarmurthi (DR Scheme) presented a nice model to identify
problem in complex modern access-control
at dagsthul.
What is interesting is that they offer a tool (margrave) to see if
there is no strange configuration, especially in the sense
of evolution of the access control.
Apparently now there are languages to express access control: XACML
seems the most important.
Stef
