Re: Suggestion: "Delete field" buttons
Peter Schulte-Stracke <mail-OvSX7JRiA6TkXZrADh/[email protected]>
| Newsgroups | gmane.comp.gnome.apps.pybliographer |
|---|---|
| Message-ID | <1110762188l.1795l.0l@britten> |
Am 04.03.2005 12:08:46 schrieb(en) Hendrik Fuss: > Here's a suggestion for the pybliographer GUI. I find deleting > unwanted extra fields after a PubMed search quite awkward: > focussing on each text field, selecting all text and deleting. > Wouldn't it be nice to have a small delete button next to the > title of each field? Or maybe a clear button; that would be > easier to implement, I guess. I tend to disagree, I'm afraid. If the problem is that surplus information is *imported* (as after an external database query), then the correct way to deal with this problem is to restrict the flow of information across the import reader. 1. For »tagged« readers, as MEDLINE, it is simple to exclude some »tags« from import processing. As tagged readers are the most important class a.t.m. this should prove worthwhile to implement. 2. Another quite useful and versatile customisation technique is to call appropiate *user-exits*, say (pending systematic naming ;-)), for every import record from Pyblio import userexit x = userexit.post_medline_import_record (entry) if x: #accept (modified) record else: # ignore record The latter is in addition quite simple to implement, so it will be done for 1.2.7, while I'm not sure whether the first option can be realised in time for the samme release. Reagrds, Peter ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click