2011/8/29 Stéphane Ducasse <[email protected]>: > > On Aug 29, 2011, at 11:13 PM, Hernán Morales Durand wrote: > >> Hi Stef, >> >> I just want to know if OB will be supported in Pharo >= 1.4 even if >> you don't maintain it, because I've spent energy and time learning the >> framework, and I have written one developer guide for OB and I have >> planned at least 5 more browsers. > > I did that too sadly. Alex and me wrote a complete chapter for Pharo by > example 2. > Now I do not invest in system that cannot handle multiple selection and trees. > So good luck. For me trees are the basic minimum. > >
Thanks. I read all your OB chapters/papers and they are very good. I will continue using OB, nothing against Nautilus or Glamour, except that as you already know I'm out of time for learning new ST frameworks and tools. I agree, trees are a must. Now, for OB supporters/maintainers (only Lukas?): - Is that hard to add trees to the column panes without rewriting everything? -- I replaced the "code pane" with an Explorer and ImageMorph in the MagmaBrowser, the code is in SqS for almost 2 years, see http://www.youtube.com/watch?v=VxUaOFRHFPk it is not the same as handling column interactions but it's a start. There is also a feature to paginate very large lists that nobody cared to mention or even steal. -- IIRC O2 could manage trees at some point right? - The same for multiple selections (I've implemented in the old Squeak classic system browser), is the problem understanding OB or is too difficult to modify or both? - Anyone willing to collaborate or review the OB article I wrote can contact me anytime. Hernán
