Hi,
sorry if this is a known thing, but I’ve just notices this and it made my day. So in GTInspector you can browse filesystem, but when you select a fuel file, you can press a "plus” button in top right corner, and it materialises the object. Amazing. Uko |
:) Doru On Tue, Sep 30, 2014 at 10:11 PM, Yuriy Tymchuk <[hidden email]> wrote: Hi, "Every thing has its own flow"
|
On 30.09.2014, at 22:12, Tudor Girba <[hidden email]> wrote:
Hehe ;) Took me 10 minutes on MooseDay (including showing meta info) :D GT rocks! |
That's very nice!!! And that ... together with the ability to define #addPostMaterializationAction: is a super awesome combination :) On Tue, Sep 30, 2014 at 5:17 PM, Max Leske <[hidden email]> wrote:
Mariano http://marianopeck.wordpress.com |
Hi Mariano, I am not sure I understand the implication of using addPostMaterializationAction: in combination with the inspector materialization extension. Where do you see the opportunity? Cheers, Doru On Tue, Sep 30, 2014 at 10:52 PM, Mariano Martinez Peck <[hidden email]> wrote:
"Every thing has its own flow"
|
On Wed, Oct 1, 2014 at 2:25 AM, Tudor Girba <[hidden email]> wrote:
What I thought is the following..... if you are at the inspector level, and you are watching a .fuel it is nice that it materializes the file and then let you inspect the materialized object. However, if the graph was serialized with postMaterializationActions, those would be executed after you click in the inspector. This trick of the postMaterializationActions was used, for example, for when you serialize test failures or debuggers, in order to directly open a new debugger with the materialized stack upon materialization. So.... you are in the inspector, you see a fueled out stack or test failure, you click on it, and you have the debugger opened :)
Mariano http://marianopeck.wordpress.com |
Free forum by Nabble | Edit this page |