> One of my goals for Magritte and Pier is to slowly move to
> 3.9, because it offers things (Pragmas) that will make our
> life easier and that I have been waiting for a long long time
> now. For now I will try to keep compatibility for 3.7, 3.8 and 3.9.
>
> Lukas
I would hope that 3.8 remains the primary target at the very least until
after 3.9 is actually released.
Hi,
If I trie to create a Page with "_ *aLink* text" as content the Document
Parser runs into an error "Token not expected".
I tried to convince the Document Parser to accept a link behind a
horizontal rule but I don't get the right rules for the parser and
scanner. I think the parser creates a paragraph and don't expects a
horizontal rule there. If I add HorizontalRule to paragraph start and
let it return an empty array it works but creates beside the horizontal
rule a paragraph if i have linebreak after the "_". Any ideas how to
solve it a better way?
Regards, Thomas
Hi Cédrick,
> I'm still doing tests on how to model my exprience attributes with
> Magritte... I don't avance as I'd like but I get a better
> understanding on how Magritte and Seaside works... I think I
> mainly have to use existing descriptions while creating specific
> views as you suggested to me whereas at start, I was trying to do
> specific descriptions...
>
> ExpAttribute are a kind of proxy on a real value (traditional
> attribute) to which I add a simple attribute (range) that reflects
> an analyses (traduces the relevance of the attribute in the
> occurence of the event).
>
> I hope on monday I'll be able to show you something better...
> I've made some hacks in Magritte like the possibility to put
> descriptions in a collection in the class side ( not sure useful
> though :) but in that way I can see and change all of them in one
> place). Also I added a revert (or cancel) buttons to
> MAOneToOneComponent so as to cancel the memento and choose another
> classe...
the descriptions are already within a collection accessible from the
class-side, even-tough you define them within separate methods. Send
the message #description to your class and you get your collection.
Well actually it is a bit more, you get an instance of
MAPriorityContainer supporting the whole collection protocol.
> I ve tried to adapt what Michel Bany did (http://
> cdrick.seasidehosting.st/seaside/LiveTests the scrollbar) to the
> new renderer to have a MARangeComponent compatible with all browser
> but without success... Does it seems possible to you as it uses
> some functions of seaside Async ? anyway, I'll see that point
> later...
No, MARangeComponent only works in KHTML based browsers, such as
Safari or Konqueror. It is based on the draft of the next XHTML
standard and it gently degenerates to a plain input box if not
supported.
I don't use SeasideAsync, there are a few experimental controls using
script.aculo.us. This library works nicely together with seasides
canvas framework and would also provide a cross-browser compatible
slider, that could be integrated if I (or somebody else) had the time.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
I have a couple of MADateDescription to manage the effective date and
the expiration date of a structure and their values could be either a
valid date or nil.
The problem is that once a date object is assigned to these variables
through the fields generated by MADateDescription, it is not possible
to assign a nil value just by deleting the content of the fields.
MADateDescription always tries to parse the field as a date.
1. Left the field empty, effectiveDate is nil.
2. Input a date in the field, effectiveDate is a valid date.
3. Delete the content of the field, MADateDescription complains about
an invalid date format.
Is there a way to avoid that parsing?
Hi,
since the structures have a "name" beside the "title" it's very
difficult to create internal Links when you renamed (rather "retitled")
a structure.
You have to always remember the name you gave the structure first
because if you want to create internal links you have to use now this
name else the link is broken. I don't think thats a good Idea because no
one can guess the hidden "name" of structures....
Regards,
Thomas
If the text area for the contents is left empty, PRPage>>contents:
receives a nil object and fails to parse it as a document.
The reason is that the parser can only interpret string objects and
not nil objects.
PRDocumentParser parse: nil.
The solution could be to assign an empty PRDocument if the value of
aString is an nil object.
PRPage>>contents: aString
aString
ifNil: [ self document: PRDocument new ]
ifNotNil: [ self document: (self parserClass parse: aString) ].
Hi
I made an image with Pier as the default application
(http://cdrick.seasidehosting.st) but when I want to access component I
have a problem because it tries to access them via another path...
cdrick.seasidehosting.st/mini-calendar instead of
.../seaside/mini-calendar
I change the default application after having made the image...
nevertheless, it's also impossible to add new pages, component and so
on... Is it because I made the image before changing the default path ?
Also I noticed there isn't the remove command ... How to remove an
existing structure ?
See you
Cédrick
*//*
--------------------------------
L'ENIT vous invite a sa journee portes ouvertes le 17 mars 2006 de 13h30 a 19h30
Enit , 47 avenue d'Azereix 65000 Tarbes
Bus N°1, arret ENI
I've called a MAPersonEditor from my WATask, but pressing "Save" in
the editor does not seem to answer to the task. Do I need to override
a save message or something?
Thanks,
Chad
After one update of pier I have only the MATextInputFieldComponent in the section PRContentsWidget. There was the MATextAreaComponent before and I didn't find the place changing the widget from MATextInputFieldComponent to MATextAreaComponent.
Thanks in advance,
Frank
