January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] packages in 3.0

by Esteban Lorenzano

On 29 Jan 2014, at 11:25, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 28.01.2014 um 23:47 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 28 Jan 2014, at 23:34, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 28.01.2014 um 22:50 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> they do not appear because they shouldnât :) >>>> >>>> MCPackage = RPackage in 3.0 >>>> >>> Ah, very good. I see this of course shortly after I applied ones again stupid package names to be able to separate tests. >>> >>>> that means that you need 3 mc packagesâ¦ or 1 r packages + 2 tags >>>> >>> tags? What year is it? At the moment Iâm feeling as I had been off the list for quite a while! Ok, Iâll try to find these myself. >>> >>> Btw. 30 minutes ago I found metacello stuff (create baseline, create development version) in the menu of the monticello packages. Great stuff! Are you sure there isnât a lot of good stuff sneaking in without anyone noticing? >>> >>>> btwâ¦ there are still some glitches with that that need to be fixed. Please report if/when you find them :) >>>> >>> Oh my, I hate it because that is the one thing Iâm good atâ¦.finding bugs. >> >> coolâ¦ we need more like you (and so far Stef has the podium) :) >> > Is there anything to take care in a mixed environment. I have 2.0/3.0 mixed setting here. From now on I like to develop in 3.0 even if the code is loaded into a 2.0 image. Can I expect trouble when loading the finer grained packages produced via 3.0 in a 2.0 image? it should work without problemâ¦ but of course if you attempt to save in 2.0 package A will include A-B and A-C :) Esteban > > Norbert > >>> >>> Norbert >>> >>>> Esteban >>>> >>>> On 28 Jan 2014, at 22:29, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>>> I have a project that defines a package >>>>> >>>>> Project-Core >>>>> >>>>> then I added some more like >>>>> >>>>> Project-Core-Exception >>>>> Project-Core-Command >>>>> â¦ >>>>> >>>>> but those do not appear in the monticello package. Is it supposed to be that way from 3.0 on or is this a bug? >>>>> >>>>> Norbert >

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Sebastian Sastre

On Jan 29, 2014, at 9:33 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > It has already been concluded that fogbugz was a mistake. Itâs just not made > for an open source project. > > Now moving will be *a lot* of work and we have not even found a replacement > that is scriptable. > > We first need to release Pharo3 before we sink indefinite amounts of time into this. Cool. I agree in the prioritisation. I have a couple of ideas about how to improve the whole thing I should blog about it to contribute to this healthy conversation keep the great wotk sebastian o/

Jan. 29, 2014

Re: [Pharo-dev] No more MouseWheelEvents?

by Sean P. DeNigris

Nicolai Hess wrote > The blue rectangle looks like a drop indicator. you can drag another > window > over nautilus' package tree and you'll the this rectangle moving. Yes, and there is a bug. If you accidentally drop a non-package-related Morph on a Nautilus tree package pane, you will get a DNU #passenger and your Morph will disappear! ----- Cheers, Sean -- View this message in context: http://forum.world.st/No-more-MouseWheelEvents-tp4739999p4740104.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 29, 2014

Re: [Pharo-dev] No more MouseWheelEvents?

by Sebastian Sastre

On Jan 29, 2014, at 10:08 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > So I have stopped using gestures at all with Nautilus and instead do manual scrolls dragging the scroll bar. I understand this is the symptom of an early release of course

Jan. 29, 2014

Is it possible to remove users from your own SmalltalkHub?

by Mariano Martinez Peck

Hi Nico, I wonder if that's possible because I cannot find a way of doing it. I need to remove another's user account. I am using my own shub instance and I do have access to the image/mongo if I should do it from there. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

Jan. 29, 2014

Re: [Pharo-dev] Where to report bugs?

by Noury Bouraqadi

Thanks Hilaire. Noury On 29 janv. 2014, at 09:13, Hilaire Fernandes wrote: > Le 28/01/2014 16:53, Noury Bouraqadi a Ã©crit : >> I tried fogbugz but I failed to connect... > > Reading your email I can't help smiling, and it make me fill I was not > so idiot when I could'nt use the bugs tracker. > > Seriously you should read the instruction and view the video tutorial at > https://pharo.fogbugz.com/ > because it is a bit unusual, especially to get your password. > > Hilaire > > > -- > Dr. Geo http://drgeo.eu > > Noury Bouraqadi Ecole des Mines de Douai http://car.mines-douai.fr/noury --

Jan. 29, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30728 Home: https://github.com/pharo-project/pharo-core

Jan. 29, 2014

[pharo-project/pharo-core] d23a26: 30728

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d23a264d85adaa9070dad39f8d1a2378b96877e2 https://github.com/pharo-project/pharo-core/commit/d23a264d85adaa9070dad39f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-29 (Wed, 29 Jan 2014) Changed paths: M Monticello.package/MCPackageManager.class/class/system changes/classModified_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script381.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30728.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/AbstractClassInstaller.class/instance/initialization/initialize.st A Slot.package/AbstractClassModification.class/instance/testing/isPropagation.st A Slot.package/ClassModification.class/instance/testing/isPropagation.st M Slot.package/ClassModificationPropagation.class/README.md A Slot.package/ClassModificationPropagation.class/instance/testing/isPropagation.st A Slot.package/PharoClassInstaller.class/instance/notifications/basicClassDefinitionChangedFrom_to_using_.st M Slot.package/PharoClassInstaller.class/instance/notifications/classDefinitionChangedFrom_to_by_.st M Slot.package/PharoClassInstaller.class/instance/notifications/shallowClassDefinitionChangedFrom_to_by_.st M Slot.package/PharoClassInstaller.class/instance/notifications/slotsChangedFrom_to_by_.st R Slot.package/PharoClassInstaller.class/instance/private/basicClassDefinitionChangedFrom_to_.st M Slot.package/SlotClassBuilder.class/definition.st M Slot.package/SlotClassBuilder.class/instance/accessing/client_.st M Slot.package/SlotClassBuilder.class/instance/accessing/environment.st M Slot.package/SlotClassBuilder.class/instance/accessing/environment_.st A Slot.package/SlotClassBuilder.class/instance/accessing/installer_.st M Slot.package/SlotClassBuilder.class/instance/initialize-release/build.st M Slot.package/SlotClassBuilder.class/instance/initialize-release/buildNewClass.st M Slot.package/SlotClassBuilder.class/instance/private/applyAndUpdateFormat_.st M Slot.package/SlotClassBuilder.class/instance/private/applyAndUpdateSlots_.st M Slot.package/SlotClassBuilder.class/instance/private/applyAndUpdateSuperclass_.st M Slot.package/SlotClassBuilder.class/instance/private/installTraitComposition_.st M Slot.package/SlotClassBuilder.class/instance/private/migrateClasses_.st M SlotTests.package/SlotAnnouncementsTest.class/README.md M SlotTests.package/SlotAnnouncementsTest.class/definition.st R SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/assertOnlyOneAnnouncementOf_within_.st A SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/collectedAnnouncementClasses.st A SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/collectedAnnouncements.st R SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/countAnnouncements_.st R SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/saveAnnouncementOnce_.st R SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/saveAnnouncement_.st A SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/subscribeOn_.st M SlotTests.package/SlotAnnouncementsTest.class/instance/running/setUp.st A SlotTests.package/SlotAnnouncementsTest.class/instance/running/tearDown.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testChangeInSuperclassShouldNotAnnounceSubclassModified.st R SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassAddedAnnounced.st R SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassAddedAnnouncedOnlyOnce.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassCreationShouldAnnounceClassAdded.st R SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassFormatChangedAnnounced.st R SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassModifiedAnnounced.st R SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassModifiedAnnouncedOnlyOnce.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassRecategorizationShouldAnnounceClassModified.st R SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testClassRecategorizedAnnounced.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testLayoutChangeShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests/testSlotAdditionShouldAnnounceClassModified.st R System-Announcements.package/ClassAnnouncement.class/instance/testing/isPropagation.st R System-Announcements.package/ClassModifiedClassDefinition.class/instance/accessing/isPropagation.st Log Message: ----------- 30728 12731 Traits modifications cause a DNU https://pharo.fogbugz.com/f/cases/12731 http://files.pharo.org/image/30/30728.zip

Jan. 29, 2014

Re: [Pharo-dev] No more MouseWheelEvents?

by Nicolai Hess

2014-01-29 kilon alios <kilon.alios(a)gmail.com> > yes Nautilus also acts crazy with magic mouse gestures. Also there is > weird blue rectangle that surrounds one of the packages that refuses to go > away. So I have stopped using gestures at all with Nautilus and instead do > manual scrolls dragging the scroll bar. > > > On Wed, Jan 29, 2014 at 12:34 PM, Sebastian Sastre < > sebastian(a)flowingconcept.com> wrote: > >> There is something about the wheel because often, at least in Nautilus, >> you get crazy scrolls you dind't asked for >> >> Specially if using trackpad, two finger, scroll >> >> >> >> On Jan 29, 2014, at 6:09 AM, Hilaire Fernandes < >> hilaire.fernandes(a)gmail.com> wrote: >> >> > I am not exactly sure, but I think mouseWheelEvents were always >> > simulated with Ctrl events. >> > >> > >> > Hilaire >> > >> > >> > Le 29/01/2014 00:06, Nicolai Hess a Ã©crit : >> >> How it comes we lost the MouseWheelEvents. >> >> The SimpleHierarchicalListMorph in FileList does not scroll on >> >> MouseWheelEvents. >> >> Or at least it worked that way in Pharo2. But now the MouseWheel >> creates >> >> a keyboardevent "<Ctrl->". >> >> (Other ListMorphs can handle this, but the ListMorph in FileList can >> not.) >> >> >> >> nicolai >> >> >> > >> > >> > -- >> > Dr. Geo http://drgeo.eu >> > >> > >> >> >> > The blue rectangle looks like a drop indicator. you can drag another window over nautilus' package tree and you'll the this rectangle moving.

Jan. 29, 2014

Re: [Pharo-dev] process to collaborate on cleaning morphic

by Hilaire Fernandes

Le 28/01/2014 18:41, Pharo4Stef a Ã©crit : > this is years since I clean Morphic (may be Iâm that good at it) but this is important to > go step by step. So I would really like to get a list of simple actions. > Do you have an idea? What about a brutal scheme, independent of all code quality considerations: - dedicate a Pharo release process *only* to Morphic cleaning so people will know it gona be brutal - mark as deprecated all morphic methods unsused in the system. When a client (like me with DrGeo), use some of the deprecated method, fill a bug ticket, then discussion should arise about what to do: i. unmark it as deprecated ii. move it in external package iii. adoption by the client in its application code - do the same with unused classes from the Morph hierarchy. I guess Steph already did some of this in the past. The idea is you don't want to refactor unused code, right? -- Dr. Geo http://drgeo.eu

Jan. 29, 2014