I use it when you switch classes and methods.
To avoid interrupting method browsing I set a
loading morph and have an async task with a priority lower than
UI. When there is no UI interaction the task gets critics and
displays them. Usually the ���loading��� morph is there only for a
fraction of a second, but if you are on a class with dozens of
ivars and even more methods, then it can take a longer time.
I don���t feel that the spinning cog is important
there, but also I think that it would be nice if we have some
���in progress��� indicator. Maybe there is already something in
Bric though.
Cheers.
Uko
Hi Yiruy
when do you use it because I could see it in action?
We can package the animation out of komitter and fix this
ugly state pattern (so naive :)).
Stef
Le 24/11/15 19:58, Yuriy
Tymchuk a ��crit��:
Good catch.
At the time when I was developing it,
the loading morph implementation was such a magic
for me, that I was super happy after finishing it
and forgot that I depend on Komitter.
Is there any alternative for that?
Otherwise I will simply remove the spinning cog, I
don���t feel that this is super important.
Uko
BTW: it
would be good that QA does not refer to
Komitter. And package it as a separate project.
QA should
not dependent on Komitter because we can remove
Komitter. And it makes no sense!