Le 04/03/2014 14:02, Alexandre Bergel a écrit :
I usually never switch between Log and other packages / classes, except if
those packages are related (i.e., from the same application). When I need to
see other classes that have nothing to do with my application, I usually open a
new browser.
Ok, then another question:
- When working on one application, would you prefer all searches and
refactorings be:
a) scoped to your application
b) system wide
c) both (:))
I implemented a) for classes and packages, but I'm wondering if this is
the right balance: a) is very convenient, but at times I want b), which
means c).
I also have a problem of a good GUI representation of the fact the
browser is scoped, and which scope exactly it is. Why?
Because, when scoping is easy, then you can drill down through code by
scoping over scoping: first a package / then a class / then a group of
methods... And then explaining what the scope is at that point is... not
easy.
Thierry
Alexandre
On Mar 4, 2014, at 9:29 AM, Goubier Thierry <[email protected]> wrote:
Now in Nautilus I often type Log to only the Log package so what display
your search bar
Hi Stef,
when you do that, do you usually:
- work only with Log in that Nautilus instance (i.e. your package search entry
is staying with Log all the time)
- Or switch between Log and other packages / classes (i.e. you write Log
multiple times in the search bar)
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
