[Pharo-project] Refactoring Browser depenences
Lukas: I am doing a Metacello ConfigurationOfRefactoringBrowser and I see I need these three packages for pharo: AST-Core Refactoring-Core Refactoring-Spelling Now, my question is, do you know the depences between them ? Rught now I noticed Refactoring-Spelling depends on Refactoring-Core Refactoring-Core depends on AST-Core There are more ? and dependences with external packages? Thank you. Mariano
Exactly,
Refactoring-Spelling depends on Refactoring-Core Refactoring-Core depends on AST-Core
AST-Core doesn't depend on anything.
There are more ? and dependences with external packages?
No more dependencies. However, this configuration is hardly any useful, because there is no user-interface, this is just the model of the refactoring engine. To get the UI tools consider loading these packages with the following dependencies: OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard OB-Shout --> OB-Morphic OB-SUnitIntegration --> OmniBrowser OB-Standard --> OmniBrowser OB-Morphic --> OmniBrowser OmniBrowser --> (none) ECompletionOmniBrowser --> ECompletion ECompletion --> Shout ShoutWorkspace --> Shout Shout --> (none) HTH, Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Fri, Dec 18, 2009 at 6:31 PM, Lukas Renggli <renggli@gmail.com> wrote:
Exactly,
Refactoring-Spelling depends on Refactoring-Core Refactoring-Core depends on AST-Core
AST-Core doesn't depend on anything.
There are more ? and dependences with external packages?
No more dependencies.
ok...
However, this configuration is hardly any useful, because there is no user-interface, this is just the model of the refactoring engine. To get the UI tools consider loading these packages with the following dependencies:
OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard OB-Shout --> OB-Morphic OB-SUnitIntegration --> OmniBrowser OB-Standard --> OmniBrowser OB-Morphic --> OmniBrowser OmniBrowser --> (none) ECompletionOmniBrowser --> ECompletion ECompletion --> Shout ShoutWorkspace --> Shout Shout --> (none)
I was asking particulary about the ob repository, but you information is even better :) Thank you very much. Mariano HTH,
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Fri, Dec 18, 2009 at 6:31 PM, Lukas Renggli <renggli@gmail.com> wrote:
Exactly,
Refactoring-Spelling depends on Refactoring-Core Refactoring-Core depends on AST-Core
AST-Core doesn't depend on anything.
There are more ? and dependences with external packages?
No more dependencies.
However, this configuration is hardly any useful, because there is no user-interface, this is just the model of the refactoring engine. To get the UI tools consider loading these packages with the following dependencies:
OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard OB-Shout --> OB-Morphic OB-SUnitIntegration --> OmniBrowser OB-Standard --> OmniBrowser OB-Morphic --> OmniBrowser OmniBrowser --> (none) ECompletionOmniBrowser --> ECompletion ECompletion --> Shout
Lukas, the ECompletion wiki says "Requires the packages RoelTyper and Shout 4" . Is this still true ? Or as you said it now only requieres Shout (no RoelTyper) ? Thanks Mariano
ShoutWorkspace --> Shout
Shout --> (none)
HTH, Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
AFAIK, RoelTyper is not a hard dependency, but if loaded eCompletion provides better results. Don't have a computer to check right now. Lukas On Saturday, December 26, 2009, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Fri, Dec 18, 2009 at 6:31 PM, Lukas Renggli <renggli@gmail.com> wrote:
Exactly,
Refactoring-Spelling depends on Refactoring-Core Refactoring-Core depends on AST-Core
AST-Core doesn't depend on anything.
There are more ? and dependences with external packages?
No more dependencies.
However, this configuration is hardly any useful, because there is no user-interface, this is just the model of the refactoring engine. To get the UI tools consider loading these packages with the following dependencies:
  OB-Refactory --> Refactoring-Core, OB-Standard   OB-Regex --> Refactoring-Core, OB-Standard   OB-Shout --> OB-Morphic   OB-SUnitIntegration --> OmniBrowser   OB-Standard --> OmniBrowser   OB-Morphic --> OmniBrowser   OmniBrowser --> (none)   ECompletionOmniBrowser --> ECompletion   ECompletion --> Shout
Lukas, the ECompletion wiki says "Requires the packages RoelTyper and Shout 4" . Is this still true ? Or as you said it now only requieres Shout (no RoelTyper) ?
Thanks
Mariano    ShoutWorkspace --> Shout
  Shout --> (none)
HTH, Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
On Sat, Dec 26, 2009 at 6:40 PM, Lukas Renggli <renggli@gmail.com> wrote:
AFAIK, RoelTyper is not a hard dependency, but if loaded eCompletion provides better results. Don't have a computer to check right now.
Ok, I will take it as a dependency then. Another question, do you know what Refactoring-Spelling is and who depends on it ? Do you think we should put that as Pharo dev? I saw that here you put it: http://code.google.com/p/pharo/wiki/ImageBuildScripts But I wonder who or where it is used. Thanks Mariano
Lukas
On Saturday, December 26, 2009, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Fri, Dec 18, 2009 at 6:31 PM, Lukas Renggli <renggli@gmail.com>
wrote:
Exactly,
Refactoring-Spelling depends on Refactoring-Core Refactoring-Core depends on AST-Core
AST-Core doesn't depend on anything.
There are more ? and dependences with external packages?
No more dependencies.
However, this configuration is hardly any useful, because there is no user-interface, this is just the model of the refactoring engine. To get the UI tools consider loading these packages with the following dependencies:
OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard OB-Shout --> OB-Morphic OB-SUnitIntegration --> OmniBrowser OB-Standard --> OmniBrowser OB-Morphic --> OmniBrowser OmniBrowser --> (none) ECompletionOmniBrowser --> ECompletion ECompletion --> Shout
Lukas, the ECompletion wiki says "Requires the packages RoelTyper and
Shout 4" . Is this still true ? Or as you said it now only requieres Shout (no RoelTyper) ?
Thanks
Mariano ShoutWorkspace --> Shout
Shout --> (none)
HTH, Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Another question, do you know what Refactoring-Spelling  is
Yes, I wrote it :-) It reactors your spell errors away :-P
and who depends on it ?
See attached PDFs. This is what Package-Dependencies produces in a few second: highlighted cyclic dependencies, it removes transitive dependencies, and it creates a simple graph that carries all information to load. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
2009/12/28 Lukas Renggli <renggli@gmail.com>
Another question, do you know what Refactoring-Spelling is
Yes, I wrote it :-)
It reactors your spell errors away :-P
and who depends on it ?
See attached PDFs. This is what Package-Dependencies produces in a few second: highlighted cyclic dependencies, it removes transitive dependencies, and it creates a simple graph that carries all information to load.
Thanks Lukas. I was looking at the pdf about the dependencies of OB but it is different to what you told me at the beginning. For example, you told me: OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard But in the pdf I see OB-Regex --> OB-Refactory I just need to know the DIRECT dependencies. Those classes you use, extend, reference or whatever. If OB-Regex used directly classes from OB-Standard for example, ok, then it is a dependency. But, if you told me OB-Standard just because it was a dependency for OB-Refactory (and this was a dependency for OB-Regex), then, I don't care about it. I just need to know the direct dependencies (not also the dependencies or my dependencies haha ) Cheers Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Thanks Lukas. I was looking at the pdf about the dependencies of OB but it is different to what you told me at the beginning. For example, you told me:
OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard
But in the pdf I see OB-Regex --> OB-Refactory
I just need to know the DIRECT dependencies. Those classes you use, extend, reference or whatever. If OB-Regex used directly classes from OB-Standard for example, ok, then it is a dependency. But, if you told me OB-Standard just because it was a dependency for OB-Refactory (and this was a dependency for OB-Regex), then, I don't care about it. I just need to know the direct dependencies (not also the dependencies or my dependencies haha )
I don't get what you mean, but the PDF is correct because it is created from the code. The PDF only contains direct dependencies, transitive ones are removed, only the information you need to know to load correctly. We create the Seaside loaders with this information. Lukas
Cheers
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
El sáb, 02-01-2010 a las 17:42 +0100, Lukas Renggli escribió:
Thanks Lukas. I was looking at the pdf about the dependencies of OB but it is different to what you told me at the beginning. For example, you told me:
OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard
But in the pdf I see OB-Regex --> OB-Refactory
I just need to know the DIRECT dependencies. Those classes you use, extend, reference or whatever. If OB-Regex used directly classes from OB-Standard for example, ok, then it is a dependency. But, if you told me OB-Standard just because it was a dependency for OB-Refactory (and this was a dependency for OB-Regex), then, I don't care about it. I just need to know the direct dependencies (not also the dependencies or my dependencies haha )
I don't get what you mean, but the PDF is correct because it is created from the code.
How can I get the dependencies of a given package by software? Mind to share the package? Thanks
The PDF only contains direct dependencies, transitive ones are removed, only the information you need to know to load correctly. We create the Seaside loaders with this information.
Lukas
Cheers
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
How can I get the dependencies of a given package by software? Mind to share the package?
Thanks
I think I found it. Dependency Browser from Hernán Morales: http://cs.hernanmorales.com.ar/projects/dependencyBrowser/DBrowser-en.php Or are you using something else? Thanks anyway. -- Miguel Cobá http://miguel.leugim.com.mx
2010/1/12 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
How can I get the dependencies of a given package by software? Mind to share the package?
Thanks
I think I found it. Dependency Browser from Hernán Morales:
http://cs.hernanmorales.com.ar/projects/dependencyBrowser/DBrowser-en.php
Or are you using something else?
That's what I used, as it has a nice UI and it is easy to use. But there is also something from Lukas that they use in Seaside and does that kind of graphics. I don't know if it has a UI or a tutorial anywhere, thus. Cheers
Thanks anyway.
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
That's what I used, as it has a nice UI and it is easy to use. But there is also something from Lukas that they use in Seaside and does that kind of graphics. I don't know if it has a UI or a tutorial anywhere, thus.
Load it using: Gofer new renggli: 'packaging'; package: 'GraphViz'; package: 'Package-Dependencies'; load Then have a look at the examples on the class side of PDPackageAnalyzer. It creates a .dot file that can be fed into GraphViz. Preferably you generate an SVG graphic as it has nice tooltips. Contrary to the other tool, Package-Dependencies does not show unnecessary transitive dependencies. It only displays the direct and shortest dependencies. Circular dependencies are highlighted in red. Very useful for complicated packages like Seaside (http://builder.seaside.st/distributions/004-Seaside3.0.0-a5/seaside.svg). I should add it to the build-server :-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch
El mar, 12-01-2010 a las 09:40 +0100, Lukas Renggli escribió:
That's what I used, as it has a nice UI and it is easy to use. But there is also something from Lukas that they use in Seaside and does that kind of graphics. I don't know if it has a UI or a tutorial anywhere, thus.
Load it using:
Gofer new renggli: 'packaging'; package: 'GraphViz'; package: 'Package-Dependencies'; load
Then have a look at the examples on the class side of PDPackageAnalyzer.
It creates a .dot file that can be fed into GraphViz. Preferably you generate an SVG graphic as it has nice tooltips.
Contrary to the other tool, Package-Dependencies does not show unnecessary transitive dependencies. It only displays the direct and shortest dependencies. Circular dependencies are highlighted in red. Very useful for complicated packages like Seaside (http://builder.seaside.st/distributions/004-Seaside3.0.0-a5/seaside.svg). I should add it to the build-server :-)
Cool, thanks for the tip.
Lukas
-- Miguel Cobá http://miguel.leugim.com.mx
2009/12/28 Lukas Renggli <renggli@gmail.com>
Another question, do you know what Refactoring-Spelling is
Yes, I wrote it :-)
It reactors your spell errors away :-P
mmmmmmm I never seen that working in my code and it seems to be installed in almost all PharoDev images... Do I need to do something to enable it ? how do I use it ? Does it depends on something ? I ask because Stef said that maybe it depends in a library or something like that. I saw there is a SpellingPlugin. Is that compiled in all VMs? do you know ? Sorry, too many questions hahahah
and who depends on it ?
See attached PDFs. This is what Package-Dependencies produces in a few second: highlighted cyclic dependencies, it removes transitive dependencies, and it creates a simple graph that carries all information to load.
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
It reactors your spell errors away :-P
mmmmmmm I never seen that working in my code and it seems to be installed in almost all PharoDev images...
Do I need to do something to enable it ?
It is an extension to SmallLint. You need to run lint to see it point out your errors. To see the wavy lines live in your code you need Helvetia (probably I could also patch Shout).
 Does it depends on something ? I ask because Stef said that maybe it depends in a library or something like that.
No, it depends on nothing other than the refactoring engine.
I saw there is a SpellingPlugin. Is that compiled in all VMs? do you know ?
Only on OS X. But as I said, there is an alternative stupid spellchecking engine written in Smalltalk include. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Mon, Jan 11, 2010 at 11:17 PM, Lukas Renggli <renggli@gmail.com> wrote:
It reactors your spell errors away :-P
mmmmmmm I never seen that working in my code and it seems to be installed in almost all PharoDev images...
Do I need to do something to enable it ?
It is an extension to SmallLint. You need to run lint to see it point out your errors. To see the wavy lines live in your code you need Helvetia (probably I could also patch Shout).
Ahhh ok, that's explain why I didn't see it :) You know, it is funny becuase sometimes I miss to have a spell checker in code with undeline, but then, when I have it, it bothers me hahhahaha
Does it depends on something ? I ask because Stef said that maybe it depends in a library or something like that.
No, it depends on nothing other than the refactoring engine.
Ok, perfect.
I saw there is a SpellingPlugin. Is that compiled in all VMs? do you know ?
Only on OS X.
But as I said, there is an alternative stupid
spellchecking engine written in Smalltalk include.
Cool thanks lukas!
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Lukas Renggli -
Mariano Martinez Peck -
Miguel Enrique Cobá Martinez