-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add basic display layer #15
Comments
OK... from an implementation point of view, it'll be easier to implement this before / in parallel with #14 since there's quite a bit of mutual dependency between them in terms of PyQt code. |
Yet to create an Issue to Gherkin the functionality of allthese things, but tentatively: |
Yes, that's probably a post-alpha feature. |
For the 9/24 sprint, we've committed to integration against the development environment, i.e., it should be possible to to
|
Not sure if this is the best place on GH for this, but here is ye dummy content! |
Ack on dummy content. Most of the features of this have landed via merging #29. |
fair, closing since the remainder of this functionality is tracked in #32 |
To be used like below. pip3 install -r requirements.txt --index-url https://dev-bin.ops.securedrop.org/simple
Once we have the ability to authenticate (#14) and synchronize data (#5), we should display the available data to the user. For now we can use the first prototype as a guidepost for the client design, but we will iterate on the design as we go, so we can use placeholder colors, icons, etc. for now. Regardless of the final design, we will need a source list view and a per-source detail view.
The data we want to display as part of the list view in the UI is:
Once we can decrypt messages, we want to also display
NOTE: It may not be possible to display some legacy replies; see #4.
The scope of this task is just the display of information in the list and detail view, not the interactions, which will be tracked separately.
For the first iteration of the display layer, we should not concern ourselves with read/unread status, or the number of new or total messages/submissions for a given source.
The text was updated successfully, but these errors were encountered: