(sorry wrong thread)
Error: There is no free space in this set!
I got this error when attempting to add a page
any ideas?
Keith
___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
a first attempt
Name: Pier-Security-kph.33
Author: kph
Time: 22 June 2006, 2:03:14 am
UUID: 4efb7bda-2fd7-b04d-8858-41ae19a61f37
Ancestors: Pier-Security-lr.32
Added Pier Widget for User/group management
___________________________________________________________
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" The Wall Street Journal
http://uk.docs.yahoo.com/nowyoucan.html
> > This is a subclass of the Squeak to VisualWorks code exporter
> > (implemented by Avi) adapted to properly export all the Magritte and
> > Pier packages and to get the namespaces right. Running the exporter
> > makes it possible to load all the code into VisualWorks, but I never
> > had the time to make it actually run in there ... so that is what
> > requires the next steps ...
> >
> Lukas,
>
> Just wondering if I wanted to go down this path, where can I find this
> code exporter tool -- is
> it on the Squeak side or the Visual Works side? I'd like to give it a
> shot even though I'm somewhat
> green behind the ears!
First of all you need PackageInfo-Exporters from SqueakMap. Then you
need the package "Magritte-VisualWorks" from
<http://mc.lukas-renggli.ch/magritte>. Evaluating "MADistribution
fileOutForVisualWorks" should produce you a couple of files that can
be loaded into VisualWorks, however I never actually tried to do it
;-)
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Hi,
since the current persistency models do not work (at least for me), I
have created my own which saves the image on each modification:
PRPersistency suclass: #PRSaveImagePersistency
...
PRSaveImagePersistency>>snapshot
[SmalltalkImage current snapshot: true andQuit: false]
forkAt: Processor userBackgroundPriority
PRSaveImagePersistency>>log: aContext
self snapshot
PRSaveImagePersistency>>do: aBlock
Nothing more
!-- DIV {margin:0px;}-->Yes the PRForms work perfectly in the newest Pier. The main cause was indeed the missing readUsing: and write:using: methods.
Here's my attempt at understanding what went wrong:
In my case, the missing readUsing: method caused the readUsing: method in Object to respond instead, which read the description of a PREditFormCommand instance rather than the description from the metamodel of the PRForm instance, which was missing a bunch of descriptions.
I'm not quite sure how does Pier knows what descriptions it needs to look for when I fed it the wrong descriptions. Can anyone shed some light?
Thanks,
-Bill
----- Original Message ----
From: Damien Cassou <damien.cassou(a)laposte.net>
To: Bill Sun <billksun(a)yahoo.com>
Sent: Tuesday, July 25, 2006 11:02:46 AM
Subject: Re: Trouble Following Pier Example in Master Thesis
Bill Sun wrote:
> Damien,
>
> Ah, I see, the example from the thesis was integrated into the latest
> Pier. That's probably why you already have it.
>
> The main difference that I see from the newest Pier and the code that I
> entered manually is that the PREditFormCommand class has both readUsing:
> and write:using: methods in the latest Pier while the code that I
> entered from the master thesis did not.
Does it work on the new version ? Do you understand why it doesn't on
the old one ? More questions ?
Bye
Damien,
Ah, I see, the example from the thesis was integrated into the latest Pier. That's probably why you already have it.
The main difference that I see from the newest Pier and the code that I entered manually is that the PREditFormCommand class has both readUsing: and write:using: methods in the latest Pier while the code that I entered from the master thesis did not.
-Bill
----- Original Message ----
From: Damien Cassou <damien.cassou(a)laposte.net>
To: Bill Sun <billksun(a)yahoo.com>
Sent: Tuesday, July 25, 2006 12:28:25 AM
Subject: Re: Trouble Following Pier Example in Master Thesis
Bill Sun wrote:
> Hi Damien,
Hi Bill,
> Thanks for your response! Here's the file-out.
>
> I'll try out the latest version of Magritte and Pier from
> Monticello later today.
Your class is already present in my image so you may find your answer
into the last Magritte and Pier versions on monticello (repository:
http://mc.lukas-renggli.ch/magritte or /pier)
If this is still not clear, ask here.
Hi all,
I've been having trouble with the Pier Adaptive Forms example in the thesis titled "Magritte — Meta-Described Web Application Development".
In particular, I've typed all the necessary code in my browser, prefixing "PR" and "MA" where I think should be appropriate. I can add the Form, but the "Edit Form" command that I created will not work. I get the following output when clicking on the "Edit Form" link:
(In HTML format)
PREditFormCommand(Object)>>doesNotUnderstand: #labelselfa PREditFormCommandtempsaMessagelabelinst varspropertiesnilcontexta PRContext stucture: 'Test Form' command: 'Edit Form'answernilmetamodela MAContainer label: '' comment: nilMASelectorAccessor>>read:self(MASelectorAccessor read: #label write: #label:)tempsaModela PREditFormCommandinst varspropertiesnilreadSelector#labelwriteSelector#label:PREditFormCommand(Object)>>readUsing:selfa PREditFormCommandtempsaDescriptiona MAStringDescription label: 'Label' comment: nilinst varspropertiesnilcontexta PRContext stucture: 'Test Form' command: 'Edit Form'answernilmetamodela MAContainer label: '' comment: nil[] in MACheckedMemento(MAMemento)>>pullRaw {[:each | result at: each put: (self model readUsing: each)]}selfa MACheckedMemento model: a PREditFormCommandtempsresulta Dictionary(a MAStringDescription label: 'Kind' comment: nil->'Edit Form' )eacha MAStringDescription label: 'Label' comment: nilinst varspropertiesnilmodela
PREditFormCommanddescriptiona MAPriorityContainer label: 'Container' comment: nilcacheniloriginalnil(snipped)
Also, there seems to be a missing closing parenthesis on page 41 in the Form>>description method definition.
The Pier setup is obtained by installing the Pier Unix Security 1.0.3-alpha from SqueakMap Package Loader. In this version of Pier, clicking on the "Environment" command link will also crash Pier, is this expected?
Note: I am new to Smalltalk and Squeak.
Thanks,
-Bill
>>> How would you calculate dynamically #isAbstract for a PRCommand
>>> for example ? If I remember correctly, for the project I've done
>>> using Magritte/Pier/MySQL, I implemented #doExecute for an
>>> abstract command.
>> Something along the lines ...
>> Behavior>>isAbstract
>> ^ self allSelectors anySatisfy: [ :each |
>> (self lookupSelector: each)
>> hasLiteral: #subclassResponsibility ] ]
>
>
> I think this works for real abstract classes. But it doesn't work
> when the developer expect subclasses to send super and not override
> particular methods.
True. Object is an example, but can't think of any other core class
that does this.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
> How would you calculate dynamically #isAbstract for a PRCommand for
> example ? If I remember correctly, for the project I've done using
> Magritte/Pier/MySQL, I implemented #doExecute for an abstract command.
Something along the lines ...
Behavior>>isAbstract
^ self allSelectors anySatisfy: [ :each |
(self lookupSelector: each)
hasLiteral: #subclassResponsibility ] ]
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
