- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Canvas transform bug when rendering text?

by Michael Rueger

On 4/10/2010 10:02 AM, Hilaire Fernandes wrote: > Does Polymoprh based on Rome is something making sense, or is it just > non-sense (ie not related). I try to understand what is the value behing > Rome. Rome (in this case especially Rome Cairo) brings true vector based drawing to Squeak/Pharo allowing for drawing with transformations and lossless scaling. Rome is also a framework to unify drawing using different backends, which right now isn't the case as the different Canvas classes support different protocols. Or even worse implement some calls differently. Most of the drawing code in Morphic would need to be rewritten though, so it isn't that simple a task. Michael

April 10, 2010

Re: [Pharo-project] SqueakSource is unusable

by Michael Haupt

Hi, why not just forward it to squeak-dev? Like this? Best, Michael ;-) Am 10.04.2010 um 09:16 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.f r>: > Thanks jason > > I do not know who is in charge of Squeak source nowadays. > Adrian lukas do you know it? > > Stef > > On Apr 10, 2010, at 6:38 AM, jaayer wrote: > >> or if not that, then nearly so. >> >> The biggest problem is the overall smallness of each page. The site >> is far too narrow and apparently was designed for monitors with >> 800x600 screen resolutions. This was unacceptable five years ago >> and is even more unacceptable now. Further, the fonts are tiny, and >> worse, they and almost every other sized property are specified >> using hard-coded pixel widths. For scalable, cross-platform design, >> percentages and em-widths should be preferred. Links should display >> some sort of text-decoration when moused-over so it is always clear >> which link will be selected when the user clicks, even when two or >> more links are especially close together. SqueakSource is, after >> the primary home pages, the public face of the Squeak and Pharo >> projects. It is crucial then that it look--if not great--at least >> decent. Enclosed is prettified CSS that fixes some of these >> defects. (Note that Image url() references need to be filled in, >> and it still probably needs some tweaking.) >> >> body { >> border:0; >> background:gray; >> text-align:center; >> margin:0; >> padding:10px; >> font-size:0.9em; >> } >> >> body,div,table,tr,td,th,form input,form submit { >> font-family:Geneva, Arial, Helvetica, sans-serif; >> } >> >> table,tr,td,th,form { >> border:0; >> margin:0; >> padding:0; >> } >> >> th { >> text-align:left; >> } >> >> a,a:visited { >> color:#360484; >> text-decoration:none; >> } >> >> a:hover,a:active { >> text-decoration:underline; >> } >> >> #container { >> width:90%; >> background:white url(/inserturl) repeat-y 4%; >> border:1px solid black; >> border-top:5px solid black; >> border-bottom:5px solid black; >> text-align:left; >> margin:auto; >> } >> >> #top { >> width:100%; >> height:50px; >> background:url(/inserturl) no-repeat; >> border-bottom:1px solid black; >> font-size:0.7em; >> text-align:right; >> } >> >> #sstoolbar { >> height:2em; >> border-bottom:1px solid black; >> background:white; >> } >> >> #sstoolbar a { >> display:block; >> float:left; >> margin-left:-1px; >> border-left:1px solid black; >> border-right:1px solid black; >> line-height:2em; >> height:2em; >> letter-spacing:1px; >> text-decoration:none; >> padding:0px 10px; >> } >> >> #sstoolbar a:hover,#sstoolbar a:active { >> background-color:#360484; >> color:white; >> text-decoration: none; >> } >> >> #page { >> padding:0; >> } >> >> #page td,#page th { >> padding-right:5px; >> vertical-align:top; >> } >> >> #navigation { >> float:left; >> width:12%; >> padding:0 10px 10px 10px; >> } >> >> #navigation .title { >> margin-top:11px; >> font-weight:bold; >> } >> >> #contents { >> width:70%; >> height:auto; >> text-align:justify; >> margin:0 0 0 16%; >> padding:5px 10px 10px; >> } >> >> #contents h1 { >> margin-top:0; >> font-size:20px; >> } >> >> #contents h2 { >> margin-bottom:5px; >> font-size:15px; >> } >> >> #contents h3 { >> margin-bottom:5px; >> font-size:13px; >> } >> >> #contents hr { >> border:none; >> border-bottom:1px dotted black; >> } >> >> #contents p { >> width:90%; >> } >> >> #bottom { >> padding-left:5px; >> padding-right:5px; >> clear:both; >> border-top:1px solid black; >> background:white; >> margin:0; >> } >> >> .TabSelected { >> background-color:#360484; >> color:white; >> width:95px; >> text-align:center; >> } >> >> .TabUnselected { >> background-color:#D0C4E2; >> width:95px; >> text-align:center; >> } >> >> .TabSpacer { >> width:5px; >> } >> >> .TabLine { >> background-color:#360484; >> } >> >> #batch { >> text-align:center; >> margin-top:8px; >> } >> >> .evenRow { >> background-color:#E7E1F0; >> } >> >> .largeLabel { >> width:120px; >> } >> >> .mediumLabel { >> width:100px; >> } >> >> .smallLabel { >> width:80px; >> } >> >> .activityTable { >> margin-left:auto; >> margin-right:auto; >> } >> >> #window-titlebar { >> background-color:#D0C4E2; >> margin-bottom:10px; >> width:100%; >> } >> >> #window-title { >> text-align:right; >> width:66%; >> } >> >> #window-close { >> text-align:right; >> } >> >> .column-choice select { >> min-width:15em; >> } >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 10, 2010

Re: [Pharo-project] Canvas transform bug when rendering text?

by Hilaire Fernandes

Michael Rueger a Ã©crit : > On 4/9/2010 11:42 PM, Chris Muller wrote: >> Thank you Henrik, it looks like a huge improvement! The attached >> screen shots help explain why I only said "improvement" instead of >> "perfect". Look at the color of my translucent morph when it is >> upright vs. rotated. The translucency is now preserved, which is > > With Freetype now being used for text rendering it might be possible to > do it right by performing a transformed rendering instead of rotating a > bitmap. > Actually a nasty surprise we had in the Sophie project when it turned > out that even Tweak only did the bitmap trick, but Rome came to the > rescue :-) > > Michael That's interesting. All efforts done in Sophie should not be lost, it would be a pitty. Does Polymoprh based on Rome is something making sense, or is it just non-sense (ie not related). I try to understand what is the value behing Rome. Hilaire

April 10, 2010

Re: [Pharo-project] SqueakSource is unusable

by StÃ©phane Ducasse

Thanks jason I do not know who is in charge of Squeak source nowadays. Adrian lukas do you know it? Stef On Apr 10, 2010, at 6:38 AM, jaayer wrote: > or if not that, then nearly so. > > The biggest problem is the overall smallness of each page. The site is far too narrow and apparently was designed for monitors with 800x600 screen resolutions. This was unacceptable five years ago and is even more unacceptable now. Further, the fonts are tiny, and worse, they and almost every other sized property are specified using hard-coded pixel widths. For scalable, cross-platform design, percentages and em-widths should be preferred. Links should display some sort of text-decoration when moused-over so it is always clear which link will be selected when the user clicks, even when two or more links are especially close together. SqueakSource is, after the primary home pages, the public face of the Squeak and Pharo projects. It is crucial then that it look--if not great--at least decent. Enclosed is prettified CSS that fixes some of these defects. (Note that Image url() references need to be filled in, and it still probably needs some tweaking.) > > body { > border:0; > background:gray; > text-align:center; > margin:0; > padding:10px; > font-size:0.9em; > } > > body,div,table,tr,td,th,form input,form submit { > font-family:Geneva, Arial, Helvetica, sans-serif; > } > > table,tr,td,th,form { > border:0; > margin:0; > padding:0; > } > > th { > text-align:left; > } > > a,a:visited { > color:#360484; > text-decoration:none; > } > > a:hover,a:active { > text-decoration:underline; > } > > #container { > width:90%; > background:white url(/inserturl) repeat-y 4%; > border:1px solid black; > border-top:5px solid black; > border-bottom:5px solid black; > text-align:left; > margin:auto; > } > > #top { > width:100%; > height:50px; > background:url(/inserturl) no-repeat; > border-bottom:1px solid black; > font-size:0.7em; > text-align:right; > } > > #sstoolbar { > height:2em; > border-bottom:1px solid black; > background:white; > } > > #sstoolbar a { > display:block; > float:left; > margin-left:-1px; > border-left:1px solid black; > border-right:1px solid black; > line-height:2em; > height:2em; > letter-spacing:1px; > text-decoration:none; > padding:0px 10px; > } > > #sstoolbar a:hover,#sstoolbar a:active { > background-color:#360484; > color:white; > text-decoration: none; > } > > #page { > padding:0; > } > > #page td,#page th { > padding-right:5px; > vertical-align:top; > } > > #navigation { > float:left; > width:12%; > padding:0 10px 10px 10px; > } > > #navigation .title { > margin-top:11px; > font-weight:bold; > } > > #contents { > width:70%; > height:auto; > text-align:justify; > margin:0 0 0 16%; > padding:5px 10px 10px; > } > > #contents h1 { > margin-top:0; > font-size:20px; > } > > #contents h2 { > margin-bottom:5px; > font-size:15px; > } > > #contents h3 { > margin-bottom:5px; > font-size:13px; > } > > #contents hr { > border:none; > border-bottom:1px dotted black; > } > > #contents p { > width:90%; > } > > #bottom { > padding-left:5px; > padding-right:5px; > clear:both; > border-top:1px solid black; > background:white; > margin:0; > } > > .TabSelected { > background-color:#360484; > color:white; > width:95px; > text-align:center; > } > > .TabUnselected { > background-color:#D0C4E2; > width:95px; > text-align:center; > } > > .TabSpacer { > width:5px; > } > > .TabLine { > background-color:#360484; > } > > #batch { > text-align:center; > margin-top:8px; > } > > .evenRow { > background-color:#E7E1F0; > } > > .largeLabel { > width:120px; > } > > .mediumLabel { > width:100px; > } > > .smallLabel { > width:80px; > } > > .activityTable { > margin-left:auto; > margin-right:auto; > } > > #window-titlebar { > background-color:#D0C4E2; > margin-bottom:10px; > width:100%; > } > > #window-title { > text-align:right; > width:66%; > } > > #window-close { > text-align:right; > } > > .column-choice select { > min-width:15em; > } > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 10, 2010

Re: [Pharo-project] Canvas transform bug when rendering text?

by Michael Rueger

On 4/9/2010 11:42 PM, Chris Muller wrote: > Thank you Henrik, it looks like a huge improvement! The attached > screen shots help explain why I only said "improvement" instead of > "perfect". Look at the color of my translucent morph when it is > upright vs. rotated. The translucency is now preserved, which is With Freetype now being used for text rendering it might be possible to do it right by performing a transformed rendering instead of rotating a bitmap. Actually a nasty surprise we had in the Sophie project when it turned out that even Tweak only did the bitmap trick, but Rome came to the rescue :-) Michael

April 10, 2010

[Pharo-project] SqueakSource is unusable

by jaayer

or if not that, then nearly so. The biggest problem is the overall smallness of each page. The site is far too narrow and apparently was designed for monitors with 800x600 screen resolutions. This was unacceptable five years ago and is even more unacceptable now. Further, the fonts are tiny, and worse, they and almost every other sized property are specified using hard-coded pixel widths. For scalable, cross-platform design, percentages and em-widths should be preferred. Links should display some sort of text-decoration when moused-over so it is always clear which link will be selected when the user clicks, even when two or more links are especially close together. SqueakSource is, after the primary home pages, the public face of the Squeak and Pharo projects. It is crucial then that it look--if not great--at least decent. Enclosed is prettified CSS that fixes some of these defects. (Note that Image url() references need to be filled in, and it still probably needs some tweaking.) body { border:0; background:gray; text-align:center; margin:0; padding:10px; font-size:0.9em; } body,div,table,tr,td,th,form input,form submit { font-family:Geneva, Arial, Helvetica, sans-serif; } table,tr,td,th,form { border:0; margin:0; padding:0; } th { text-align:left; } a,a:visited { color:#360484; text-decoration:none; } a:hover,a:active { text-decoration:underline; } #container { width:90%; background:white url(/inserturl) repeat-y 4%; border:1px solid black; border-top:5px solid black; border-bottom:5px solid black; text-align:left; margin:auto; } #top { width:100%; height:50px; background:url(/inserturl) no-repeat; border-bottom:1px solid black; font-size:0.7em; text-align:right; } #sstoolbar { height:2em; border-bottom:1px solid black; background:white; } #sstoolbar a { display:block; float:left; margin-left:-1px; border-left:1px solid black; border-right:1px solid black; line-height:2em; height:2em; letter-spacing:1px; text-decoration:none; padding:0px 10px; } #sstoolbar a:hover,#sstoolbar a:active { background-color:#360484; color:white; text-decoration: none; } #page { padding:0; } #page td,#page th { padding-right:5px; vertical-align:top; } #navigation { float:left; width:12%; padding:0 10px 10px 10px; } #navigation .title { margin-top:11px; font-weight:bold; } #contents { width:70%; height:auto; text-align:justify; margin:0 0 0 16%; padding:5px 10px 10px; } #contents h1 { margin-top:0; font-size:20px; } #contents h2 { margin-bottom:5px; font-size:15px; } #contents h3 { margin-bottom:5px; font-size:13px; } #contents hr { border:none; border-bottom:1px dotted black; } #contents p { width:90%; } #bottom { padding-left:5px; padding-right:5px; clear:both; border-top:1px solid black; background:white; margin:0; } .TabSelected { background-color:#360484; color:white; width:95px; text-align:center; } .TabUnselected { background-color:#D0C4E2; width:95px; text-align:center; } .TabSpacer { width:5px; } .TabLine { background-color:#360484; } #batch { text-align:center; margin-top:8px; } .evenRow { background-color:#E7E1F0; } .largeLabel { width:120px; } .mediumLabel { width:100px; } .smallLabel { width:80px; } .activityTable { margin-left:auto; margin-right:auto; } #window-titlebar { background-color:#D0C4E2; margin-bottom:10px; width:100%; } #window-title { text-align:right; width:66%; } #window-close { text-align:right; } .column-choice select { min-width:15em; }

April 10, 2010

Re: [Pharo-project] potential bugfix for orphan OCompletion menus

by Henrik Sperre Johansen

On 10.04.2010 02:21, Alexandre Bergel wrote: > Yes, the window announcements are in 1.1 > > Alexandre Doh, I didn't notice they'd been integrated! :D

April 10, 2010

Re: [Pharo-project] potential bugfix for orphan OCompletion menus

by Henrik Sperre Johansen

On 10.04.2010 01:51, Romain Robbes wrote: > Thanks! > > So that would be for the Pharo 1.1 version, I suppose? > > Romain Hopefully, yes :) Personally I find it the most annoying things in rc4 to be: 1 it doesn't close immediately when a) I mouseclick another location in the text (only when I type something) b) change focus to another window 2 It does not update the list location when a) I've mouse-clicked another place in the morph and started typing again. b) I've moved/resized the editor 3) It takes ~ 0.5 -1 second to update if I press down, and on each character typed thereafter with items still in list (Te - down - s - t, s and t take some time to input) 4) Mouse-click on a list item does not select it. 1 is somewhat remedied by the patch I guess, for the rest I guess 2 and 4 should solvable by additional logic, and 3 would require some profiling. 1b and 2a in combination is quite annoying, as the list will be below the morph when you refocus, and in many cases you will be able to see suggestions for the new location. (1/2 b would also be easy to solve with window announcements) In essence, I feel it still could use some improvement with regards to awareness of mouse activity and multiple editors. Cheers, Henry

April 10, 2010

Re: [Pharo-project] potential bugfix for orphan OCompletion menus

by Alexandre Bergel

Yes, the window announcements are in 1.1 Alexandre On 9 Apr 2010, at 19:51, Romain Robbes wrote: > Thanks! > > So that would be for the Pharo 1.1 version, I suppose? > > Romain > > On Apr 9, 2010, at 7:46 PM, Henrik Sperre Johansen wrote: > >> On 10.04.2010 01:35, Romain Robbes wrote: >>> >>> Hi Mariano, >>> >>> I couldn't find a better way. The model has to be notified that >>> the system window closes, and so far I haven't found where that is >>> done (if at all). >>> Of course, I'll be glad to be enlightened on that issue :-). >>> >>> Cheers, >>> Romain >>> >>> >>> >> With the Window Announcements Alexandre made, you could. >> Those are not in core yet, though, and the fix would not work >> elsewhere. (Found in Morphic package in PharoTaskForces on >> squeaksource) >> You'd probably want support for weak announcements/variable >> annoucement args first as well, as unsubscribing whenever an >> OCompletion morph is closed would be somewhat of an exercise >> otherwise. >> >> Cheers, >> Henry >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Romain Robbes > http://romain.robb.es > rrobbes(a)dcc.uchile.cl > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 10, 2010

Re: [Pharo-project] potential bugfix for orphan OCompletion menus

by Alexandre Bergel

I was about to say this. Alexandre On 9 Apr 2010, at 19:46, Henrik Sperre Johansen wrote: > On 10.04.2010 01:35, Romain Robbes wrote: >> >> Hi Mariano, >> >> I couldn't find a better way. The model has to be notified that the >> system window closes, and so far I haven't found where that is done >> (if at all). >> Of course, I'll be glad to be enlightened on that issue :-). >> >> Cheers, >> Romain >> >> >> > With the Window Announcements Alexandre made, you could. > Those are not in core yet, though, and the fix would not work > elsewhere. (Found in Morphic package in PharoTaskForces on > squeaksource) > You'd probably want support for weak announcements/variable > annoucement args first as well, as unsubscribing whenever an > OCompletion morph is closed would be somewhat of an exercise > otherwise. > > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 10, 2010