Discoverability: first steps a new user has to be told about
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 15/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- c
- Bereich
- desktop-dev, documentation
Rechercherichtung
Start from the Help menu entry "on Organizer…", the File menu that changes with tree selection, the right-click menu on "Local data", and the New Calculation code choice, since the issue names these as the places to change. The help index holds the "Running codes" pages the issue wants linked, and the Help → Support diagnostics zip is the item to surface. The issue is a set of six discoverability changes with no agreed design yet, so it needs maintainer decisions before code work. Done means each step is either implemented or split into its own issue.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Collected from the first-use instructions written for a new macOS (Apple silicon) tester of 9.1.0. Each step below had to be explained in prose because the program does not lead to it. Discoverability and bug fixes are the focus of the next releases; reports from testers will be added here or filed separately.
Steps that needed explaining
- Help → "on Organizer…" is the entry point for all of the help, including the platform pages, but its label suggests a page about the Organizer only. Rename it (e.g. "ECCE Help") and keep Ctrl+H.
- Running other codes. After a local start only ECCE-QM is available. How to get ORCA, NWChem etc. is in "Running codes on macOS" (and the Linux/Windows equivalents), reachable only through the help index. The program should point there when a user looks for a code that is not set up (e.g. from New Calculation's code choice, or a Help menu entry "Running codes on this computer").
- Register Machines is under Tools, where a new user does not look for the place to make a code available. Link it from the same places as item 2.
- Creating a project or calculation is offered on right-click of "Local data" and in a File menu that changes with the tree selection. With nothing selected there is no visible way to start. Offer New Project / New Calculation in the File menu regardless of selection (defaulting to Local data), and say that a project is a folder.
- Example calculations. File → Open Example Calculations is the quickest way to see what ECCE does, but nothing suggests it. Import the examples automatically on the first start, into their own project ("Examples"), and record that this was done, so that deleting them does not bring them back. Applies to every deployment mode (each user's own data on a central server). File → Open Example Calculations stays, to restore them.
- Help → Support builds the diagnostics zip for a ticket; testers need to be told it exists. Mention it in the help start page and in error dialogs that ask the user to report a problem.
Related: #219 (help rewrite), #264 (first-calculation walkthroughs), #240 (first start).
- Vorherrschende Sprache
- C
- Sterne
- 10
- Forks
- 8
- Ø Merge
- 21 Min.
- Gemergte PRs (30 T.)
- 1
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus FriendsofECCE/ECCE
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
FriendsofECCE/ECCE#336 · 1 Kommentar ·
-
Viewer under XWayland: MO Diagram window opens black; bottom strip blinks on property switchesOffen
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 43/100
FriendsofECCE/ECCE#361 · 1 Kommentar ·
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 20/100
FriendsofECCE/ECCE#359 ·
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 28/100
FriendsofECCE/ECCE#358 ·
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 20/100
FriendsofECCE/ECCE#357 · 3 Kommentare ·
Alle Issues in FriendsofECCE/ECCE
Ähnliche Issues
-
native-cpu: -Wreturn-type in skainet_row_threads.c:150 (worker fn has no return)Evtl. vergeben @Doomguy-BFG9000 hat das heute übernommen. Offengood first issue size:xs skill:native
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 78/100
SKaiNET-developers/SKaiNET#1358 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 64/100
libsdl-org/SDL#16539 ·
Maintainer antworten meist innerhalb von 1 Tag
-
git-workflow task-4
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
dosemu2/dosemu2#3178 · 1 Kommentar · 1 Reaktion ·
Maintainer antworten meist innerhalb von 1 Tag