>> > Thanks Stef and Ben. I did get it to work with the latest Pharo-1.3 core. It > has > a clean interface that I look forward to using it when it becomes official. > > I am not familiar enough with the Pharo Core -> Pharo Dev process so I was > not able to get the Mercury Panel (if it works in Nautilus), the refactoring > tools and navigation history to work.
it does not. Ben will add refactoring support soon (matter of menus), navigation and search. > Actually, the project that I'm currently on also makes uses of some of the > underlying components in Pharo-1.2 like Morphs and Editors so I can't really > use the bleeding edge in Pharo-1.3. But I would like to use it soon. So some > questions for you as core developers: > > 1) Do you have a API for Pharo-1.2? I know that you can do WorldMenu > Help > and browse to Pharo > API Reference but there is nothing official there > stating > that those are the "official" APIs. not that I know :) > 2) When do you expect to have an API freeze for Pharo-1.3? That way I can > start porting what we to make sure that it works. 1.3 is stable, really stable. > Anyway back to O2. I'm in the process of getting the O2 packages to work. > I've > gotten them to load for the most part and from my own use they seem to work. > I'll try to make the remaining failing/error tests pass and then post my > initial changes. I already know that some things don't work like undo/redo > but I (or > someone else) can fix those later. I would not invest on O2. This is the past and it bends too much OB so have a look at nautilus the groups are working much better. Stef > > Thanks! > > -- > Nick > > -- > View this message in context: > http://forum.world.st/Code-Navigation-Navigation-History-in-System-Browser-tp3438888p3442194.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >
