- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Looking for preferences to move the debugger buttons

by Brad

touchÃ© Brad Selfridge > On Aug 7, 2016, at 3:42 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi > > I'm FEDUP to have to go up to click on buttons in the debugger. > > I know that some of you have a preferences to fix this problem (yes doru nicely explain that we do not understand anything > > and this is part of design but I do not care of design I care about my efficiency - as if Apple wuld not break their design rules in any version of iTunes). > > And I would like to use such preferences. > > > Stef > >

Aug. 7, 2016

Re: [Pharo-dev] Status of SmallPOS

by Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾

Well, general procedure is loading magritte, then loading seaside 2.8, then loading SmallPOS...I made some packaging efforts, see https://code.google.com/archive/p/smalltalkpos/wikis/FullyAutomatedGoferScr… But, well, at the moment simplest possibility is sending you pre-configured image. I may make one for you, if you want. Another trouble is: SmallPOS is not the management software, it's a framework for making management software. I.e., if only smallpos loaded, then you can't look at how it *works*. If you want, I may tinker a small SmallPOS-based example, it's easy and usefull anyway, so do not hesitate to ask :) Something like "Firms and persons", or "books, authors and bookholders" or "teachers, students and courses" - feel free to propose one. There ARE some real-life examples at the same repo, but trouble is they are tinkered for russian market, so all the labels in russian :) Greetings, Yuriy Mironenko 2016-08-07 14:36 GMT+03:00 stepharo <stepharo(a)free.fr>: > There is no configuration and I tried to load the latest version and it > looks like it depends on magritte. > > How do you load it? > > > Stef > > > Le 30/7/16 Ã 19:16, Yuriy Mironenko a Ã©crit : > >> Sorry for answering the "deadly long forgotten" post, but, anyway: it >> happens >> >> at the moment of migration to ss3, I believe. I don't really remember >> actual >> "relicensing" process, I think it was just...welll...selecting from the >> drop-down list, and this time I selected another option. >> >> If you or somebody else will ever need SmallPOS under any other open >> license, I will be glad to deliver it under this license. >> >> >> >> -- >> View this message in context: http://forum.world.st/Status-o >> f-SmallPOS-tp4649796p4908797.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >> > >

Aug. 7, 2016

Re: [Pharo-dev] Status of SmallPOS

by stepharo

There is no configuration and I tried to load the latest version and it looks like it depends on magritte. How do you load it? Stef Le 30/7/16 Ã 19:16, Yuriy Mironenko a Ã©crit : > Sorry for answering the "deadly long forgotten" post, but, anyway: it happens > at the moment of migration to ss3, I believe. I don't really remember actual > "relicensing" process, I think it was just...welll...selecting from the > drop-down list, and this time I selected another option. > > If you or somebody else will ever need SmallPOS under any other open > license, I will be glad to deliver it under this license. > > > > -- > View this message in context: http://forum.world.st/Status-of-SmallPOS-tp4649796p4908797.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Aug. 7, 2016

Re: [Pharo-dev] Status of SmallPOS

by stepharo

Excellent! I will have a look to get an idea :) Le 7/8/16 Ã 12:39, Yuriy Mironenko a Ã©crit : > I just checked: SmallPOS was relicensed under MIT in the middle of year 2012. > So it *is* under MIT license now. > > > > -- > View this message in context: http://forum.world.st/Status-of-SmallPOS-tp4649796p4909835.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Aug. 7, 2016

Re: [Pharo-dev] Status of SmallPOS

by Yuriy Mironenko

I just checked: SmallPOS was relicensed under MIT in the middle of year 2012. So it *is* under MIT license now. -- View this message in context: http://forum.world.st/Status-of-SmallPOS-tp4649796p4909835.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 7, 2016

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

by Ben Coman

On Sun, Aug 7, 2016 at 3:39 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > Seriously I do not get why printing in the debugger cannot just print the > text without putting these ^%&*^*&()**(&%^*( double quote around. I believe the behaviour was introduced for the Workspace/Playground so that inserting the result into the text wouldn't screw up the syntax highlighting or running it again. Perhaps this behaviour was copied/inherited by the Debugger without considering it might be a different use case. ?? cheers -ben > > Why do we change such basic functionality and in particular we do not > propose ANY alternative. > > If you need a pop up and do not care of manipulating text this is ok but WHY > the default behavior has to be changed. > > I hate so much that the GTTool ALWAYS want to IMPOSE a flow. Your &^%*^(& > flow is not mine. > > Should I go and hack to get back the default behavior. WHY do I have to do > that? > > Seriously. > > Especially since the solution was super simple: introduce a new binding > living nicely close to PrintIt > > but no "we have to change the default one with something that may fuck your > flow but who cares because my flow is better." > > Why do we get systematically this message? Why such changes are damaging TDD > practices without any notices? > > May be I should use another Smalltalk at the end. > > Stef > >

Aug. 7, 2016

Looking for preferences to move the debugger buttons

by stepharo

Hi I'm FEDUP to have to go up to click on buttons in the debugger. I know that some of you have a preferences to fix this problem (yes doru nicely explain that we do not understand anything and this is part of design but I do not care of design I care about my efficiency - as if Apple wuld not break their design rules in any version of iTunes). And I would like to use such preferences. Stef

Aug. 7, 2016

when Cmd-P can just display a string in the debugger

by stepharo

Hi Seriously I do not get why printing in the debugger cannot just print the text without putting these ^%&*^*&()**(&%^*( double quote around. Why do we change such basic functionality and in particular we do not propose ANY alternative. If you need a pop up and do not care of manipulating text this is ok but WHY the default behavior has to be changed. I hate so much that the GTTool ALWAYS want to IMPOSE a flow. Your &^%*^(& flow is not mine. Should I go and hack to get back the default behavior. WHY do I have to do that? Seriously. Especially since the solution was super simple: introduce a new binding living nicely close to PrintIt but no "we have to change the default one with something that may fuck your flow but who cares because my flow is better." Why do we get systematically this message? Why such changes are damaging TDD practices without any notices? May be I should use another Smalltalk at the end. Stef

Aug. 7, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

by stepharo

Le 5/8/16 Ã 05:28, Martin Dias a Ã©crit : > Hi Stef, good, I take note. I improved filters in the recent releases > and will continue improving. Thanks Martin I have problems with the menu item names :) To me redo looks strange when I get a crash I want to import the changes not redo them. Then I do not get what undo means (yes I know this is probably revert) May be some pharoers have better names than mine. Stef > > Martin > > On Wed, Aug 3, 2016 at 5:30 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Thanks Martin. > > We missed yesterday: show only the latest version of every > entities. :) > > > Setf > > > Le 3/8/16 Ã 11:23, Marcus Denker a Ã©crit : > > On 03 Aug 2016, at 11:07, GitHub <noreply(a)github.com > <mailto:noreply@github.com>> wrote: > > > Log Message: > ----------- > 60163 > 18831 Integrate new Epicea version > https://pharo.fogbugz.com/f/cases/18831 > <https://pharo.fogbugz.com/f/cases/18831> > > ChangeLog for this: > > - Case 18813: Implement redo and undo of protocol addition and > removal. > > - Case 18612: disable drag&drop until TreeModel supports it > correctly. > > - Case 18384: Redo and undo: show on any selection (not only > when all selected entries are code changes). > > - Enhancement: Improve lost changes detection; show only the > events actually lost. > > - Enhancement: Pass on filters. > > - Clean up: Do not show the "absent entry" item anymore since > it was not useful at all. > > - Clean up: Remove unused "commit tags" in log browser. > > - Clean up: Remove unused tests. They were good idea, we can > re-introduce them but working and covering more cases. > > - Clean up: Rename #displayWidget to #asMorph in > EpLogBrowserItem''s hierarchy. It is more meaningful. > > - Workaround: Hide "Open in Sorter" menu action since it is > useless until Treemodel drag&drop is fixed. > > > > 18768 Inlined method const could be implemented by metalinks > https://pharo.fogbugz.com/f/cases/18768 > <https://pharo.fogbugz.com/f/cases/18768> > > 18835 Update RBParser-Nodes class comments > https://pharo.fogbugz.com/f/cases/18835 > <https://pharo.fogbugz.com/f/cases/18835> > > http://files.pharo.org/image/60/60163.zip > <http://files.pharo.org/image/60/60163.zip> > > > > > > >

Aug. 7, 2016

Re: [Pharo-dev] Refactoring HelpTopic (needs review)

by Nicolai Hess

2016-07-28 16:18 GMT+02:00 stepharo <stepharo(a)free.fr>: > I will! > > I love to read nice comments > > Stef > > I updated the slice and added some more example (much more is needed but I think it is better than having no doc :) ). I changed some help topics on refactoring support in nautilus to directly used the refactoring classes comments (no need to maintain two docs), but this is not applicable for all refactorings, for example "generate superclass" and "insert superclass" needs its own description, as there is only one RBAddClassRefactoring comment. please help with reviewing, I am not good at writing this kind of text. The refactoring engine is a great and powerfull piece of code and it would be great to have a proper documentation "in-image". I have seen some bugs, bad code or wrong bug fixes by contributors not fully understanding the framework (me too :) ). just load the slice and open HelpBrowser openOn: RefactoringHelp. thanks nicolai > Le 28/7/16 Ã 00:38, Nicolai Hess a Ã©crit : > > Hi, > > I recently added some class comments to the Refactoring-Package. > (RBBrowserEnvironments, RBRefactoring, RBNamespace). > > Now I added some more HelpTopics describing the refactoring framework, > some background information, RBPatternParser and Metavariables, some > examples and put the existing class comments into the HelpBook. > > see fogbugz issue 18829 > <https://pharo.fogbugz.com/f/cases/18829/Add-a-RefactoringFramework-System-H…> > Add a RefactoringFramework System HelpTopic > you can load the slice and open the HelpBook with > > HelpBrowser openOn: RefactoringHelp. > > Would be nice if someone can help with proofreading and of course, amy > feedback is welcome. > > nicolai > > >

Aug. 6, 2016