- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 806e9c: 50629

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 806e9c045788b45d43e023febb323e9c99b6f7e6 https://github.com/pharo-project/pharo-core/commit/806e9c045788b45d43e023fe… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-07 (Mon, 07 Mar 2016) Changed paths: M AST-Core.package/RBParser.class/instance/private-parsing/parseLiteralByteArrayObject.st M BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/api projectSpec/baseline_.st M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/development_.st M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/pre2%5F4%5F0_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/pre2%5F5%5F0_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F4%5F0_.st M ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/development_.st M ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/stable_.st R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/pre0%5F12%5F0_.st A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/pre0%5F13%5F0_.st A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F12%5F0_.st A Graphics-Display Objects.package/extension/DummyUIManager/instance/checkForNewDisplaySize.st A Graphics-Display Objects.package/extension/DummyUIManager/instance/newDisplayDepthNoRestore_.st M QualityAssistant.package/QASettings.class/definition.st M QualityAssistantRecording.package/QAEventCollector.class/instance/events/recordAnnouncement_.st A QualityAssistantRecording.package/QARecordingSettings.class/README.md A QualityAssistantRecording.package/QARecordingSettings.class/class/accessing/uniqueInstance.st A QualityAssistantRecording.package/QARecordingSettings.class/class/cleanup/cleanUp.st A QualityAssistantRecording.package/QARecordingSettings.class/class/settings-accessing/qaGroupSettingsOn_.st A QualityAssistantRecording.package/QARecordingSettings.class/class/settings-accessing/showErrors.st A QualityAssistantRecording.package/QARecordingSettings.class/class/settings-accessing/showErrors_.st A QualityAssistantRecording.package/QARecordingSettings.class/class/settings-definition/showErrorsSettingsOn_.st A QualityAssistantRecording.package/QARecordingSettings.class/definition.st A QualityAssistantRecording.package/QARecordingSettings.class/instance/accessing/inspectorPluggin_.st A QualityAssistantRecording.package/QARecordingSettings.class/instance/accessing/showErrors.st A QualityAssistantRecording.package/QARecordingSettings.class/instance/accessing/showErrors_.st A QualityAssistantRecording.package/QARecordingSettings.class/instance/initialization/initialize.st A Renraku.package/ReInvocationOrderCritic.class/README.md A Renraku.package/ReInvocationOrderCritic.class/class/instance creation/withAnchor_by_method_condition_.st A Renraku.package/ReInvocationOrderCritic.class/definition.st A Renraku.package/ReInvocationOrderCritic.class/instance/initialization/initializeRule_sourceAnchor_method_condition_.st A Renraku.package/ReInvocationOrderCritic.class/instance/testing/providesChange.st A Renraku.package/ReInvocationSequenceRule.class/README.md A Renraku.package/ReInvocationSequenceRule.class/class/compiling/noteCompilationOf_meta_.st A Renraku.package/ReInvocationSequenceRule.class/class/example/exampleSequenceMethods.st A Renraku.package/ReInvocationSequenceRule.class/class/testing/isVisible.st A Renraku.package/ReInvocationSequenceRule.class/definition.st A Renraku.package/ReInvocationSequenceRule.class/instance/accessing/name.st A Renraku.package/ReInvocationSequenceRule.class/instance/adding/add_requiresPostSend_.st A Renraku.package/ReInvocationSequenceRule.class/instance/adding/add_requiresPreSend_.st A Renraku.package/ReInvocationSequenceRule.class/instance/critic creation/critic_for_at_regarding_.st A Renraku.package/ReInvocationSequenceRule.class/instance/critic creation/postCriticFor_at_regarding_.st A Renraku.package/ReInvocationSequenceRule.class/instance/critic creation/preCriticFor_at_regarding_.st A Renraku.package/ReInvocationSequenceRule.class/instance/initialization/initialize.st A Renraku.package/ReInvocationSequenceRule.class/instance/running/basicCheck_.st A Renraku.package/ReInvocationSequenceRule.class/instance/running/check_forCriticsDo_ifNone_.st A Renraku.package/ReInvocationSequenceRule.class/instance/running/postCheck_forCriticsDo_.st A Renraku.package/ReInvocationSequenceRule.class/instance/running/preCheck_forCriticsDo_.st A Renraku.package/ReInvocationSequenceRuleSequence.class/README.md A Renraku.package/ReInvocationSequenceRuleSequence.class/class/instance creation/before_after_.st A Renraku.package/ReInvocationSequenceRuleSequence.class/definition.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/accessing/after.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/accessing/afterMatches_.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/accessing/before.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/accessing/beforeMatches_.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/initialization/initializeBefore_after_.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/printing/afterDescriptionString.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/printing/beforeDescriptionString.st A Renraku.package/ReInvocationSequenceRuleSequence.class/instance/printing/descriptionStringFor_.st A Renraku.package/ReLaterInvocationCritic.class/README.md A Renraku.package/ReLaterInvocationCritic.class/definition.st A Renraku.package/ReLaterInvocationCritic.class/instance/accessing/description.st A Renraku.package/ReLaterInvocationCritic.class/instance/accessing/title.st A Renraku.package/RePriorInvocationCritic.class/README.md A Renraku.package/RePriorInvocationCritic.class/definition.st A Renraku.package/RePriorInvocationCritic.class/instance/accessing/description.st A Renraku.package/RePriorInvocationCritic.class/instance/accessing/title.st A Renraku.package/extension/RBProgramNode/instance/reverseNodesDo_.st M Renraku.package/extension/RBSelfSentNotImplementedRule/instance/check_forCriticsDo_ifNone_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50628.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50629.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50628.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50629.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R UIManager.package/DummyUIManager.class/instance/display/checkForNewDisplaySize.st R UIManager.package/DummyUIManager.class/instance/display/newDisplayDepthNoRestore_.st Log Message: ----------- 50629 17745 RBParser>>parseLiteralByteArrayObject doesnt consume token on error https://pharo.fogbugz.com/f/cases/17745 17762 move DisplayScreen related DummyUIManager messages to the Graphics-Display Objects package https://pharo.fogbugz.com/f/cases/17762 17760 QualityAssistant v2.4.0 https://pharo.fogbugz.com/f/cases/17760 http://files.pharo.org/image/50/50629.zip

March 7, 2016

Re: [Pharo-dev] Spotter and parent file directory

by Tudor Girba

Hi, > On Mar 6, 2016, at 11:26 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi Doru/Andrei > > I just produced a video on using spotter for files/dir navigation. Cool > > Here is my feedback > > - why don't we get dir when we request files? We created two different processors for #files and #directories. So, when you search for #files, you only get the files. It looked like a good idea at the time, and until now, I still think it is Ok. It is conceivable to merge though. What do you think? > - I tried ./../ #files :) > Would be nice to have it Indeed. This is missing. > - I'm spoiled with Spotter Good :) > I tried to navigate a mcz file :) > any taker to get the contents of the file displayed This is funny, because I was just thinking about the same as a demo the other day. I might look at it. Cheers, Doru > > Stef > > -- www.tudorgirba.com www.feenk.com "Every successful trip needs a suitable vehicle."

March 7, 2016

Re: [Pharo-dev] For future version of Spotter

by Henrik Nergaard

The ShortcutReminder tool includes a button which resets parts of its state from the settings. The methods used for this can be found under the "settings" protocol on the instance side. Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Yuriy Tymchuk Sent: Sunday, March 6, 2016 2:52 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] For future version of Spotter I want to have the same thing for > On 06 Mar 2016, at 14:44, stepharo <stepharo(a)free.fr> wrote: > > > > Le 6/3/16 11:39, Tudor Girba a Ã©crit : >> Hi, >> >> This is on the todo list, but I would rather want to have that in settings with a button. > > sure > >> I did not check if this is possible yet. Does anyone know if it is? I want to have the same thing for my stuff. Let me know if you find out how to do that. (Juraj was working with settings. Maybe he knows something) Cheers. Uko > > it could be also in the help. > Normally you do not shoot videos every day or need to get to a clean state. >> >> Cheers, >> Doru >> >> >>> On Mar 6, 2016, at 10:53 AM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Add a menu doing >>> >>> GTSpotter cleanUp. >>> GTSpotter dontShowPreview >>> >>> Stef >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Every thing should have the right to be different." >> >> >> >> >> >> > >

March 7, 2016

Re: [Pharo-dev] [ANN][Bloc] February report

by Alexandre Bergel

Hi Alex, This is a fantastic report. Unfortunately, I will not be at Pharoâs days. We will have a very close look at it as Bloc will be the base of Roassal3. Cheers, Alexandre > On Mar 6, 2016, at 8:34 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi all > > Today is sunday meaning that we should make a monthly report on what happened in Bloc in February. > > - BlLinearLayout (stack layout + proportional layout) > â¢ Uses gtExample for examples and tests: BlLinearLayoutExamples > â¢ Has extensive class docs and method docs. Still some methods are missing docs. > â¢ Has "book" chapter (more info below) > - Integration with OS-Window > â¢ Finally works, really fast. > â¢ Events do not work as expected because of https://pharo.fogbugz.com/f/cases/17757 > - Unified shape scaling behaviour. > â¢ By default shape scales to fill BlElement's extent. > â¢ Supports different resizing strategies. > â¢ Started "book" chapter > - Added documentation to various parts of Bloc > â¢ Still there are a lot of places not covered with docs. > â¢ Also we auto-generate "book" chapters from bloc example classes. In attachment you can find linear-layout and not finished shape chapter. > > Future > > - Bloc presentation on PharoDays2016 > â¢ 01 April 2016 > â¢ 11:05â11:25 Bloc: Towards a vector-based GUI > - Working on > â¢ Grid layout (all rules above apply, docs + tests + chapter) > â¢ Bloc tests > â¢ Documentation > > Cheers, > Alex > > <bloc-documentation.zip> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 6, 2016

Call about Numerical Methods in Pharo :)

by Ben Coman

On Sun, Mar 6, 2016 at 5:05 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 05 Mar 2016, at 19:57, Ben Coman <btc(a)openinworld.com> wrote: >> >> On Sun, Mar 6, 2016 at 2:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>> On 05 Mar 2016, at 18:22, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>> >>>> Stef, >>>> >>>> On Mar 5, 2016, at 12:10 AM, stepharo <stepharo(a)free.fr> wrote: >>>> >>>>> You probably leave in a protected environment but I do not live in the same. >>>>> Did you check numPy recently or R? momemtum? >>>>> Do you think that people do not know how to count? >>>>> In 1980 my students were not even born, so how can it be better than >>>>> python, java, c#, lua, ... >>>>> >>>>> Do you think that it makes me happy to see my old friends leaving our language and do node.js. >>>>> Seriously. >>>>> Why do you blame me? Frankly tell to leave Pharo and I will leave. I can tell you. >>>>> I think that I need a break in my life in this moment so it would be a good opportunity. >>>>> Because if each time I do something to improve the wealth and visibility of our system >>>>> I get such kind of feedback then may be this is the time to do something. >>>>> Afterall I may be wrong. >>>>> Seriously if you think that I'm not doing a good job and you want to stay with old friends >>>>> just let me know. but if I stay then do not tell me that I'm an asshole that does not want to >>>>> promote smalltalk. >>>> >>>> I do not blame you. I am offended by Pharo disavowing the Smalltalk name. I am offended when people state Pharo is not Smalltalk. I want to refute false assumptions about the name Smalltalk, such as the equating it with cobol. Instead of taking it personally why don't you address my points about older programming languages whose names (AFAICT) are not perceived negatively? >>>> >>>> >>>> I support this community and am excited to participate in it. I admire and respect your efforts, StÃ©phane, in developing, organizing and supporting this community. But that does not mean I will keep quiet about something I profoundly disagree with and think is wrong. And that thing is to deny Pharo is Smalltalk. >>>> >>>> And I do this not because I am a zealot, but because words meaning are important, because to understand each other we should call a spade a spade, and because I am grateful for and delighted by this thing called Smalltalk, and I will not support taking credit away from it. Ruby is inspired by Smalltalk. Pharo is the real thing. >>> >>> Pharo was started because a certain situation existed in the Squeak community that blocked progress for a group of people that had another vision. Pharo was started and exists to fulfil that grand vision, a vision that is clearly rooted in Smalltalk history, but goes beyond that. >>> >>> If you want to focus on words, your sentence 'Pharo is Smalltalk' is not so innocent or politically free, as you know very well, even if it looks like factually correct (it is BTW). >>> >>> We say it differently because of what I just wrote, because we want to be free of backwards compatibility (if necessary), because we want to have a larger future than maintaining something old (even though we absolutely respect and acknowledge it). Yes, it is a bit of a play of words, but not without reason. >>> >>> Here is one writeup that tries to describe the same idea: >>> >>> http://www.tudorgirba.com/blog/pharo-is-pharo >>> >>> But the best documents are the Pharo vision documents. >> >> >> The counter argument is that there was Smalltalk-71, -72, -76, -78, >> -80. Some of these were distinctly different from the last. So >> Smalltalk was an *evolving* system. Why can't it be so again!? and >> be Smalltalk-Renew, Smalltalk-Next, Smalltalk-Evolved, Smalltalk-16, >> Smalltalk-P16 or Smalltalk-P5 "Pharo 5". >> >> As long as the emphasis is on Pharo being an *evolution* of Smalltalk >> (which is not in doubt), I think we cover all bases - stimulating the >> interest of newcomers and/or detractors of old, as well as Smalltalk >> stalwarts without being constrained by the past. As much as we might >> want to promote Pharo being separate from Smalltalk (which I believe >> was a reasonable strategy to establish identity at the time of the >> fork from Squeak), Smalltalk is always going to be there for anyone >> who scratches beneath the surface and they end up thinking "Oh its >> *just* Smalltalk" anyway. So this remains the "elephant in the room", >> *subtly* undermining of our marketing. Its the sort of weakness that >> can be better to hit head on as "Smalltalk-Evolved" (since "Evolved" >> is a term with positive connotations in the gaming / sci-fi >> communities.) >> >> cheers -ben > > Really, Ben, are you suggesting we stop calling it Pharo ? > Come on, let's be serious. Thats not a serious question. Pharo could only be called Pharo. Now just to be clear, I sit in the middle on this. I never experienced the constraint felt before the fork from Squeak, and on the flip side I have no big history with Smalltalk. To me, Pharo is just Pharo and there is nothing to stop us developing the system how we like. However I see the attempt to distance Pharo from past problems by branding with a fresh coat of paint false economy. People *will* scratch beneath the surface and the only way to address their perceived problems with Smalltalk is to address them - one by one. The essence of dispute is: on the one hand... A1. Future development without outside constraint A2. Avoid the perception of being an antiquated system and on the other hand... B1. Stronger recognition of our Smalltalk lineage I just don't see these as incompatible. B1 might be addressed in a small way by a simple changing in language from "inspired by" to "derived from". I think its a premature optimisation to be concerned that this might impinge on A1. The Pharo "way" is well established. For A2, I read Stef's reply "we want that people that learned smalltalk in the 90 do not discard Pharo because..." and understand my view of this is limited from my corner of the world. But I contend that while you may get these people in through the door, when they look around their next thought is "Hey, this *is* Smalltalk" and all their old prejudices reassert and they walk away without a further thought. I just feel its better overall for us to be upfront and say "Historically Smalltalk didn't do XX very well, and here is how we've fixed it!" That way, their old prejudice is actually what hooks them to come have a look. To use a strange analogy, its like those superstars who screw up really badly, then > > What makes Pharo different is this: you (and so many others) came to this community as a stranger (for us), started contributing in various ways, we saw that you were serious/good and we accepted your work, letting you work on very fundamental code that had the potential to break everything. There is simply no way that you could have done or be allowed to do that in any other Smalltalk, let alone the place where we forked from. It is as simple as that. That is why it is called Pharo, why we say Pharo is yours. I'm glad to have had the opportunity to contribute. I'm very glad that Pharo is all that it is, but this openness is more about Pharo's vision and mission and less about its roots. But you should know, I came to Pharo because I was looking for Smalltalk (from the whisper of a taste 15 years ago.) If it wasn't for that, (to my detriment) I might never have arrived. Perhaps this colours my perspective. cheers -ben > >>>>> Stef >>>>> >>>>> Le 5/3/16 02:18, Eliot Miranda a Ã©crit : >>>>>> >>>>>> >>>>>> On Fri, Mar 4, 2016 at 12:08 PM, stepharo <stepharo(a)free.fr> wrote: >>>>>> >>>>>>> SciPharo? Not so great news from my POV. >>>>>>> What is so much pharo specific in this library? >>>>>>> Is Smalltalk scientific community large enough for yet another split? >>>>>> Split of what? Let us be tagged with a name of 1980 and die in peace. Yes this looks like a >>>>>> smart move. >>>>>> There are just Python and R and Javascript around (not talking about ruby and swift) >>>>>> so this is a great move. We are not the cobol of object-oriented programming!! >>>>>> >>>>>> When I read sentiments like this it makes me want to leave the community. I find it so offensive that the Pharo community uses Smalltalk but wants to distance itself. It feels like theft or massive disrespect for the inventors of the language, or a complete lack of gratitude. >>>>>> >>>>>> C is older than Smalltalk and no one says "C is the cobol of low-level imperative languages". List is much older than C but no one wants to rename Lisp because it is perceived as old. >>>>>> >>>>>> Smalltalk is a beautiful name, carefully chosen to differentiate and identify the system as different, not arrogant, not hieroglyphic. Further, Smalltalkl /is/ different and distinctive materially. Why anyone would be ashamed of that incredible heritage and pervasive influence is beyond me. >>>>>> >>>>>> Offended, >>>>>> Eliot > >

March 6, 2016

Re: [Pharo-dev] [ANN][Bloc] February report

by stepharo

Nice! Since the development of pillar will restart at the end of the month it would be good to make sure that the new version does not break this output. So it would be good to have a job that generates and publish the doc on the web We could have it under http://books.pharo.org I did a new version with Alpha Books and Bloc documentation could go there if you want. Now it may be too early. Stef Le 6/3/16 14:53, Tudor Girba a Ã©crit : > Hi, > > The readable htmls are already pre-built in the zip file: > ./build/layouts/linear/linear.html > ./build/shape/path/shape.html > > These files are produced out of source code that is based on a little engine for describing such step-by-step tutorials. But, the details of this engine are still being worked on. > > Cheers, > Doru > > >> On Mar 6, 2016, at 2:43 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi Alex >> >> How can I "compile" the doc and read it? >> Clement in his tutorial on VM use pillar and download an image and extract from the image the examples >> so may be we could do the same. >> Should I run the examples when I do a change to make sure that I'm not breaking something. >> How do you get green tests? >> >> Stef >> >> >> Le 6/3/16 12:34, Aliaksei Syrel a Ã©crit : >>> Hi all >>> >>> Today is sunday meaning that we should make a monthly report on what happened in Bloc in February. >>> >>> - BlLinearLayout (stack layout + proportional layout) >>> â¢ Uses gtExample for examples and tests: BlLinearLayoutExamples >>> â¢ Has extensive class docs and method docs. Still some methods are missing docs. >>> â¢ Has "book" chapter (more info below) >>> - Integration with OS-Window >>> â¢ Finally works, really fast. >>> â¢ Events do not work as expected because of https://pharo.fogbugz.com/f/cases/17757 >>> - Unified shape scaling behaviour. >>> â¢ By default shape scales to fill BlElement's extent. >>> â¢ Supports different resizing strategies. >>> â¢ Started "book" chapter >>> - Added documentation to various parts of Bloc >>> â¢ Still there are a lot of places not covered with docs. >>> â¢ Also we auto-generate "book" chapters from bloc example classes. In attachment you can find linear-layout and not finished shape chapter. >>> >>> Future >>> >>> - Bloc presentation on PharoDays2016 >>> â¢ 01 April 2016 >>> â¢ 11:05â11:25 Bloc: Towards a vector-based GUI >>> - Working on >>> â¢ Grid layout (all rules above apply, docs + tests + chapter) >>> â¢ Bloc tests >>> â¢ Documentation >>> >>> Cheers, >>> Alex >>> > -- > www.tudorgirba.com > www.feenk.com > > "Don't give to get. Just give." > > > > > > > >

March 6, 2016

Re: [Pharo-dev] Call about Numerical Methods in Pharo :)

by stepharo

Le 6/3/16 14:53, Nicolai Hess a Ã©crit : > > > Thank you StÃ©phane Ducasse, > thank you Eliot Miranda, > and all other people of this community. > > I appreciate what all you are doing (as a teacher / developer / user / > supporter) > for <enter your favourite name for this great exceptional computing > environment> > and it is a pleasure for me to work with you. Me too :) > (this is all I have to say to this topic) > > Thanks ! And go one :-) > > nicolai

March 6, 2016

GTInspector feedabck

by stepharo

Hi guys I'm doing some videos 3 or 4 on GTInspector (I love it). Now I did Smalltalk globals inspect because I wanted to have a large object tree. I tried different ways to filter the presented list but they all failed. - when I typed stupidly Point I got a DNU (so the search should have a exception wrapper) - then after reading the ghost text I each = #Point So I will not show this aspect and just focus on the others. Stef

March 6, 2016

Re: [Pharo-dev] Call about Numerical Methods in Pharo :)

by Torsten Bergmann

It is understandable that over time an own identity for Pharo is helpful (especially because of the bad Smalltalk marketing, failures of commercial vendors in the past, ...). But also no one can not deny/hide the original roots of Pharo: the primary foundations with pure objects all the way down and messages and concepts just plain Smalltalk. Same for the basic class hierarchy, ... So this discussion is useless, especially because Pharo still lacks many of the features a portable, integratable environment should have (and that Smalltalk failed to deliver, at least in a common way). We should not confuse wishes/dreams with existing state of the technology and facts. Also why discuss about this now again? Did we discuss about renaming SUnit into PUnit? No. This just burns our cycles. For the marketing part there is a primary question to be answered: what are the (business) problems Pharo can solve. At least if we want Pharo to be commercially viable and get money (not only our own) into the community. This is the part that was answered by other languages and technologies so far and the simple reason why they are used: even when they are ugly they solve a problem. Nonetheless: ============ If there is a rename I would suggest to rename "SciSmalltalk" intoÂ "Polymath". Â Â - https://en.wikipedia.org/wiki/Polymath - it can be applied to many subject areas - would be related to Math and science - would also have a "P" like Pharo in the name - Da Vinci was a polymath person, as well as Imhotep :) Bye T.

March 6, 2016

Re: [Pharo-dev] For future version of Spotter

by Tudor Girba

Hi, Done: https://pharo.fogbugz.com/f/cases/17759/Spotter-help-should-point-to-the-re… Cheers, Doru > On Mar 6, 2016, at 2:44 PM, stepharo <stepharo(a)free.fr> wrote: > > > > Le 6/3/16 11:39, Tudor Girba a Ã©crit : >> Hi, >> >> This is on the todo list, but I would rather want to have that in settings with a button. > > sure > >> I did not check if this is possible yet. Does anyone know if it is? > > it could be also in the help. > Normally you do not shoot videos every day or need to get to a clean state. >> >> Cheers, >> Doru >> >> >>> On Mar 6, 2016, at 10:53 AM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Add a menu doing >>> >>> GTSpotter cleanUp. >>> GTSpotter dontShowPreview >>> >>> Stef >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Every thing should have the right to be different." >> >> >> >> >> >> > > -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

March 6, 2016