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

Questions about CodeAssist #44

Closed
almr0 opened this issue Dec 11, 2021 · 3 comments
Closed

Questions about CodeAssist #44

almr0 opened this issue Dec 11, 2021 · 3 comments

Comments

@almr0
Copy link
Contributor

almr0 commented Dec 11, 2021

I'm sorry that I combined everything into one question, but I think it will be more convenient this way.

Questions:
— Will CodeAssist be published on Google Play?
— Will real error output be added when editing code? So that when you click on the error code, an Alert with error information is displayed. I also noticed that sometimes the text is not highlighted the first time and the Analyzing window appears ... (sometimes it interferes)

  • Will cloning of projects from Git repositories be added?

Requests:
— The same wish about allowing the project to be imported from a shared repository. Storing projects in the application folder is not very convenient, because the project directly depends on the existence of the application on the device + you will need to copy the existing project to the CodeAssist folder, well, at least inconvenient.

Thanks, that's it for me. I hope you pay attention

@tyron12233
Copy link
Owner

  1. Yes, once the project reaches beta.
  2. Currently if you long press on a code with an error, a toast will show with the current information about the error.
    2.5. This is a limitation of the code editor library, there is no support for background highlighting yet so on large files, it waits till the analysis is complete and then highlight the file.
  3. There are plans for adding git support, but its not a priority right now.
  4. These are how android apps are supposed to work now (Creating directories on the root storage and leaving files upon uninstall is not recommended). On android 10 and above, android introduced FUSE which severely impacts performance of operations with java.io.File. During compilation, a lot of reads and writes are performed by the compiler which will be slowed down running on a FUSE mounted storage. The only place where FUSE isn't mounted and the user can still access is the app's external storage directory

@tyron12233
Copy link
Owner

For more info about FUSE take a look at this link

One example of this affecting performance is with AIDE if you notice its nearly impossible to edit files smoothly on android 11

@almr0
Copy link
Contributor Author

almr0 commented Dec 11, 2021

  1. Yes, once the project reaches beta.
  2. Currently if you long press on a code with an error, a toast will show with the current information about the error.
    2.5. This is a limitation of the code editor library, there is no support for background highlighting yet so on large files, it waits till the analysis is complete and then highlight the file.
  3. There are plans for adding git support, but its not a priority right now.
  4. These are how android apps are supposed to work now (Creating directories on the root storage and leaving files upon uninstall is not recommended). On android 10 and above, android introduced FUSE which severely impacts performance of operations with java.io.File. During compilation, a lot of reads and writes are performed by the compiler which will be slowed down running on a FUSE mounted storage. The only place where FUSE isn't mounted and the user can still access is the app's external storage directory

Thanks for the answers! Could you also please pay attention to this problem: #41

I almost lost my project :(

@almr0 almr0 closed this as completed Dec 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants