What should I do to be able to use roassal2 representation on Pharo? Because I’ve tried to load Roassal2 group form ConfigurationOfGlamour, but then it loads newer version of glamour which breaks in some way the inspector.
This why slowly we should meta data in the image so that we can manage
better loaded configurations and the rest.
Christophe should have a beta soon.
On 29/10/14 05:31, Yuriy Tymchuk wrote:
> Hi,
>
> What should I do to be able to use roassal2 representation on Pharo? Because I’ve tried to load Roassal2 group form ConfigurationOfGlamour, but then it loads newer version of glamour which breaks in some way the inspector.
>
> Uko
>
You should load the default group of the ConfigurationOfGTInspector. This will load Roassal2, the binding with Glamour and the inspector extensions that use Roassal2.
Cheers,
Doru
On Wed, Oct 29, 2014 at 11:31 AM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,
What should I do to be able to use roassal2 representation on Pharo? Because I’ve tried to load Roassal2 group form ConfigurationOfGlamour, but then it loads newer version of glamour which breaks in some way the inspector.
but when I load all glamour, I end up with an error when opening inspector because there is no such class as: GLMTabSelectorBrick.
Uko
On 29 Oct 2014, at 13:07, Tudor Girba <[hidden email]> wrote:
Hi,
You should load the default group of the ConfigurationOfGTInspector. This will load Roassal2, the binding with Glamour and the inspector extensions that use Roassal2.
Cheers,
Doru
On Wed, Oct 29, 2014 at 11:31 AM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,
What should I do to be able to use roassal2 representation on Pharo? Because I’ve tried to load Roassal2 group form ConfigurationOfGlamour, but then it loads newer version of glamour which breaks in some way the inspector.
If you load the GTInspector (not just Glamour), you should get all packages updated. Could you try that?
Doru
On Wed, Oct 29, 2014 at 4:52 PM, Yuriy Tymchuk <[hidden email]> wrote:
Ok,
but when I load all glamour, I end up with an error when opening inspector because there is no such class as: GLMTabSelectorBrick.
Uko
On 29 Oct 2014, at 13:07, Tudor Girba <[hidden email]> wrote:
Hi,
You should load the default group of the ConfigurationOfGTInspector. This will load Roassal2, the binding with Glamour and the inspector extensions that use Roassal2.
Cheers,
Doru
On Wed, Oct 29, 2014 at 11:31 AM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,
What should I do to be able to use roassal2 representation on Pharo? Because I’ve tried to load Roassal2 group form ConfigurationOfGlamour, but then it loads newer version of glamour which breaks in some way the inspector.