- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Slack, fragmentation and design information

by Dimitris Chloupis

The thing that annoy me the most with C2 is that almost each time I googled Smalltalk when I wasstill a beginner with Pharo and Smalltalk this came up often http://wiki.c2.com/?WhyIsSmalltalkDead But yes I agree, its nice to have a place to put information and never worry about it getting delete. On the matter of Slack, my Discord bot , lighthouse has evolved to message the online chat with replies to the mailing list which gave a good look inside how chat bots work. Esteban made me admin in Slack so the next step is to have the bot connect to Slack and copy the Slack messages to Discord chat , which means you wont need a Slack plan, because Discord never deletes messages. This way we can use Discord as a backup for our Slack messages and the bot could also copy the messages to a file , I am considering SQLite which we support, so that we never lose the content. Problem solved and it also solves the problem of fragmentation. The mailing list is already connected to Discord via my bot, Slack will also connect to discord via my bot and pretty much anything else can be brought into this hub so everyone can keep using Slack or whatever way he or she prefers to communicate without the fear of fragmentation. On Tue, Feb 14, 2017 at 1:07 PM Pierce Ng <pierce(a)samadhiweb.com> wrote: > On Mon, Feb 13, 2017 at 11:51:23PM +0000, Dimitris Chloupis wrote: > > wiki. They end messy and very badly documented. Especially c2 is quite a > > mess, probably the worst wiki I have ever seen. > > To me the lack of organization is in the nature of a wiki. It's like a > place to > be explored. Must be said C2's Smalltalk content is rather meh last I > looked a > few years ago. > > <obPharoContent> My personal wiki has ~800 pages. Already there are nooks > and > crannies that I've not visited in a while. Naturally, Pharo is the tool I > am > using to help me navigate. > > Pierce > >

Feb. 14, 2017

Re: [Pharo-dev] Slack, fragmentation and design information

by Pierce Ng

On Mon, Feb 13, 2017 at 11:51:23PM +0000, Dimitris Chloupis wrote: > wiki. They end messy and very badly documented. Especially c2 is quite a > mess, probably the worst wiki I have ever seen. To me the lack of organization is in the nature of a wiki. It's like a place to be explored. Must be said C2's Smalltalk content is rather meh last I looked a few years ago. <obPharoContent> My personal wiki has ~800 pages. Already there are nooks and crannies that I've not visited in a while. Naturally, Pharo is the tool I am using to help me navigate. Pierce

Feb. 14, 2017

Re: [Pharo-dev] [QA] Scoped

by Ben Coman

Maybe... Browse selected package in a context that limits the scope of analysis tools (e.g. 'Senders of...', 'Implementors of...', 'Class refs...') cheers -ben On Tue, Feb 14, 2017 at 5:26 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > What about the Nautilus Scoped button tooltip to be more explicit for > newbie? > > What about: > > 'Browse the selected packaged in a scoped context: analysis tools as > 'Senders of...', 'Implementors of...', 'Class refs...', etc. are limited > to the package. > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 14, 2017

[QA] Scoped

by Hilaire

Hi, What about the Nautilus Scoped button tooltip to be more explicit for newbie? What about: 'Browse the selected packaged in a scoped context: analysis tools as 'Senders of...', 'Implementors of...', 'Class refs...', etc. are limited to the package. Thanks Hilaire -- Dr. Geo http://drgeo.eu

Feb. 14, 2017

Re: [Pharo-dev] GLMAction and PharoShortcut

by Hilaire

Thanks for the update. Based on previous Steph post, should we move this bug ticket to Pharo7 or keep it for Pharo6? Hilaire Le 13/02/2017 Ã 18:46, Andrei Chis a Ã©crit : > Hi, > > Good catch. Indeed GLMAction>>#shortcutAsString should go to the keymap object. > > Apart from the inconsistencies that you mention, there is in my view > another one. For example, in the debugger in the context menu of the > stack modifiers are displayed using special characters (at least on > mac). In tooltips they are display using Shift, Meta, Ctrl, etc. > Right now the logic for printing shortcuts that way is in > ToggleMenuItemShortcut>>#owner:keyText: and it's a bit complicated to > reuse. See GTSpotterCategoryTitleBrick>>#setShortcutBrickTextFor: for > an example. > > Cheers, > Andrei -- Dr. Geo http://drgeo.eu

Feb. 14, 2017

[pharo-project/pharo-core]

by GitHub

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

Feb. 14, 2017

[pharo-project/pharo-core] 561180: 60388

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 561180ebfea3ed409128b3186f830a8a136d1d19 https://github.com/pharo-project/pharo-core/commit/561180ebfea3ed409128b318… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-14 (Tue, 14 Feb 2017) Changed paths: M GT-EventRecorder.package/GTBasicRecorderEvent.class/definition.st A GT-EventRecorder.package/GTEventCollector.class/class/examples/notRegisteredCollector.st A GT-EventRecorder.package/GTEventCollector.class/instance/gt-inspector-extension/gtInspectorActionHelp.st A GT-EventRecorder.package/GTEventRecorder.class/instance/gt-inspector-extension/gtInspectorActionHelp.st A GT-EventRecorder.package/GTEventRecorderHelp.class/README.md A GT-EventRecorder.package/GTEventRecorderHelp.class/class/accessing/bookDescription.st A GT-EventRecorder.package/GTEventRecorderHelp.class/class/accessing/bookName.st A GT-EventRecorder.package/GTEventRecorderHelp.class/class/accessing/pages.st A GT-EventRecorder.package/GTEventRecorderHelp.class/class/pages/analysis.st A GT-EventRecorder.package/GTEventRecorderHelp.class/class/pages/client.st A GT-EventRecorder.package/GTEventRecorderHelp.class/class/pages/introduction.st A GT-EventRecorder.package/GTEventRecorderHelp.class/class/pages/server.st A GT-EventRecorder.package/GTEventRecorderHelp.class/definition.st A GT-EventRecorder.package/GTEventTool.class/instance/gt-inspector-extension/gtInspectorActionHelp.st M Nautilus.package/ClassWidget.class/instance/private list model/selectedClassIndex.st A Nautilus.package/ClassWidget.class/instance/protocol/showHierarchy_forClass_.st M Nautilus.package/NautilusUI.class/instance/accessing/showHierarchy_.st A Network-UUID.package/UUID.class/instance/initialization/readFrom_.st R Network-UUID.package/UUID.class/instance/instance creation/readFrom_.st A Network-UUID.package/UUID.class/instance/private/readHexByteFrom_.st R Network-UUID.package/UUID.class/instance/private/readHexFrom_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60387.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60388.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60387.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60388.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Base.package/ToolRegistry.class/instance/menu/menuItems.st Log Message: ----------- 60388 19695 UUID>>#readHexFrom: accidentally overwrites an inherited method https://pharo.fogbugz.com/f/cases/19695 19510 Nautilus Hierarchy view of superclasses does not show all the superclasses https://pharo.fogbugz.com/f/cases/19510 19693 GTEventRecorder should be documented https://pharo.fogbugz.com/f/cases/19693 19696 Debug world menu still use "Workspace" but open a playgound. https://pharo.fogbugz.com/f/cases/19696 http://files.pharo.org/image/60/60388.zip

Feb. 14, 2017

Re: [Pharo-dev] Slack, fragmentation and design information

by Stephan Eggermont

On 13/02/17 16:39, Esteban A. Maringolo wrote: > If haven't used the c2 wiki or the squeak wiki then you haven't > experienced what it meant, at that time, to find everything there, or > expand articles with your own content. It was really useful, c2 still > is. The squeak wiki is also still very valuable. Lot's of broken links, but also lots of snippets of explanation of why things are as they are. It was essential for getting my Morphic understanding together. Stephan

Feb. 14, 2017

Re: [Pharo-dev] FastTableModel switched from default single-select to multi

by Stephan Eggermont

On 13/02/17 12:52, Andrei Chis wrote: > Is this in the Glamour model or in the Spec one? In the Spec one, so I might be a bit late in noticing. Stephan

Feb. 14, 2017

Re: [Pharo-dev] Project Mirrors: ConfigurationOf vs. BaselineOf

by Dimitris Chloupis

Â§ On Tue, Feb 14, 2017 at 1:31 AM Sean P. DeNigris <sean(a)clipperadams.com> wrote: An increasing number of projects are hosted both on an mcz repo e.g. StHub, which loads via ConfigurationOf; and GitHub, which loads via a BaselineOf. Do we have an elegant (i.e. not requiring copy/pasting between the config and baseline) way of managing loading for such a project? For example, I want to fork NeoCSV from GitHub and load my fork, but there is no BaselineOf because the "main" repo is on StHub and the GitHub repo is a mirror (with seemingly limited value since it doesn't seem possible to load from there). Thanks! I distribute all my projects through Catalog Browser and Github, no interest on StHub. None has complained to me so far. Super easy, simple, flexible and powerful. The configuration that is added in metarepo loads the latest from master branch , which I use as a stable release.I add it once per pharo version and never both with it again. Baseline does the heavy lifting of loading dependencies. Git tags mark the versions, independent releases in zip files for those wanting a standalone pharo distribution with just the library in it are also easy to make. Version control wise, I rely completely on git. You do not need a baseline to load a git fork into pharo because git plus filetree can do this , but obviously one must be provided because its much cleaner this way. Especially if the latest code is quite unstable and buggy.

Feb. 14, 2017