Do it the git way :) Propose your slice and let the people in charge of Pharo decide if they want it or not :)
Each time you take an image and work in it, you do a "branch". Proposing a slice is just a pull-request :) Ben On Sep 20, 2013, at 9:47 PM, kilon <[email protected]> wrote: > As you may or may not know, I am working on the pharo help tool. I already > see areas that I could improve it. I have started my own help browser tool > called "Prometheas" subclassing the existing one. However I also see that I > would like to extend and modify the existing HelpTopic class. > > Implementing Prometheas I found that I don't like the way TreeMorph works. > It practically make it impossible for me to navigate by code through the > tree and activate/select the corresponding node. It works if the father node > is expanded. If it is not, the node is not selected even after I expand the > father node, I have to resend the message to work. > > Also for some strange reason owner returns none and children returns only > the first child. So it looks like there are several issues with TreeMorph > from this first look. > > My question is how to proceed ? I have read the docs about submiting slices > after I opened the relevant issue in fogbuz, but should I do that ? > > I am very new to pharo and hence my hesitation . I dont want to mess things > up and frustrate people. I would also like to document TreeMorph , methods > that are not commented. > > > > -- > View this message in context: > http://forum.world.st/Should-I-contribute-to-Pharo-or-should-I-keep-things-separate-tp4709427.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >
