future of Nautilus (the non package tree version)
From time to time it happens that we introduce bugs in the "old" Nautilus browser if we do changes for the default browser (PackageTreeNautilus) For example: 13640 <https://pharo.fogbugz.com/default.asp?13640> no menu on package pane in Nautilus (the non package tree nautilus)
Is a working "old" Nautilus on high priority? Or should we consider PackageTreeNautilus as a replacement for Nautilus? nicolai
On 22 Jul 2014, at 14:26, Nicolai Hess <nicolaihess@web.de> wrote:
From time to time it happens that we introduce bugs in the "old" Nautilus browser if we do changes for the default browser (PackageTreeNautilus) For example: 13640 no menu on package pane in Nautilus (the non package tree nautilus)
Is a working "old" Nautilus on high priority? Or should we consider PackageTreeNautilus as a replacement for Nautilus?
yes. I made the PackageTreeNautilus as a replacement, but an extension because I was using Nautilus to develop Nautilus. Now we should merge it. Esteban
nicolai
2014-07-22 14:28 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
On 22 Jul 2014, at 14:26, Nicolai Hess <nicolaihess@web.de> wrote:
From time to time it happens that we introduce bugs in the "old" Nautilus browser if we do changes for the default browser (PackageTreeNautilus) For example: 13640 <https://pharo.fogbugz.com/default.asp?13640> no menu on package pane in Nautilus (the non package tree nautilus)
Is a working "old" Nautilus on high priority? Or should we consider PackageTreeNautilus as a replacement for Nautilus?
yes. I made the PackageTreeNautilus as a replacement, but an extension because I was using Nautilus to develop Nautilus. Now we should merge it.
This might be a big effort, but this also gives us the opportunity to clean up.
Esteban
nicolai
Yes but I think that it is necessary. What esteban introduced was nice: a design with less conditional. Stef
On 22 Jul 2014, at 14:26, Nicolai Hess <nicolaihess@web.de <mailto:nicolaihess@web.de>> wrote:
From time to time it happens that we introduce bugs in the "old" Nautilus browser if we do changes for the default browser (PackageTreeNautilus) For example: 13640 <https://pharo.fogbugz.com/default.asp?13640> no menu on package pane in Nautilus (the non package tree nautilus)
Is a working "old" Nautilus on high priority? Or should we consider PackageTreeNautilus as a replacement for Nautilus?
yes. I made the PackageTreeNautilus as a replacement, but an extension because I was using Nautilus to develop Nautilus. Now we should merge it.
This might be a big effort, but this also gives us the opportunity to clean up.
Esteban
nicolai
participants (3)
-
Esteban Lorenzano -
Nicolai Hess -
stepharo