In AdvancedInstaller it's possible to customize file using the Permissions Tab of the file or folder properties dialog.
This is not available for INI files created using the INI File Dialog.
How can I customize INI file acces permissions?
As stated in this AI community posting this is not directly possible. But there is a workaround to accomplish it:
In order to customize permissions for Application Folder\myApp.ini created using the INI File Dialog, create a new physical file with the same name in your filesystem (e.g. c:\installer\myApp\myApp.ini).
In AdvancedInstaller add that file to the same folder where your myApp.ini already resides in: Application Folder in this case. Skip the INI import functionality.
Now it should look like you have two myApp.ini files in your Application Folder and you can edit all the file access permissions on the imported myApp.ini just like you do on any other files or folders.
These customizations will be applied to the installed myApp.ini on the target machine.
Related
I created an iOS app with file manager that browses inside subfolder in Documents.
The folders in app's documents are:
Settings
Root
Tmp
trash
The app's file manager browses only inside "Root" folder. Other folders must be hidden to users and inaccessible.
I want to share the "Root" folder with Files App that comes with iOS, so I added the following keys in info.plist:
<key>UIFileSharingEnabled</key>
<true/>
<key>LSSupportsOpeningDocumentsInPlace</key>
<true/>
It worked, but all of the folders are exposed, I only want to expose "Root" folder.
Is it possible to share a specific folder in Files app ?
Thank you very much.
Before using file system of iOS, Please check the usage of different directories of the iOS file system.
You can refer this link: https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html
As per above link, apple has clearly mentioned that:
For Documents Directory : It clearly says that this directory should only contain files that you may wish to expose to the user.
If you want something that should not be exposed to User, then dont use Documents directory, instead use Library directory for this.
For Library directory: Use the Library subdirectories for any files you don’t want exposed to the user. Your app should not use these directories for user data files.
Here, see the following screenshot from above link, which says about which directory to use when?
In short, keep your root directories content in Document directory and move all other directory with their content to Library directory OR Library/Application Support Directory. So, your intended purpose will get fulfilled.
I am using the SDK to build a Firefox addon. In the addon options, the user can specify a directory of images for my addon to use (these will be added to a webpage).
I cannot figure out how to obtain a list of the files in the directory the user specified (Note that I know how to get this directory using simple-prefs). I also need to know how to get a specific file.
The file I get will be sent to a contentScriptFile to add to a webpage (as a background-image) using pageMod, via worker.port.emit(...).
So my question: How do I obtain a list of files in a directory, and how to get one of those files to send to a contentScriptFile?
I have found out how to do it, using the Low-Level API io/file
After you require() it using var fileIO = require("sdk/io/file"); you can do the following:
List files and directories in a directory using fileIO.list(path), where path is the path to the directory
Read a file using fileIO.read(path), this returns a string with the contents of the file
I need to open iphone folder like photos/videos.
I need to show content of that folder to user and when user selects a file from that I need to copy that particular file from that folder to my application folder.
Let me know what APIs I need to use for that.
Also let me know whether this is feasible or not using Marmalade.
have you tried looking at the s3eImagePicker example? under examples\s3e\s3eImagePicker
Is there any way a new image upload from a PHP form sent to directory a can be copied to directory b after it has been uploaded? In this case it's not possible to alter the upload path itself or copy it during upload so I'm looking for some kind of automatic replication of new directory contents into another directory after the file has been uploaded.
Is there an automated service/script that can move the content of one directory on our server to another directory? We upload files to www.mysite.com/upload/thumb for example but need them to be moved automatically to www.mysite.com/cs/upload/thumb - is this possible without running a move_uploaded_file PHP script (I would prefer it to be done by the server because we use the same page for many different landing page functions).
do you look for copy (http://php.net/manual/en/function.copy.php)?
I cleaned up someone's style sheet for a Dreamweaver site, by editing the css directly, and now the secretary is having trouble using her old template.
Most of the files in her site reside in subdirectories of the 'upload' directory. For example, I would have expected to see the stylesheet in
../assets/css/ etc.
but in fact I'm finding it in
../upload/assets/css/ etc.
In addition to assets, I am also finding Templates and images as subdirectories of 'upload'.
Do you know why this 'upload' directory was used?
I am considering two possible approaches.
(1) Make sure everything needed is in ../upload/ and remove the subdirectories that are directly in the root directory
(2) Edit the template to remove all references to ../upload/
Note that (2) appeals to me because the file structure will be simpler; but I wonder if the client has some sort of extension in her Dreamweaver that causes everything she ftp's to be put into the 'upload' directory.
Note that so far I have copied my cleaned up css file over to ../upload/assets/ as a short-term solution. But they want to be able to make changes to their template, and add new pages, on their own in future.
Thanks.
The likely problem is how she has her FTP remote settings specified. It appears that it now points to the upload folder rather than the web root. Or, it could be that her FTP user account is tied to the upload folder rather than the web root.