Hallo Doru,

thank you that was it!

I had my data processing code out side this:

gtInspectorMyStuffIn: composite
    <gtInspectorPresentationOrder: 30>
    <gtInspectorTag: #myTag>

    ....
    ....
    .....

^ composite roassal2
        title: 'myTitle';
        initializeView: [
             b build
            ]

this solved the issue:

gtInspectorMyStuffIn: composite
    <gtInspectorPresentationOrder: 30>
    <gtInspectorTag: #myTag>

^ composite roassal2
        title: 'myTitle';
        initializeView: [

            ....
            ....
            ....

             b build
            ]

Stupid me.
Thanks!
Sebstian

Am 12.05.2015 um 07:22 schrieb Tudor Girba:

This is what happens in Glamour if you do the computation in the blocks of a Glamour presentation.

For example, for a Roassal presentation use only display: and painting: blocks and you will get lazy loading.

Or paste here a sketch of your code so that we can look deeper.

Doru

On Tue, May 12, 2015 at 4:18 PM, Sebastian Heidbrink <sheidev@yahoo.de> wrote:

Hi All!

I implemented a small data analyser based on Glamour and Roassal.
I took the gtInspector to Glamour browser approach and this was very easy!

No I have one problem. For one object I have 5 tabs of Roassal visualiyation and I am reading data from a DB. It is not much but the post processing for the view seems to be a little too complicated....
Is there a way to make such processing just lazy? I mean only once the user actually opens a particular tab?

Thanks!
Sebastian
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev