flone-dnb / fbugreporter Goto Github PK

Because in order to use FBugReporter you need to have Rust installed we can have install scripts written in Rust instead of Go. This will eliminate the need to install additional software (Go).

P.S. Don't forget to update README with new install instructions.

Looking at the server code, it seems that a big part of it (handling connections, encryption, reading from sockets) could be removed if you would use a web framework (such as rocket or actix).
This could improve code readability (less code, better structured), security/stability (replacing custom implementations with tested ones) and perhaps even performance. Also using a more standard way would make it easier to grasp what's going on and expand the functionalities.

What do you think? Or is there a reason why you chose to not use a web framework?

We should also "officially" support:

• Unreal Engine,
• Cryengine,
• Unity.

And also provide a way for custom game engines to integrate FBugReporter (manually).
By "officially" I mean being able to use scripts from the install directory to automatically set everything up.

Since Druid's development is becoming slower and slower, moving to Iced will resolve some minor GUI issues that we currently have, and additionally will help up support the GUI side with less issues due to the fact that Iced development is much faster and it already has more features than Druid.

I'd suggest using a logging crate, to reduce boilerplate code. Preferably one that uses log facade, such as env_logger or flexi_logger. I know flexi_logger can be customized a lot (formatting, where to write, mirroring to file and stdout), but other crates probably also have such functionalities.

This would also handle logs from libraries that are logging using log crate, which currently are being ignored (if there are such crates in your dependencies).

As it was suggested, it would be a great feature to have an ability to attach a screenshot.

Godot seems to have some functionality to capture the screen, but I don't know if Godot has functions to save it in JPEG format. So this would require us to compress the image. Plus, we should also resize it to 720p if it's big, so that it wouldn't be that bad for storage.

On Linux it's a standard to use XDG Base Directory specification to decide where files should be stored.
For example, config files would be stored in $XDG_CONFIG_HOME and log files in $XDG_STATE_HOME.

This can be easily achieved with xdg crate.

Allow to specify path(-s) to attach file(-s).
Allow to specify key-value pairs with developer info.
Set maximum attachment size to 5 MB by default, allow changing in server config.

Allow reporter to be used to send reports to other bug reporting systems (and similar issue tracking systems) instead of our server/database, such as:

• GitHub issues (supports report attachments?),
• GitLab issues (supports report attachments?),
• Gitea (supports report attachments?),
• YouTrack (supports report attachments?),
• Trello (supports report attachments?).
• Mantis Bug Tracker (supports report attachments?),
• Jira (supports report attachments?),

Leave a comment with your bug tracking (and similar issue tracking) system if it's not listed here. Will see how long it will take for me to implement this. :)