October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Is there a Roadmap for Pharo 3.0 and Pharo 4.0

by StÃ©phane Ducasse

thanks I will have a look :) Stef On Oct 16, 2013, at 4:31 AM, btc(a)openInWorld.com wrote: > StÃ©phane Ducasse wrote: >> >>>> the problem with this is that we do not have a clear roadmap for Pharo4 (yet). >>>> How it works now is: at the beginning of a year iteration we make a list of what we want, taking into account what emerged latest year (both new possibilities opened and new/old problems that emerged). >>>> >>>> That gives us what we can more or less call a "next release road map". And is "more or less" because situation can change. For example we wanted a complete revamp of Pharo3 L&F, and we wanted also a complete migration of Morph to be rendered with Athens, and reality showed that is not achievable this year... so it will wait until next one (and that does not means at all that we stopped work on that area, just that the completion of the task will take more time than expected). >>>> So... what's the roadmap for Pharo4? No Idea :) >>>> What we already know is that we made a huge move forward in infrastructure for Pharo3 (starting by Opal, but not restrained to that), and now we want to focus in the tools (but without doing *just* that, because there are lots of tasks to do in kernel, modularization, cleanups, etc.) >>>> >>>> in general, for pharo there is a vision document that shows the long (really long) term goals. Now I do not remember where is it, but should be somewhere in the pharo site (probably not visible enough). >>>> >>>> >>> The problem is that I think we already did a lot of that vision. We need a new one. >>> >> >> I will update it :) >> And I want a bootstrap and mini core and â¦. >> >>> >> >> >> >> > Stef, > > A few weeks back I had occasion to review the Pharo Vision document again. In the process of adding an additional Use-Case, I ended up marking lots of small editorial improvements throughout the document. My focus was not on eliminating grammar mistakes by non-native-english authors (it was pretty good) - but more on trying to find the 'best' way to phrase something. Eliminating the sort of things that creep into my own writing until the third or fourth review, along the lines of that saying about the writing process... "The job is not done until there is nothing left to remove" > > cheers -ben > <pharovision-btc-markup-2013-09-11.pdf>

Oct. 16, 2013

Re: [Pharo-dev] TxText status (was Re: bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated] )

by StÃ©phane Ducasse

please note that the re is a little undo frameworks made by alain plantec in the image. I think that phil is refeergin to paragraph and textEditor not undo/redo Stef On Oct 16, 2013, at 4:02 AM, btc(a)openInWorld.com wrote: > I guess Phil is referring to the difficulties of the current undo mechanism, which you've already discovered. > One of the problems with web interfaces to a mailling-list is sometimes losing context. (I'm using Thunderbird 2.0 and it doesn't do threads.) > > btw, What is the plan/schdule for TxText integration into Pharo mainline? > > cheers -ben > > > > kilon wrote: >> >> philippeback wrote >> >>> Don't enter that if you aren't ready to invest a couple of weeks. >>> TxText will change it all anyway. >>> >>> Disclaimer: I spent the couple of weeks. >>> >>> Phil >>> >> >> Sorry don't understand what you mean . Are you referring to me ? Enter what >> ? >> >> >> >> >> -- >> View this message in context: http://forum.world.st/bug-4993-Typing-cmd-L-cancel-all-typing-and-we-can-t-… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> >> >

Oct. 16, 2013

Re: [Pharo-dev] about your heated discussion on fonts from stef Ze wize and busy man

by StÃ©phane Ducasse

not having two classes and all the mess around when we can have one with alpha: by default. In 2013 Colors can support translucency Stef On Oct 15, 2013, at 11:26 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Just curious, > What's wrong with translucent colors? > > Alexandre > >> Le 15-10-2013 Ã 16:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : >> >> Hi guys >> >> Two points: >> - I'm sorry I got too busy to read the thread - when I have time for pharo I'm fighting with removing translucentColor and it explode my image. >> I'm working on too many fronts and must close and finish some of my tasks (admininistration/team management included). >> >> - Pay attention not to put too much heat in your discussions. ;D >> >> Stef >

Oct. 16, 2013

Re: [Pharo-dev] Is there a Roadmap for Pharo 3.0 and Pharo 4.0

by Marcus Denker

On Oct 16, 2013, at 4:32 AM, btc(a)openinworld.com wrote: >> >> >> >> > Stef, > > A few weeks back I had occasion to review the Pharo Vision document again. In the process of adding an additional Use-Case, I ended up marking lots of small editorial improvements throughout the document. My focus was not on eliminating grammar mistakes by non-native-english authors (it was pretty good) - but more on trying to find the 'best' way to phrase something. Eliminating the sort of things that creep into my own writing until the third or fourth review, along the lines of that saying about the writing process... "The job is not done until there is nothing left to remove" > > cheers -ben > <pharovision-btc-markup-2013-09-11.pdf> very nice! Thanks! I will make a pass to integrate your suggestions. Marcus

Oct. 16, 2013

Re: [Pharo-dev] Outdated Bug [7245] Autocomplete highlighting out of sync w editor after partial match

by btc＠openinworld.com

Oct. 16, 2013

Re: [Pharo-dev] Outdated Bug [7245] Autocomplete highlighting out of sync w editor after partial match

by btc＠openinworld.com

Oct. 16, 2013

Re: [Pharo-dev] default monospaced code font

by btc＠openinworld.com

Nicolas Cellier wrote: > Pushing the newcomers argument: if newcomers are used to using if then else > and switch case, why did you deprecate usage caseOf:? > If newcomers argument counts, shouldn't we remove text editing, browser, > etc..., go back to file based development and create an eclipse (or emacs) > plugin? > > I saw very good arguments for proportional: more readable/natural/more text > on the line... > So I'm inlne with Pavel, > > Is there any argument for fixed space (but the hypothetical newcomer). > There are some times when we must educate rather than imitate. > > > Links [1] & [2] provide some good points both ways. I agree that we ultimately want to educate - but sometimes its good to avoid educating too-much at once. I think the point is that fonts are not a "distinctive" feature Smalltalk, although Eliot argued Smalltalk it has a tighter binding that other languages. Even so, lets not deter newcomers on the basis of fonts before we hook them with experience of Smalltalk's advantages. Before you consider glossing over this thinking "it shouldn't be a big deal to newcomers, they should get over it" consider the emotion evoked in this thread. One significant cognitive rule of persuasion is "that you cannot use logic to argue a decision made on the basis emotion". I think it is useful for newcomers to have time to absorb the alien nature of Smalltalk without the distraction of acclimatising to a different font regime. Some interesting points I picked up. * Most proportional fonts are designed for prose and only little punctuation (which in turn is usually one or rarely two characters). The C family of languages have lots of punctuation, which simply does not look good [with proportional] and is harder to read than necessary. [2] [and Smalltalk is more like prose.] * [With proportional...] feel better about using longer, more descriptive variable names (maybe because they scan better, maybe because the horizontal size of the text is compressed) [2] * All it takes is a few hours of trying to figure out why a search isn't finding something because you have 2 spaces instead of 1 in your literal, to realize you should use Monospace fonts. [2] * With monospace you can select rectangular sections [1] Not sure how well that relates to Smalltalk. Now having tried the directions provided by Pavel to sample the new font, upon review of a small amount of code, I quite like the font. In comparison the proportional font seems too compressed. However this could be resolved for the proportional font by making the 'spaces' wider. (One of the central features of graphic design is liberal use of whitespace.) In the end I am sitting on the fence. Perhaps there just needs to be a welcome screen that with a big switch easily thrown between the choices, along with a couple of others like Smart Quotes that are foreign and irritating to newcomers (and even though I sometime try again, I still struggle with and have to turn off) cheers -ben [1] http://programmers.stackexchange.com/questions/5473/does-anyone-prefer-prop… [2] http://stackoverflow.com/questions/218623/why-use-monospace-fonts-in-your-i…

Oct. 16, 2013

Re: [Pharo-dev] Is there a Roadmap for Pharo 3.0 and Pharo 4.0

by btc＠openinworld.com

Oct. 16, 2013

Re: [Pharo-dev] Is there a Roadmap for Pharo 3.0 and Pharo 4.0

by btc＠openinworld.com

Oct. 16, 2013

TxText status (was Re: bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated] )

by btc＠openinworld.com

Oct. 16, 2013