[Moose-dev] Re: moosetechnology.org

Hi Tudor, On 09/14/2014 01:51 PM, Tudor Girba wrote: Yes In fact I got it, and follow your example and send a several updates and questions[1][2][3] about my attempts to implement your suggestion [1] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2014-September… [2] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2014-September… [3] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2014-September… The main conceptual issue I have is that most of the examples I see on the Deep into Pharo and Moose Books on custom browsers are mapping the flow of information in transmissions in one sense from general to particular: packages to classes -> to protocols -> to methods -> to code editor, but, in my case what I want is to make a two ways communication: from nodes tree to node content and back, so once you have selected a particular node in the tree, the content of the node is shown and once you change the text of that content in this is updated (automatically or explicitly of the first is not possible) in the nodes tree. Sending message to outside seems the way to do it, but I don't know how to send a message that captures all the text in a pane and, as I said in the follow ups of your suggestion a direct implementation of them gets the two panes (nodes tree and node content) disconnected. Is a general explanation of the issue (details are in the referred messages) but I think than that's the core issue of what I'm trying to do. As I said there, I would love to write the article about this experience on the software itself (I'm calling it Software Selfies :-P), but I hit a wall about this conceptual issue. Thanks. That are my details until now. Would be nice to have some kind of updateOn message that connects ports on specific events (text pane gets updated, node gets moved or something like that). Cheers, Offray