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

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=mac… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 17, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=win… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 17, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=lin… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 17, 2013

Re: [Pharo-dev] TxTextLayout

by stephane ducasse

Guys can you make you emails short! > Be assured, i will get there (once i will finish my vacation and > Athens path geometry > functionality ;). > > I really appreciate of what you doing (and i know multiple people who > can put +1 here) Yes me for example + 10 > The fact that you joined the project by your own will, is what makes > open-source development much more sustainable and powerful, comparing > to "traditional" development behind closed doors. > > Because when you write code you don't like (because it's your job > which pays your bills), you just in "get things done" mode, > but when you self-motivated and really care about result (like in > open-source development), the way you do is quite different, and > results too, as a consequence. > > I would really like if Alain and you could join the effort to make new editor > be ready for next Pharo release (so we can get rid of confusing and scary code). > ;) Yes alain is back from holidays soon too :) Stef > >> Best regards, >> Denis > > -- > Best regards, > Igor Stasenko. >

May 17, 2013

[update 2.0] #20604

by Marcus Denker

20604 ----- 10653 Some Jenkins images show a stdout is closed error https://pharo.fogbugz.com/f/cases/10653 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-CommandLine-MarcusDenker.81.diff

May 17, 2013

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

by kilon

Thank you all for your replies. I have used the solution I get new errors now. Is there an example how to create a context with NBOpenGL because the examples NBOpenGL is coming with are confusing at best ? -- View this message in context: http://forum.world.st/Understanding-NBOpenGL-tp4686514p4688138.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 17, 2013

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

by Esteban Lorenzano

On May 16, 2013, at 11:53 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 15 May 2013 09:37, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> On May 14, 2013, at 12:45 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> How did you loaded NBOpenGL? >>> For 2.0/3.0 pharo image use >>> (ConfigurationOfNBOpenGL project version: '2.0') load >> >> I added this important piece of information into http://smalltalkhub.com/#!/~PharoExtras/NBOpenGL :) >> It would be a lot better to make >> >> ConfigurationOfNBOpenGL load. >> > > unless you put a lot of complex logic behind that "load", > it will never work. Why? load should be ConfigurationOfNBOpenGL class>>#load ^ self project stableVersion load. and nothing else > That's why i prefer to giving a version numbers. This version of > config works with 2.0 image, > and no pain, no surprises. > Now, when people get used to do "ConfigurationOfNBOpenGL load" > it is less pain, but just for the next major update of whatever > infrastructural parts in Pharo. again... why? Because what happens now is that people try to do what is the convention for metacello. Also, that means that by not following the conventions, NBOpenGL will never be able to be loaded through configuration browser :( > > And second, for me, as developer , it is much more helpful to deal > with problem reports like: > "this version doesn't loads/works with this version of image" > instead of "i tried and it doesn't works" :) he, I'm sorry, I disagree... If you as a developer promote a version as a release by assigning a #stable symbolic version to configuration, you know exactly which version the guy is trying to load. And you will not have the problem "this version does not loads...", which is a consequence of not declaring a version as stable for a platform. Looks to me that the problem you try to avoid is in fact happening because the configuration is not adapted to the convention, not the opposite :) As proof... lot's of complex project follow the convention (seaside, for example), and nobody has the issue you say. Recently they prepared the configuration for 2.0, and that means that seaside now loads fine in 1.4 and 2.0.... cheers, Esteban > >> work out of the box, and also to copy them to MetaRepoForPharo20... so everybody can load without needing to thing a lot about. >> >> Esteban > > > > -- > Best regards, > Igor Stasenko. >

May 17, 2013

Re: [Pharo-dev] TxTextLayout

by stephane ducasse

Denis I think that alain will start to look at TextModel too because we do not want to have rubric competing with it and WE WANT ATHENS IN PHARO BEFORE the end of June. Igor when you are back from holidays we will push athens into Pharo and start hakcing like mad :) Stef On May 16, 2013, at 10:32 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/5/16 Camillo Bruni <camillobruni(a)gmail.com> > > On 2013-05-16, at 13:04, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hello. > > > > 2013/5/16 Camillo Bruni <camillobruni(a)gmail.com> > > > >> I have a question concerning the new TxText layout. > >> How hard is it support inline non-text nodes (aka inline morphs) in a text > >> layout? > >> > > > > Do you mean supporting "TxMorphSpan" objects from text model at text layout > > level? > > I think it is is not hard. Main issue here is supporting such kind of spans > > at text model level. But I think it is not difficult too, > > I should look at code to answer in detail (can't do it now). > > > > > >> > >> My dream is still to be able to drag and drop an "instance" from an > >> inspector to a workspace and do some operations on it using standard > >> smalltalk. > > > > > > +1 > > And I want drag and drop objects between inspectors and between workspaces. > > > > > >> The only difference here would be instead of using a variable or > >> expression to get an instance of something I would have a textual/visual > >> node directly representing an instance! > >> > > > > I'm not understand it. > > By dropping some object to workspace It can create named variable and then > > you can use it for scripting inside workspace. > > But what you suggest here? Can you explan deeply? > > > Indeed I am not very clear (as usual :). > a) I want to have a morph representing an object > b) I want to embed these morphs into text > c) I want to interact with these morphs and the text > > Let's say [Set] is the morph representing a set and I have the following > source code with this morph inside: > > [Set] includes: #a > > Then this would be equivalent to the following: > > Smalltalk at: #MySetInstance put Set new. > > MySetInstance includes: #a > > However [Set] is not just text but a real morph I can drag around, right click > and get a decent, instance specific menu on... and so forth :) > > is that more clear? > > Ok. Now I understand what you want. > > I look at code. > As I sad before. TxMorphSpan requires some changes in text model code and layout code. > Now TxLayout is collection of TxLayoutLine's where TxLayoutLine is collection of TxLayoutSpan's. And now TxLayoutSpan is interval of TxCharacterSpan. So TxLayoutSpan know that it is layout of characters. It has font. > One of the options to support TxMorphSpan layout is to introduce TxLayoutMorphSpan and implement all required protocol. To hook up this object during layout building you should implement something like: > > TxMorphSpan>>layoutContentsBy: aLayoutBuilder > aLayoutBuilder currentSpan: (TxLayoutMorphSpan on: self) > aLayoutBuilder completeSpan > > You see it is quite simple. > > Now I almost finich edit decorators stuff. (I have TxNoneEditDecorator, TxMaskEditDecorator, TxInsertModeEditDecorator, TxSmartCharsEditDecorator). And next my task will validation/filtering of input. I think it will require text model changes, so I will think about morph span too. > And of couse if you again join to TxText development it will be perfect! You and Igor started this project. > > Best regards, > Denis > . >

May 17, 2013

[update 3.0] #30138

by Marcus Denker

30138 ----- 10640 unify CompiledMethod #classBinding and methodClassAssociation https://pharo.fogbugz.com/f/cases/10640 10655 fix failing test: SymbolTest.testReadFrom https://pharo.fogbugz.com/f/cases/10655 10643 remove remove CompiledMethod>>receiver:withArguments:executeMethod: https://pharo.fogbugz.com/f/cases/10643 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1454.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Strings-MarcusDen… http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Core-MarcusDenker.150.diff

May 17, 2013

Re: [Pharo-dev] Monkey Validation

by Igor Stasenko

On 16 May 2013 20:03, <btc(a)openinworld.com> wrote: > ClÃ©ment Bera wrote: >> >> Camillo we should really spend some time updating the plots in the jenkins >> job : https://ci.inria.fr/pharo/job/Pharo-3.0-CodeCritics-Beta/ . >> >> > > What is "JSHint Trend" on the graph heading? > Are you advertising something to do with Javascript? :) > (Sorry, its just the first thing that popped into my head looking at it.) > > Yes, this is related to javascript.. looks like guys forced it to work with smalltalk :) https://wiki.jenkins-ci.org/display/JENKINS/JSHint+Checkstyle+Plugin -- Best regards, Igor Stasenko.

May 16, 2013