In general we need to discuss about Pharo3 non-bug improvements⦠=> we need to take care not to overdue it. If we change Pharo3 a lot, this will add a lot of double work and might introduce new bugs. => My personal rule is: even for bug fixes, if they are to be back ported to Pharo3 not just because âit would be niceâ. My personal threshold for that is simple: I will not do it, but if the fix is important enough *for someone else* to back port, than this is of a kind that should be considered. => We need to be cautious with new features⦠but then there might be cases where it makes sense.
On 04 Nov 2014, at 17:45, Paul DeBruicker <pdebruic@gmail.com> wrote:
Thanks for the tip Max. I've uploaded the packages to the Pharo30Inbox repo.
Max Leske wrote
Hi Paul,
You also need to include the two dependencies of the slice, those need to be uploaded to the inbox too.
Cheers, Max
On 04.11.2014, at 06:19, Paul DeBruicker <
pdebruic@
> wrote:
Hi -
The attached slice makes the 'Search Code' menu item in Nautilus work like it did prior to the adoption of Nautilus in Pharo 3. I do not have commit rights to Pharo30Inbox but would submit it there if I did. I have not sent the contributor agreement but will tomorrow.
The issue in fogbugz is: https://pharo.fogbugz.com/f/cases/14382/Fix-Search-Code-refactoring-menu-ite...
Paul
<SLICE-Issue-14382-Fix-Search-Code-refactoring-menu-item-in-Nautilus-PaulDeBruicker.1.mcz>
-- View this message in context: http://forum.world.st/Fix-Search-Code-menu-item-in-Nautilus-tp4788273p478838... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.