Re: [Pharo-project] SqueakSource is unusable

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] SqueakSource is unusable

Michael Haupt-3
Hi,

why not just forward it to squeak-dev? Like this?

Best,

Michael ;-)

Am 10.04.2010 um 09:16 schrieb Stéphane Ducasse <[hidden email]
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
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] SqueakSource is unusable

Bert Freudenberg
Thanks.

I just merged the stuff I developed lately for our Squeak source server with Lukas' latest (lr.1038) and published back to the shared repository. But the new layout was not in there yet.

- Bert -


On 10.04.2010, at 10:17, Michael Haupt wrote:

>
> Hi,
>
> why not just forward it to squeak-dev? Like this?
>
> Best,
>
> Michael ;-)
>
> Am 10.04.2010 um 09:16 schrieb Stéphane Ducasse <[hidden email]>:
>
>> 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
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] SqueakSource is unusable

Lukas Renggli
> I just merged the stuff I developed lately for our Squeak source server with Lukas' latest (lr.1038) and published back to the shared repository. But the new layout was not in there yet.

Sorry, I did not commit my changes yet. I've done so now.

Pay attention there could be some www.squeaksource.com specific
modifications in the code.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch

Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] SqueakSource is unusable

stephane ducasse-2
In reply to this post by Bert Freudenberg

On Apr 10, 2010, at 7:16 PM, Bert Freudenberg wrote:

> Thanks.
>
> I just merged the stuff I developed lately

which is?

> for our Squeak source server with Lukas' latest (lr.1038) and published back to the shared repository. But the new layout was not in there yet.
>
> - Bert -


Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] SqueakSource is unusable

Bert Freudenberg
On 10.04.2010, at 21:19, stephane ducasse wrote:
>
>
> On Apr 10, 2010, at 7:16 PM, Bert Freudenberg wrote:
>
>> Thanks.
>>
>> I just merged the stuff I developed lately
>
> which is?

Most importantly, projects can have parent projects now (only if a site-wide setting is enabled). This is to support "inbox" style use - when mailing out diffs, the diff based is searched in a project's parent project too.

Also, you can enable developers to move versions, not just admins. This is a per-project setting, again to enable developers to clean out an "inbox" repository. There can also be a default target project for moves.

Since SSProject grew too many instance variables, I added a properties dictionary just like we have for versions and repositories. Refactoring might be in order but I just copied and pasted. Sorry ;)

There are a few minor changes, see the version history :)

- Bert -



Reply | Threaded
Open this post in threaded view
|

Re: SqueakSource is unusable

Bert Freudenberg
In reply to this post by Lukas Renggli
On 10.04.2010, at 19:45, Lukas Renggli wrote:
>
>> I just merged the stuff I developed lately for our Squeak source server with Lukas' latest (lr.1038) and published back to the shared repository. But the new layout was not in there yet.
>
> Sorry, I did not commit my changes yet. I've done so now.

Ah, thanks. Now source.squeak.org has a variable-width, layout, too. Nice :)

> Pay attention there could be some www.squeaksource.com specific
> modifications in the code.

Yes, listing the packages might not be the best for the trunk repo ... maybe if there are more than a handful packages they should be listed inline rather than as bullet list. Also, would be cool if the package names were clickable? Anyway, if I find the list too annoying I'll just add a setting ;)

I prefer to keep the code-base as close as possible. I just had not merged your stuff in a while because your package has dependencies (mine doesn't), and merging in MC tries to merge those too. I had to work around that, but now we're in sync again.

- Bert -



Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] SqueakSource is unusable

stephane ducasse-2
In reply to this post by Bert Freudenberg
thanks.
Yes cleaning.
I would like to have a move "Package and its dependents" (move all the versions of the package and all
its dependents versions...) in addition to what we have right now.


>>> Thanks.
>>>
>>> I just merged the stuff I developed lately
>>
>> which is?
>
> Most importantly, projects can have parent projects now (only if a site-wide setting is enabled). This is to support "inbox" style use - when mailing out diffs, the diff based is searched in a project's parent project too.
>
> Also, you can enable developers to move versions, not just admins. This is a per-project setting, again to enable developers to clean out an "inbox" repository. There can also be a default target project for moves.
>
> Since SSProject grew too many instance variables, I added a properties dictionary just like we have for versions and repositories. Refactoring might be in order but I just copied and pasted. Sorry ;)
>
> There are a few minor changes, see the version history :)
>
> - Bert -
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] SqueakSource is unusable

Igor Stasenko
On 11 April 2010 00:18, stephane ducasse <[hidden email]> wrote:
> thanks.

My thanks too. It is just GREAT improvement! Keep moving guys! :)

--
Best regards,
Igor Stasenko AKA sig.