I have a magritte component clas that uses some javascript stuff. But I couldn't get it to run. It seems that magritte components don't get the chance to. I think that MAContainerComponent is supposed to give its children the chance to update the root as well.
The attached changeset adds it to MAContainerComponent.
What do you think?
Norbert
I have a command that is a quick command and on execute time I do something like
thisStructure := self context structure.
parentStructure := thisStructure parent.
self answer: (self context structure: parentStructure)
The context then contains the right structure (parentStructure) but the url line in the browser still tells the url of thisStructure. The only thing I could confirm is that this doen't happen if isQuick is false. Then the url is updated correctly.
Any ideas?
Norbert
I'm embedding a component in a page like this
+component|className=HRWine+
On the embedded component I have
descriptionContextClassName
^ MAStringDescription new
parameterName: 'className';
accessor: #contextClassName;
priority: 100;
label: 'Name of the context class';
beRequired;
yourself
What I get is an entry in the components properties with an association description -> value. That is good so far. I'm asking myself what is the best way to access the value. If I don't specify an accessor on the description magritte creates one itself leading to equality check failing in properties when doing
self propertyAt: self class descriptionContextClassName.
But if I have to specify an accessor I'm wondering why the accessor isn't used to store the value in the component.
Do I misunderstand something or is there a preferred way of accessing parameter values?
thanks,
Norbert
Hi
The rush of Pier powered sites continues unabated .... We've just made
getitmade.com live.
Still lots to do - not least of which is to find some launch customers who
want to turn their prototype creations into products....
Thanks to everyone and especially Lukas for patiently answering my
Seaside/Magritte/Pier questions.
I'm particularly pleased with our Magritte forms - see attached image. It's
a fantastically powerful, yet flexible framework.
Thanks again
Nick
Very nice! It would be wonderful to see a little write-up on how you
constructed this. Which parts you were able to re-use and what you had to
build yourself.
-david
On Fri, Oct 22, 2010 at 11:02 AM, David Pennell <dpennell(a)good-cloud.com>wrote:
> Very nice! It would be wonderful to see a little write-up on how you
> constructed this. Which parts you were able to re-use and what you had to
> build yourself.
>
> -david
>
>
> On Fri, Oct 22, 2010 at 10:35 AM, Lukas Renggli <renggli(a)gmail.com> wrote:
>
>> Hi Nick,
>>
>> Very cool design. I've already added the link to the known sites after
>> reading you tweet :-)
>>
>> Lukas
>>
>> On Friday, October 22, 2010, Nick Ager <nick.ager(a)gmail.com> wrote:
>> > Hi
>> > The rush of Pier powered sites continues unabated .... We've just made
>> getitmade.com live.
>> > Still lots to do - not least of which is to find some launch customers
>> who want to turn their prototype creations into products....
>> >
>> > Thanks to everyone and especially Lukas for patiently answering my
>> Seaside/Magritte/Pier questions.
>> > I'm particularly pleased with our Magritte forms - see attached image.
>> It's a fantastically powerful, yet flexible framework.
>> >
>> > Thanks again
>> > Nick
>> >
>> >
>> >
>>
>> --
>> Lukas Renggli
>> www.lukas-renggli.ch
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
>
Impressive; congratulations Nick!
This is exactly what I've been looking for; I'll be posting product
ideas soon...
Good luck,
/Reza
At 17:12 22/10/2010, Nick Ager wrote:
>Hi
>
>The rush of Pier powered sites continues unabated .... We've just
>made <http://getitmade.com>getitmade.com live.
>
>Still lots to do - not least of which is to find some launch
>customers who want to turn their prototype creations into products....
>
>Thanks to everyone and especially Lukas for patiently answering my
>Seaside/Magritte/Pier questions.
>
>I'm particularly pleased with our Magritte forms - see attached
>image. It's a fantastically powerful, yet flexible framework.
>
>Thanks again
>
>Nick
>
>
>Content-Type: image/png; name="getitmade-magritte form.png"
>Content-Disposition: attachment; filename="getitmade-magritte form.png"
>X-Attachment-Id: f_gfl768py0
>
>_______________________________________________
>Magritte, Pier and Related Tools ...
>https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Thanks Lukas for your feedback and integration! Let me add that this
is just the "starter". As an extension to the OLPC project idea and
implementation, I continue to believe that there is space to deploy
one server per citizen, and a batch of 100000 servers in already
being planned for a relatively close future (so, you would probably
need to somehow automate their integration in your "installations"
page ;-)). I'll keep you informed.
/Reza
At 12:22 21/10/2010, Lukas Renggli wrote:
>Wow, thank you, that's a wealth of new sites. I've added them to the list on
>
> http://www.piercms.com/doc/examples
>
>Lukas
>
>On 20 October 2010 14:41, Reza Razavi <razavi(a)acm.org> wrote:
> > Hi Lukas,
> >
> > Please find below a few new websites that run Pier.
> >
> > For your convenience, I've organised them according to the categories in
> > your "installations" page at http://www.piercms.com/doc/examples.
> >
> > Good luck for your PhD defense.
> > Regards,
> > Reza
> >
> > Projects
> > - AAS-Platform (http://aas-platform.com/)
> > - User-Generated Services: a demo website (http://afacms.com/)
> >
> > Organizations and Groups
> > - Pontoon Community (http://pontoonity.com/)
> >
> > Companies
> > - Ambient Activity Systems (http://www.urfid.biz/)
> >
> > Individuals
> > - Reza Razavi (http://rezarazavi.com/)
> > - Goya Razavi (http://goyarazavi.com/)
> >
> > _______________________________________________
> > Magritte, Pier and Related Tools ...
> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> >
>
>
>
>--
>Lukas Renggli
>www.lukas-renggli.ch
>_______________________________________________
>Magritte, Pier and Related Tools ...
>https://www.iam.unibe.ch/mailman/listinfo/smallwiki
At 15:54 19/10/2010, Lukas Renggli wrote:
>That should be the default from Pier 1.2 on (see
>http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-July/137375.html).
>The reason why you are asking is probably because it is broken in Pier
>2.0?
If I remember well, I lost that feature after you integrated the
#isRestful test in PRContext >> urlOn:. Unfortunately, I don't have
access right now to my working image to investigate it more.
Hoping this helps,
Reza
Hi,
I remember reading or someone saying that in Pier it's possible to remove
the _s and _k from a Url? I've searched my image and the repositories and
drawn a blank. Any pointers?
Thanks
Nick
