22 Jan
2007
22 Jan
'07
6:38 a.m.
Hi all,
I am building a mostly static website that can take advantage of some
automation, so I have written it using Pier. I just took a look at the MC
repo and noticed I am a ways behind in revisions (i'm at 79) so maybe there
is a way to do this now. Or maybe there was before I just didn't understand
it.
What I am doing is making a band website. One of the things we need on the
page are CD's. What I would like to do is; in Pier do a normal Component
add, but I would select PRCDPage instead of the normal one. Then I can edit
the CD from the Edit command. Simple enough.
But it occurs to me that this is a more general problem. I have an object
which may be image only, or it may actually live in the database. I want to
do a "PRModelPage" add, have the edit let me select the model and then after
the model is known the Edit command will edit the object directly.
I really think something like this would be helpful for the site overall. I
think this is the type of thing you get easily from Rails. So before I go
off and implement it, I thought I was ask, what do you guys think? Does
this exist already? Is there some better way it should be implemented them
how I am suggesting (i.e. the Migretta meta-information will have to be kind
of "two phase")?
Thanks for any insight you can provide,
Jason
_________________________________________________________________
Turn searches into helpful donations. Make your search count.
http://click4thecause.live.com/search/charity/default.aspx?source=hmemtagli…
22 Jan
22 Jan
7:47 a.m.
I am building a mostly static website that can take
advantage of some
automation, so I have written it using Pier. I just took a look at
the MC
repo and noticed I am a ways behind in revisions (i'm at 79) so
maybe there
is a way to do this now. Or maybe there was before I just didn't
understand
it.
What package? There are several packages with version 79, some of
them even have multiple branches with a 79 version. Pier-All-lr.79?
What I am doing is making a band website. One of the
things we
need on the
page are CD's. What I would like to do is; in Pier do a normal
Component
add, but I would select PRCDPage instead of the normal one. Then I
can edit
the CD from the Edit command. Simple enough.
But it occurs to me that this is a more general problem. I have an
object
which may be image only, or it may actually live in the database.
I want to
do a "PRModelPage" add, have the edit let me select the model and
then after
the model is known the Edit command will edit the object directly.
I am a bit confused. First you talk about Components, I guess you
ment structures.
Now you talk about models, what is a "PRModelPage"?
Then you talk about the addition of a structure. And about the fact
the user has to choose the type (Page, File, Component) before adding
it.
I really think something like this would be helpful
for the site
overall. I
think this is the type of thing you get easily from Rails. So
before I go
off and implement it, I thought I was ask, what do you guys think?
Does
this exist already? Is there some better way it should be
implemented them
how I am suggesting (i.e. the Migretta meta-information will have
to be kind
of "two phase")?
Isn't this already the default behavior? Adding lets you select the
type, then an editor on the selected type is displayed. Two-phases,
the first one always looks the same, the second one is different
depending on the type selected and its user customizable settings.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
7:48 p.m.
From: Lukas Renggli <renggli(a)iam.unibe.ch>
Reply-To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Subject: Re: PRModel
Date: Mon, 22 Jan 2007 07:47:03 +0100
What package? There are several packages with version 79, some of
them even have multiple branches with a 79 version. Pier-All-lr.79?
Well, the point is, it's old now. It is Pier-model-lr.79 I think and
Pier-seaside-lr.79.
But it occurs
to me that this is a more general problem. I have an
object
which may be image only, or it may actually live in the database.
I want to
do a "PRModelPage" add, have the edit let me select the model and
then after
the model is known the Edit command will edit the object directly.
I am a bit confused. First you talk about Components, I guess you
ment structures.
Now you talk about models, what is a "PRModelPage"?
Then you talk about the addition of a structure. And about the fact
the user has to choose the type (Page, File, Component) before adding
it. Isn't this already the default behavior? Adding
lets you select the
type, then an editor on the selected type is displayed. Two-phases,
the first one always looks the same, the second one is different
depending on the type selected and its user customizable settings.
It is. I was just thinking of one more layer between. Thanks for the quick
feedback.
_________________________________________________________________
Laugh, share and connect with Windows Live Messenger
http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://im…
8:37 p.m.
What package?
There are several packages with version 79, some of
them even have multiple branches with a 79 version. Pier-All-lr.79?
Well, the point is, it's old now. It is Pier-model-lr.79 I think
and Pier-seaside-lr.79. Then you talk
about the addition of a structure. And about the fact
the user has to choose the type (Page, File, Component) before adding
it.
Well, I guess at 4am it seemed clear enough. :) What I was basically
thinking was (as clearly as I can remember it) if I have some class
that was
previously in the image (for example) that happens to be a domain
object,
then maybe we could have a generic class that has a member variable
"model".
The initial "Edit" command in pier would let you point this model
variable
at a given class, database table or whatever. After that, the
class would
have the meta-descriptions so that the pier "Edit" command would
let you
edit an instance of the actual domain object, etc. :) I realize you can do this from Magritte by adding the
meta information
directly, but I was just trying to think of a way to make it more
automatic.
Maybe it's a bad idea, which is why I wanted to ask before I go
writing
misguided code. :)
The example I am giving above needs some work. It is a bit too
complex for people not being familiar with the underlying model. If
you want to improve, feel free to do so ...
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
24 Jan
24 Jan
6:02 a.m.
New subject: Magritte Collection Description
Hi all,
I am writing some Magritte descriptions for a class of mine and I don't see
something I really expected to see. This of course makes me think I am
missing something.
What I have is, a class with various fields I want to have set, including a
collection of strings. The others were no problem, MANumberDescription and
so on, but I don't see anything for handling a collection. The nearest
thing I saw was MAToManyDescription? But that seems to want something more
complex. Perhaps it is for linking classes together. I looked at
MACollection but that said it is for a collection of *descriptions*. I
tried it anyway, and it didn't understand #default. :)
Thanks for any help you can give me. If I just have to write one, or
upgrade that is ok. I just wanted to make sure I'm not missing something
fundamental.
Thanks,
Jason
_________________________________________________________________
Laugh, share and connect with Windows Live Messenger
http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://im…
9:13 a.m.
New subject: Magritte Collection Description
Support for collections in Magritte is weak. For quite some time I
planned to add support for multiplicities like in EMOF and UML,
however I never found the time to actually do it.
What I have is, a class with various fields I want to
have set,
including a collection of strings. The others were no problem,
MANumberDescription and so on, but I don't see anything for
handling a collection. The nearest thing I saw was
MAToManyDescription?
Yes, MAToManyDescription is what you are looking for. If you are not
using fully described objects as children, you want to check out its
subclass MAToManyScalarRelationDescription. Maybe Philippe can give
you more hints on how to use that?
The description probably looks something like this:
^ (MAToManyScalarRelationDescription selector: #flowers)
reference: MAStringDescription new;
default: #();
yourself
I looked at MACollection but that said it is for a
collection of
*descriptions*. I tried it anyway, and it didn't understand
#default. :)
I don't have MACollection in my image, only MAContainer. As you said,
this is a collection of descriptions; not a description on collections.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
11:10 a.m.
New subject: Magritte Collection Description
2007/1/24, Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
Support for collections in Magritte is weak. For quite
some time I
planned to add support for multiplicities like in EMOF and UML,
however I never found the time to actually do it.
Yeah, that's about it. Check out ICalMagritte for examples:
descriptionComments
^(MAToManyScalarRelationDescription selector: #comments label:
'Comments' priority: 5000)
classes: (Array with: String);
reference: MAMemoDescription new;
yourself
Note that MAToManyScalarRelationDescription is really just a hack and
hopefully disappears once multiplicities are fixed. So use it with
caution.
Cheers
Philippe
What I have is, a class with various fields I
want to have set,
including a collection of strings. The others were no problem,
MANumberDescription and so on, but I don't see anything for
handling a collection. The nearest thing I saw was
MAToManyDescription?
Yes, MAToManyDescription is what you are looking for. If you are not
using fully described objects as children, you want to check out its
subclass MAToManyScalarRelationDescription. Maybe Philippe can give
you more hints on how to use that?
The description probably looks something like this:
^ (MAToManyScalarRelationDescription selector: #flowers)
reference: MAStringDescription new;
default: #();
yourself I looked at
MACollection but that said it is for a collection of
*descriptions*. I tried it anyway, and it didn't understand
#default. :)
I don't have MACollection in my image, only MAContainer. As you said,
this is a collection of descriptions; not a description on collections.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
6541
days inactive
6543
days old
6 comments
3 participants
participants (3)
-
J J -
Lukas Renggli -
Philippe Marschall