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

Re: [Pharo-dev] 50378 -> builds need to be redone?

by Stephan Eggermont

On 10-10-15 20:41, stepharo wrote: > Hi stefan > > could you open a bug entry and publish a merge? > We participated to an hackaton with esteban, pablo, kevin and cyril and we > are not really happy about the tools, the frameworks... > :( I can fix those. How do I check for (partially?) missing source code? Stephan

Oct. 10, 2015

Re: [Pharo-dev] 50378 -> builds need to be redone?

by stepharo

Hi stefan could you open a bug entry and publish a merge? We participated to an hackaton with esteban, pablo, kevin and cyril and we are not really happy about the tools, the frameworks... :( Le 10/10/15 10:38, Stephan Eggermont a Ã©crit : > On 10-10-15 10:28, Stephan Eggermont wrote: >> >> RubFloatingEditorBuilder>>whenReturnEntered: anAnnouncement >> >> RubFloatingEditorBuilder class>>exampleCommandLauncher >> >> RubFloatingEditorBuilder class>>exampleEditableStringMorph >> > > In Inbox theer are two 285s, and changes from Alain were not merged > > Stephan > > >

Oct. 10, 2015

Re: [Pharo-dev] [Moose-dev] Re: Roassal3D is moving...

by Yuriy Tymchuk

I do not remember the causes under first question. Something was broken and some layouts were not working. Iâve made a heavy usage of classes that align all elements alone some pane, and they were removed from RoassalWoden, so I have to add them as my own classes. Also Iâve added a lot of helper methods to the bounding box class, like getting its corrections. Secondly itâs not really an issue of Woden but more of the way Iâve designed ViDI. There is actually no such thing as a âcity layoutâ. If you take a look at the latest CodeCity by Ricky, there are plenty layouts (like rectangle packing, grid, wall, stack) and a nice way to compost them. Now besides having this functionality I also wanted to be able to dynamically change the view i.e. method getâs deleted, visualization is re-layedout. Thatâs why I have a custom âBuildingâ classes, that know their bricks (methods) and can lay them out and inform the parent container if the bonds were changed. The point is that ViDI should not be restricted only to 3D so I donât want to code all the re-layout logic into 3D subclasses. I think that at the moment I can just port orbiting controls to the old Roassal3D. Maybe in the future I will have time to create ViDI v2. Or maybe Iâll find a student willing to do that :) Uko > On 10 Oct 2015, at 13:18, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Yes, I would like to understand why you cannot migrate to woden > Alexandre > > Le 10 oct. 2015 Ã 04:55, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> a Ã©crit : > >> >> >> Le 9/10/15 19:59, Yuriy Tymchuk a Ã©crit : >>> 2 reasons: >>> >>> 1) something is always incompatible (Iâve tried 2 times already) >>> 2) I have too many things hardcoded in Roassal3D subclasses. I have to move it into a proper model, and this will take time. >> >> >> Alex you should have a look at the missing hooks mentioned by Yuriy because I'm quite sure that other >> people will have the same problems and this is not good to duplicate effort. >> >> Yiriy can you point alex to the hardcoded points? >> >>> >>> Iâll take a look at the Orbiter. Although as far as I remember Roassal3D and Woden have different interfaces. >>> >>> Cheers. >>> Uko >>> >>> >>>> On 09 Oct 2015, at 19:54, Alexandre Bergel < <mailto:alexandre.bergel@me.com>alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>>> >>>> Ah sorry. >>>> Teseo has written the class OrbitController. I think you should be able to reuse it for Roassal3d Old. But why not trying to migrate to Woden instead? >>>> >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>>> On Oct 9, 2015, at 2:15 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >>>>> >>>>> No, the control the interaction that moves you around the object when you drag mouse instead of "rotating your headâ as in fps game. >>>>> >>>>> Uko >>>>> >>>>> >>>>>> On 09 Oct 2015, at 19:11, Alexandre Bergel < <mailto:alexandre.bergel@me.com>alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>>>>> >>>>>> By flyover you mean having a text tooltip? >>>>>> >>>>>> Alexandre >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel <http://www.bergel.eu/>http://www.bergel.eu <http://www.bergel.eu/> >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>>> On Oct 9, 2015, at 12:40 PM, Yuriy Tymchuk < <mailto:yuriy.tymchuk@me.com>yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >>>>>>> >>>>>>> No, honestly Iâd really appreciate if someone can help me to add this flyover interaction to ViDI, so we can run some kind of controlled experiment on it (and for now itâs not an option to move ViDI to Woden). >>>>>> >>>>>> _______________________________________________ >>>>>> Moose-dev mailing list >>>>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >>

Oct. 10, 2015

Re: [Pharo-dev] [Moose-dev] Re: Roassal3D is moving...

by Alexandre Bergel

Yes, I would like to understand why you cannot migrate to woden Alexandre > Le 10 oct. 2015 Ã 04:55, stepharo <stepharo(a)free.fr> a Ã©crit : > > > > Le 9/10/15 19:59, Yuriy Tymchuk a Ã©crit : >> 2 reasons: >> >> 1) something is always incompatible (Iâve tried 2 times already) >> 2) I have too many things hardcoded in Roassal3D subclasses. I have to move it into a proper model, and this will take time. > > > Alex you should have a look at the missing hooks mentioned by Yuriy because I'm quite sure that other > people will have the same problems and this is not good to duplicate effort. > > Yiriy can you point alex to the hardcoded points? > >> >> Iâll take a look at the Orbiter. Although as far as I remember Roassal3D and Woden have different interfaces. >> >> Cheers. >> Uko >> >> >>> On 09 Oct 2015, at 19:54, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> >>> Ah sorry. >>> Teseo has written the class OrbitController. I think you should be able to reuse it for Roassal3d Old. But why not trying to migrate to Woden instead? >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On Oct 9, 2015, at 2:15 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> >>>> No, the control the interaction that moves you around the object when you drag mouse instead of "rotating your headâ as in fps game. >>>> >>>> Uko >>>> >>>> >>>>> On 09 Oct 2015, at 19:11, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> >>>>> By flyover you mean having a text tooltip? >>>>> >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>>> On Oct 9, 2015, at 12:40 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>>> >>>>>> No, honestly Iâd really appreciate if someone can help me to add this flyover interaction to ViDI, so we can run some kind of controlled experiment on it (and for now itâs not an option to move ViDI to Woden). >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

Oct. 10, 2015

Re: [Pharo-dev] 50378 -> builds need to be redone?

by Stephan Eggermont

On 10-10-15 10:28, Stephan Eggermont wrote: > > RubFloatingEditorBuilder>>whenReturnEntered: anAnnouncement > > RubFloatingEditorBuilder class>>exampleCommandLauncher > > RubFloatingEditorBuilder class>>exampleEditableStringMorph > In Inbox theer are two 285s, and changes from Alain were not merged Stephan

Oct. 10, 2015

50378 -> builds need to be redone?

by Stephan Eggermont

RubFloatingEditorBuilder>>whenReturnEntered: anAnnouncement RubFloatingEditorBuilder class>>exampleCommandLauncher RubFloatingEditorBuilder class>>exampleEditableStringMorph

Oct. 10, 2015

Re: [Pharo-dev] [Moose-dev] Re: Roassal3D is moving...

by stepharo

Le 9/10/15 19:59, Yuriy Tymchuk a Ã©crit : > 2 reasons: > > 1) something is always incompatible (Iâve tried 2 times already) > 2) I have too many things hardcoded in Roassal3D subclasses. I have to > move it into a proper model, and this will take time. Alex you should have a look at the missing hooks mentioned by Yuriy because I'm quite sure that other people will have the same problems and this is not good to duplicate effort. Yiriy can you point alex to the hardcoded points? > > Iâll take a look at the Orbiter. Although as far as I remember > Roassal3D and Woden have different interfaces. > > Cheers. > Uko > > >> On 09 Oct 2015, at 19:54, Alexandre Bergel <alexandre.bergel(a)me.com >> <mailto:alexandre.bergel@me.com>> wrote: >> >> Ah sorry. >> Teseo has written the class OrbitController. I think you should be >> able to reuse it for Roassal3d Old. But why not trying to migrate to >> Woden instead? >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Oct 9, 2015, at 2:15 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com >>> <mailto:yuriy.tymchuk@me.com>> wrote: >>> >>> No, the control the interaction that moves you around the object >>> when you drag mouse instead of "rotating your headâ as in fps game. >>> >>> Uko >>> >>> >>>> On 09 Oct 2015, at 19:11, Alexandre Bergel <alexandre.bergel(a)me.com >>>> <mailto:alexandre.bergel@me.com>> wrote: >>>> >>>> By flyover you mean having a text tooltip? >>>> >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>>> On Oct 9, 2015, at 12:40 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com >>>>> <mailto:yuriy.tymchuk@me.com>> wrote: >>>>> >>>>> No, honestly Iâd really appreciate if someone can help me to add >>>>> this flyover interaction to ViDI, so we can run some kind of >>>>> controlled experiment on it (and for now itâs not an option to >>>>> move ViDI to Woden). >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

Oct. 10, 2015

Re: [Pharo-dev] Smalltalkhub instable

by stepharo

do we have a document to show how to do such reboot? Le 7/10/15 16:55, Marcus Denker a Ã©crit : > >> On 07 Oct 2015, at 15:47, Blondeau Vincent >> <vincent.blondeau(a)worldline.com >> <mailto:vincent.blondeau@worldline.com>> wrote: >> >> Hi, >> It is very hard to work because Smalltalkhub is very instable today. >> I wanted to launchhttps://ci.inria.fr/moose/job/moose-6.0but I get >> either an 400 or 500 errorâ¦ (It seems to work now but for how long?) >> Can somebody could look at this issue ? > I restarted apacheâ¦which seems to be the source of the problem when > loading static files makes problems. > > Marcus >

Oct. 10, 2015

50378 broke source

by Stephan Eggermont

I found it in 50379, but it was introduced in 50378. 50377 looks ok. The FTSearch is fixed in 50380 RubFloatingEditorBuilder>>whenReturnEntered: anAnnouncement RubFloatingEditorBuilder class>>exampleCommandLauncher RubFloatingEditorBuilder class>>exampleEditableStringMorph Stephan

Oct. 9, 2015

Re: [Pharo-dev] Yet another Athens font thread

by Aliaksei Syrel

No, they are needed. Because glyphs must be calculated (getGlyphs:of:) after(!) setting font size. Otherwise there are huge gaps between characters. When font problem appears, some characters are of size 14 even if font size 10. So glyphs of big characters have larger extent as it should be. In your example you set font size and fix font, so all characters are rendered correctly, but at wrong positions. That is a source of unnecessary gaps. Thete is a way to break font: 1) Get new pharo image 2) Get Bloc 3) Switch to bloc 4) remove all morphs 5) save and quite 6) open image 7) open nautilus Do something to fix font. Repeat 4-7. If fix is "fake" fonts will be broken.. On Oct 9, 2015 10:31 PM, "Nicolai Hess" <nicolaihess(a)web.de> wrote: > > > 2015-10-08 18:05 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > >> Do you remember a hack with scaling? (scaleBy: 1.0001(a)1.0001) It makes >> letters to have the same height, so no more huge ones with small fonts. But >> it doesn't fix a bug when letters have wrong width so there is a space >> between characters. The same effect can be achieved if we set font size >> manually after setting scaled font before drawing glyphs with cairo. It >> means that at some point we get wrong calculated glyphs. So if we "fix" >> scaled font before glyph calculation - the problem would be gone. In the >> patch I set scaled font, manually apply font size, retrieve "fixed" scaled >> font and calculate glyphs based on it. >> >> Also after investigation I found something interesting. If we clean real >> font of a logical font the problem gets fixed for some period of time. I >> assume that FreeTypeFont gets broken after a while and logical font always >> returns broken real font. Setting realFont to nil forces logical font to >> create a new working free type font. As soon as new free type font is >> created cairo produces scaled font and caches it. So actual problem lies >> deep in FreeTypeFont... >> >> I even opened two images: one with broken fonts and one with working. >> Then I compared in inspector two free type fonts - they are absolutely the >> same and have identical instance variable in a whole object tree, except of >> handler pointers to C structure which I can't inspect from pharo... >> >> Saving image fixes fonts because of >> >>> LogicalFont>>shutDown: quitting >>> self allSubInstances do: [:i | i clearRealFont]. >> >> >> Cheers, >> Alex >> > > This is great. > > I looked at your change. And noticed the call to > setFontSize > this was never called until now. Maybe this was the problem. > > Now, I just changed > > renderGlyphs: cairoGlyphs > > font lock. > canvas > setPathMatrix; > setScaledFont: font; > setFontSize: originalFont pixelSize. "<< new " > canvas paint loadOnCairoCanvas: canvas. > > canvas showGlyphs: cairoGlyphs address size: cairoGlyphs size. > font unlock. > > And it seems the font issue is gone. Maybe the other changes (set and get > scaled font in #glyphsOf:from:to: ) > isn't needed? (needs more tests) > > > >> On Thu, Oct 8, 2015 at 5:43 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> How did you fix it? >>> Am 08.10.2015 17:06 schrieb "Aliaksei Syrel" <alex.syrel(a)gmail.com>: >>> >>>> Hi >>>> >>>> It looks like I fixed that weird text rendering problem... Just get the >>>> latest Athens-Cairo. >>>> >>>> Cheers, >>>> Alex >>>> >>>> On Mon, Aug 3, 2015 at 9:32 PM, Nicolai Hess <nicolaihess(a)web.de> >>>> wrote: >>>> >>>>> >>>>> >>>>> 2015-06-10 12:01 GMT+02:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >>>>> >>>>>> Hi >>>>>> >>>>>> I noticed that if I force use "Source Code Pro" as standard font for >>>>>> all elements in the image I never have problems with font rendering. In >>>>>> case of "Source Sans Pro" font is just not usable becasue of rendering bugs >>>>>> on mac, windows and linux(?). If "Lucida Sans Pro" is used - no bugs too. >>>>>> >>>>>> Because bug is reproducable on all platform - it's platform >>>>>> independent bug. >>>>>> Because it's reproducable only with one specific font - maybe it's >>>>>> not an athens issue but bug in font itself and if someone could >>>>>> change/update Source Sans Pro to a newly version or to a similar font the >>>>>> problem will be solved? >>>>>> >>>>> >>>>> Did you try to use a new font version ? >>>>> I don't know exactly how embedded fonts are included. I tried to >>>>> create the font with a newer version but it did not work ( or at least I >>>>> could not see any difference). >>>>> >>>>> >>>>> >>>>>> >>>>>> Cheers, >>>>>> Alex >>>>>> >>>>> >>>>> >>>> >> >

Oct. 9, 2015