it seems that #layout is expecting a LayoutFrame as argument.

But since I do not know what Stef and Igor changed (and what they didn't fix 
^^) I can't tell more than that :s

And I do not have too much time right now, sorry

Ben

On Jan 8, 2013, at 4:05 PM, Pavel Krivanek wrote:

> It does in plugin specs, for example
> 
> defaultSpec
> 
>       ^{ #ComposableSpec.
>               #vResizing:.    #shrinkWrap.
>               #add:. {{self. #textModel}.
>                               #layout:. #(0 0 1 1 0 0 0 0)}.
>       }
> 
> -- Pavel
> 
> On Tue, Jan 8, 2013 at 3:59 PM, Benjamin
> <[email protected]> wrote:
>> Can you show me your SpecLayout please ?
>> 
>> 
>> Ben
>> 
>> On Jan 8, 2013, at 3:57 PM, Pavel Krivanek wrote:
>> 
>>> Hi Stef,
>>> 
>>> get it here:
>>> 
>>> Gofer new
>>>   smalltalkhubUser: 'PavelKrivanek' project: 'Periscope';
>>>   package: 'Periscope';
>>>   load.
>>> 
>>> activate with:
>>> 
>>> Nautilus pluginClasses add: {(Smalltalk at: #NautilusPeriscopePlugin). 
>>> #none} .
>>> 
>>> I tried to change it to the array form but it doesn't help. This is
>>> the error stack:
>>> 
>>> #('Array(Object)' 'doesNotUnderstand: #layoutFrame:')
>>> #('SpecInterpreter' 'actionToPerformWithSelector:arguments:')
>>> #('SpecInterpreter' 'interpretASpec:')
>>> #('SpecInterpreter' 'interpretASpec:model:superSpec:')
>>> #('SpecInterpreter class' 'private_interpretASpec:model:superSpec:')
>>> #('[...] in SpecInterpreter' 'interpretASpec:')
>>> #('Array(SequenceableCollection)' 'collect:')
>>> #('SpecInterpreter' 'interpretASpec:')
>>> #('SpecInterpreter' 'interpretASpec:model:superSpec:')
>>> #('SpecInterpreter class' 'private_interpretASpec:model:superSpec:')
>>> #('SpecInterpreter' 'retreiveSpecFrom:')
>>> #('SpecInterpreter' 'interpretASpec:')
>>> #('SpecInterpreter' 'interpretASpec:model:superSpec:')
>>> #('SpecInterpreter class' 'private_interpretASpec:model:superSpec:')
>>> #('[...] in SpecInterpreter' 'interpretASpec:')
>>> #('Array(SequenceableCollection)' 'collect:')
>>> #('SpecInterpreter' 'interpretASpec:')
>>> #('SpecInterpreter' 'interpretASpec:model:superSpec:')
>>> #('SpecInterpreter class' 'private_interpretASpec:model:superSpec:')
>>> #('SpecInterpreter class' 'interpretASpec:model:superSpec:')
>>> 
>>> -- Pavel
>>> 
>>> On Tue, Jan 8, 2013 at 2:59 PM, Stéphane Ducasse
>>> <[email protected]> wrote:
>>>> 
>>>>> Hi Ben,
>>>>> 
>>>>> trying to run Periscope on the latest Pharo image, I see that
>>>>> everything is broken again. Please, start to write some documentation
>>>>> about Spec development, what have you changed, what do you plan to
>>>>> change, what are the new prefered ways to write UI specification and
>>>>> how to migrate old code. At least write some short mails here.
>>>> 
>>>> Hi pavel
>>>> 
>>>> where is your code?
>>>> Because we did a massive refactoring with igor to free layoutFrame users 
>>>> from the tyranny of fractions:offset:
>>>> 
>>>> so you can have a look at some spec in the latest 20 and you will see that 
>>>> now
>>>> we use
>>>> 
>>>> 
>>>>       #layout: . #(0 0 1 1 0 22 0 0)
>>>> 
>>>> when it was
>>>>       #layout:
>>>>                       {#LayoutFrame . #fractions:offsets:.    (0@0 corner: 
>>>> 1@0).      (0@0 corner: 0@20).
>>>> 
>>>> 
>>>> Now may be LayoutFrame should not be in morphic so that Spec is 
>>>> independent from Morphic but for now we prefered to avoid
>>>> to have reference to LayoutFrame and more important use of 
>>>> #fractions:offsets:
>>>> 
>>>> Esteban will start to work on a UIBuilder because we do not want to have 
>>>> to code such methods and he will do a pass on Spec.
>>>> After we will stabilize it.
>>>> 
>>>> 
>>>>> I know, it is a lot of work but we cannot write tools and bindings to
>>>>> other user interface if the basic UI framework is undocumented and
>>>>> changing silently.
>>>>> 
>>>>> Cheers,
>>>>> -- Pavel
>>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 
> 


Reply via email to