December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] about DependencyBrowser
by Mariano Martinez Peck Jan. 5, 2010

Jan. 5, 2010

On Sat, Dec 26, 2009 at 10:06 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Hi Mariano! > Nice to see you liked the Dependency Browser, let's clarify some > points about it then, > > 2009/12/26 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi HernÃ¡n: First let me say that this tool is really great and useful. It > is > > helping me a lot to build the metacello configurations. Now, I have a > couple > > of questions: > > > > 1) What do the colors mean ? (red, orange, etc). I read here > > > http://cs.hernanmorales.com.ar/projects/dependencyBrowser/DBrowser-en.php > > but found nothing :( > > Colors were originally for idenfitying dependency types of external > packages, but the package infos names aren't normalized, E.g. > Normalized name = "Collections", Un-normalized name = > "Collections-Strings", hence you will see a lot of false external > packages colorized. > > Orange -> Dependecy of class reference of "external" package, or class > reference in un-normalized package name. > Brown -> Dependency of external package loose method, or loose method > in un-normalized package name. > Red -> Dependency of inheritance, or inheritance in un-normalized package > name. > Blue -> Dependency of a unsolved binding (like a class not present in > the image). > Thanks for the explanation. Now, as a good programmer you can reuse this explanation and put it in the website :) > > > > > 2) It would be EXCELLENT to be able to distinguish between PharoCore or > > exernal packages. Suppose you are building a tool or whatever, it would > be > > useful to know if it all what it is required is already on a PharoCore or > if > > it is external (it will require to install also another packages). > However, > > I am not sure how implement this :( > > Yes, it would be cool for a new package system to implement a protocol > for asking if a package is distributed originally in a release or not, > like: > > aPackage isOfficial > > With so many forks around, I found difficult to find a single way to > detect official packages installed in an image, and there should be an > easier solution than scanning though all package dates. Maybe this has > changed now? > I really don't know. Maybe we can send a separate thread asking about this. Hey! I have more questions :) 3) Please, take a Pharo dev image and you will see that the package OCForOB for example, only depends on OmniBrowser and OB-Standard (using dependency browser). However, that package also depends on OCompletion I think. Look for example the method OBTextPanel >> createCompletionController (category ocforob) and you will see that it uses the class OController which is from the package OCompletion....So, shouldn't be OCompletion a dependency ? 4) There are certain packages that are not listed in the dependency browser. Examples OB-Standard, OB-Morphic, O2-Standard , etc...most of them (maybe all) seem to have the pattern XXX-YYY. Do you know what can be the problem here? Maybe something related to what you told me about normalized and un-normalized? I would really like to see these packages also. 5) Why there are some packages that have their self as dependency ? For example, take OmniBrowser and you will see that has a dependency OmniBrowser also (as Inheritance and Reference). Thank you very much. Mariano > Kind regards, > > HernÃ¡n > > > > > Thank you very much. > > > > Mariano > > >

5 9

[Pharo-project] [update 1.1] #11126 - 27 (final methodTrailer cool cleanup
by StÃ©phane Ducasse Jan. 4, 2010

Jan. 4, 2010

BIG THANKS igor!!! 11127 ----- - Issue 1690: New Method Trailer part 7 (cs 9)

5 17

[Pharo-project] Can't use <Enter> key to select notifier action
by danklein Jan. 4, 2010

Jan. 4, 2010

When a notifier pops up, you can tab (or shift-tab) to the Proceed/Abandon/Debug/Create buttons at the top of the window. However, when the one you want is highlighted, I would like to be able to just press the to execute it, but you have to actually click on it. Is there a configuration setting to affect this behavior? -- View this message in context: http://n2.nabble.com/Can-t-use-Enter-key-to-select-notifier-action-tp419464… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 4

[Pharo-project] Issue 1692: MNU when tried to navigate pop up menus with the keyboard
by Francisco Ortiz PeÃ±aloza Jan. 4, 2010

Jan. 4, 2010

Pharo image: Pharo-core Pharo core version: PharoCore1.1ALPHA Latest update: #11116 Virtual machine used: Squeak 4.2.2beta1U | Cocoa Squeak 5.0.0b9 64*32 Steps to reproduce: 1. Open a pop up using your mouse o pressing <esc> 2. Try to select an action using your keyboard. Enter text to narrow down your matching items or using the arrow keys, neither work anymore. Francisco

3 4

[Pharo-project] Does OCompletion depend on ECompletion?
by Mariano Martinez Peck Jan. 3, 2010

Jan. 3, 2010

I thought that yes, but in my dev image I have OCompletion but not ECompletion. Can someone clarify me this ? Thanks Mariano

3 4

[Pharo-project] Issue 1704: Cancelling "extract method" refactoring raises OR2UICancellationError
by Danny Chan Jan. 3, 2010

Jan. 3, 2010

Hi! In the current 1.0 release candidate I get an UICancellationError when I select some source code, choose "refactor source/extract method", and then cancel the dialog asking for the selector name. Danny

2 1

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols
by David RÃ¶thlisberger Jan. 2, 2010

Jan. 2, 2010

> May be you can contact david probably on holidays to see how we can > make progress? > I know that we can publish in david repository so may be a lot of > the problems are simple glicth. > Having a configuration for O2 would be good. > What I am not sure, David, can you confirm this ? is if what we talk > in our private email a about the O2-Refactory (the problem we still > have) is the same problem we are talking here. Because, in my opinion, > one thing is just to depend and another thing is to depend and override. > If there are overrides, it matters the order and a lot more stuff. > That's why I am asking you :) > > Is it the same? I hope so :) I do not know, I cannot reproduce this bug (1721) in pharo1.0-10502-rc1web09.12.2. You say in the bug report you can reproduce it neither? So what is the problem you get and how can I reproduce it? I see in the attached stack trace from the creator of 1721 that his bug has something to do with dynamic protocols, but I cannot see the cause from the strack trace. I need to know which Pharo version, which browser version and which packages are loaded to reproduce and locate the problem. It might or might not be related to the problem we discussed, I can't tell yet. Cheers, David

4 4

[Pharo-project] Solving the documentation problem. Capturing tacit knowledge. Knowledge reuse.
by Stan Shepherd Jan. 2, 2010

Jan. 2, 2010

Situation ----------- Pharo/Squeak is potentially a very productive development environment. It has not achieved the widespread use in production systems that we feel it deserves. Complication ----------------- The Pharo world relies on a few people with a lot of knowledge. Starting to use Pharo means relying on those people to provide the knowledge they have. The knowledge that is transferred this way is not captured for reuse. Lack of documentation is usually cited by people evaluating Pharo/Squeak for new projects. For example "#addScript: and #addStyle: are actually ment for internal use. It is currently used by the methods WAComponent>>#styles and WAComponent>>#scripts." http://n4.nabble.com/Script-in-head-tag-td98415.html This is not in the comments. It is tacit knowledge. I'm sure you know of similar examples; they are not rare. Resolution ------------- If documentation maintenance were separated from code maintenance, this tacit knowledge could be captured immediately, by the person who requested it. Maintaining documentation then becomes largely a task for the users of the system. Action -------- One possible mechanism would be to place comments in a wiki. For each class, and each method of that class, there would be a corresponding wiki section. Any user could update the comment at any time. The developer/maintainer of that class could revert any inaccurate edits with one click. Incorrect edits would not affect the function of a method, hence no requirements to unit test / integration test. Commits of code would ideally also update the wiki comment section. There is obviously potential for some problems here, but a wiki structure would make it easy to identify/reconcile parallel edits. When a build happens, a process would update the source with latest comments from the wiki. Plan ---- I'd be willing to put some time into a proof of concept, if people agree that it's worthwhile and they would use it. Any thoughts? ...Stan P.S. Other areas that could be maintained this way: Welcome information workspace on download images. Known problems. (Examples of class use) ... -- View this message in context: http://n2.nabble.com/Solving-the-documentation-problem-Capturing-tacit-know… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

9 22

[Pharo-project] where can I see the slices that were removed from inbox?
by Mariano Martinez Peck Jan. 1, 2010

Jan. 1, 2010

I need to load a slice in 1.0 which was integrated in 1.1 and removed from PharoInbox. Where can I find it? thanks mariano

2 2

[Pharo-project] I still don't understand how this work
by Mariano Martinez Peck Jan. 1, 2010

Jan. 1, 2010

I took a clean pharo1.0-10502-rc1dev09.12.2. I open Monticello Browser, and of course, there is no dirty (modified) package. I select the package OB-Standard, then select the repo http://source.wiresong.ca/ob , and click on changes 1) First, I would expect to have no changes with an Image I have just downloaded, without doing nothing and even when Monticello Browser showed me there is no dirty package. But.....this showed me several changes!!!

3 8