Skip to content

TODO.md

Latest commit

 

History

History
81 lines (63 loc) · 4.42 KB

TODO.md

File metadata and controls

81 lines (63 loc) · 4.42 KB

FUTURE

--- NOTES

  1. Working on Path env variable remember to change values for both installer and uninstaller!

--- QUAIL

  1. BUGS

    1. Not dangerous. COMPARESEARCH::ArrayPartFirstMatchVector inside open\open.hpp reads outside it's memory. Still within my program scope. When we're checking against a string with a key that has more characters we are bypassing the EOS sign and reading outside of the variable memory (possibly, ... its std::vector).
    2. Not dangerous. Configuration files (main, global, include, +project files) being still in use. Its an edge case but it happens sometimes. Making uninstaller not uninstalling everything properly.
    3. include space in path bug fix via "" or `` or ''.
    4. queue , bug fix.

  2. Have a better look at: Making projects in global.txt. There might be potential bugs and unchecked errors.

  3. Differentiate between "topConfigsFolder" and "installedBinaryFolder". This will help in making top-level-configs located outside Quail directory.

  4. Make it so global config values can be overridden by normal config values.

  5. Customizable styling for command display -> registry keys and values.

  6. Adding Quail configuration data using --add command: like quail -a module key "value".

  7. Edit Quail configuration data using --edit command: like quail -e module key "value".

  8. --optimize, -x to test the memory allocations, the amount of required data that is needed Store that in Windows Registry and we reuse it as the first allocation size the open buffer.

  9. Replace std::vector's with one buffer only.

  10. Quail setting - coloring.

  11. Quail setting - spacing - registry value.

  12. Quail setting - spacing - 0 means no limiting.

  13. ???. Maybe directory as -d or --directory to open directory of a defined project.

  14. Replace "IsForceC8Display" with flags variable.

  15. Add a --show, -s with an allias. It prints the WHOLE command-value in one line just like version is.

  16. Add HIDDEN - new feature 'tags' now befors '=' sign a tag can be created. Tags can be defined by quail itself or by the user (but thats a far future). !cmd HIDDEN = start "" "something". HIDDEN tag makes the command or queue not visible in view.

  17. Add GROUP, MODULE, VARIABLE, SPECIAL - new feature 'tags' for module syntax. This highlights text according to tag.

  18. ? Quail HotKey via RegisterHotKey() with either MOD_ALT or MOD_CONTROL. This would run the quail -o <rest_of_the_command>. However an input box app would be neccessery for providing the rest_of_the_command.

  19. .qtf - quail text file, give an option to use such extension reqistring in as openable via notepad/++. This would allow an easier way of identifing quail files maybe even support creating syntax highlight for them in future.

--- INSTALLER

  1. Move created window objects outside WM_PAINT.
  2. Last, Browse, Path, Components windows use loses focus of main window. making use of arrows impossible. Fix it.
  3. Make the download and installing run on a separate Threat so that GUI wont lag.
  4. Make installer display centered.
  5. Give an option in installer to rename the batch file.
  6. Distinguish data and view layer.
  7. Double check for folder creation.
  8. BUG. Directory path that is being displayed at confirmation sometimes goes off screen.
  9. Shared icon for installer and uninstaller with a pc in the back.

--- UNINSTALLER

  1. When folder is being opened during deinstalation it wont remove itself.
  2. Shared icon for installer and uninstaller with a pc in the back.

--- GITHUB

  1. More info on Global files.
  2. Give info on shell changing and that by default it is batch
  3. Add a new build to github with "--settings" feature.
  4. Provide information on how to build quail without quail.

--- OTHER

  1. Make script for automatic releases.
  2. Examples:
  • gimp
  • blender
  1. Git tag and rebuild and release
  2. Create a roadmap
  3. DEBUG_FLAG_POSTLOGGING implementation - file/buffer logging

REMOVED PLANS

  1. New type Secrets / Defines - How to tell the new user what specific constant he is missing?

Instead provide a system for dimming highlight meaning that a constant is missing. This also means that no error have to be thrown during that operation as it is doing now.

  1. New feature 'groups' e.g. "cmake_remove" -> make it so user can match with "cma rem".

Instead provide new feature tags. tagging a module will force displaying it in a different color. Tags are: GROUP, MODULE, VARIABLE. Syntax: ^-name GROUP = location.