Hi,
I am not quite sure I understand your problem, but I believe what you want is
to only react to a change in a text.
This information is placed in the #text port. Here is a basic example of how to
react to it:
http://ws.stfx.eu/ETEC2JH7363M
Cheers,
Doru
> On Feb 6, 2017, at 2:16 AM, Offray
Hi,
For my Grafoscopio notebooks, I have implemented a way to auto-updating
the content of a node, so it is automatically saved in the notebook when
a node content is changed. The problem is that a node contains an
embedded playground that produces text as output when executed (for
example t
Very interesting read Ben thanks for sharing
By the way I added the singleton and I optimised the loading of some image
files. More optimizations will follow the next weeks. So now you should not
be annoyed with multiple instances of ChronosManager
Thank you all for your interest in ChronosManage
Thanks for the vote of confidence :-) but sadly due to my move I won’t be able
to spend much time on Pharo in the near future :-(
--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please
see http://emailcharter.org .
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD an
Hi,
The dependencies extensions are available in the ConfigurationOfGTInspector (or
in the Moose image).
You have to inspect a version object:
Cheers,
Doru
> On Feb 5, 2017, at 4:51 PM, Peter Uhnak wrote:
>
> Hi,
>
> maybe I was dreaming but I thought I saw somewhere that GTInspector c
Hi,
maybe I was dreaming but I thought I saw somewhere that GTInspector could show
the dependencies and groups in ConfigurationOf classes. Does something like
that exist? (Obviously when I inspect any such class it doesn't show it).
Thanks,
Peter
Hi,
I finally started to move to Pharo 6, so now I can play with Icerberg...
my question is:
how can I load a repository with all its dependencies?
In other words... can I tell Icerberg that for the given Ice Repository to
execute BaselineOf?
Or is the use case:
1. use metacello to load proj
On Sun, Feb 5, 2017 at 8:32 AM, Cyril Ferlicot D.
wrote:
> Le 05/02/2017 à 01:08, Dimitris Chloupis a écrit :
>> The initial intention was to not make it a singleton to allow for
>> multiple instances of timers. Hence why it's wiped out. But making it a
>> singleton is something Phil asked for too
May be more naive eyes will more likely see glitches
Le 04/02/2017 à 22:45,
serge.stinckw...@gmail.com a écrit :
> I guess we can find better qualified people about UI quality than me ;-)
> Doru or Johan are examples.
--
Dr. Geo
http://drgeo.eu
>
> I could see some use cases there. My intention was just not to have to set
> time/break limits on every open. Another option would be to lazily
> initialize those defaults into class vars instead of hardcoding...
>
>
Well my intention also was to provide a way to save preset settings and
defaul
The idea was to use this as a fail safe in case you lost the reference to
your instance.
Singleton does not prevent you to have two or more instances existing at
the same time cause this is standard behavior for OOP. What it does is
making sure that it avoid unintentional creation of instances.
M
11 matches
Mail list logo
