Nabble - SmallWiki

Magritte question: how to describe a Dictionary?

2008-05-07T12:17:25Z

Hi,

Let's say I have to fill a Dictionary, with pairs of "size->price", and I need to allow users to fill that dictionary...

How do I have to describe that with magritte?

Is it possible?

Thanks,

Esteban

"Querer es suscitar las paradojas"

Camus - El mito de Sísifo

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Magritte descriptions in hierarchies of classes

2008-05-05T16:28:43Z

Suppose I have a hierarchy like this:

Object subclass: #ClassA
instanceVariableNames: 'name'
classVariableNames: ''
poolDictionaries: ''
category: 'Example'

ClassA subclass: #ClassB
instanceVariableNames: 'bInstVar'
classVariableNames: ''
poolDictionaries: ''
category: 'Example'

ClassB subclass: #ClassC1
instanceVariableNames: 'c1InstVar'
classVariableNames: ''
poolDictionaries: ''
category: 'Example'

ClassB subclass: #ClassC2
instanceVariableNames: 'c2InstVar'
classVariableNames: ''
poolDictionaries: ''
category: 'Azteca-Model'

ClassA is just an abstract parent with the common functionality for the
other classes. Same for ClassB.
Only objects from ClassC1 and ClassC2 are to be created.

Should I create a "descriptionName" method in the class side of ClassA
to be inherited for ClassC1 and ClassC2 or should I create a
"descriptionName" once for each of ClassC1, ClassC2.
The same question about the inst vars for ClassB.

Summary, when you have a previously created hierarchy of classes and you
are trying to refactor code (deleting duplicated code and replace it
with magritte) how should you proceed?

It is valid to inherit the descriptions of parent classes?

What if for ClassC1 name should be displayed as 'Name' and for ClassC2
should be displayed 'Title'?

Regards,
Miguel Cobá

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: MASingleOptionDescription optionsAndLabels asDynamicObject d'ont work

2008-05-05T14:40:40Z

On May 5, 2008, at 15:46 , Dario Trussardi wrote:

> Hi All,
>
> i have one description based on MASingleOptionDescription.
>
> Now it work well when define the items with the options:
> [ MACityModel DataBase asArray] asDynamicObject.
>
> But because i need to view more text for any item in the list,
> i define the options with the method
>
> optionsAndLabels:[( MACityModel DataBase asArray) collect:[:itm|
> Association key: itm value: itm display]] asDynamicObject
>
> With it the list is right create but d'ont update at " dynamic time
> " with new item or change to MACityModel DataBase items.
>
> How i can solve my problem ?

If you look at #optionsAndLabels: you see that the code disassembles
the list. #options: does not do that. So if you want to use
#optionsAndLabels: you can't use #asDynamicObject. As you can read in
the FAQ I discourage to use #asDynamicObject anyway.

http://www.lukas-renggli.ch/smalltalk/magritte/faq

I suggest to use option (1).

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Descriptions definition

2008-05-05T09:19:26Z

Hi :-)

On Mon, May 5, 2008 at 4:51 PM, Dario Trussardi <dtrussardi@...> wrote:

>
>
> Hi,
>
> i work with Magritte framework for define more data about one specific
> problem.
>
> Now some data is defined as subclass of another class.
> [...]
> My questions are :
>
> A) What's the best method for not replicate the SuperClass descriptions ?

You just add the descriptions for the new attributes to the
subclasses. Descriptions are inherited.

> B) If i need to change the label of the priority of one of SuperClass
> description how i can do it ?

Override the superclass method with the modified description.

> C) When i need to do copy of one description and after send to the copy
> specific messages ?
>
> D) When i have a specific description,
> for example descriptionNazionality based on MASingleOptionDescription,
> and i have in the "data base" some reference to it ,
> i can define only one basic descriptionNationality and use it ( or copy
> of it ) with specific attribute ( label priority accessor ) ?

I don't understand what you want to do. Maybe

http://onsmalltalk.com/programming/smalltalk/using-magritte-with-seaside/

can give you some hints?

> What's the solution for have the best performance ? ( I think to port
> it to GLASS )

I'd advise you to program the solution that is the simplest to
program. Maybe the performance of that solution is completely OK for
your application. For persistence, see also

http://onsmalltalk.com/programming/smalltalk/simple-image-based-persistence-in-squeak/

Cheers

Matthias

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Descriptions definition

2008-05-05T07:51:30Z

Hi,

i work with Magritte framework for define more data about one specific problem.

Now some data is defined as subclass of another class.

For example :

SuperClass with descriptionCode with descriptionComment with descriptionAddress with descriptionReference and ......

SubClassOptionA with descriptionCostumer and ....other specific description for OptionA

SubClassOptionB with descriptionSupply and ..... other specific description for OptionB

My questions are :

A) What's the best method for not replicate the SuperClass descriptions ?

B) If i need to change the label of the priority of one of SuperClass description how i can do it ?

C) When i need to do copy of one description and after send to the copy specific messages ?

D) When i have a specific description,

for example descriptionNazionality based on MASingleOptionDescription,

and i have in the "data base" some reference to it ,

i can define only one basic descriptionNationality and use it ( or copy of it ) with specific attribute ( label priority accessor ) ?

What's the solution for have the best performance ? ( I think to port it to GLASS )

Any pointers would be greatly appreciated!

Thanks!

Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

MASingleOptionDescription optionsAndLabels asDynamicObject d'ont work

2008-05-05T06:46:08Z

Hi All,

i have one description based on MASingleOptionDescription.

Now it work well when define the items with the options:[ MACityModel DataBase asArray] asDynamicObject.

But because i need to view more text for any item in the list,

i define the options with the method

optionsAndLabels:[( MACityModel DataBase asArray) collect:[:itm| Association key: itm value: itm display]] asDynamicObject

With it the list is right create but d'ont update at " dynamic time " with new item or change to MACityModel DataBase items.

How i can solve my problem ?

" I thinks to found the same problem with MAMultipleOptionsDescription "

Thanks for any consideration,

Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: pier blog and google reader

2008-05-03T14:00:16Z

Hi Doru,

it works over here. See the screenshot of my blog.

Lukas

On May 3, 2008, at 22:45 , Tudor Girba wrote:

> Hi,
>
> I just noticed that Google Reader does not manage to read a Pier blog.
> I tried with both ming and Lukas, and it finds "no items".
>
> Any idea why?
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
> www.tudorgirba.com/blog
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Picture 1.png (92K) Download Attachment

pier blog and google reader

2008-05-03T13:45:58Z

Hi,

I just noticed that Google Reader does not manage to read a Pier blog.
I tried with both ming and Lukas, and it finds "no items".

Any idea why?

Cheers,
Doru

--
www.tudorgirba.com
www.tudorgirba.com/blog

"When people care, great things can happen."

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Smallwiki update

2008-05-01T13:33:20Z

There are new versions of both Smallwiki and Smallwiki SCG on Bern Store

Changes Smallwiki

- Metatag Redirect
- Metatag Custom RSS
- RSS fix moved here from Smallwiki SCG

Changes Smallwiki SCG

- Using new Google Analytics script
- No analytics for internal and logged in users
- Logged in users have access to internal pages

Alas I was not able to checkout Smallwiki in a fresh image to run the
test (in the SCG wiki 9 tests fail due to changes in Smallwiki SCG).
There seems to be an issue with Store and version ids.

cheers,
AA

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: TableDescription questions

2008-04-30T13:35:09Z

> Now my problem is:
> i can't not know the rowLabels: OrderedCollection......
> definition because it depend on the my istance of ApplicationModel.
>
> Questions:
>
> A) How i can dinamic update the rowLabels after the
> descriptionTable builder ?

See the first question at:

http://www.lukas-renggli.ch/smalltalk/magritte/faq

> B) How i can dinamic update the data of the table ?
>
> Now when the data of the table change when press the save
> buttons the system create error : Input is conflicting with current
> modification.
>
> But the table is readonly.

That's a bug. I fixed in:

Name: Magritte-All-lr.264
Author: lr
Time: 30 April 2008, 10:32:50 pm
UUID: d7c0752e-8680-40c2-aa45-2e0bdc179a71
Ancestors: Magritte-All-lr.263
Dependencies: Magritte-Model-lr.312, Magritte-Tests-lr.140, Magritte-
Seaside-lr.261, Magritte-Morph-lr.42

- do not validate invisible or readonly fields

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

TableDescription questions

2008-04-30T13:13:32Z

Hi All,

i have my ApplicationModel with some description.

Now i'm interested to display a small table based on TableDescription and TableMode.

I define the descriptionTable

descriptionTable

^MATableDescription
columnsLabels: OrderedCollection ..........

rowLabels: OrderedCollection .............

selectorAccessor: returnTableModel

beReadonly

Now my problem is:

i can't not know the rowLabels: OrderedCollection...... definition because it depend on the my istance of ApplicationModel.

Questions:

A) How i can dinamic update the rowLabels after the descriptionTable builder ?

B) How i can dinamic update the data of the table ?

Now when the data of the table change when press the save buttons the system create error : Input is conflicting with current modification.

But the table is readonly.

Any pointers would be greatly appreciated!

Thanks!

Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: MAToOneRelationDescription dispaly data

2008-04-29T08:42:22Z

Mhh, I just noticed that there is a possible bug in
MAExternalEditorComponent related to printing one-to-one relations.
This is ready to review in Magritte-Seaside-lr.261.

Lukas

On Apr 29, 2008, at 17:01 , Lukas Renggli wrote:

>> | If so, try this
>>
>> | reference: (MAContainer with: (MAStringDescription new
>> | selectorAccessor: #printString; yourself))
>>
>> | and implement your own printOn: method in your referenced object as
>> | you wish.
>>
>> I've test this solution but d'ont work.
>>
>> The printOn: method in my referenced object is never call.
>>
>> I work with vw7.5 and seaside 2.8a1.
>
> This is odd, because it works on Squeak.
>
> Actually in Squeak you don't even need to specify any reference
> description, because the default is an MAStringDescription what causes
> #asString to be sent to the object.
>
> Since you are on VisualWorks #asString might not work as expected.
> Maybe you want to try and implement it yourself on your object and
> don't specify any reference description?
>
> I added a test in Squeak that should find that kind of bug.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: MAToOneRelationDescription dispaly data

2008-04-29T08:01:39Z

> | If so, try this
>
> | reference: (MAContainer with: (MAStringDescription new
> | selectorAccessor: #printString; yourself))
>
> | and implement your own printOn: method in your referenced object as
> | you wish.
>
> I've test this solution but d'ont work.
>
> The printOn: method in my referenced object is never call.
>
> I work with vw7.5 and seaside 2.8a1.

This is odd, because it works on Squeak.

Actually in Squeak you don't even need to specify any reference
description, because the default is an MAStringDescription what causes
#asString to be sent to the object.

Since you are on VisualWorks #asString might not work as expected.
Maybe you want to try and implement it yourself on your object and
don't specify any reference description?

I added a test in Squeak that should find that kind of bug.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: MAToOneRelationDescription dispaly data

2008-04-29T03:10:41Z

> I need to dispaly more data near the button.

| This means you want a different string to be displayed?

Yes

> I have add, to the descriptionAddress definition the:
> reference: ( MAAddressModel descriptionCity, MAAddressModel
> descriptionRegion)

| If so, try this

| reference: (MAContainer with: (MAStringDescription new
| selectorAccessor: #printString; yourself))

| and implement your own printOn: method in your referenced object as
| you wish.

I've test this solution but d'ont work.

The printOn: method in my referenced object is never call.

I work with vw7.5 and seaside 2.8a1.

Cheers,
Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

descriptionContainer addCondition

2008-04-29T03:10:34Z

Hi All,

i see my last message "descriptionContainer addCondition" in the wiki are wrong formatted.

I resubmit the message.

I have define descriptionContainer with addCondition to mange the control of the data to dictionary.

The definition is:

descriptionContainer
^( super descriptionContainer)

addCondition:[ :memento | ( self controlToDataBase: memento)]

labelled:' Member not definable'; yourself

It work fine.

But when create the component with:

self call: ( ModelClass descriptionFieldOne, ModelClass descriptionFieldTwo, ModelClass descriptionFieldThree ) asComponenetOn: anModel) addValidateForm; yourself

the descriptionContainer addCondition d'ont work.

Thanks for any consideration,

Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: MAToOneRelationDescription dispaly data

2008-04-28T22:25:11Z

> I need to dispaly more data near the button.

This means you want a different string to be displayed?

> I have add, to the descriptionAddress definition the:
> reference: ( MAAddressModel descriptionCity, MAAddressModel
> descriptionRegion)

If so, try this

reference: (MAContainer with: (MAStringDescription new
selectorAccessor: #printString; yourself))

and implement your own printOn: method in your referenced object as
you wish.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: ie6 cant update tables

2008-04-28T22:10:10Z

Indeed, tables cannot be changed after they are build in IE 6. However
I think the latest version of prototype should avoid that problem by
rebuilding the whole thing if you are in IE and if you are trying to
change an existing table?

Lukas

On Apr 29, 2008, at 03:23 , Keith Hodges wrote:

> Hello Lukas,
>
> I discovered that where
>
> MAReport-renderContentOn:
>
> creates a table with an ajaxId. If you try to use a scriptaculous
> updater on this id it works in firefox, but not in ie6. So it looks
> like
> we need an enclosing div
>
> cheers
>
> Keith
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

ie6 cant update tables

2008-04-28T18:23:19Z

Hello Lukas,

I discovered that where

MAReport-renderContentOn:

creates a table with an ajaxId. If you try to use a scriptaculous
updater on this id it works in firefox, but not in ie6. So it looks like
we need an enclosing div

cheers

Keith

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

MAToOneRelationDescription dispaly data

2008-04-28T13:58:33Z

Hi All,

my english language is very limited, i'm sorry.

I have a PersonModel with some descriptions.

One of it, descriptionAddress is based on MAToOneRelationDescription

with componentClass: MAExternalEditorComponent

and classes: ( Array with: MAAddressModel )

When rendering PersonModel asComponent for the descriptionAddress the system
display the relative low priotity description near the Remove and Edit buttons.

I need to dispaly more data near the button.

I have add, to the descriptionAddress definition the:

reference: ( MAAddressModel descriptionCity, MAAddressModel descriptionRegion)

but d'ont work well.

The same problem i found in MASingleOptionDescription where reference: d'ont work.

For MASingleOptionDescription i have solve with optionsAndLabels:

In the MAToManyRelationDescription the reference: define the data to display for any item.

I think same behaviour in MAToOneRelationDescription and MASingleOptionDescription but i wrong. ?!

My question now is:

how i can display some data near the Remove / Edit buttons relative to the MAAddressModel instance.

Cheers,

Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

descriptionContainer addCondition

2008-04-26T07:36:10Z

Hi All,

i have define descriptionContainer with addCondition to manage the control for the add of maModel to Database.

descriptionContainer
    ^(super descriptionContainer)
           addCondition: [:memento | (self controlToDataBase: memento)]
          labelled: 'Member not definable';   yourself

It work fine but when i create the component with:

self call: ((ModelClass descriptionFieldOne, ModelClass descriptionFieldTwo, ModelClass descriptionFieldThree)
asComponentOn: aModel) addValidatedForm; yourself

the  descriptionContainer d'ont work.

I have add descriptionContainer to the array of description but d'ont work well.

Thanks for any consideration,

Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Memory filling up

2008-04-23T23:56:33Z

Ahh, Keith: I removed your extension to reset the macro expander. I
guess this is not needed anymore? I don't like to have to reset things
to make bugs disappear ;-)

Lukas

On Apr 24, 2008, at 08:54 , Lukas Renggli wrote:

> I changed the macro expander to use accessors instead of blocks. If
> you load the latest version of Magritte and Pier this issue should be
> solved. If you don't have any custom macros defined, loading the code
> should work out of the box.
>
> Name: Pier-All-lr.284
> Author: lr
> Time: 24 April 2008, 8:52:30 am
> UUID: cc09a278-7890-4fa2-b3ef-61ef2e787a15
> Ancestors: Pier-All-lr.283
> Dependencies: Pier-Model-lr.219, Pier-Tests-lr.94, Pier-Seaside-lr.
> 270, Pier-Security-lr.105, Pier-Blog-lr.73
>
> - changed the macro expander to use accessors instead of blocks
> (requires the latest magritte)
> - macro expander was origianlly ported from smallwiki on vw, where
> blocks are reentrant, however in squeak blocks potentially cause bad
> things when used concurrently
>
>
> On Apr 24, 2008, at 07:53 , Lukas Renggli wrote:
>
>>> I had lots of instances of PRDocument, at one point it reported
>>> 88000...
>>
>> I've never seen this issue before.
>>
>>> The key to clearing them out appeared to be, re-initializing,
>>> PRMacroExpander,
>>
>> This doesn't change the number of PRDocument instances in my image.
>>
>>> Inspecting PRMacroExpander default, the #table dictionary of blocks,
>>> those blocks
>>> had temps, with a #context defined, and that context had properties
>>> etc...
>>
>> Maybe the problem is that Squeak blocks are not really reentrant? But
>> then you should at least get a debugger.
>>
>> Lukas
>>
>> --
>> Lukas Renggli
>> http://www.lukas-renggli.ch
>>
>>
>> _______________________________________________
>> SmallWiki, Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Memory filling up

2008-04-23T23:54:12Z

I changed the macro expander to use accessors instead of blocks. If
you load the latest version of Magritte and Pier this issue should be
solved. If you don't have any custom macros defined, loading the code
should work out of the box.

Name: Pier-All-lr.284
Author: lr
Time: 24 April 2008, 8:52:30 am
UUID: cc09a278-7890-4fa2-b3ef-61ef2e787a15
Ancestors: Pier-All-lr.283
Dependencies: Pier-Model-lr.219, Pier-Tests-lr.94, Pier-Seaside-lr.
270, Pier-Security-lr.105, Pier-Blog-lr.73

- changed the macro expander to use accessors instead of blocks
(requires the latest magritte)
- macro expander was origianlly ported from smallwiki on vw, where
blocks are reentrant, however in squeak blocks potentially cause bad
things when used concurrently

On Apr 24, 2008, at 07:53 , Lukas Renggli wrote:

>> I had lots of instances of PRDocument, at one point it reported
>> 88000...
>
> I've never seen this issue before.
>
>> The key to clearing them out appeared to be, re-initializing,
>> PRMacroExpander,
>
> This doesn't change the number of PRDocument instances in my image.
>
>> Inspecting PRMacroExpander default, the #table dictionary of blocks,
>> those blocks
>> had temps, with a #context defined, and that context had properties
>> etc...
>
> Maybe the problem is that Squeak blocks are not really reentrant? But
> then you should at least get a debugger.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Memory filling up

2008-04-23T22:53:03Z

> I had lots of instances of PRDocument, at one point it reported
> 88000...

I've never seen this issue before.

> The key to clearing them out appeared to be, re-initializing,
> PRMacroExpander,

This doesn't change the number of PRDocument instances in my image.

> Inspecting PRMacroExpander default, the #table dictionary of blocks,
> those blocks
> had temps, with a #context defined, and that context had properties
> etc...

Maybe the problem is that Squeak blocks are not really reentrant? But
then you should at least get a debugger.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Memory filling up

2008-04-23T16:52:57Z

I had some thing strange going on...

I had lots of instances of PRDocument, at one point it reported 88000...

The key to clearing them out appeared to be, re-initializing,
PRMacroExpander,

Inspecting PRMacroExpander default, the #table dictionary of blocks,
those blocks
had temps, with a #context defined, and that context had properties etc...

still it freed up 100Mb...

Keith

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: MASingleOptionDescription with add button

2008-04-23T12:53:53Z

Hi Dario
> selectorAccessor: 'nazione';
You should probably use a symbol, something like #nazione.

In the latest version of Magritte you can even write

accessor: #nazione

and Magritte will take care to instantiate the right access strategy.
> beEditable;
> beSearchable;
Note, that these two properties are extensions of Pier. If you are
outside this context they won't change anything in Magritte. Unless
you have your own specific interpretation of these custom properties
of course.
> 1) In the rendering of it, where i can select one option,
> i can manage add buttons to add new element to options ?
You need to write your own view. If you are using Magritte together
with Seaside this will probably be a subclass of
MASingleSelectionComponent.

> 2) reference: MANazionalityModel description
> What's the sense of this declaration?
To render the label of the referenced object.
> When define MANazionalityModel descriptionWithOnlyOneDescription
> the system d'ont answer well ?
Sorry, I don't understand this question.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Cool Idea!

2008-04-23T11:12:01Z

>> The second class PRPierBasicBP moves the layout to:
>>
>> /environment/layout
>> /environment/style
>>
>> Again it will be cached for you "off-site" until an environment is
>> added.
>>
>
> I guess I'll have to look at the source code. I don't understand how
> different are supposed to work then? For example seaside.st uses 4
> different environments, my personal site uses 2.
>
>

No different... perhaps I should have written:

The path that a page uses to find its layout is:

*<one of my parent's local environment>*/environment/layout
*<one of my parent's local environment>*/environment/style

So I can have

/site/environment-1/layout
/site/environment-1/style

/site/environment-2/layout
/site/environment-3/style
/site/environment-4/layout

If my content looks like..

/home/intro/mine/cv

If /home/intro's local environment is set to environment-1, it and all
of its children get the layout and style from environment-1.

But /home has no environment so it will use the one cached and supplied
by the PRFrameSubclass component.

If cv is set to environment-3 , it will use the style from
environment-3, and the layout from environment-1
...

Adding this configuration as a PRKernel setting, isnt quite the right
place. PRKernel is part of the Model, and should not include any seaside
elements to do with rendering of the model. You could argue that the
environment is part of the "data", but it isnt really, its "the
configuration of the rendering". If seaside was not loaded then you
wouldnt need it.

I think PRPierFrame is the right place:

Scenario: I have written a Seaside application and I want to write some
user documentation. I put a link in my application to "Help", Help calls
a component which renders the pier documents in response to
#openOnTopic: , with a nice "Return" button at the bottom. That
component would be a variant of PRPierFrame, called
PRPierFrameReadOnlyReference.

For authoring the help documents I can use a full normal installation of
pier, but in place in another application, it would be nice to be able
to have the whole of pier as a component.

best regards

Keith

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

MASingleOptionDescription with add button

2008-04-23T08:43:22Z

Hello All,

i have one description based on MASingleOptionDescription:

linkDescription
	^(MASingleOptionDescription new)
		reference: MANazionalityModel description;
		selectorAccessor: 'nazione';

		options: [MANazionalityModel DataBase asArray] asDynamicObject ;

		label: 'Nazione';
		beSorted;
		beRequired; 
		beEditable;
		beSearchable; 
		priority: 40;
		yourself

Now my questions are:

1) In the rendering of it, where i can select one option,

    i can manage add buttons to add new element to options ?

2) reference: MANazionalityModel description

    What's the sense of this declaration?

    When define MANazionalityModel descriptionWithOnlyOneDescription the system d'ont answer well  ?

Thanks,

Dario

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Cool Idea!

2008-04-23T05:54:26Z

> The hierarchy of choices available as swappable replacements for
> PRPierFrame, is starting to mature.

I don't really know if changing PRPierFrame is the right way to go?
After all this is a rather low-level Seaside component. Maybe it would
be better to have some property in the kernel?

> The second class PRPierBasicBP moves the layout to:
>
> /environment/layout
> /environment/style
>
> Again it will be cached for you "off-site" until an environment is
> added.

I guess I'll have to look at the source code. I don't understand how
different are supposed to work then? For example seaside.st uses 4
different environments, my personal site uses 2.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Minor Inconsistency

2008-04-23T03:19:17Z

> When a PRPage is initialized it has a #document if however you edit
> that document and make it empty, the #document disappears, and
> #hasDocument reports false, even though it does really have a
> document, but it is empty.

Isn't the default document something like ...

"To edit the page bla bla ..."

?

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Cool Idea!

2008-04-22T22:12:36Z

Hello Lukas,

The hierarchy of choices available as swappable replacements for
PRPierFrame, is starting to mature.

The first, PRPierFrameCentral, implements the wiring in order for it to
be the centre of attention as I suggested yesterday. It aims to preserve
the existing behaviour, however it has a nice innovation:

If your site has no environment at all, it caches one for you. i.e. your
layout can be provided as part of your PRPierFrame subclass, and does
not need to be user visible or editable. If you edit the code that
generates your layout directly, it will get used for the next session.

And that's not all. If you add an empty page, and set that as an
environment in a structure's settings, it will automatically populate.

==
The second class PRPierBasicBP moves the layout to:

/environment/layout
/environment/style

Again it will be cached for you "off-site" until an environment is added.

==
A third class PRPierBasicCWS is a first attempt at an alternative to
blueprint.
==
A fourth class is PRPierAdmin provides a non edittable environment for
admin purposes.

cheers

Keith

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Minor Inconsistency

2008-04-22T20:35:12Z

When a PRPage is initialized it has a #document if however you edit that
document and make it empty, the #document disappears, and #hasDocument
reports false, even though it does really have a document, but it is empty.

Keith

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Blueprint

2008-04-22T07:27:22Z

Lukas Renggli wrote:

> That's interesting. So you essentially have two entry points to your
> site. For example
>
> www.seaside.st
>
> for the normal visitors and
>
> admin.seaside.st
>
> for an administrative interface to the same site?
>
> Lukas
>
>

Exactly! A whole additional dimension. It was a eureka moment for me I
think this could be very useful.

Keith

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Blueprint

2008-04-22T04:07:40Z

That's interesting. So you essentially have two entry points to your
site. For example

www.seaside.st

for the normal visitors and

admin.seaside.st

for an administrative interface to the same site?

Lukas

On Apr 22, 2008, at 10:09 , Keith Hodges wrote:

> Just to give a further example as to how this can be used...
>
> PRFrameAdmin class comment explains:
> ====
> This frame displays the site using the layout in /environment/admin,
> rather than the default.
>
> This allows a second seaside application to be set up which shows an
> admin interface to the whole site.
> This application can be configured to need authorization before
> viewing,
> while the main site is public.
>
> Thus, two (or potentially more) levels of security can be configured
> without using Pier-Security.
>
> ===
>
> Keith
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: What this for?

2008-04-22T04:06:16Z

> I am curious as to what purpose this serves in the following method.

Legacy. I guess it is not used anymore.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Re: Cool Idea!

2008-04-22T04:05:54Z

> Important methods for setting things up, such as #defaultEnvironment
> are
> on PRStructure of all places! Styles are here, layouts are there, and
> content is yet somewhere else (PRKernel class defaultRoot).

I agree, this is not ideal.

> I have tried out a solution! Route everything through the PRPierFrame,
> then you can pick a PRFrame subclass in seaside/config, or embed it in
> another Seaside application.
>
> 1. Style Libraries (currently manually added in seaside/config)
> 2. Script Libraries (currently manually added in seaside/config)
> 3. Policy for finding Layout from the structure. (currently in
> PRStructure)
> 4. Policy for finding StyleSheets (currently in PRStructure)
> 5. Default Environment (currently in PRStructure)
> 6. Default Layout (currently in PRStructure)
> 7. Default Kernel Content (currently in PRKernel class)
> 8. Not Found Handler (currently in PRMain)
> 9. Forbidden Handler (currently in PRMain)
> 10. XHTML Doctype/Strict etc. (already in PRFrame)
> 11. Ability to override the body cssClass (currently obtained from the
> structure)
> 12. Option to adapt the #settingsDescription for components being
> editted. (can add/remove fields)
>
> I have been able to provide my own preferred policies for all of the
> above, and now I feel able to deliver a "Pier for Something" module.

Sounds interesting.

> p.s. some code is in Pier-Jetsam-Environment

I will have a look, thanks.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki