- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Coordinates problem with Athens and Morphic while coding Hyperion

by btc＠openinworld.com

Nov. 29, 2013

Re: [Pharo-dev] Nautilus Tree

by kilon alios

Currently I am working on Hyperion, a vector editor for Athens. Then I will work on Prometheas, on board documentation tool again with Athens. My third tool, if ever reach that far is Cyclops which will target the system browser. Now I am no fan of hierarchy trees. I find them hard to navigate and messy when hierarchy gets too complex. I see two solution on this one a) Sophisticated search facility, we have that already with the finder tool . I feel its time for the finder tool to go and be one with the system browser. b) Tag based browsing. That means attach tags to your classes and methods , make it easy this way to make things belong to groups and most importantly one thing could belong to more than one group. This also means bye bye packages, and instead replaced with infinite level groups, a group can be inside another group which can be inside another group etc. Of course those groups wont "exist" only their tags will "exist". I am also smiling to the Glamour philosophy of having a browser tool that can have multiple ways of viewing your classes. Bottom line is that I will be using existing ideas and I hope also code to push things just tiny bit further. So for me at least smart browsing plus tags plus good search facility can easily replace ugly hierarchy trees and packages with really long names. Just using common logic can take you a long way into improving the tools, the hard part is actually coding all this because it takes time and effort. On Fri, Nov 29, 2013 at 6:55 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > kilon alios wrote > > I dont see much room for thought, this looks to me like ideal behavior. > > I agree in theory, but it seems that the tree is primarily about chunking > information into manageable pieces. > > A primary difficulty here is that packages are often divided for reasons > that have nothing to do with the domain model, e.g. the ubiquitous > MyPackage-Platform, which is an artifact of Metacello that is not all that > relevant to a user wanting to understand the system. > > From the naive user perspective, if I'm exploring from the top level of the > system, I want to see things like: > - CodeImport > - Collections > - Compiler > > From this perspective, the 14 entries for Collections, multiplied by a few > dozen top-level categories make the list unwieldy and only marginally less > daunting than the flattened list we used to have (see > http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two) > <http://forum.world.st/file/n4726287/Picture_1.png> > > > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Nautilus-Tree-tp4723819p4726287.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Nov. 29, 2013

I'd say Pharo is fitting the bill for me. What would you love it to have?

by phil＠highoctane.be

Check http://mir.aculo.us/2013/11/27/5-things-ive-learned-in-5-years-of-running-a… Seriously, I am interested in your feedback. Shoot! Phil

Nov. 29, 2013

Re: [Pharo-dev] Nautilus Tree

by Sean P. DeNigris

kilon alios wrote > I dont see much room for thought, this looks to me like ideal behavior. I agree in theory, but it seems that the tree is primarily about chunking information into manageable pieces. A primary difficulty here is that packages are often divided for reasons that have nothing to do with the domain model, e.g. the ubiquitous MyPackage-Platform, which is an artifact of Metacello that is not all that relevant to a user wanting to understand the system. >From the naive user perspective, if I'm exploring from the top level of the system, I want to see things like: - CodeImport - Collections - Compiler >From this perspective, the 14 entries for Collections, multiplied by a few dozen top-level categories make the list unwieldy and only marginally less daunting than the flattened list we used to have (see http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two ): <http://forum.world.st/file/n4726287/Picture_1.png> ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-Tree-tp4723819p4726287.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 29, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30612 Home: https://github.com/pharo-project/pharo-core

Nov. 29, 2013

[pharo-project/pharo-core] de71ab: 30612

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: de71ab662c12d07b0cd1f996d5b4e59e60a6668d https://github.com/pharo-project/pharo-core/commit/de71ab662c12d07b0cd1f996… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-29 (Fri, 29 Nov 2013) Changed paths: M NautilusRefactoring.package/ChangesBrowser.class/class/specs/defaultSpec.st M NautilusRefactoring.package/ChangesBrowser.class/definition.st A NautilusRefactoring.package/ChangesBrowser.class/instance/accessing/changesTree.st R NautilusRefactoring.package/ChangesBrowser.class/instance/accessing/pickList.st A NautilusRefactoring.package/ChangesBrowser.class/instance/initialization/initializeChangesTree.st R NautilusRefactoring.package/ChangesBrowser.class/instance/initialization/initializePickList.st M NautilusRefactoring.package/ChangesBrowser.class/instance/initialization/initializePresenter.st M NautilusRefactoring.package/ChangesBrowser.class/instance/initialization/initializeWidgets.st M NautilusRefactoring.package/ChangesBrowser.class/instance/initialization/setFocus.st M NautilusRefactoring.package/ChangesBrowser.class/instance/initialization/setShortcuts.st R NautilusRefactoring.package/ChangesBrowser.class/instance/private/labelClicked_.st M NautilusRefactoring.package/ChangesBrowser.class/instance/private/pickedChanges.st R NautilusRefactoring.package/ChangesBrowser.class/instance/private/registerWidget_.st M NautilusRefactoring.package/ChangesBrowser.class/instance/protocol/accept.st M NautilusRefactoring.package/ChangesBrowser.class/instance/protocol/change_.st M SUnit-Core.package/ClassFactoryForTestCase.class/definition.st R SUnit-Core.package/ClassFactoryForTestCase.class/instance/accessing/createdClasses_.st R SUnit-Core.package/ClassFactoryForTestCase.class/instance/accessing/createdTraits_.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/cleaning/delete_.st R SUnit-Core.package/ClassFactoryForTestCase.class/instance/cleaning/initialize.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating - silently/silentlyNewClassInCategory_.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating - silently/silentlyNewSubclassOf_instanceVariableNames_classVariableNames_.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating - silently/silentlyNewSubclassOf_instanceVariableNames_classVariableNames_category_.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating - silently/silentlyNewSubclassOf_instanceVariableNames_classVariableNames_package_.st R SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating - silently/withNotificationsNewClass.st R SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating - silently/withNotificationsNewClassWithInstanceVariableNames_.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating/newClass.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating/newClassInCategory_.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating/newTrait.st M SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating/newTraitInCategory_.st A SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating/withNotificationsNewClass.st A SUnit-Core.package/ClassFactoryForTestCase.class/instance/creating/withNotificationsNewClassWithInstanceVariableNames_.st A SUnit-Core.package/ClassFactoryForTestCase.class/instance/initialization/initialize.st M SUnit-Tests.package/ClassFactoryForTestCaseTest.class/instance/testing/testDuplicateClassWithNewName.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script267.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30612.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/TreeModel.class/instance/protocol-events-compatibility/whenSelectedItemChanged_.st Log Message: ----------- 30612 12274 ClassFactoryForTestCase do not clean properly created behaviors https://pharo.fogbugz.com/f/cases/12274 12287 ChangesBrowser on refactoring does not well display diffs https://pharo.fogbugz.com/f/cases/12287 http://files.pharo.org/image/30/30612.zip

Nov. 29, 2013

Re: [Pharo-dev] Nautilus Tree

by Benjamin

+1 Ben On 29 Nov 2013, at 17:25, kilon alios <kilon.alios(a)gmail.com> wrote: > I dont see much room for thought, this looks to me like ideal behavior. > > > On Fri, Nov 29, 2013 at 6:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sean P. DeNigris wrote > > I noticed that right now, separate packages within the same project are > > not collapsed. E.g. if I have MyProject-Core and MyProject-Platform, they > > will be siblings in the tree, instead of both under MyProject. It seems > > like it would be more useful to have > > - MyProject > > - Core > > - Platform > > in the tree > > Bump... thoughts? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nautilus-Tree-tp4723819p4726272.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Nov. 29, 2013

Re: [Pharo-dev] Nautilus Tree

by kilon alios

I dont see much room for thought, this looks to me like ideal behavior. On Fri, Nov 29, 2013 at 6:20 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Sean P. DeNigris wrote > > I noticed that right now, separate packages within the same project are > > not collapsed. E.g. if I have MyProject-Core and MyProject-Platform, they > > will be siblings in the tree, instead of both under MyProject. It seems > > like it would be more useful to have > > - MyProject > > - Core > > - Platform > > in the tree > > Bump... thoughts? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Nautilus-Tree-tp4723819p4726272.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Nov. 29, 2013

Re: [Pharo-dev] Nautilus Tree

by Sean P. DeNigris

Sean P. DeNigris wrote > I noticed that right now, separate packages within the same project are > not collapsed. E.g. if I have MyProject-Core and MyProject-Platform, they > will be siblings in the tree, instead of both under MyProject. It seems > like it would be more useful to have > - MyProject > - Core > - Platform > in the tree Bump... thoughts? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-Tree-tp4723819p4726272.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 29, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] ba3c45: 30606

by Sean P. DeNigris

GitHub wrote > [snip] > Changed paths: > A Komitter.package/BigCogInitialState.class/README.md > A Komitter.package/BigCogInitialState.class/class/private/imageData.st > A Komitter.package/BigCogInitialState.class/class/private/size.st > [reaaaaaaaaaally long snip] > > Log Message: > ----------- > 30606 > 12209 RPackage initialization dependent on Monticello > https://pharo.fogbugz.com/f/cases/12209 > ... Are these messages configurable? If so, where is the code? I'd like the log message to be at the top, and think the links should be Penelope links to make them useful to non-core-developers... ----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-project-pharo-core-ba3c45-30606-tp4725955p47262… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 29, 2013