tahoe-lafs
/
trac-2024-07-25
2
0
Issues 1.1k Wiki

put sparklines on front page #172

New Issue
Open
opened 2007-10-11 03:16:38 +00:00 by zooko · 5 comments
zooko commented 2007-10-11 03:16:38 +00:00
Copy Link

I want to make miniature (but live, automatically and frequently updated) munin graphs up front on the wiki, on the front page somewhere. Things like public test grid usage, upload/download speed, mem usage, code coverage.

:-)

I want to make miniature (but live, automatically and frequently updated) munin graphs up front on the wiki, on the front page somewhere. Things like public test grid usage, upload/download speed, mem usage, code coverage. :-)
zooko added the
website
major
enhancement
0.6.0
 labels 2007-10-11 03:16:38 +00:00
zooko added this to the 0.7.0 milestone 2007-10-11 03:16:38 +00:00
zooko commented 2007-10-11 03:17:37 +00:00
Author
Copy Link

Oh, and builbot, too. Squeeze those things down so that they convey actual information but still fit into, basically, the space of a bullet-point or decoration or logo or one-sentence. :-)

Oh, and builbot, too. Squeeze those things down so that they convey actual information but still fit into, basically, the space of a bullet-point or decoration or logo or one-sentence. :-)
zooko commented 2007-11-01 18:14:44 +00:00
Author
Copy Link

We're focussing on an imminent v0.7.0 (see the roadmap) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.

We're focussing on an imminent v0.7.0 (see [the roadmap](http://allmydata.org/trac/tahoe/roadmap)) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.
zooko added
0.6.1
 and removed
0.6.0
 labels 2007-11-01 18:14:44 +00:00
zooko modified the milestone from 0.7.0 to undecided 2007-11-01 18:14:44 +00:00
zooko commented 2007-12-13 00:13:18 +00:00
Author
Copy Link

The word for pretty shrunken graphs which are small enough to fit into the flow of text is "sparklines".

The word for pretty shrunken graphs which are small enough to fit into the flow of text is ["sparklines"](http://en.wikipedia.org/wiki/Sparkline).
zooko changed title from put shrunken graphs on front page to put sparklines on front page 2007-12-13 00:13:18 +00:00
warner commented 2008-06-01 21:04:53 +00:00
Copy Link

and, for reference, taking a full-sized graph and referencing it with an IMG tag that has small height= and width= attributes is unsatisfying, as non-Quartz-enabled browsers don't tend to scale images very well.. the result is usually unreadable. Actual sparklines are created at the target size.

and, for reference, taking a full-sized graph and referencing it with an IMG tag that has small height= and width= attributes is unsatisfying, as non-Quartz-enabled browsers don't tend to scale images very well.. the result is usually unreadable. Actual sparklines are created at the target size.
warner modified the milestone from eventually to undecided 2008-06-01 21:04:53 +00:00
terrell commented 2009-02-12 17:56:13 +00:00
Owner
Copy Link

a few links to python sparkline implementations...

Matthew Perry's module - just needs Python Image Library (PIL)

Gary Perez's CSS-only solution

Joe Gregorio's Sparklines_in_data_URIs solution

Will Larson's port of Sparklines.js to python

a few links to python sparkline implementations... [Matthew Perry's module](http://www.perrygeo.net/wordpress/?p=64) - just needs Python Image Library (PIL) [Gary Perez's CSS-only solution](http://xiix.wordpress.com/2005/12/08/generating-css-only-sparklines-in-python/) [Joe Gregorio's Sparklines_in_data_URIs solution](http://bitworking.org/news/Sparklines_in_data_URIs_in_Python) [Will Larson's port of Sparklines.js to python](http://lethain.com/entry/2008/sep/13/sparklines-js-port-to-python/)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No Milestone
undecided
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#172
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?