You might be able to move storage by setting ios.newStorageLocation=false 
which will place stoage under the caches directory. Notice that it might 
have adverse effects on some things but I doubt it will impact you much.

1. It might be recreated since things like Preferences use storage and we 
use Preferences internally. 
2, 3. Not at this time
4. I think that will work. Didn't test this though
5. Such as? We have the app home directory which we use when you open a 
file association etc.
On Friday, June 4, 2021 at 9:45:03 AM UTC+3 P5music wrote:

> Ok,
> I meant for new projects or for developers who are aware of it, before 
> publishing the app, like me.
>
> However, I would like to understand if some other solution is available 
> for my project.
> My app does not use the Storage at all. It just has two data files in the 
> Library/Application Support folder, and uses the Documents folder. Both are 
> managed with the FileSystem access.
>
> 1 - Can I delete the cn1storage folder? 
> 2 - Can its re-creation be prevented?
> 3 - Can I hide the folder? 
> 4 - Can it be deleted by mistake but that being harmless, so I do not care 
> if the user deletes it, even when it is hidden?
> 5 - What about the other CN1 content that can be seen in the Documents 
> folder?
>
> Regards
> Il giorno venerdì 4 giugno 2021 alle 03:09:24 UTC Shai Almog ha scritto:
>
>> We can't change something dynamically as it will break compatibility. You 
>> can submit an RFE or pull request which provides the different storage 
>> location option as an API or configuration.
>>
>> On Thursday, June 3, 2021 at 4:10:05 PM UTC+3 P5music wrote:
>>
>>> Can the cn1storage folder be under the Library directory on iOS instead 
>>> of Documents for new maven templates or as an option for existing projects 
>>> (at least those unpublished yet like mine)?
>>>
>>> My app exposes the Documents folder to the user.
>>> The user doesn't want to see other content among the "documents". It 
>>> also can be accidentally deleted 
>>> even if it is made not visible, but it could be an option, I think. I 
>>> saw also other files there, as for example a sort of package.
>>> There is no technical reason to leave it in the Documents directory, the 
>>> Library folder is under control of the app. 
>>>
>>> My app also created Library/Application Support, that is private to it.
>>> Also other folders can be created under Library, that are different from 
>>> the Application Support one (please do not put it there).
>>>
>>> Regards
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/db0a8c9b-0527-4fcf-a9fc-f838ea7e2daan%40googlegroups.com.

Reply via email to