April 2010 - Pharo-dev - lists.pharo.org

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

by Michael Rueger

On 4/10/2010 10:51 AM, Hilaire Fernandes wrote: > Michael Rueger a Ã©crit : >> On 4/10/2010 10:31 AM, Hilaire Fernandes wrote: >> >>> Will it allow us to have vector based UI element or is non sense? >> >> No, not non sense :-), that is exactly what it would allow. > > Yes, vector based UI is where we should move to keep in the course. > Is it what you did for Sophie? If so, did you use some bitmap caching > technic? Tweak does (or did back then) some caching. You have to be careful though with caching, as you might end up copying a lot of bits around even if caching doesn't really make sense for your particular application. IIRC (it's been a while) in Tweak you first draw to the cache, then the cache is drawn to the Squeak Display bitmap and then that is drawn to the screen. No great when you are playing e.g. a video. Michael

April 10, 2010

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

by Hilaire Fernandes

Michael Rueger a Ã©crit : > On 4/10/2010 10:31 AM, Hilaire Fernandes wrote: > >> Will it allow us to have vector based UI element or is non sense? > > No, not non sense :-), that is exactly what it would allow. Yes, vector based UI is where we should move to keep in the course. Is it what you did for Sophie? If so, did you use some bitmap caching technic?

April 10, 2010

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

by Michael Rueger

On 4/10/2010 10:31 AM, Hilaire Fernandes wrote: > Is it correct to say a well integrated Rome Cairo framework in Moprhic > could simplify the whole graphic framework of the system. Yes it should. Alain did some work with Rome in Miro, so he might have more experience with it. > Will it allow us to have vector based UI element or is non sense? No, not non sense :-), that is exactly what it would allow. Michael

April 10, 2010

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

by Hilaire Fernandes

Is it correct to say a well integrated Rome Cairo framework in Moprhic could simplify the whole graphic framework of the system. Will it allow us to have vector based UI element or is non sense? Hilaire Michael Rueger a Ã©crit : > 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.

April 10, 2010

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