GnomeScan
|
Size: 2606
Comment:
|
Size: 2127
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| * '''Packages affected''': xsane, gnome-scan | * '''Packages affected''': xsane, gnomescan |
| Line 10: | Line 10: |
| GnomeScan should substitute Xsane in the next release. | [[http://live.gnome.org/GnomeScan|GnomeScan]] should substitute Xsane in the next release. |
| Line 16: | Line 16: |
| This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) It is mandatory. |
In an effort to provide the easy to use user experience, we need to replace Xsane with something more user friendly. Gnome Scan provides a much simpler UI and is better integrated in GNOME. |
| Line 22: | Line 20: |
| This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. | Xsane is complicated to use, we should default to a tool that might be less powerful and more user friendly. |
| Line 26: | Line 24: |
| * Jill has a document to scan for work, she puts the document into the scanner, scans it and emails it to a co-worker. * Larry has some old photos he wants to add to his photo library, he places the photos in the scanner one and a time. After scanning them he imports the photos to his library. |
|
| Line 27: | Line 29: |
That gnomescan really works, we didn't have a scanner to test with. We will test it on real hardware before making the change. |
|
| Line 30: | Line 34: |
| You can have subsections that better describe specific parts of the issue. | None |
| Line 34: | Line 38: |
| This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: | The gnomescan package in Karmic needs to be updated. There is a package for debian waiting to be uploaded, we should do that and sync it. |
| Line 38: | Line 42: |
| Should cover changes required to the UI, or specific UI that is required to implement this | None |
| Line 42: | Line 46: |
| Code changes should include an overview of what needs to change, and in some cases even the specific details. | None |
| Line 46: | Line 50: |
| Include: * data migration, if any * redirects from old URLs to new ones, if any * how users will be pointed to the new way of doing things, if necessary. |
None |
| Line 53: | Line 54: |
| It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage. This need not be added or completed until the specification is nearing beta. |
Functional testing, we should be able to accomplish the user stories specified above. |
| Line 59: | Line 58: |
| This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. | None known yet |
| Line 63: | Line 62: |
| Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. | During our session, we discussed Xsane, GNOME Scan, and gscan2pdf. Nobody was really in favor of sticking with Xsane. Gscan2pdf looks pretty powerful, but the UI is a little more complex and it isn't as well integrated into the GNOME desktop. GNOME Scan has a very simple UI, and would be appropriate for inclusion. |
Launchpad Entry: desktop-karmic-gnomescan
Created: 2009-05-24
Contributors: KenVanDine
Packages affected: xsane, gnomescan
Summary
GnomeScan should substitute Xsane in the next release. Xsane is not integrated in the Gnome desktop and personally I find it too difficult to use for a beginner. GnomeScan is easy to use and fully integrated.
Release Note
In an effort to provide the easy to use user experience, we need to replace Xsane with something more user friendly. Gnome Scan provides a much simpler UI and is better integrated in GNOME.
Rationale
Xsane is complicated to use, we should default to a tool that might be less powerful and more user friendly.
User stories
* Jill has a document to scan for work, she puts the document into the scanner, scans it and emails it to a co-worker.
* Larry has some old photos he wants to add to his photo library, he places the photos in the scanner one and a time. After scanning them he imports the photos to his library.
Assumptions
That gnomescan really works, we didn't have a scanner to test with. We will test it on real hardware before making the change.
Design
None
Implementation
The gnomescan package in Karmic needs to be updated. There is a package for debian waiting to be uploaded, we should do that and sync it.
UI Changes
None
Code Changes
None
Migration
None
Test/Demo Plan
Functional testing, we should be able to accomplish the user stories specified above.
Unresolved issues
None known yet
BoF agenda and discussion
During our session, we discussed Xsane, GNOME Scan, and gscan2pdf. Nobody was really in favor of sticking with Xsane. Gscan2pdf looks pretty powerful, but the UI is a little more complex and it isn't as well integrated into the GNOME desktop. GNOME Scan has a very simple UI, and would be appropriate for inclusion.
DesktopTeam/Specs/Karmic/GnomeScan (last edited 2009-06-16 21:13:59 by cpe-071-065-240-185)