2 Dec
2009
2 Dec
'09
12:26 p.m.
On Dec 1, 2009, at 7:30 PM, Tudor Girba wrote:
Hi,
I do not understand this issue.
Glamour does not force you to get your code in one method. It's more the other way
around. If you get a small browser, then you do not need to get yourself a class for this.
But, if you have a complex browser just have a dedicated class and place the different
parts as methods in that class.
Please tale a look at GLMCodeBrowser in Glamour-Examples. This provides an example of how
you can decompose a larger browser in small methods in a dedicated class.
I know the examples. I'm still skeptical about the fact that I need a dsl to script
browser vs having plain objects with class.
So, I get back to my original question: what are the
impediments that you encountered when trying to build your browsers?
Cheers,
Doru
On 1 Dec 2009, at 17:39, Stéphane Ducasse wrote:
scripts?
versus classes.
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Jannik.
Please follow the suggestion of Simon and let us know if it works.
Now, when you say that it is difficult to modularize the browser, is it not due to the
inner complexity of the browser? I mean, except for this detail, is there anything else
that stays in your way?
Cheers,
Doru
On 1 Dec 2009, at 15:18, Laval Jannik wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Doru,
So, what I do for now is a merging of my methods.
And I don't have any problem :)
But in fact, it is difficult to modularize my browser :)
Thank you for your help.
Cheers,
Jannik
On Dec 1, 2009, at 14:52 , Tudor Girba wrote:
> Hi Jannik,
>
> I think that the problem is more complicated and I am not sure what is the right way
about it.
>
> When you capture several ports in:
> browser showOn: #feedback;
> from: #browser -> #selectedVersion;
> from: #browser -> #selectedCat;
> from: #browser -> #selectedElement;
>
> you can reason about three things when trying to #display: a presentation. In other
words, you get three objects in your block.
>
> However, in the current implementation, after this step the result of the display: is
stored in one port: #entity. And when you look at this port from inside the browser you
only see one object.
>
> Cheers,
> Doru
>
> On 1 Dec 2009, at 14:26, Laval Jannik wrote:
>
>> Yes, oki,
>>
>> Now, how can I specify parameters ?
>> I tried to use "from:"
>> But if I put "from: #selectedVersion", there is an exception.
>>
>> What is the syntax to do this ?
>>
>> Cheers
>>
>> On Dec 1, 2009, at 14:12 , Simon Denier wrote:
>>
>>> Seems like you dont take any parameter in the different subpanes of your
feedback. Then I guess you get only the default parameter of the browser, which would be
the first one, i.e. selectedVersion
>>
>>
>>
>> Jannik
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every successful trip needs a suitable vehicle."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev