Smalltalk › Pharo › Pharo Smalltalk Users

history graph widget

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

7 messages Options

tinchodias

history graph widget

I would like to have a Morphic widget like this. Does anyone know if there is something already done that I could reuse?

Maybe do it with Roassal in this way:

Use the list morph, where each row knows an image morph with its corresponding slice of the graph.

Each time the graph changes (for example, if a node is appended), render using Roassal the part of the graph has to be updated, and cut the rendered surface in the new slices for each updated row.

Any opinion?

Maybe I should think more in vectors (i.e. Athens) instead of pixels/images?

Cheers,

Martin

stephane ducasse

Re: history graph widget

did you check whtat alain did for the profiler?

On May 19, 2013, at 6:24 PM, Martin Dias <[hidden email]> wrote:

Hi

I would like to have a Morphic widget like this. Does anyone know if there is something already done that I could reuse?

Maybe do it with Roassal in this way:

Use the list morph, where each row knows an image morph with its corresponding slice of the graph.

Each time the graph changes (for example, if a node is appended), render using Roassal the part of the graph has to be updated, and cut the rendered surface in the new slices for each updated row.

Any opinion?

Maybe I should think more in vectors (i.e. Athens) instead of pixels/images?

Cheers,
Martin

tinchodias

Re: history graph widget

No, I think. Where can I find it?

On Mon, May 20, 2013 at 4:42 PM, stephane ducasse <[hidden email]> wrote:

did you check whtat alain did for the profiler?

On May 19, 2013, at 6:24 PM, Martin Dias <[hidden email]> wrote:

Hi

I would like to have a Morphic widget like this. Does anyone know if there is something already done that I could reuse?

Maybe do it with Roassal in this way:

Use the list morph, where each row knows an image morph with its corresponding slice of the graph.

Each time the graph changes (for example, if a node is appended), render using Roassal the part of the graph has to be updated, and cut the rendered surface in the new slices for each updated row.

Any opinion?

Maybe I should think more in vectors (i.e. Athens) instead of pixels/images?

Cheers,
Martin

stephane ducasse

Re: history graph widget

in the image

timeprofiler

On May 20, 2013, at 5:59 PM, Martin Dias <[hidden email]> wrote:

No, I think. Where can I find it?

On Mon, May 20, 2013 at 4:42 PM, stephane ducasse <[hidden email]> wrote:

did you check whtat alain did for the profiler?

On May 19, 2013, at 6:24 PM, Martin Dias <[hidden email]> wrote:

Hi

I would like to have a Morphic widget like this. Does anyone know if there is something already done that I could reuse?

Maybe do it with Roassal in this way:

Use the list morph, where each row knows an image morph with its corresponding slice of the graph.

Each time the graph changes (for example, if a node is appended), render using Roassal the part of the graph has to be updated, and cut the rendered surface in the new slices for each updated row.

Any opinion?

Maybe I should think more in vectors (i.e. Athens) instead of pixels/images?

Cheers,
Martin

tinchodias

Re: history graph widget

ah, yes, it's great! thanks

On Mon, May 20, 2013 at 6:38 PM, stephane ducasse <[hidden email]> wrote:

in the image

timeprofiler

On May 20, 2013, at 5:59 PM, Martin Dias <[hidden email]> wrote:

No, I think. Where can I find it?

On Mon, May 20, 2013 at 4:42 PM, stephane ducasse <[hidden email]> wrote:

did you check whtat alain did for the profiler?

On May 19, 2013, at 6:24 PM, Martin Dias <[hidden email]> wrote:

Hi

I would like to have a Morphic widget like this. Does anyone know if there is something already done that I could reuse?

Maybe do it with Roassal in this way:

Use the list morph, where each row knows an image morph with its corresponding slice of the graph.

Each time the graph changes (for example, if a node is appended), render using Roassal the part of the graph has to be updated, and cut the rendered surface in the new slices for each updated row.

Any opinion?

Maybe I should think more in vectors (i.e. Athens) instead of pixels/images?

Cheers,
Martin

hernanmd

Re: history graph widget

In reply to this post by tinchodias

For the grid part the SGrid supports embedding morphs, check the examples

http://stackoverflow.com/questions/4674116/are-there-any-open-source-spreadsheet-implementations-in-smalltalk-which-are-use

cheers,

Hernán

El 19/05/2013 13:24, Martin Dias escribió:

> Hi
>
> I would like to have a Morphic widget like this. Does anyone know if
> there is something already done that I could reuse?
>
> Inline image 1
>
> Maybe do it with Roassal in this way:
>
> Use the list morph, where each row knows an image morph with its
> corresponding slice of the graph.
>
> Each time the graph changes (for example, if a node is appended), render
> using Roassal the part of the graph has to be updated, and cut the
> rendered surface in the new slices for each updated row.
>
> Any opinion?
>
> Maybe I should think more in vectors (i.e. Athens) instead of pixels/images?
>
> Cheers,
> Martin

tinchodias

Re: history graph widget

Thanks Hernán, I'll take a look.

Martín

On Mon, May 20, 2013 at 8:19 PM, Hernán Morales Durand
<[hidden email]> wrote:

> For the grid part the SGrid supports embedding morphs, check the examples
>
> http://stackoverflow.com/questions/4674116/are-there-any-open-source-spreadsheet-implementations-in-smalltalk-which-are-use
>
> cheers,
>
> Hernán
>
> El 19/05/2013 13:24, Martin Dias escribió:
>>
>> Hi
>>
>> I would like to have a Morphic widget like this. Does anyone know if
>> there is something already done that I could reuse?
>>
>> Inline image 1
>>
>> Maybe do it with Roassal in this way:
>>
>> Use the list morph, where each row knows an image morph with its
>> corresponding slice of the graph.
>>
>> Each time the graph changes (for example, if a node is appended), render
>> using Roassal the part of the graph has to be updated, and cut the
>> rendered surface in the new slices for each updated row.
>>
>> Any opinion?
>>
>> Maybe I should think more in vectors (i.e. Athens) instead of
>> pixels/images?
>>
>> Cheers,
>> Martin
>
>
>