Hello.
I glad announce new Calypso version. It is a big refactoring on navigation model and browser pluggability. Look for details in my blog http://dionisiydk.blogspot.fr/2017/12/new-calypso-version-08-is-out.html. Now I start document new design and will post progress on it. Notice: this version is not adopted for TelePharo and Cargo. It will be done soon. Best regards, Denis |
Hi Denis, Congratulations on the new release! Two quick question: 1) does this work on latest Pharo 6.1 ; 2) Is it safe to update images with Calypso already installed by doing the same baseline loading as the original installation ? Thanks On Tue, Dec 12, 2017 at 9:05 AM, Denis Kudriashov <[hidden email]> wrote:
|
2017-12-12 13:25 GMT+01:00 Mariano Martinez Peck <[hidden email]>:
Yes
I think not. But I not try. I just have impression that complex updates are not properly work in Pharo. All package structure is changed and it can be a problem for such update.
|
I found some performance problem with this version. I know the reason. It will be fixed soon. Now you can try disable critiques plugin with github instructions. 2017-12-12 13:52 GMT+01:00 Denis Kudriashov <[hidden email]>:
|
Hi Denis,
I use it without critiques and it works fine. I have some observations: - test cases in an abstract class can be executed, it might be disabled as it does not make sense to execute them - test cases defined in a superclass cannot be executed separately (only as all test cases by clicking on the class icon) - it might be a good option to be able to execute failing test cases (there is a dedicated method group that appears in such situations) - and maybe also when browsing “inherited methods” Thanks for the great job! Juraj
|
In reply to this post by Denis Kudriashov
And I made new release v0.8.4 which solves performance problem. I found very nice solution to ensures single Calypso UI update after multiple changes from single UI command. For example implementors window updates only once when you rename implementor message. Before number of updates was equals to number of implementors because every rename triggers method remove. Same problem is relevant to current MessageBrowser. Now in Calypso there is general solution to the problem. Also in this version there is context menu item to switch order of class hierarchy in variables view and method visibility view. So people who prefer classic order for hierarchy should be satisfied. Best regards, Denis 2017-12-14 18:45 GMT+01:00 Denis Kudriashov <[hidden email]>:
|
In reply to this post by Juraj Kubelka
Hi Juraj
2017-12-14 19:36 GMT+01:00 Juraj Kubelka <[hidden email]>:
It is in my todo. For abstract test cases I do not think it should be disabled. It should run all hierarchy tests. It works like that in other IDE's and it is very suitable.
|
In reply to this post by Denis Kudriashov
On Mon, Dec 18, 2017 at 9:56 AM, Denis Kudriashov <[hidden email]> wrote:
Can you explain it? I think most UI apps will benefit from that :)
|
2017-12-18 10:31 GMT+01:00 Guillermo Polito <[hidden email]>:
Approach is quite simple but with little trick. Data source of table is responsible to update it when underlying query result is changed. And when it happens data source just marks itself as dirty and defer actual update to the next UI iteration using "UIManager default defer: [self runUpdate]". In case when data source is already dirty it just ignores the event. It means that current UI command will continue required system modifications without actual UI update. And only when it will complete the deferred update will be executed. Also update is forced in case when user manually interact with dirty data source. In that case following deferred update will be ignored. So I guess trick with dirty flag and deferring update can be reused by other applications.
|
Free forum by Nabble | Edit this page |