19 Oct
2014
19 Oct
'14
8:54 p.m.
Hi guys,
It would be really cool to drop a 'smart' table into the patches page, or
have an alternative page that provided that support. Datatables is a great
example of this. It's a pseudo excel style table, backed by some
javascript. it would make it easy to search through commits, export data to
excel, sort of date, etc.
Just a thought,
Calvin
19 Oct
19 Oct
9:15 p.m.
New subject: [trinity-devel] new website - patches
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Hi guys,
It would be really cool to drop a 'smart' table into the patches page, or
have an alternative page that provided that support. Datatables is a great
example of this. It's a pseudo excel style table, backed by some
javascript. it would make it easy to search through commits, export data
to
excel, sort of date, etc.
Just a thought,
Calvin
I've been thinking about how to fix the patches page, so this was a timely
message. I'll consider that option when deciding what to do. :-)
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlREKeoACgkQLaxZSoRZrGFGPgDeORN2cjZl7+q+nL4J9y1E3Scy
Ww1u/yKqY6dsjADgtMhza/ZbtVjioHfsbNJaZRUzUKlnEdeTZhoryA==
=UhH5
-----END PGP SIGNATURE-----
11:35 p.m.
New subject: [trinity-devel] new website - patches
On Sunday 19 of October 2014 23:15:23 Timothy Pearson wrote:
Do you remember my earlier script that generated patches page as links to CGIT
interface? Visually, the result of the script differed in the fact that the
date, time and zone were in one column. Besides, they would benefit in that
it did not require additional disk space for patches. The script also
contained prepare for the possibility of pagination...
--
Slávek
Hi guys,
It would be really cool to drop a 'smart' table into the patches page, or
have an alternative page that provided that support. Datatables is a
great example of this. It's a pseudo excel style table, backed by some
javascript. it would make it easy to search through commits, export data
to
excel, sort of date, etc.
Just a thought,
Calvin
I've been thinking about how to fix the patches page, so this was a timely
message. I'll consider that option when deciding what to do. :-)
Thanks!
Tim
20 Oct
20 Oct
2:11 a.m.
New subject: [trinity-devel] new website - patches
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
On Sunday 19 of October 2014 23:15:23 Timothy Pearson
wrote:
Do you remember my earlier script that generated patches page as links to
CGIT
interface? Visually, the result of the script differed in the fact that
the
date, time and zone were in one column. Besides, they would benefit in
that
it did not require additional disk space for patches. The script also
contained prepare for the possibility of pagination...
--
Slávek
Thanks for reminding me. I'll take a look at it and see what I can use.
Tim
Hi guys,
It would be really cool to drop a 'smart' table into the patches page,
or
have an alternative page that provided that
support. Datatables is a
great example of this. It's a pseudo excel style table, backed by some
javascript. it would make it easy to search through commits, export
data
to
excel, sort of date, etc.
Just a thought,
Calvin
I've been thinking about how to fix the patches page, so this was a
timely
message. I'll consider that option when deciding what to do. :-)
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlREb08ACgkQLaxZSoRZrGEgLADfTGPxS6wB/w6gG+8CRfSa2ENw
s+Gv0IkrDo+pjgDcDSXVdfWxl1hYRQBeNYyd661GHrKGjJeO/ktJpw==
=vNMj
-----END PGP SIGNATURE-----
2:23 a.m.
New subject: [trinity-devel] new website - patches
Even if you don't adopt anything new, you could reduce the amount of
bandwidth by quite a bit by not writing valign=TOP width=50% and using css
to accomplish the same
On 19 October 2014 22:11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net>
wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
On Sunday 19 of October 2014 23:15:23 Timothy
Pearson wrote:
Do you remember my earlier script that generated patches page as links to
CGIT
interface? Visually, the result of the script differed in the fact that
the
date, time and zone were in one column. Besides, they would benefit in
that
it did not require additional disk space for patches. The script also
contained prepare for the possibility of pagination...
--
Slávek
Thanks for reminding me. I'll take a look at it and see what I can use.
Tim
Hi guys,
It would be really cool to drop a 'smart' table into the patches page,
or
have an alternative page that provided that
support. Datatables is a
great example of this. It's a pseudo excel style table, backed by some
javascript. it would make it easy to search through commits, export
data
to
excel, sort of date, etc.
Just a thought,
Calvin
I've been thinking about how to fix the patches page, so this was a
timely
message. I'll consider that option when deciding what to do. :-)
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlREb08ACgkQLaxZSoRZrGEgLADfTGPxS6wB/w6gG+8CRfSa2ENw
s+Gv0IkrDo+pjgDcDSXVdfWxl1hYRQBeNYyd661GHrKGjJeO/ktJpw==
=vNMj
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
24 Oct
24 Oct
9:33 p.m.
New subject: [trinity-devel] new website - patches
On Sun, 19 Oct 2014 22:23:17 -0400
Calvin Morrison <mutantturkey(a)gmail.com> wrote:
Even if you don't adopt anything new, you could
reduce the amount of
bandwidth by quite a bit by not writing valign=TOP width=50% and using css
to accomplish the same
Okay, I've had a chance to take a look at this now, and two sets of
fixes are required:
In the HTML page:
-Change the table element to <TABLE CLASS="patchtable">
-Change the header row to use <TH> elements rather than going to the
trouble of <TD><B>
-Remove all the VALIGN=TOP notations.
-While it has nothing to do with the table styles, the <s at the beginning of
the email addresses really should be encoded as < . Currently, the
W3C's validator detects more than 200 errors on this page, nearly all
of them due to this.
To the stylesheet, add the following:
/*patches table*/
.patchtable TR TD {vertical-align:top}
.patchtable TR TH {text-align:left;
font-weight:bold;
vertical-align:top}
.patchtable {width:100%;}
If you want to put the 50% width constraint for the last cell back in, also
add the line:
.patchtable TR TD:last-child {width:50%;}
Surprisingly, even Konqueror understands this selector, despite it technically
being a CSS3 construct.
This is not sufficient to make the table fit correctly on small screens at a sane
font size--for that, you need to cut down those date columns, as I mentioned
before. It's also much grumpier about reducing correctly with the new,
white-border-less design than it was with the original.
I'm going to look at the Bugzilla skin now.
E. Liddell
11:53 p.m.
New subject: [trinity-devel] new website - patches
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
On Sun, 19 Oct 2014 22:23:17 -0400
Calvin Morrison <mutantturkey(a)gmail.com> wrote:
Thanks for the tips; page updated and date columns reworked.
Tim
Even if you don't adopt anything new, you
could reduce the amount of
bandwidth by quite a bit by not writing valign=TOP width=50% and using
css
to accomplish the same
Okay, I've had a chance to take a look at this now, and two sets of
fixes are required:
In the HTML page:
-Change the table element to <TABLE CLASS="patchtable">
-Change the header row to use <TH> elements rather than going to the
trouble of <TD><B>
-Remove all the VALIGN=TOP notations.
-While it has nothing to do with the table styles, the <s at the beginning
of
the email addresses really should be encoded as < . Currently, the
W3C's validator detects more than 200 errors on this page, nearly all
of them due to this.
To the stylesheet, add the following:
/*patches table*/
.patchtable TR TD {vertical-align:top}
.patchtable TR TH {text-align:left;
font-weight:bold;
vertical-align:top}
.patchtable {width:100%;}
If you want to put the 50% width constraint for the last cell back in,
also
add the line:
.patchtable TR TD:last-child {width:50%;}
Surprisingly, even Konqueror understands this selector, despite it
technically
being a CSS3 construct.
This is not sufficient to make the table fit correctly on small screens at
a sane
font size--for that, you need to cut down those date columns, as I
mentioned
before. It's also much grumpier about reducing correctly with the new,
white-border-less design than it was with the original.
I'm going to look at the Bugzilla skin now.
E. Liddell -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlRK5nMACgkQLaxZSoRZrGH6qADcC3lyz1ceUul9bETHZmJ1hCqI
41p2jrr+8gtZTADfZ+ev7I7ds376vNP5FlqiUKyTv1GzAqq9zUq3Ww==
=zGZ4
-----END PGP SIGNATURE-----
25 Oct
25 Oct
midnight
New subject: [trinity-devel] new website - patches
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
<snip>
I'm going to look at the Bugzilla skin now.
E. Liddell
Sounds good; the webdev site looks good (much more refined) and I'm ready
to deploy as soon as the bugzilla and Wiki skins match.
Thanks for all your work on this!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlRK6CsACgkQLaxZSoRZrGHPGwDfZKO7Tat9wBKVtkTVT7zSMC3W
ZU9IIEF6Jcv1nwDff3QfjRltjJyOVhPupiiRGkJKUalmkOC4V4xC6g==
=liPG
-----END PGP SIGNATURE-----
3476
days inactive
3482
days old
7 comments
4 participants
participants (4)
-
Calvin Morrison -
E. Liddell -
Slávek Banko -
Timothy Pearson