Skip to content
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

ToDo list for 1.0.3. #2

Open
2 of 8 tasks
mzhukov1973 opened this issue May 30, 2018 · 0 comments
Open
2 of 8 tasks

ToDo list for 1.0.3. #2

mzhukov1973 opened this issue May 30, 2018 · 0 comments
Assignees
Labels
ToDo list ToDo list (for a specific version or milestone). towards 1.0.3 This issue is required to be resolved before version 1.0.3 can be committed.
Milestone

Comments

@mzhukov1973
Copy link
Owner

mzhukov1973 commented May 30, 2018

ToDo for version 1.0.3:

  • Fix the issue with LongHours UI mod menu item in .../user/settings being not clickable if SSH Keys item is currently selected.
  • Include javascript.svg logo icon with the mod installation set, amend installation instructions accordingly.
  • Add a quick-settings menu drop-up into the standard Gogs footer.
  • Fill the settings page itself with properly named and annotated (even if yet unconnected) controls to set mod's parameters. Use either exactly the elements found in other settings pages or use Semantic (for now use version 2.3.1, later - guess it from the active Gogs installation itself).
  • Add a general enable/disable control to the .../user/settings page, to control if LongHours is to run at all upon injection and properly connect it to the data - this one control should be completely functional.
  • Make this JS logo change appearance to further indicate injections' status (i.e. not present, loaded, active, error(?), disabled, waiting to go active, modified settings, original settings) and add the same status as text popup, appearing on hover over the settings item.
  • In order to avoid depending on any external framework or library as well as for general lightness of code implement two-way coupling between settings values stored in global object's properties and UI controls for setting them, as found on .../user/settings page. Do so, by creating a proxy for the object with handler monitoring .set(...) calls and informing all concerned parties of any changes via custom events.
  • Implement some simple client-side storage for mod settings' values (at this point - not necessarily connected to the particular Gogs instalaltion)
@mzhukov1973 mzhukov1973 added towards 1.0.3 This issue is required to be resolved before version 1.0.3 can be committed. ToDo list ToDo list (for a specific version or milestone). labels May 30, 2018
@mzhukov1973 mzhukov1973 added this to the 1.0.3 milestone May 30, 2018
@mzhukov1973 mzhukov1973 self-assigned this May 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ToDo list ToDo list (for a specific version or milestone). towards 1.0.3 This issue is required to be resolved before version 1.0.3 can be committed.
Projects
None yet
Development

No branches or pull requests

1 participant