pharo-project
Spotter cannot search with case sensitivity on
Spotter cannot perform the following with case sensitivity ON. SystemNavigation default browseMethodsWithSourceString: 'aBuilder item: #' matchCase: true.
I suggest Spotter has a checkbox to turn on and off case sensitivity.
If Spotter returns too many results for "plusTerms" as currently, I would like to narrow it down to match case "plusTerms". Spotter should have match-case and whole-word options which is the standard these days.
Similarly, autocomplete insists on match-case always when I often don't remember the exact case used in spelling. Equally frustrating.
You see if nobody helps it will not happen. You should have a look at bit at the PRs we are merging to see the amount of work we are doing. And we do a lot but we will never have the time to handle everything. So why don't take an issue and try to propose an improvement.
The more serious issue is the following. Pharo needs new blood. New developers already have experience with VSCode, Visual Studio, Eclipse, Matlab, Word, Excel, Browsers, etc. All have standardized on common basic operations and UI behaviors. Pharo needs to too. Otherwise, new users will be immediately turned off and never come back. My creation of issues is along these lines. Pharo community needs to prioritize this problem. We need to come down from our ivory tower to work on basic tools and basic conventions. Basic tools must always be rock solid and follow common conventions.
I totally agree.
One explanation is that most Pharo contributors, myself included, are not very good at and not very interested in UI/UX.
On the other hand, it is mainly a question of taking good care of the environment while things are evolving.
Thanks for understanding. I really believe this problem threatens Pharo and Smalltalk long term existence. All the great capabilities of Smalltalk will not be noticed, if newcomers don't get past the discomfort of the basic tools and turn away. Even for seasoned Smalltakers, the unconventional behavior of Pharo basic tools is a drain of mental energy which is most precious for our small community.
I love all YOUR must and must and must. I think that you have no clue
- about what is the deal with old frameworks and systems with limited tests.
- the number of tools we are maintaining and enhancing. And the resources we have.
Sorry but so far I did not much about the seasoned Smalltalkers in terms of help, contributions and more besides Kasper that actually really helped building microdown. Of course the old seasoned Smalltalkers apparently that are so great at building systems cannot cope with a tool failing.
Just a question. How much is a VW, VA license fee? Did you join the pharo association because I'm talking 0.27 cts per day?
Finally did you READ the bug report of Guillermo because he found the cause of the problem and alexis was doing another analysis. Should I conclude that you could not try to see if trying their proposal would solve the problem and just let us know - I'm not talking about sending a PR because it is often too arcane for seasoned Smalltalk.
Of course WE have to do it.
So sorry but I start to be pissed off by your consumer (who does not pay) feedback. I will see if during MY holidays I have a bit of time to go and check what Guille found and explore how to solve the problem (as if I would know it upfront).
I am very glad my reported issues are being worked on. Thanks. The worrisome thing to me is that I had to even report them. Basic tools must always work and follow familiar conventions. Tests should check that.
Old Smalltalkers are retiring en masse. All the more reason for Pharo/Smalltalk to attract young programmers. We must meet their minimum standards for basic tools, before they will discover Smalltalk's live programming, purity and consistency, reflection, debugger, etc.