Questions about CodeAssist about codeassist HOT 3 CLOSED

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

from codeassist.

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

from codeassist.

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 :(

from codeassist.