Hi Damien,
> I have some questions:
>
> - why do you use random numbers in PRMailLink>>urlEntry?
The class comment of PRMailLink says it all: "I am an external link
pointing to a mail address. I encode my URL to prevent spam bots
collecting the address."
> - why is it not possible to use #mailto: in WAAnchorTag in Seaside
> anymore (it's deprecacted)?
It is useless, isn't it? The attribute and the body of the tag require
different encoding anyway and this is only possible when using a
propre URL object.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Hi,
Here is what I did:
- I downloaded the latest Seaside.app
- Started Pier in the browser
- Edit Design
- Save
This results in a page that shows the pages referenced in the
Environment as missing.
The problem seems to be that the relative links in the Environment are
now solved differently. Before, they were solved relative to the
Environment, but now they seem to be solved relative to the page from
where I invoke Edit Design.
I figured this out because if you sy Edit Design from the Environment
page, the links are resolved correctly :).
So, is this the intended behavior? If it is, it means that we have to
specify the Environment with absolute links.
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Sometimes the best solution is not the best solution."
Hello--
Newbie here. :-)
I'm writing a Json visitor for a project and I'd like to stream
MAFileModel on it but I'm at a loss about how to proceed.
For most simple descriptions, streaming the value is just a matter of
rendering the value according to the description using the normal
visitor pattern. However, MAFileModel is a full-blown class and
doesn't have a corresponding description to guide the process.
What would be the most interesting path here: add the required
descriptions to the classes or just go ahead and stream the
attributes?
It seems to me that the second options make the Json visitor to
tightly coupled to the MAFileModel class. On the other hand, adding
the descriptions may not be that interesting because it would mean
changing a Magritte base class.
Any suggestions?
Thanks. :-)
--
Ronaldo Ferraz
http://log.reflectivesurface.com
Hi
The purpose or PRMeta is to add meta information to structure...
"additional fields to any structure (sort of a replacement of
Pier-Form)" .
Is it this kind of extension that could help resize picture for
instance (we add 2 Number that describe height and weight).
I don't see really well how to use them. Can you provide me a simple example ?
What is the way to use these meta variables in computation ?
Also, would PRMeta extensions to PRStructure could be added to MADescription ?
I want to make a description wich is basically a single option
description, except that I'd like to extend the description with a
symetric matrix that held comparison similarity numbers. For instance,
let's consider an attribute weatherCondition, it's options are:
(excellent, good, bad, extreme).
Let say, I have the following comparison matrix for the attribute
weatherCondition:
excellent good bad extreme
excellent 1 0.8 0.1 0
good 1 0.2 0
bad 1 0.7
extreme 1
so that: similarityBetween: 'good' and: 'bad' returns 0.2
I'd like to attach this matrix to the description, and was thinkink an
extension like meta could do it. It will allow me to edit the
similarity matrix too (sort of edit meta like in pier).
If you see any obvious alternative to do what I want, please tell me,
but I find this could be nicey done with Magritte.
Thanks
Cédrick
Hi,
When I look at the code of OrderedCollection>>removeAll from de Squeak-
Web image I see:
removeAll
"remove all elements quickly"
self become: OrderedCollection new
It seem to me that is not a fast way of removing all element of the
collection.
I would rather do:
removeAll
self setCollection: (Array new: self size)
I do not see the #removeAll method in other image and by looking at
the sender it seem that is aida who use it.
Mth
Hi
I'd like to be able to put condition on cells of my table. I want them
to be Number (float between 0 and 1 or integer between 0 and 100).
So I changed the method buildDescriptionTable in MATableComponent (a copy of it)
buildDescriptionTable
^ self dataTable collect: [ :row :col :each |
self description reference copy "(-> return a MAStringDescription)"
accessor: MANullAccessor new;
label: row asString , '/' , col asString;
propertyAt: #row put: row;
propertyAt: #column put: col;
yourself ]
becomes:
buildDescriptionTable
^ self dataTable collect: [ :row :col :each |
MANumberDescription new
accessor: (MABlockAccessor
read: [ :model | (model memento cache at: (self description) )
at: row at: col ]
write: [ :model :object | self halt. (model memento cache at:
(self description) )at: row at: col put: object]);
min: 0 max: 1;
label: row asString , '/' , col asString;
readonly: (col < row);
propertyAt: #row put: row;
propertyAt: #column put: col;
yourself ].
I think that instead of a NullAccessor and write:using: and readUsing:
which I removed, I can have a real accessor that can do the job. but
this doesn't really work :)
I'm sure I messed something with the memento (all table value are the
same now), so if you see something wrong in what I did, please tell
me.
Thanks,
Cédrick
Hi,
Still for my descriptor (attribute). I defined a similarity matrix in
the class side.
I've never used Magritte to edit class inst var, so out of curiosity,
what accessor would you use ?
I've use a Block Accessor.
(MABlockAccessor
read: [ :model | model class matrix]
write: [ :model :object | model class matrix: aMatrix]);
Is it ok to edit class side inst var ? What would you use ?
Also, I was doing a matrix description, but I saw MATableModel and
MATableComponent... it seems to be a "matrix", isnt'it ?
Thanks
Cédrick
Hi,
My import through SIXX is OK.
I can load it but when I try to login, the squeak image crash.
Does someone have experienced the same problem or have an idea of the
problem origin ?
only updating the image causes trouble too.
Thanks
Cédrick