[Bugs] #904 UNSP: Read Etexts-11, search result path information unnecessary for user to see
SugarLabs Bugs
bugtracker-noreply at sugarlabs.org
Thu May 28 16:28:37 EDT 2009
#904: Read Etexts-11, search result path information unnecessary for user to see
------------------------------------------+---------------------------------
Reporter: garycmartin | Owner: jdsimmons
Type: enhancement | Status: new
Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team
Component: Read Etexts | Version: Unspecified
Severity: Unspecified | Resolution:
Keywords: | Distribution: Unspecified
Status_field: Unconfirmed |
------------------------------------------+---------------------------------
Comment(by jdsimmons):
I kind of agree with this, but not quite. If you look at the Help text
(under the Groucho Marx quote) you'll see an example of why you might need
the path. Gutenberg has two different path conventions: a new one based
on the text number which is mostly correct and an older one that
occasionally is not. My first attempt at this only used the new path, but
that meant that some of Gutenberg's choicest titles were unavailable. Now
some books have both old and new entries. For instance. Alice in
Wonderland works for the new one but not the old. You need a way to know
which is which.
Also, the columns can be sorted so the easiest way for me to get the path
for downloading is to get it from the table. If this was a Java Swing
table I'd know how to have information be in the table but not visible to
the user. For pygtk tables I haven't figured it out yet.
Finally, Project Gutenberg Australia has its own offline catalog including
2,000 some odd books that are out of copyright there but not in the U.S.
I want to merge that catalog with the other one so a user who is allowed
to can download these titles. I really need to show which titles are
which so we're not accused of encouraging children to steal the
intellectual property of an author who's been dead 50 years.
Not saying this isn't a bug, just looking for some ideas.
--
Ticket URL: <http://dev.sugarlabs.org/ticket/904#comment:1>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list