Re: [Pharo-users] understanding existing code

2017-01-08 11:28 GMT+01:00 Hilaire : > Yet, the pane feature of Calypso will not help when browsing for > implementors > It will always help :). For example I want to add matcher/rewrite tool as tab which will work on selected scope. So in system browser it will allow search/rewrite in selected p

Re: [Pharo-users] understanding existing code

Le 08/01/2017 à 10:44, Stephane Ducasse a écrit : > We think about it since long time ago. This is why we rewrote and > produce Nautilus (but the design was not good) - remember in nautilus we > could edit mutliple methods but it was not good and why that because we > needed also panes and .

Re: [Pharo-users] understanding existing code

2017-01-07 11:42 GMT+01:00 Siemen Baader : > Thanks for all these tips and reflections. There are a number of things > for me to try now. > > @Hilaire: I'll try try Calypso. > And please, report any ideas on UI, missing features, bugs here . It is ver

Re: [Pharo-users] understanding existing code

We think about it since long time ago. This is why we rewrote and produce Nautilus (but the design was not good) - remember in nautilus we could edit mutliple methods but it was not good and why that because we needed also panes and . I agree with you about tooltip and ghost for input. You se

Re: [Pharo-users] understanding existing code

Thanks for all these tips and reflections. There are a number of things for me to try now. @Hilaire: I'll try try Calypso. There are indeed several things one could experiment with in making the important connections more visible in the development tools. I have also been thinking of a more OSX/GT

Re: [Pharo-users] understanding existing code

mind maps can extend into infinite complexity and detail, so yes the mind map will become a memory the more you use it but you still can create thousands of mind maps like I did with little chance of remembering all. I will say that for experts mind maps are far more important because a newbie ev

Re: [Pharo-users] understanding existing code

Well, what can help is the ability to create a gist and retrieve/search/list them. https://developer.github.com/v3/oauth/#scopes https://gist.github.com/caspyin/2288960 https://developer.github.com/v3/oauth_authorizations/#create-a-new-authorization This would be nice to be able to push things fr

Re: [Pharo-users] understanding existing code

Once you are an expert the mind map is in your mind, but it does not mean the mind map is useless for newbie. So every thing helping the newbie to build their own mind map is important to catch them and more importantly to make them stay with Pharo Le 06/01/2017 à 21:39, Dimitris Chloupis a écrit

Re: [Pharo-users] understanding existing code

A thing I want to try is is creating mind maps tool inside Pharo, a variant of the pen and paper technique I was using when I was studying Law. Because our Law curriculum was enormous with no chance of remembering even most of it, also my memory is kinda weak. I decided to start creating mind map

Re: [Pharo-users] understanding existing code

What you say here is very important, it is usability problem report. Often expert users and developers are trapped in their own world: want to add the super cool and elaborated features in the browser, but can't see that super cool and simple feature addition to the browser that will make life eas

Re: [Pharo-users] understanding existing code

On Fri, Jan 6, 2017 at 3:24 AM, Siemen Baader wrote: > Hi All, > > I may be missing the obvious, but what are good strategies to understand the > structure of existing code? Specifically, I'm trying to understand more of > PharoJS to solve my own problems and eventually also to contribute back - >

Re: [Pharo-users] understanding existing code

> On 6 Jan 2017, at 14:39, Henrik Johansen wrote: > > >> On 5 Jan 2017, at 20:24 , Siemen Baader wrote: >> >> Hi All, >> >> I may be missing the obvious, but what are good strategies to understand the >> structure of existing code? Specifically, I'm trying to understand more of >> PharoJS

Re: [Pharo-users] understanding existing code

> On 5 Jan 2017, at 20:24 , Siemen Baader wrote: > > Hi All, > > I may be missing the obvious, but what are good strategies to understand the > structure of existing code? Specifically, I'm trying to understand more of > PharoJS to solve my own problems and eventually also to contribute back

Re: [Pharo-users] understanding existing code

On Thu, Jan 5, 2017 at 9:33 PM, Dimitris Chloupis wrote: > After 5 years of using Pharo by far the best way to understand code is to > ask questions here. > > I have read and still read a fair amount of code, but in 50% of the cases > I have no clue what I am reading because following the chain o

Re: [Pharo-users] understanding existing code

On Thu, Jan 5, 2017 at 9:13 PM, p...@highoctane.be wrote: > Another option: > > Use the Moose Image and explore code using Roassal. > http://www.moosetechnology.org/#install > > This is an interesting approach. Thanks! > Check > > http://agilevisualization.com/ > > Also RTUMLClassBuilder can be

Re: [Pharo-users] understanding existing code

--- Begin Message --- I found that at first I was very slow at reading/groking Smalltalk code, it was like being in a twisty maze with lots of paths leading to tiny little rooms that make little sense if you're only thinking about the room that you're in. I wondered if Smalltalk wasn't over complic

Re: [Pharo-users] understanding existing code

After 5 years of using Pharo by far the best way to understand code is to ask questions here. I have read and still read a fair amount of code, but in 50% of the cases I have no clue what I am reading because following the chain of method calls can be confusing and frustrating even inside a cool I

Re: [Pharo-users] understanding existing code

Another option: Use the Moose Image and explore code using Roassal. http://www.moosetechnology.org/#install Check http://agilevisualization.com/ Also RTUMLClassBuilder can be useful. http://forum.world.st/Addling-lines-to-RTUMLClassBuilder-td4876221.html Phil On Thu, Jan 5, 2017 at 8:24 P

Re: [Pharo-users] understanding existing code

You can take an expression and "debug it" using over and through + run to here, inspecting things all over. You can also use Halt>>if: #selector Halt if: is really useful: if: condition "This is the typical message to use for inserting breakpoints during debugging. The argument can be one of th