xtrabytes / xcite.old Goto Github PK

In Controls.DatePicker.qml, change the background color of the currently-hovered date on mouse hover. A slightly-lighter version of its current background color should work well.

• Move the "Tools" section out of DashboardForm.qml into its own area ("Tools" folder?)
• Leave it inaccessible from the Module menu for now, until it's implemented in the future

We have additional binding loop warnings on Login/TwoFactorAuthForm.qml:53 and Login/SignupForm.qml:67.

These need a similar fix to #81

• Node Level (1, 2, or 3)
• Node Details
• Node Confirmation

Currently the ButtonDiode control allows itself to be unselected by clicking on it again after selecting it. The majority of the time (with the exception being the Online indicator, for example) unselection should only be performed by selecting a different ButtonDiode. Add a property to the ButtonDiode control that defaults to not allowing unselection but allows it to be set if needed.

As pointed out by bilen in discord, for some modules it will be necessary to add scroll ability, primarily vertically.

Can be seen here, right-hand pane is covering it:

It would be nice to create a page to show search results.

In my opinion, ideally:

• It must be shown on current view as a semi-transparent rectangle under the search bar, or on top of current view just as search works in PluralSight. This would prevent users from losing context. The box should implicitly grow in height with most results.
• Results should be available for (1) views (xChange, XChat, etc) (2) My Contacts (3) My Addresses

For now, I think results for Views should be enough.

Implement a reusable success/fail component to give the user feedback that an operation was completed successfully.

Expand address book width when window size is expanded: found in ReceiveCoin

For aesthetic purposes, slightly increase left hand pane

Create CONTRIBUTING.md

Follow the guidance in this article:

https://help.github.com/articles/setting-guidelines-for-repository-contributors/

Module menus using a bunch of bools to manage what's visible, could probably be simplified to a simplified selectedBoard variable.

• Update the current version in xcite.pro to the upcoming release 0.1.2
• Display the version in the UI (perhaps in the title bar or "popup" area)

Current color coding of the history page is confusing with no real indication of why some stuff is blue and others are red. Receives should likely be marked as blue and sends as red. Will add comments to inform future use of such designs.

Is there something I'm missing with the current colors (presumably they're like that to look pretty)? Probably a non-issue but worth fixing for now to avoid confusion.

The main window size is currently statically set which results in window clipping off the edge of the screen when the available screen size isn't sufficient. Change the main window size to size itself down if there isn't enough available screen space.

Implement as per design

Instead of setting visible: true or false to show or hide components, utilize the QML Loader to delay creating the component until it's demanded.

http://doc.qt.io/qt-5/qml-qtquick-loader.html

From the docs:

Loader is used to dynamically load QML components.

Loader can load a QML file (using the source property) or a Component object (using the sourceComponent property). It is useful for delaying the creation of a component until it is required: for example, when a component should be created on demand, or when a component should not be created unnecessarily for performance reasons.

Remove the Login area StackView and replace it with visibility changes.

• The transitions add what almost feels like "lag"
• We aren't using transitions everywhere else

On X-BOARD, the buttons in the side-menu should be:

HOME , TRANSFER, HISTORY, NODES

Implement send coins as per designs

We need a nice set of components for validating forms and feeding back errors to users.

Adding new people to the send coins address list seems like a good fit with which to test this.

Currently one can only send coins to the highlighted addressbook entry, even if they have changed the contents of the form.

We ought to handle this nicely:

• When a user changes the address in the form, perhaps change the UI to make it obvious that they're doing a 'quick send' and deselect the item in the addressbook.
• Should change related dialogs/messaging to take it into account.

Charting will be necessary within the Wallet and Nodes areas.

Examples:

https://github.com/evonove/qnite
https://github.com/jwintz/qchart.js/tree/master

All components should follow a consistent naming convention. Need to update the new items I've added so that the language follows through.

XCITE UI/UX Terminology

X-BOARD = A Module
HOME = A View
Balance = A Diode

Restructuring the address book to use C++ models has broken the saving of changes.

Need to refactor the buttons to emit signals on click and handle it further up in the tree.

Number of unnecessary folders and files exist that are unlikely to be used.

Requested Deletion 1: xcite/workarea
Requested Deletion 2: xcite/documentation

Searching for more bloat, will submit pull request when comprehensive search is completed. Let me know if these need to stay in.

Send Payment button not visible on small screens as read from Zendesk.

currently working on a fix

To avoid rework, add a placeholder image/graph on X-BOARD->Home for now.

The X-Chat popup UI isn't a pixel-perfect replica of the mockups. Change the UI to more accurately reflect the mockups.

Current Design:

Mockup Design:

Create STYLEGUIDE.md

Adopt Qt's "QML Coding Conventions" as a style guide to help keep our coding style consistent.

http://doc.qt.io/qt-5/qml-codingconventions.html

Include a reference to "preferences -> Qt Quick -> QML/JS Editing: Enable auto format on save" as a way of automatically adhering to the style guide when saving any file.

Create a reusable modal dialog component for asking the user to confirm operations.

e.g. Are You Sure?
[Yes] [No]

Homepage of Nodes needs design input

LoginForm.qml:67:9 outputs qrc:/Login/LoginForm.qml:67:9: QML ButtonPlainText: Binding loop detected for property "width"

The name "ButtonDiode" is a carryover from early UI prototypes. Rename the control and change its references from "ButtonDiode" to the more general name "ButtonIcon".

To reproduce:

• Run app
• Click the small 'Sign Up' link at the bottom
• Click the Sign Up button

Error:
qrc:/main.qml:21:5: QML StackView: replace: qrc:/Login/DashboardForm.qml:-1 No such file or directory

Long inputs on the X-Chat overflow the boundaries of the box: https://cdn.discordapp.com/attachments/388344677952126977/409398538225844227/unknown.png

Update the properties of the input to scroll or auto-size the input.

https://help.github.com/articles/adding-a-license-to-a-repository/

To research which license would be most suitable, this site (by GitHub) might be helpful:

https://choosealicense.com/

Few factors to consider here:

• Full screen app on large screens, should we limit the maximum size?
• Screens smaller than 1440x1024, we'll need to hide some elements and resize others. Need input from design here.
• Anything in-between, we'll need to size the view components appropriately to fill available space

Amounts larger than 6 figures currently get slapped with an exponent, likely smaller amounts do too.
Hardcode a balance of >= 1,000,000 to see this in action.

Hat-tip to MarineOne on Discord!

Probably the same thing again:

qrc:/Login/ForgotPasswordForm.qml:52:9: QML ButtonPlainText: Binding loop detected for property "width"

Send and receive coins both feature a similar address book, we ought to attempt to refactor them to reuse a shared component rather than duplicating the buttons.