Re: [pygtk] Re: pygtk.org mockup
Panos Laganakos wrote: http://panos.solhost.org/pygtk/ Alright everything should be looking fine now. I've moved all the pages to the new template layout, except "screenshots" section. If we are to keep this, I think we could use some new screenshots. If someone would be willing to take some it'd be great - if we are to keep this section. Gustavo: The header now behaves as a link to the index. mc/others: I changed the way fonts are defined. I hope its Ok now. I think we're almost ready to upload to the main site. Lemme know if we need anything else. It's great except the date/author line is still not readable. It would really be much better if the text color was a darker gray or other color to provide more contrast. John ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
2006/7/30, Panos Laganakos <[EMAIL PROTECTED]>: http://panos.solhost.org/pygtk/ Alright everything should be looking fine now. I've moved all the pages to the new template layout, except "screenshots" section. If we are to keep this, I think we could use some new screenshots. If someone would be willing to take some it'd be great - if we are to keep this section. Everything looks fine except the "learn more" box where the text overlaps the picture. see enclosed image. With firefox 1.5.0.5 on ubuntu. ciao -- Gian Mario Tagliaretti http://www.parafernalia.org/pygtk/ http://pygstdocs.berlios.de learn_more.png Description: PNG image ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
What's the meaning of the little house in the footer of the page? -- Lawrence http://www.oluyede.org/blog ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
http://panos.solhost.org/pygtk/ Alright everything should be looking fine now. I've moved all the pages to the new template layout, except "screenshots" section. If we are to keep this, I think we could use some new screenshots. If someone would be willing to take some it'd be great - if we are to keep this section. Gustavo: The header now behaves as a link to the index. mc/others: I changed the way fonts are defined. I hope its Ok now. I think we're almost ready to upload to the main site. Lemme know if we need anything else. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Hello, I want very hard this site stay readable for me (and other tired
eyes), so I have play with your css. only a few changes.
It seems respect your mind...
--
Marie-Claude Collilieux
Bretagne
/* changed only all font-size in % and add font-family "bitstream vera sans" behind Arial */
/* {{{ License
*
* This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike
* 2.5 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/2.5/
* or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco,
* California, 94105, USA.
*
* Copyright: Panos Laganakos.
*
* }}} */
/* {{{ Basic Elements */
body {
margin: 0em;
padding: 0em;
font: 100% Arial, "bitstream vera sans", sans-serif;
}
h2 {
margin: 0em 0em 0em 0em;
padding: 0em 0em 0.4em 0em;
font-weight: bold;
font-size: 260%;
color: #3465a4;
}
h3 {
font-size: 110%;
font-weight: bold;
margin: 0em 0em 0.2em 0em;
}
p.note {
line-height: 145%;
background: #8AE234;
border: 2px solid #73D216;
border-left: 12px solid #73D216;
padding: 1.1em;
margin: 0em 8em 3em 0em;
}
span.date {
display: block;
color: #babdb6;
text-align: right;
margin: 1em 0em 0em 0em;
padding: 0em;
}
span.rss {
visibility: hidden;
}
a.rss {
background: url(./img/img/rss-icon.png) no-repeat;
text-decoration: none;
}
div.newsentry {
border-left: 12px solid #EC;
margin: 0em 0em 3em 0em;
padding: 0em 0em 0em 1.5em;
}
div.developer {
margin: 0em 0em 5em 0em;
padding: 0em 0em 0em 5em;
background: url(./img/face-monkey.png) no-repeat left center;
}
p#boxed {
font-size: 120%;
font-weight: bold;
float: right;
background: #8AE234 url(./img/text-x-generic.png) no-repeat center top;
padding: 3.0em 1em 0em 1em;
margin: 0em;
text-align: center;
line-height: 120%;
}
/* }}} */
/* {{{ Divisions */
#header {
background: #3465A4;
padding: 1.5em 1.5em 0.8em 1em;
margin: 0em;
}
#header h1 {
height: 56px;
background: url(./img/logo.png) center right no-repeat;
padding: 0em;
margin: 0em;
}
#header span {
display: none;
}
#menubar {
background: #729FCF;
text-align: right;
padding: 0em;
margin: 0em;
}
#menubar ul {
padding: 0em;
margin: 0em;
list-style-type: none;
}
#menubar a {
font-size: 130%;
font-weight: bold;
text-decoration: none;
width: 10em;
color: #FF;
padding: 0em 1em 0em 1em;
margin: 0em;
}
#menubar a:hover {
background-color: #3465A4;
}
#menubar li {
display: inline;
padding: 0.1em 0em 0.1em 0em;
margin: 0em;
}
#container {
padding: 2em 2em 1em 2em;
margin: 0em 0em 2em 0em;
}
#leftmenu {
float: left;
padding: 0.5em 1em 0em 1em;
background: #EC;
border-top: 2px solid #D3D7CF;
border-bottom: 2px solid #D3D7CF;
}
#leftmenu h2 {
font-weight: bold;
font-size: 110%;
color: #555753;
text-align: center;
}
#leftmenu h3 {
font-weight: bold;
font-size: 400%;
color: #D3D7CF;
text-align: right;
margin-top: 2em;
}
#leftmenu ul {
list-style-type: none;
padding: 0.5em 0em 0.5em 0em;
margin: 0em;
}
#leftmenu li {
border-left: 2px solid #D3D7CF;
}
#leftmenu li:hover {
background-color: #D3D7CF;
}
#leftmenu a {
color: #555753;
display: block;
font-weight: bold;
text-decoration: none;
padding: 0.2em 0.2em 0.2em 1em;
}
#content {
padding: 0em;
margin: 0em 0em 0em 13.5em;
}
#content h2 {
}
#content h2 a {
background: url(./img/rss-icon.png) no-repeat center right;
height: 32px;
}
#content span.heading {
display: none;
}
#footer {
background: #EC;
min-height: 2em;
margin: 0em;
padding: 0.9em 0em 0em 0em;
clear: both;
}
#footer p {
font: bold 100% Arial,"bitstream vera sans";
color: #BABDB6;
text-align: center;
padding: 0em;
margin: 0em;
}
#baseprojects {
position: absolute;
background: url(./img/a.png) no-repeat;
width: 117px;
height: 49px;
top: 3.5em;
left: 43px;
margin: 0em;
padding: 0.5em 1.2em 0.5em 1.2em;
}
#baseprojects a {
width: 2em;
padding: 0.3em;
}
p.pageicon {
height: 48px;
margin-left: 4em;
}
p.pageicon span {
display: none;
}
#home {
background: url(./img/go-home.png) no-repeat;
}
#documentation {
background: url(./img/go-home.png) no-repeat;
}
#james-henstridge {
margin: 0em 0em 5em 0em;
padding: 0em 0em 0em 5em;
background: url(./img/face-devil-grin.png) no-repeat left center;
}
#articles {
width: 100%;
}
#articles thead {
background: #729FCF;
}
#articles td {
padding: 0.5em;
}
#articles tr.row2 {
background: #EC;
}
/* }}} */
___
pygtk mailing list pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Panos Laganakos wrote:
Hello, i have look at your page and it's nice but please, think it can
be more nice for old eyes with a simple :
body {
margin: 0em;
padding: 0em;
font: 1em Arial, sans-serif;
}
font 1em and not size in pt, and firefox adjust real size with my view.
Thanks
Marie: Haven't applied this yet, I'm thinking on how to do it properly.
Stay tuned.
Oh thanks and I am sorry having write to your mail instead of on the
list, it is error of night !
--
Marie-Claude Collilieux
Bretagne
___
pygtk mailing list pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Preben Randhol wrote: > On Fri, 28 Jul 2006 01:36:07 +0300 > "Panos Laganakos" <[EMAIL PROTECTED]> wrote: > >> http://panos.solhost.org/pygtk/ >> > > Look nice, but I don't understand why there is the Gnome foot? GTK > doesn't have anything to do with Gnome. Shouldn't it rather be the gtk That's plainly wrong. GTK is very closely tied to the Gnome project, schedule, financial support, legal, infrastructure etc etc. -- Johan Dahlin <[EMAIL PROTECTED]> Async Open Source ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On Sex, 2006-07-28 at 15:31 +0200, Preben Randhol wrote: > On Fri, 28 Jul 2006 01:36:07 +0300 > "Panos Laganakos" <[EMAIL PROTECTED]> wrote: > > > http://panos.solhost.org/pygtk/ > > > > Look nice, but I don't understand why there is the Gnome foot? > GTK doesn't have anything to do with Gnome. I disagree. Besides, pygtk.org is also home for GnomePython*, not just PyGTK. -- Gustavo J. A. M. Carneiro <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> The universe is always one step beyond logic. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On Fri, 28 Jul 2006 01:36:07 +0300 "Panos Laganakos" <[EMAIL PROTECTED]> wrote: > http://panos.solhost.org/pygtk/ > Look nice, but I don't understand why there is the Gnome foot? GTK doesn't have anything to do with Gnome. Shouldn't it rather be the gtk logo (although it would be nice to skip both and just keep the python logo) Regards, Preben ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
I'd like to suggest making the big 'PyGTK' word at the top right a link to the home page. I know there is already a 'Home' link but most users (including me) always expect the title of the site to be a link to the home page. Lorenzo: I'm using the FIR technique for most of the image displaying. One of the benefits is, that if the browser doesn't support CSS, the visitor will still get the text. ie: If on Firefox, try View->Page Style->No Style You'll still get a nice PyGTK header which is a link as you suggested. I'm gonna try to find a work around to make the bounding box linkable. Uploaded the latest version of the generated site. 90% of the links is functional and the style is almost done. I licensed the style under CC Attribution-NonCommercial-ShareAlike. Andi: It tutorial/reference looks great. I'll break the CSS down into more specific files so you can just use the base one (without the pageicon images and table stuff). ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
I'd like to suggest making the big 'PyGTK' word at the top right a link to the home page. I know there is already a 'Home' link but most users (including me) always expect the title of the site to be a link to the home page. Just my .2 cents Lorenzo El vie, 28-07-2006 a las 01:36 +0300, Panos Laganakos escribió: > http://panos.solhost.org/pygtk/ > > Moved some more templates to the new theme. > > Christian: Check this sidebar. I made it a bit smaller and expanded > the content region. Removed the left/right borders to make it feel > less intruding on the horizontal space. > ___ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Hi, first of all, congratulations for the new theme. It looks great! I've made some additions to the XSL to make the reference and the tutorial fit into the new layout. Obviously this needs some fine tuning but it looks pretty good so far. Reference: http://www.andialbrecht.de/pygtk2reference/ Tutorial: http://www.andialbrecht.de/pygtk2tutorial/ Andi Am Freitag, den 28.07.2006, 01:36 +0300 schrieb Panos Laganakos: > http://panos.solhost.org/pygtk/ > > Moved some more templates to the new theme. > > Christian: Check this sidebar. I made it a bit smaller and expanded > the content region. Removed the left/right borders to make it feel > less intruding on the horizontal space. > ___ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
http://panos.solhost.org/pygtk/ Moved some more templates to the new theme. Christian: Check this sidebar. I made it a bit smaller and expanded the content region. Removed the left/right borders to make it feel less intruding on the horizontal space. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On Fri, Jul 28, 2006 at 12:08:38AM +0300, Panos Laganakos wrote: > >I liked the design a lot. My only concern with it is the menu on the > >LHS, which takes up a lot of space and doesn't seem to include content > >which is very important. Am I missing something? Could we get away with > >floating that to the right, or doing something different? > > Christian: The reason I want to move the vertical menu on the left > instead of the right, is that the eye gets easily distracted by object > on middle-right objects, thus making the site unfriendly to read > through. My main concern with it is that the effect is an empty block in the left-hand side, which gives the page content a rather peculiar layout. It's not a blocker, but if we could find a better way to do that, I think I'd prefer that. > Its purpose is to give quick hint on the current version release and > give a second chance to the visitor to find what he's looking for, > *if* he's not satisfied by the major categories of the horizontal bar > menu. Yeah, I understand. But there may be other designs that give you the same hint and not be so constraining of the page layout; perhaps you could consider some alternatives? > I could give it a smaller size and see how that works out or use > JavaScript/CSS to make it expandable/collapsable, but I wouldn't like > to do that (the JS/CSS thingy). Reason being, making them (users) take > a decision on something as trivial as this, once again distracts them > from the actual content. Yeah, I don't think expandability is what we want -- just smart placement of that information. -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125 ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
I liked the design a lot. My only concern with it is the menu on the LHS, which takes up a lot of space and doesn't seem to include content which is very important. Am I missing something? Could we get away with floating that to the right, or doing something different? Christian: The reason I want to move the vertical menu on the left instead of the right, is that the eye gets easily distracted by object on middle-right objects, thus making the site unfriendly to read through. Its purpose is to give quick hint on the current version release and give a second chance to the visitor to find what he's looking for, *if* he's not satisfied by the major categories of the horizontal bar menu. I could give it a smaller size and see how that works out or use JavaScript/CSS to make it expandable/collapsable, but I wouldn't like to do that (the JS/CSS thingy). Reason being, making them (users) take a decision on something as trivial as this, once again distracts them from the actual content. Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125 ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On Fri, Jul 21, 2006 at 12:50:16AM -0300, Johan Dahlin wrote: > Panos Laganakos skrev: > >On 7/20/06, Lawrence Oluyede <[EMAIL PROTECTED]> wrote: > >>I really like your mockups but I'm not in charge of the decisions :-) > >>Anyway, good job Panos! > > > >Thanks Lawrence :) > >I'm waiting to hear from the pygtk maintainers, their opinion on it, > >and if positive, I can start implementing the actual style/site. > I like it, it's a quite a bit nicer than the current design. > We'd need to check with at least Gustavo, the Johns, Rafael and Kiko > too, to see if they have any constructive to add or any objections. I liked the design a lot. My only concern with it is the menu on the LHS, which takes up a lot of space and doesn't seem to include content which is very important. Am I missing something? Could we get away with floating that to the right, or doing something different? -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125 ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Work is mostly done on moving the current site to the new theme. I had to do some changes to the design, in order to comply with the current pygtk.org structure. http://panos.solhost.org/pygtk/ Pages that are currently done: http://panos.solhost.org/pygtk/news.html http://panos.solhost.org/pygtk/downloads.html http://panos.solhost.org/pygtk/development.html and my favorite: http://panos.solhost.org/pygtk/people.html :) I expect to be with it by the weekend, so we can probably merge it with the CVS trunk. On 7/24/06, Baiju M <[EMAIL PROTECTED]> wrote: On 7/24/06, Yaakov Nemoy <[EMAIL PROTECTED]> wrote: > Ah, works very nicely, and resizes well in firefox. Good for any > resolution. Congrats. > > Have you tested it with lynx (or something else)? It is fully readable in lynx, but please provide alternative labels for images. Regards, Baiju M ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On 7/24/06, Yaakov Nemoy <[EMAIL PROTECTED]> wrote: Ah, works very nicely, and resizes well in firefox. Good for any resolution. Congrats. Have you tested it with lynx (or something else)? It is fully readable in lynx, but please provide alternative labels for images. Regards, Baiju M ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Ah, works very nicely, and resizes well in firefox. Good for any resolution. Congrats. Have you tested it with lynx (or something else)? Yaakov 2006/7/24, Panos Laganakos <[EMAIL PROTECTED]>: Lorenzo, thanks for the comments. At one of my posts, I mentioned that the current site was kinda stale etc, I didn't mean it in any offending way. Baiju, I'd vote for plone to be used as a Gnome CMS. The style is mostly done now, and only a few quirks left to iron out. here's the proof of concept: http://panos.solhost.org/pygtk/ I think I should just work with what we currently have now and wait till Gnome approves one CMS, so I can build a theme for it then. I have some ideas for making some parts more dynamic/simpler, but for now, I'll start implementing the style to the actual templates. On 7/24/06, Baiju M <[EMAIL PROTECTED]> wrote: > On 7/24/06, Erik Grinaker <[EMAIL PROTECTED]> wrote: > > On Mon, 2006-07-24 at 09:07 +0200, Lorenzo Gil Sanchez wrote: > > > When I wrote the current pygtk website I try use mod_python (or any > > > other similar approach) to allow more dynamism to the website and I > > > faced to gnome.org rules for websites and scripting. They are pretty > > > simple: no scripting allowed :-) > > > > > > That's why I wrote stp.py[1]. We may not have a lot of dynamism in pygtk > > > but we try to make the website easy to maintain. Stp.py is used to > > > pregenerate the website from a set of files. > > > > It seems that everything stp.py does is combine several files into a > > single page. This could also be done using Apache server-side includes, > > surely gnome.org must allow that? > > > > http://httpd.apache.org/docs/1.3/howto/ssi.html > > GNOME websites will be managed using a CMS in future. > http://live.gnome.org/GnomeWeb/CmsRequirements > > Which CMS is going to use will be decided on day after tomorrow. > So recommend your CMS there now. > > -- > Baiju M > ___ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On 7/24/06, Panos Laganakos <[EMAIL PROTECTED]> wrote: Baiju, I'd vote for plone to be used as a Gnome CMS. Good to hear that, please read this page and see whether any corrections required, If so just edit it :) http://live.gnome.org/GnomeWeb/CmsRequirements/PloneEval Thanks, Baiju M ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Lorenzo, thanks for the comments. At one of my posts, I mentioned that the current site was kinda stale etc, I didn't mean it in any offending way. Baiju, I'd vote for plone to be used as a Gnome CMS. The style is mostly done now, and only a few quirks left to iron out. here's the proof of concept: http://panos.solhost.org/pygtk/ I think I should just work with what we currently have now and wait till Gnome approves one CMS, so I can build a theme for it then. I have some ideas for making some parts more dynamic/simpler, but for now, I'll start implementing the style to the actual templates. On 7/24/06, Baiju M <[EMAIL PROTECTED]> wrote: On 7/24/06, Erik Grinaker <[EMAIL PROTECTED]> wrote: > On Mon, 2006-07-24 at 09:07 +0200, Lorenzo Gil Sanchez wrote: > > When I wrote the current pygtk website I try use mod_python (or any > > other similar approach) to allow more dynamism to the website and I > > faced to gnome.org rules for websites and scripting. They are pretty > > simple: no scripting allowed :-) > > > > That's why I wrote stp.py[1]. We may not have a lot of dynamism in pygtk > > but we try to make the website easy to maintain. Stp.py is used to > > pregenerate the website from a set of files. > > It seems that everything stp.py does is combine several files into a > single page. This could also be done using Apache server-side includes, > surely gnome.org must allow that? > > http://httpd.apache.org/docs/1.3/howto/ssi.html GNOME websites will be managed using a CMS in future. http://live.gnome.org/GnomeWeb/CmsRequirements Which CMS is going to use will be decided on day after tomorrow. So recommend your CMS there now. -- Baiju M ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On 7/24/06, Erik Grinaker <[EMAIL PROTECTED]> wrote: On Mon, 2006-07-24 at 09:07 +0200, Lorenzo Gil Sanchez wrote: > When I wrote the current pygtk website I try use mod_python (or any > other similar approach) to allow more dynamism to the website and I > faced to gnome.org rules for websites and scripting. They are pretty > simple: no scripting allowed :-) > > That's why I wrote stp.py[1]. We may not have a lot of dynamism in pygtk > but we try to make the website easy to maintain. Stp.py is used to > pregenerate the website from a set of files. It seems that everything stp.py does is combine several files into a single page. This could also be done using Apache server-side includes, surely gnome.org must allow that? http://httpd.apache.org/docs/1.3/howto/ssi.html GNOME websites will be managed using a CMS in future. http://live.gnome.org/GnomeWeb/CmsRequirements Which CMS is going to use will be decided on day after tomorrow. So recommend your CMS there now. -- Baiju M ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On Mon, 2006-07-24 at 09:07 +0200, Lorenzo Gil Sanchez wrote: > When I wrote the current pygtk website I try use mod_python (or any > other similar approach) to allow more dynamism to the website and I > faced to gnome.org rules for websites and scripting. They are pretty > simple: no scripting allowed :-) > > That's why I wrote stp.py[1]. We may not have a lot of dynamism in pygtk > but we try to make the website easy to maintain. Stp.py is used to > pregenerate the website from a set of files. It seems that everything stp.py does is combine several files into a single page. This could also be done using Apache server-side includes, surely gnome.org must allow that? http://httpd.apache.org/docs/1.3/howto/ssi.html -- Erik Grinaker <[EMAIL PROTECTED]> http://erikg.codepoet.no/ "We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about." -- Albert Einstein ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Hi Panos, I'm the author of the current website design and one of its maintainers. No need to say that your mockup rocks! :-) When I wrote the current pygtk website I try use mod_python (or any other similar approach) to allow more dynamism to the website and I faced to gnome.org rules for websites and scripting. They are pretty simple: no scripting allowed :-) That's why I wrote stp.py[1]. We may not have a lot of dynamism in pygtk but we try to make the website easy to maintain. Stp.py is used to pregenerate the website from a set of files. Having said that I wish you lots of luck in the task of convincing gnome.org maintainers to bend their policies a little bit. Come one! we are on the XXI century!! Keep up the good work Lorenzo [1] http://cvs.gnome.org/viewcvs/pygtk-web/stp.py?rev=1.2&view=markup Panos Laganakos wrote: Last time I heard, they didn't allow CGI scripting in the web server where pygtk.org is hosted. Is it possible for you to checkout the gnome cvs module pygtk-web and hack on it, maintaining the existing structure as much as possible? Yeah Gustavo, I can, although after browsing it a bit online its kinda stale/non-untuitive. It would be great to have a more interactive site, where it would be easier to update the different parts of it without having to hack on the templates etc. Plus using django as a backend we can make lots of cool stuff, and django kinda becoming a standard in the web these days, so its really easy to hack and maintain it. Even so, if we don't have any other alternative, I'll do what I can with the current structure, but I'd like to be able to do a real live website. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Last time I heard, they didn't allow CGI scripting in the web server where pygtk.org is hosted. Is it possible for you to checkout the gnome cvs module pygtk-web and hack on it, maintaining the existing structure as much as possible? Yeah Gustavo, I can, although after browsing it a bit online its kinda stale/non-untuitive. It would be great to have a more interactive site, where it would be easier to update the different parts of it without having to hack on the templates etc. Plus using django as a backend we can make lots of cool stuff, and django kinda becoming a standard in the web these days, so its really easy to hack and maintain it. Even so, if we don't have any other alternative, I'll do what I can with the current structure, but I'd like to be able to do a real live website. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Sáb, 2006-07-22 às 21:08 +0300, Panos Laganakos escreveu: > Yeah Gustavo don't worry :) > > I started implementing the base CSS of the new style and things are > looking pretty smooth. Stay tuned for a linky of a test XHTML. > > Should I just work on a theme or on a whole site build? If so, I'd be > happy to build a django powered project for the new site. Last time I heard, they didn't allow CGI scripting in the web server where pygtk.org is hosted. Is it possible for you to checkout the gnome cvs module pygtk-web and hack on it, maintaining the existing structure as much as possible? Regards, -- Gustavo J. A. M. Carneiro <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> The universe is always one step beyond logic ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Yeah Gustavo don't worry :) I started implementing the base CSS of the new style and things are looking pretty smooth. Stay tuned for a linky of a test XHTML. Should I just work on a theme or on a whole site build? If so, I'd be happy to build a django powered project for the new site. On 7/22/06, Gustavo J. A. M. Carneiro <[EMAIL PROTECTED]> wrote: Qui, 2006-07-20 às 18:39 +0300, Panos Laganakos escreveu: > I did a 1024x768 version so you can have a better look at it, and did > some other visual improvements too, which brings the mockup to version > 03: > > http://panos.solhost.org/mockups/pygtk-03.png Looks nice. I'm not Web design expert, but as long as you don't make fixed-width pages or columns, or use fixed-size fonts, I'm happy. I also hate when anything that is not a log is made into an image; make sure the menu bar is normal text, please. And allow this bar to stretch with the user-customizable font size ;-) Cheers. -- Gustavo J. A. M. Carneiro <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> The universe is always one step beyond logic ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Qui, 2006-07-20 às 18:39 +0300, Panos Laganakos escreveu: > I did a 1024x768 version so you can have a better look at it, and did > some other visual improvements too, which brings the mockup to version > 03: > > http://panos.solhost.org/mockups/pygtk-03.png Looks nice. I'm not Web design expert, but as long as you don't make fixed-width pages or columns, or use fixed-size fonts, I'm happy. I also hate when anything that is not a log is made into an image; make sure the menu bar is normal text, please. And allow this bar to stretch with the user-customizable font size ;-) Cheers. -- Gustavo J. A. M. Carneiro <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> The universe is always one step beyond logic ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On 7/21/06, Yaakov Nemoy <[EMAIL PROTECTED]> wrote: 2006/7/21, Brian <[EMAIL PROTECTED]>: > On Thu, 2006-20-07 at 18:39 +0300, Panos Laganakos wrote: > > I did a 1024x768 version so you can have a better look at it, and did > > some other visual improvements too, which brings the mockup to version > > 03: > > > > http://panos.solhost.org/mockups/pygtk-03.png > > > > On 7/20/06, Panos Laganakos <[EMAIL PROTECTED]> wrote: > > > I saw that gtkmm.org received a style update, so I thought I'd give a > > > try at a new look for pygtk.org > > > > > > Keep in mind that it'll look small on normal resolutions (1280 > ) > > > 'cause I hacked it on a 800x600 CRT (yuck!). > > > > > > http://panos.solhost.org/mockups/pygtk-01.png > > > http://panos.solhost.org/mockups/pygtk-02.png > > > > > > > > > Lemme know what you think. > > Looks nice, but... There is too little contrast for the date and author > lines. I know, I know I'm getting old :( my eyes aren't as good as > they used to be. > As for the 800 x 600 size. I like it, I often prefer slightly smaller > web page sizes especially if I'm flipping between tutorials/reference's > and an editor window. That way I can keep an eye on both. And no I > can't afford a new 30in. high resolution widescreen monitor for my old > eyes. So if you do proceed with the a new style keep the minimum sizes > for the frames reasonable for smaller page sizes when desired. What about 'flowing layouts' which are so popular in our day and age of CSS, that fit themselves to what ever the browser is sized at. They usually have a minimum resolution, and the can adapt themselves from there. Yaakov Yeah, the divisions will be floating around each other, and will be able to resize, *but* you have to take this into account when designing, 'cause the results won't be the same depending on the resolution used, speaking in border/font terms, not just division resizing and positioning. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
2006/7/21, Brian <[EMAIL PROTECTED]>: On Thu, 2006-20-07 at 18:39 +0300, Panos Laganakos wrote: > I did a 1024x768 version so you can have a better look at it, and did > some other visual improvements too, which brings the mockup to version > 03: > > http://panos.solhost.org/mockups/pygtk-03.png > > On 7/20/06, Panos Laganakos <[EMAIL PROTECTED]> wrote: > > I saw that gtkmm.org received a style update, so I thought I'd give a > > try at a new look for pygtk.org > > > > Keep in mind that it'll look small on normal resolutions (1280 > ) > > 'cause I hacked it on a 800x600 CRT (yuck!). > > > > http://panos.solhost.org/mockups/pygtk-01.png > > http://panos.solhost.org/mockups/pygtk-02.png > > > > > > Lemme know what you think. Looks nice, but... There is too little contrast for the date and author lines. I know, I know I'm getting old :( my eyes aren't as good as they used to be. As for the 800 x 600 size. I like it, I often prefer slightly smaller web page sizes especially if I'm flipping between tutorials/reference's and an editor window. That way I can keep an eye on both. And no I can't afford a new 30in. high resolution widescreen monitor for my old eyes. So if you do proceed with the a new style keep the minimum sizes for the frames reasonable for smaller page sizes when desired. What about 'flowing layouts' which are so popular in our day and age of CSS, that fit themselves to what ever the browser is sized at. They usually have a minimum resolution, and the can adapt themselves from there. Yaakov ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Brian wrote: On Thu, 2006-20-07 at 18:39 +0300, Panos Laganakos wrote: I did a 1024x768 version so you can have a better look at it, and did some other visual improvements too, which brings the mockup to version 03: http://panos.solhost.org/mockups/pygtk-03.png On 7/20/06, Panos Laganakos <[EMAIL PROTECTED]> wrote: I saw that gtkmm.org received a style update, so I thought I'd give a try at a new look for pygtk.org Keep in mind that it'll look small on normal resolutions (1280 > ) 'cause I hacked it on a 800x600 CRT (yuck!). http://panos.solhost.org/mockups/pygtk-01.png http://panos.solhost.org/mockups/pygtk-02.png Lemme know what you think. Looks nice, but... There is too little contrast for the date and author lines. I know, I know I'm getting old :( my eyes aren't as good as they used to be. There's author and date info displayed? Doesn't show on my display at all so I second having more contrast. As for the 800 x 600 size. I like it, I often prefer slightly smaller I also would like it to look good with a 800 pixel width. web page sizes especially if I'm flipping between tutorials/reference's and an editor window. That way I can keep an eye on both. And no I can't afford a new 30in. high resolution widescreen monitor for my old eyes. So if you do proceed with the a new style keep the minimum sizes for the frames reasonable for smaller page sizes when desired. I like the clean graphic look. John ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Small fixes: http://panos.solhost.org/mockups/pygtk-04.png Looks really cool.. Keep up the work... Regards, Santhosh. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
2006/7/21, Panos Laganakos <[EMAIL PROTECTED]>: http://panos.solhost.org/mockups/pygtk-04.png really a good job Panos, I like it very much. ciao -- Gian Mario Tagliaretti http://www.parafernalia.org/pygtk/ http://pygstdocs.berlios.de ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Small fixes: http://panos.solhost.org/mockups/pygtk-04.png Brian: Except the contrast, keep in mind that the fonts render kinda blurry, so that might be a reason for not being very easy to read, as I did small test with actual HTML rendering and they look much sharper/easier to read. Nonetheless, its something really easy to fix, so I can check it out later if this is persistant. On 7/21/06, Panos Laganakos <[EMAIL PROTECTED]> wrote: Thanks all for the notes and critisism. If I get a positive on implementing it, we can work out the details for the actual style. > Looks nice, but... There is too little contrast for the date and author > lines. I know, I know I'm getting old :( my eyes aren't as good as > they used to be. I'll look into this and upload a new version so you can check if its better. > As for the 800 x 600 size. I like it, I often prefer slightly smaller > web page sizes especially if I'm flipping between tutorials/reference's > and an editor window. That way I can keep an eye on both. And no I > can't afford a new 30in. high resolution widescreen monitor for my old > eyes. So if you do proceed with the a new style keep the minimum sizes > for the frames reasonable for smaller page sizes when desired. > -- > Brian <[EMAIL PROTECTED]> ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Thanks all for the notes and critisism. If I get a positive on implementing it, we can work out the details for the actual style. Looks nice, but... There is too little contrast for the date and author lines. I know, I know I'm getting old :( my eyes aren't as good as they used to be. I'll look into this and upload a new version so you can check if its better. As for the 800 x 600 size. I like it, I often prefer slightly smaller web page sizes especially if I'm flipping between tutorials/reference's and an editor window. That way I can keep an eye on both. And no I can't afford a new 30in. high resolution widescreen monitor for my old eyes. So if you do proceed with the a new style keep the minimum sizes for the frames reasonable for smaller page sizes when desired. -- Brian <[EMAIL PROTECTED]> ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On Thu, 2006-20-07 at 18:39 +0300, Panos Laganakos wrote: > I did a 1024x768 version so you can have a better look at it, and did > some other visual improvements too, which brings the mockup to version > 03: > > http://panos.solhost.org/mockups/pygtk-03.png > > On 7/20/06, Panos Laganakos <[EMAIL PROTECTED]> wrote: > > I saw that gtkmm.org received a style update, so I thought I'd give a > > try at a new look for pygtk.org > > > > Keep in mind that it'll look small on normal resolutions (1280 > ) > > 'cause I hacked it on a 800x600 CRT (yuck!). > > > > http://panos.solhost.org/mockups/pygtk-01.png > > http://panos.solhost.org/mockups/pygtk-02.png > > > > > > Lemme know what you think. Looks nice, but... There is too little contrast for the date and author lines. I know, I know I'm getting old :( my eyes aren't as good as they used to be. As for the 800 x 600 size. I like it, I often prefer slightly smaller web page sizes especially if I'm flipping between tutorials/reference's and an editor window. That way I can keep an eye on both. And no I can't afford a new 30in. high resolution widescreen monitor for my old eyes. So if you do proceed with the a new style keep the minimum sizes for the frames reasonable for smaller page sizes when desired. -- Brian <[EMAIL PROTECTED]> ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
Panos Laganakos skrev: On 7/20/06, Lawrence Oluyede <[EMAIL PROTECTED]> wrote: I really like your mockups but I'm not in charge of the decisions :-) Anyway, good job Panos! Thanks Lawrence :) I'm waiting to hear from the pygtk maintainers, their opinion on it, and if positive, I can start implementing the actual style/site. I like it, it's a quite a bit nicer than the current design. We'd need to check with at least Gustavo, the Johns, Rafael and Kiko too, to see if they have any constructive to add or any objections. Johan ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
On 7/20/06, Lawrence Oluyede <[EMAIL PROTECTED]> wrote: I really like your mockups but I'm not in charge of the decisions :-) Anyway, good job Panos! Thanks Lawrence :) I'm waiting to hear from the pygtk maintainers, their opinion on it, and if positive, I can start implementing the actual style/site. -- Lawrence http://www.oluyede.org/blog ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Re: pygtk.org mockup
I really like your mockups but I'm not in charge of the decisions :-) Anyway, good job Panos! -- Lawrence http://www.oluyede.org/blog ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
[pygtk] Re: pygtk.org mockup
I did a 1024x768 version so you can have a better look at it, and did some other visual improvements too, which brings the mockup to version 03: http://panos.solhost.org/mockups/pygtk-03.png On 7/20/06, Panos Laganakos <[EMAIL PROTECTED]> wrote: I saw that gtkmm.org received a style update, so I thought I'd give a try at a new look for pygtk.org Keep in mind that it'll look small on normal resolutions (1280 > ) 'cause I hacked it on a 800x600 CRT (yuck!). http://panos.solhost.org/mockups/pygtk-01.png http://panos.solhost.org/mockups/pygtk-02.png Lemme know what you think. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
