Le 11/04/2013 17:41, Benjamin a écrit :
Most probably yes :)
Ok then, I'll do something like : not allow rename on a MC Package,
allow rename on a RPackage. I don't know what renaming a Monticello
package is really doing, regarding things like the package history...
Did I implemented myself or is this part of the refactoring engine ?
It links directly to RPackageOrganizer without dependencies on the
refactoring engine, so it's probably you :) There is a method which may
be of interest to note, which is isValidPackageName:; why not moving it
to RPackage so that we keep a bit of self-documenting validation there?
Thierry
Ben
On Apr 11, 2013, at 2:47 PM, Goubier Thierry <thierry.goub...@cea.fr
<mailto:thierry.goub...@cea.fr>> wrote:
Hi,
I'm trying to rename packages, so I'm adding the command to AltBrowser
using the Nautilus renamePackage as the way to do it. But looking at
the code, I wonder : does this really work ?
If I select a subcategory of my Monticello package, it looks like it
will work (call RPackageOrganizer>>renamePackage:in:). But, if I
select my Monticello package itself (the one with the curly M ico)
then it seems it will rename just the RPackage and not much else (i.e.
for example, if I rename AST-Core, AST-Core-Matching, AST-Core-Nodes,
etc... will stay unchanged). Did I got that right ?
Thierry
--
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
--
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
