PyPI template improvements
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all, the recent activity on this mailinglist has kickstarted my contributing sense. As long as the mirroring debate is still ongoing I will focus my efforts somewhere else. Namely: the HTML/Javascript/CSS. In this regard I have a few questions before I really dig into these templates: - - Is there a list of improvements, maybe a nice TODO of points which people want to see improved? - - How are design changes handled, is there a committee to run them through? People who decide on what gets in and what not? (I'll outline some of my first thoughts lower in this mail) - - What are the supported browser versions by PyPI, I reckon it's IE6/7/8+, Fx 2+, Opera 9+ Safari 4+? The changes I have on my personal 'todo list' are: - - Add labels to all forms. - - Make tables consistent width (see for example the table in the top of the "Browse packages" page and compare with the table when you actually select one of the classifiers). - - Restyle the metadata display on package pages and move it up in the page. - - Have downloads readily available on the right side of the screen (at least the latest release). - - Look sternly at the top right floating account information page. - - Look at the your details page where the form does not align with the right floating profile box. - - Make one consistent styling for all forms. Include help texts in all forms. There are more things I want to do, but this is the start. I have already cloned Tarek's PyPI clone on Bitbucket and I'll add my changes there. Is there anything you guys (and the users) would really like to see improved? Regards, Simon de Vlieger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQIcBAEBAgAGBQJMGT6kAAoJEBBSHP7i+JXfHmsQALbm5rqRpLdjTDWNHLQHqoVE D4rDht/oaOFwPBfWp2FMRIhqLa9yA2AQfEAWSBFLqNMr2FGwpRPAXGgd38VOKOf0 pTORXM7cw92yjQXFz4J4xvcN7IcmyYEfftbwlITStnAEc5Q/5sl93nxyyigyQr7D y62EfCRGQP/OTfU7PYoj1KS9Qwi4ep6saD1cdL+tM7AgPiGwJMU2f29vElMVvT1G of+3gZjEi/UpsiYP/qD3JW3iFoOKv3KJbMmdHfMaPCa/vyfGRBoM4eGf5XvV+3oy U6EJ3YvvvTTS/w+TR36USxonuspYWKxoku1hUDaRsDgUC1fdW1UWVtocvnGzr1JW j06KN19ypzVK6UFoRTTsbA6K3h/pppgO1MIH9iAQgkvNY/irZiACO//x6bLT7ZFr 3PRt2ZaJzutKpUT0dGf0HjqcXdF6tPGnaQK1kkBGIgJrtXgqHqmc6Ee4S3Kd/boD tS9ZVqtIB2npJR4e0ZA6iqqGCNvpJlQEiUXSIpmTBRIgvpIjGcA/DQ+rQSIY8twS KPMGdnLm9u0HJdmlsRvJvH6/FBYIhoWDYWulil8ZpZnjHsyLAfTQjNeWzQDylEKF O750a9QgRIbeEFIOZK1kkaccy0dL3oX4MqJBfLlaJUlBJ0pYq3jTXf9+kc6g+uGc hutNfaPX84pe/oxL/z8k =hMyY -----END PGP SIGNATURE-----
On Jun 16, 2010, at 11:14 PM, Simon de Vlieger wrote:
the recent activity on this mailinglist has kickstarted my contributing sense. As long as the mirroring debate is still ongoing I will focus my efforts somewhere else. Namely: the HTML/Javascript/CSS.
Hi Simon, nice to see the Cheeseshop get some new love. I can't answer too many of your questions, but here's an issue I would really love to be solved. I can't imagine it's that difficult: https://sourceforge.net/tracker/?func=detail&aid=3017638&group_id=66150&atid=513503 This requests that when a package has uploaded documentation, that the Cheeseshop page for the package automatically link to the documentation page.
- - What are the supported browser versions by PyPI, I reckon it's IE6/7/8+, Fx 2+, Opera 9+ Safari 4+?
Can you add Chromium 5 to that list? Cheers, -Barry
Two from me:
* Make the textareas not do a hard wrap in the package info edit screen.
Right now you can't edit (or even save without editing) the metadata for
packages with long lines without breaking them, which includes breaking long
URLs.
* Kind of relatedly, make long descriptions wrap in some fashion. Right now
if you have a plain-text long_description for your project without newlines
it just gets really wide. I think that'd be fixable with just CSS.
On Wed, Jun 16, 2010 at 4:14 PM, Simon de Vlieger
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hey all,
the recent activity on this mailinglist has kickstarted my contributing sense. As long as the mirroring debate is still ongoing I will focus my efforts somewhere else. Namely: the HTML/Javascript/CSS.
In this regard I have a few questions before I really dig into these templates:
- - Is there a list of improvements, maybe a nice TODO of points which people want to see improved? - - How are design changes handled, is there a committee to run them through? People who decide on what gets in and what not? (I'll outline some of my first thoughts lower in this mail) - - What are the supported browser versions by PyPI, I reckon it's IE6/7/8+, Fx 2+, Opera 9+ Safari 4+?
The changes I have on my personal 'todo list' are: - - Add labels to all forms. - - Make tables consistent width (see for example the table in the top of the "Browse packages" page and compare with the table when you actually select one of the classifiers). - - Restyle the metadata display on package pages and move it up in the page. - - Have downloads readily available on the right side of the screen (at least the latest release). - - Look sternly at the top right floating account information page. - - Look at the your details page where the form does not align with the right floating profile box. - - Make one consistent styling for all forms. Include help texts in all forms.
There are more things I want to do, but this is the start.
I have already cloned Tarek's PyPI clone on Bitbucket and I'll add my changes there.
Is there anything you guys (and the users) would really like to see improved?
Regards,
Simon de Vlieger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iQIcBAEBAgAGBQJMGT6kAAoJEBBSHP7i+JXfHmsQALbm5rqRpLdjTDWNHLQHqoVE D4rDht/oaOFwPBfWp2FMRIhqLa9yA2AQfEAWSBFLqNMr2FGwpRPAXGgd38VOKOf0 pTORXM7cw92yjQXFz4J4xvcN7IcmyYEfftbwlITStnAEc5Q/5sl93nxyyigyQr7D y62EfCRGQP/OTfU7PYoj1KS9Qwi4ep6saD1cdL+tM7AgPiGwJMU2f29vElMVvT1G of+3gZjEi/UpsiYP/qD3JW3iFoOKv3KJbMmdHfMaPCa/vyfGRBoM4eGf5XvV+3oy U6EJ3YvvvTTS/w+TR36USxonuspYWKxoku1hUDaRsDgUC1fdW1UWVtocvnGzr1JW j06KN19ypzVK6UFoRTTsbA6K3h/pppgO1MIH9iAQgkvNY/irZiACO//x6bLT7ZFr 3PRt2ZaJzutKpUT0dGf0HjqcXdF6tPGnaQK1kkBGIgJrtXgqHqmc6Ee4S3Kd/boD tS9ZVqtIB2npJR4e0ZA6iqqGCNvpJlQEiUXSIpmTBRIgvpIjGcA/DQ+rQSIY8twS KPMGdnLm9u0HJdmlsRvJvH6/FBYIhoWDYWulil8ZpZnjHsyLAfTQjNeWzQDylEKF O750a9QgRIbeEFIOZK1kkaccy0dL3oX4MqJBfLlaJUlBJ0pYq3jTXf9+kc6g+uGc hutNfaPX84pe/oxL/z8k =hMyY -----END PGP SIGNATURE-----
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Ian Bicking | http://blog.ianbicking.org
On Jun 17, 2010, at 12:56 PM, Ian Bicking wrote:
* Kind of relatedly, make long descriptions wrap in some fashion. Right now if you have a plain-text long_description for your project without newlines it just gets really wide. I think that'd be fixable with just CSS.
How about supporting reST in descriptions? -Barry
On Thu, Jun 17, 2010 at 1:15 PM, Barry Warsaw
On Jun 17, 2010, at 12:56 PM, Ian Bicking wrote:
* Kind of relatedly, make long descriptions wrap in some fashion. Right now if you have a plain-text long_description for your project without newlines it just gets really wide. I think that'd be fixable with just CSS.
How about supporting reST in descriptions?
It is supported, but if something doesn't render cleanly as reST it is treated as plain text and wrapped in an unwrapping <pre>. -- Ian Bicking | http://blog.ianbicking.org
On 17 jun 2010, at 17:38, Barry Warsaw wrote:
This requests that when a package has uploaded documentation, that the Cheeseshop page for the package automatically link to the documentation page.
I'll look into this. On 17 jun 2010, at 17:38, Barry Warsaw wrote:
Can you add Chromium 5 to that list?
This as well (it's another webkit browser but I will test it specifically). On 17 jun 2010, at 19:56, Ian Bicking wrote:
* Make the textareas not do a hard wrap in the package info edit screen. Right now you can't edit (or even save without editing) the metadata for packages with long lines without breaking them, which includes breaking long URLs.
I'll look into this.
* Kind of relatedly, make long descriptions wrap in some fashion. Right now if you have a plain-text long_description for your project without newlines it just gets really wide. I think that'd be fixable with just CSS.
It will be fixable with just CSS. It seems I have compiled a nice list of things to fix over the weekend and I'll rummage in the sourceforge issues list to find some more HTML- related issues. I'll let the appropriate people know when I finish my patches and I'll discuss further template adjustments (in the design area) with the more appropriate catalog-sig list. Regards, Simon de Vlieger
participants (3)
-
Barry Warsaw
-
Ian Bicking
-
Simon de Vlieger