- Pharo-dev - lists.pharo.org

[Update] #40363

by Marcus Denker

14429 DebuggerTests package should be Debugger-Tests https://pharo.fogbugz.com/f/cases/14429 14431 FontInfrastructureTests package should be FontInfrastructure-Tests https://pharo.fogbugz.com/f/cases/14431 14430 EmbeddedFreeTypeTests package should be EmbeddedFreeType-Tests https://pharo.fogbugz.com/f/cases/14430

Nov. 10, 2014

Re: [Pharo-dev] Cmd+click in Rubric

by Marcus Denker

> On 10 Nov 2014, at 11:59, phil(a)highoctane.be wrote: > > I'd say that we have all have suffered enough from a sucky text editor. > > So, let's jump over the chasm with no regrets. > > We aren't doing Squeak, right? > I Squeak, there was always some simple next step. But the community always said: âNo, Genius person X is working on Y which will be oh-so-much-betterâ. And therefore, the next step was not done. Of course, Genius Person never finshed Y, because, after nearly doing it, he realised: Wow, one can do it even better! And thus nothing was ever done. Marcus

Nov. 10, 2014

Re: [Pharo-dev] Cmd+click in Rubric

by phil＠highoctane.be

I'd say that we have all have suffered enough from a sucky text editor. So, let's jump over the chasm with no regrets. We aren't doing Squeak, right? Phil On Mon, Nov 10, 2014 at 11:38 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I completely support that. > > We used Rubric in GT because we wanted to get the tools ready for Pharo > 3.0 and for early feedback in Pharo 4.0. Rubric is just a nice makeup of > the old TextMorph and it allows for finer grained programmatic support, but > it is clearly not the future. > > We have to focus on TxText. We are now in an Innovator's Dilemma > situation: TxText does not have all the bells and whistles that Rubric has, > but its foundation is dramatically better (objects all the way down, > screaming performance, vector graphics). We have to judge TxText by its > potential, not by its current state. Igor et co. has done a fantastic job, > and we have to embrace this and support their effort. > > Cheers, > Doru > > > > On Mon, Nov 10, 2014 at 11:17 AM, stepharo <stepharo(a)free.fr> wrote: > >> Guys >> >> I just discussed with Alain who is at my place working with Igor. >> Alain will not invest in Rubric. Rubric is the past. I told him to send a >> mail but he told me that he already said it. >> We should push txText. I will spend some time with igor to push it again >> but we need more people to have a look >> and help. >> >> Stef >> >> >> On 9/11/14 18:12, Yuriy Tymchuk wrote: >> >>> Dear all. >>> >>> Iâve already reported this issue but didnât make it clear. >>> >>> When I cmd+click some text in nautilus, I can âbrowseâ it. This means >>> browse class implementation, browse method implementors. When I cmd+click >>> something in rubric it opens a context menu. >>> >>> I anybody using cmd+click besides of me? >>> Can this be solved? >>> >>> Uko >>> >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 10, 2014

Re: [Pharo-dev] Cmd+click in Rubric

by Tudor Girba

I completely support that. We used Rubric in GT because we wanted to get the tools ready for Pharo 3.0 and for early feedback in Pharo 4.0. Rubric is just a nice makeup of the old TextMorph and it allows for finer grained programmatic support, but it is clearly not the future. We have to focus on TxText. We are now in an Innovator's Dilemma situation: TxText does not have all the bells and whistles that Rubric has, but its foundation is dramatically better (objects all the way down, screaming performance, vector graphics). We have to judge TxText by its potential, not by its current state. Igor et co. has done a fantastic job, and we have to embrace this and support their effort. Cheers, Doru On Mon, Nov 10, 2014 at 11:17 AM, stepharo <stepharo(a)free.fr> wrote: > Guys > > I just discussed with Alain who is at my place working with Igor. > Alain will not invest in Rubric. Rubric is the past. I told him to send a > mail but he told me that he already said it. > We should push txText. I will spend some time with igor to push it again > but we need more people to have a look > and help. > > Stef > > > On 9/11/14 18:12, Yuriy Tymchuk wrote: > >> Dear all. >> >> Iâve already reported this issue but didnât make it clear. >> >> When I cmd+click some text in nautilus, I can âbrowseâ it. This means >> browse class implementation, browse method implementors. When I cmd+click >> something in rubric it opens a context menu. >> >> I anybody using cmd+click besides of me? >> Can this be solved? >> >> Uko >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 10, 2014

Re: [Pharo-dev] Cmd+click in Rubric

by Thierry Goubier

2014-11-10 11:17 GMT+01:00 stepharo <stepharo(a)free.fr>: > Guys > > I just discussed with Alain who is at my place working with Igor. > Alain will not invest in Rubric. Rubric is the past. I told him to send a > mail but he told me that he already said it. > We should push txText. I will spend some time with igor to push it again > but we need more people to have a look > and help. > Solve the font (freetype and Athens) bug is all that is needed IMHO to integrate TxText. I would really like Igor to chart a path for that. Better font rendering in Athens; anti-aliasing for fonts doesn't seems to work (in Roassal as well). But maybe its Pharo 3.0 only ? TxText is at the point where it gaining features that Pharo overall doesn't use ;) Thierry > > Stef > > > On 9/11/14 18:12, Yuriy Tymchuk wrote: > >> Dear all. >> >> I've already reported this issue but didn't make it clear. >> >> When I cmd+click some text in nautilus, I can "browse" it. This means >> browse class implementation, browse method implementors. When I cmd+click >> something in rubric it opens a context menu. >> >> I anybody using cmd+click besides of me? >> Can this be solved? >> >> Uko >> >> > >

Nov. 10, 2014

Re: [Pharo-dev] Cmd+click in Rubric

by stepharo

Guys I just discussed with Alain who is at my place working with Igor. Alain will not invest in Rubric. Rubric is the past. I told him to send a mail but he told me that he already said it. We should push txText. I will spend some time with igor to push it again but we need more people to have a look and help. Stef On 9/11/14 18:12, Yuriy Tymchuk wrote: > Dear all. > > Iâve already reported this issue but didnât make it clear. > > When I cmd+click some text in nautilus, I can âbrowseâ it. This means browse class implementation, browse method implementors. When I cmd+click something in rubric it opens a context menu. > > I anybody using cmd+click besides of me? > Can this be solved? > > Uko >

Nov. 10, 2014

[Update] #40362

by Marcus Denker

14425 FileList should not be used as Widget for opening Folders https://pharo.fogbugz.com/f/cases/14425 14436 NautilusTests package should be Nautilus-Tests https://pharo.fogbugz.com/f/cases/14436 14435 NECompletionTests package should be NECompletion-Tests https://pharo.fogbugz.com/f/cases/14435

Nov. 10, 2014

14445 META case: Pharo4 should have green tests

by Marcus Denker

We have just 4 failing left to fix... ReleaseTest.testMethodsWithUnboundGlobals ReleaseTest.testUndeclared ObsoleteTest.testFixObsoleteSharedPools AJx64AssemblerTests.testStringOps64Mnemonics 14445 META case: Pharo4 should have green tests https://pharo.fogbugz.com/f/search/?sSearchFor=outline%3A14445

Nov. 10, 2014

[Update] #40361

by Marcus Denker

14417 remove #theme from GraphicsFontSettings class https://pharo.fogbugz.com/f/cases/14417 14260 Add gt inspector views to Ordered[Identity]Dictionary https://pharo.fogbugz.com/f/cases/14260 14441 SmartSuggestionsTests package should be SmartSuggestions-Tests https://pharo.fogbugz.com/f/cases/14441 14440 SlotTests package should be Slot-Tests https://pharo.fogbugz.com/f/cases/14440

Nov. 10, 2014

Re: [Pharo-dev] StandardFileStream>>open:forWrite: serious isse...

by Henrik Johansen

> On 07 Nov 2014, at 12:59 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Yes, weird code ;-) Seems to me open:forWrite: would be better off using retryWithGC:until:, which would trigger GC regardless of whether there are registered descriptors for the currently requested handle. That would (hopefully) help against the case where too many handles have been opened (but some are waiting to be finalized), not just the case where you try opening a file in write mode that's already been opened in write mode and discarded. (which is only a restriction on Windows, IIRC) retryWithGC:until:forFileNamed: seems more intended for operations where you are not allowed *any* open handles on the file, such as renames/deletes/moves, etc. Cheers, Henry

Nov. 10, 2014