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

bug in nautilus?

by Alexandre Bergel

Hi! Apparently, Nautilus is showing me that Roassal2 is dirty, whereas it is notâ¦ Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 17, 2014

Re: [Pharo-dev] STHub: 1190 repositories, 1001 users registered and 110365 packages uploaded

by Alexandre Bergel

Truly beautiful. Youâre raising some challenges for Roassal2 and Roassal2@Amber Alexandre On Jan 16, 2014, at 10:00 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Yes, have you seen it, http://yuriy.tymchuk.me/Smalldromeda/ ? > > On 17 Jan 2014, at 00:32, Torsten Bergmann <astares(a)gmx.de> wrote: > >> see http://smalltalkhub.com >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 17, 2014

Re: [Pharo-dev] STHub: 1190 repositories, 1001 users registered and 110365 packages uploaded

by Yuriy Tymchuk

Yes, have you seen it, http://yuriy.tymchuk.me/Smalldromeda/ ? On 17 Jan 2014, at 00:32, Torsten Bergmann <astares(a)gmx.de> wrote: > see http://smalltalkhub.com >

Jan. 17, 2014

Re: [Pharo-dev] Promoting a Tag to a separate Package

by Sean P. DeNigris

We're too fast. I went to check it and it's already integrated! -------- Original message -------- From: "EstebanLM [via Smalltalk]" <ml-node+s1294792n4737306h74(a)n4.nabble.com> Date: 01/16/2014 1:48 PM (GMT-05:00) To: "Sean P. DeNigris" <sean(a)clipperadams.com> Subject: Re: Promoting a Tag to a separate Package heh already fixed :) https://pharo.fogbugz.com/f/cases/12664 waiting for validation and integration. and you could provide feedback, because this is really tricky :D Esteban On 16 Jan 2014, at 19:33, Sean P. DeNigris <[hidden email]> wrote: > With the new scheme, can I have two packages of the form: > MyProjectName > Â - PossibleWithATag > Â - AndAnother > and > MyProjectName-SeparatePackage > > IIUC in the past we couldn't because we were pattern matching on categories. > Also, even if we can, is that an okay practice? > > As to the thread subjectâ¦ I often start out with one package, and then break > out some of the sub-categories into their own packages. Ideally, I'd love a > "Promote to Package" button in Nautilus' package pane. But in the mean time, > how do I do it in 3.0. I used to delete the working copy in MC Browser and > then create the individual packages - tedious, but working. Now, after I do > that, when I browse the MyProjectName-SeparatePackage package in MCBrowser > it is empty, and when I click "Add package" in Nautilus package pane with > the MyProjectName-SeparatePackage selected, confirming the dialog pre-filled > with "SeparatePackage", it says there is already a package with that name. > Help!! > > Thanks. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Promoting-a-Tag-to-a-separate-Package-tp4737302.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > If you reply to this email, your message will be added to the discussion below: http://forum.world.st/Promoting-a-Tag-to-a-separate-Package-tp4737302p47373… To unsubscribe from Promoting a Tag to a separate Package, click here. NAML ----- Cheers, Sean -- View this message in context: http://forum.world.st/Promoting-a-Tag-to-a-separate-Package-tp4737302p47373… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 17, 2014

Re: [Pharo-dev] STHub: 1190 repositories, 1001 users registered and 110365 packages uploaded

by Igor Stasenko

~ 1 repository , 10 packages per user :) On 17 January 2014 00:32, Torsten Bergmann <astares(a)gmx.de> wrote: > see http://smalltalkhub.com > > -- Best regards, Igor Stasenko.

Jan. 16, 2014

STHub: 1190 repositories, 1001 users registered and 110365 packages uploaded

by Torsten Bergmann

see http://smalltalkhub.com

Jan. 16, 2014

Re: [Pharo-dev] Smalltalk Impact

by Igor Stasenko

On 16 January 2014 21:15, Hilaire Fernandes <hilaire.fernandes(a)gmail.com>wrote: > Le 16/01/2014 12:55, H. Hirzel a Ã©crit : > > >>> âWe are not payed to work on Squeakâ, that is what I got toldâ¦ > > > > Probably correct at that time... > > This is usual attitude in corporate environment: you paying me to do the job, i do it and i don't care about the rest. Been there, ate that :) > It doesn't matter. The silliness of such answer is the lack of vision > and lack of community empowerment. > > > > Noteworthy however: Scratch is successful in spite of being built on a > > early version of Squeak. > > I see this has an extremely weakness. > Imagine Java applications forking Java, a total nonsense too expensive > in the long term. Hopefully Smalltalk Scratch is being ported to the > recent Pharo and saved from a long and slow bits death. And more > important: it is not a fork anymore. > > We are greatfull to the new Pharo Smalltalk vessel. Its constant care to > tiers developers willing to develop and design standalone Smalltalk > application with an opensource Smalltalk environment really open > perspective for the Smalltalk community build up. The vision is clear, > the target on sight! > > > The situation of Etoys to the contrary is not so clear. A comparison > > needs to consider more factors than just the platform it is built > > on.... > > Well, each one should take the share it deserves: forking was decided as > the path for Etoys, so now Bonne chance and bon voyage... > > When you want to build something which will stand for millennium, you call architect, when you want to build a beautiful facade to impress people who passing by, you call artist, couple porters and couple erectors :) > Hilaire > -- > Dr. Geo http://drgeo.eu > > > -- Best regards, Igor Stasenko.

Jan. 16, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 16, 2014

[pharo-project/pharo-core] 0cfef4: 30701

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 0cfef4de314c06cdcc6d7d5a05d19c3fb79ad3d3 https://github.com/pharo-project/pharo-core/commit/0cfef4de314c06cdcc6d7d5a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-16 (Thu, 16 Jan 2014) Changed paths: M ClassOrganizer-Core.package/Protocol.class/instance/accessing/addMethod_.st M ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/accessing/renameProtocol_into_.st M ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/private/moveMethodsFrom_to_.st M MonticelloGUI.package/MCSliceMaker.class/instance/user interface/rootItems.st M MonticelloGUI.package/MCSliceMaker.class/instance/user interface/window.st M Nautilus.package/AbstractNautilusUI.class/instance/drag and drop/dropInAPackage_into_.st M Nautilus.package/NautilusUI.class/instance/menus behavior/renameCategory.st A Nautilus.package/PackageTreeGroupSelection.class/instance/as yet unclassified /classes.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private/addClassCategoryBasedOn_.st A RPackage-Core.package/RPackage.class/instance/accessing/addClass_.st M RPackage-Core.package/RPackage.class/instance/class tags/addClassTag_.st A RPackage-Core.package/RPackage.class/instance/private/basicAddClassTag_.st A RPackage-Core.package/RPackage.class/instance/private/importCategory.st A RPackage-Core.package/RPackage.class/instance/private/importProtocol_forClass_.st M RPackage-Core.package/RPackageTag.class/instance/accessing/addClassNamed_.st M RPackage-Core.package/RPackageTag.class/instance/accessing/addClass_.st A RPackage-Core.package/RPackageTag.class/instance/accessing/ensureSystemCategory.st R RPackage-SystemIntegration.package/extension/RPackage/instance/importCategory.st R RPackage-SystemIntegration.package/extension/RPackage/instance/importClass_.st R RPackage-SystemIntegration.package/extension/RPackage/instance/importProtocol_forClass_.st M RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/systemClassAddedActionFrom_.st M RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/systemClassRecategorizedActionFrom_.st M RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/systemMethodRecategorizedActionFrom_.st A ScriptLoader30.package/ScriptLoader.class/instance/mc related utils/getSliceIssuesNumbers.st M ScriptLoader30.package/ScriptLoader.class/instance/menu integration actions/doneApplyingChanges.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script354.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30701.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A ScriptLoader30.package/ScriptLoader.class/instance/public/generateCommentForCurrentUpdate.st M Tools.package/AbstractTool.class/instance/category/renameCategory_from_.st Log Message: ----------- 30701 12625 toggling hierarchy/flat shows wrong package and hides selected class https://pharo.fogbugz.com/f/cases/12625 12664 move categories need to ensure RPackage and RPackageTag https://pharo.fogbugz.com/f/cases/12664 12665 Allow non-dirty packages to be included into slice https://pharo.fogbugz.com/f/cases/12665 12669 Autogenerate comment for update based on slices MC packages present https://pharo.fogbugz.com/f/cases/12669 http://files.pharo.org/image/30/30701.zip

Jan. 16, 2014

Re: [Pharo-dev] IncompatibleLayoutConflict with NativeBoost in recent #30700

by Igor Stasenko

On 16 January 2014 22:07, Torsten Bergmann <astares(a)gmx.de> wrote: > Igor wrote: > >i start feeling guilty that NB uses anonymous classes, which brings so > much problems to everyone... :) > > So now you should really be ashamed and repair the mess you created :) > > I? initially there was 'self shallowCopy methodDict: nil; superClass:self' kind of code.. and everything worked. Then people started telling that it is not using 'legal' protocols.. etc etc, so i asked: give me one. As it appears now a 'correct' implementation requires creating class/metaclass pair and involves new class builder with new and undocumented API. Which still doesn't delivers. Maybe i asking for impossible? :) ... ehh.. same story about generated code btw. To summarize, everything goes towards: - y u no use metaprogramming. Bye > T. > > -- Best regards, Igor Stasenko.

Jan. 16, 2014