We're using JDeveloper at work and we are using a library that contains 15000 files inside its parent folder (ExtJS). Every time we want to look for something via the search->find in files it goes on and searches through the whole project including that library. How can I remove that folder from the search items?
Check the working-set feature to see if it helps - https://blogs.oracle.com/jheadstart/entry/jdeveloper_11g_working_sets_ho
Related
So I have a word template that I am trying to populate within my wpf application. It works fine during development. However, when I try to edit the file after publishing/installing the application it no longer has the folder/files that were used in the development process.
What steps do I need to take to have files present after installation to manipulate, create, or delete files?
Right-click the file in VS Solution Explorer, then in file properties set Copy To Output Directory to Copy Always
Add that template as content in your solutions. You will find this from properties.
I building an installer with visual studio. To include my files I use Heatdirectory in the wixproj-file.
Heat is including all the files (including the hidden files).
That's what I want.
But: When files get copied to the target-system all of them are marked as visible. Is there any option to keep their state? I could not find anything.
greez
You can set the hidden attribute for a file when its copied by the installer. This makes the file hidden. Take a look at:
http://wixtoolset.org/documentation/manual/v3/xsd/wix/file.html (Look at the attribute Hidden)
However, I do not see an easy way to set this attribute on a file element when the file is being harvested. The only way I know of is to transform the generated output from heat as described at:
http://codedmi.com/questions/1552266/how-to-systematically-set-readonly-attribute-to-files-harvested-using-heat
Because I could not find a direct way to archive my goal I created an Custom Action and a (Pre-Build-)C#-Program.
Before building the Installer I search for hidden files and folders and create lists for them with a C#-Program.
After the files have been installed a custom actions marks these files and folders as hidden.
I have Website configured in CQ5 AEM. I am trying to move some files to a folder on the same location. I have large count of files, each and every i should select and click on move to move files.
Any suggestion to move multiple files to a folder in the same location in adobe experience manager. In spent 1 day to send 150 files to a folder. I have almost 10000 files to move. Please suggest me to reduce my work.
I got some reference
http://docs.adobe.com/content/docs/en/cq/5-6-1/wcm/page_create_edit.html
but it is showing for 1 single file using move option.
Appreciate and Thanks in advance. It helps me alot.
If it is really about files, then you can try to connect to cq instance via WebDav and operate with files like in any file manager (but it does not work for me with pages and some other node types).
Otherwise, I would suggest to create package in package manager with all files (you want to move), download it, unzip, move required files to another folder, pack it back to package, upload and install. After that you can delete files in old location.
In second case, you, probably, will have to modify filter.xml according to new files' location.
I have a web-app(browser based) which needs to access a folder full of icons that resides outside the web folder.
This folder MUST be outside the web folder, and would ideally exist outside the project folder all together
however, when specifying the path to the folder neither "../" or making use of a symlink will work
when the page attempts to load the image I always get
"[web] GET /Project|web/icons/img.png => Could not find asset Project|web/icons/img.png."
however I set the image source to "../icons/img.png"
how can i get dart to access this file properly
PS: I attempted a symlink to another part of the filesystem (where the images would be kept ideally) however this did not work either.
The web server integrated into DartEditor or pub serve only serves directories that are added as folders to the files view. When you add the folder to DartEditor you should be able to access the files. This is just for development.
You have also to find a solution for when you deploy your server app. It would be a hazardous security issue when you could access files outside the project directory. Where should the server draw the line? If this would be possible your entire server would be accessible to the world.
Like #Robert asked, I also have a hard time imaging why the files must not be in the project folder.
If you want to reuse the icons/images between different projects you could create a resource package that contains only those images and add them as a dependency to your project.
If you want a better answer you need to provide more information about your requirements.
If you wrote your own server (by using the HttpServer class) it may be possible to use the VirtualDirectory to server your external files.
Looking at look the dartiverse_search example may give you some ideas.
You could put them in the lib directory and refer to them via /packages/Project/...
Or in another package, in which case they would be in a different place in the file system. But as other people have said, your requirement seems odd.
What I want to have is some sort of file tree that people can interact with and download songs or folders of songs. I kinda got started with a file listing PHP script (which you can see here) but it requires me to copy the same index.php to every individual folder. I would be okay with this if I knew how to copy the same file to every subdirectory in the archive.
What do you guys think? Any ideas?
What you do is to use your webserver to browse the file hierarchy. But what you want is to use your script (the index.php). So instead of creating links that point to a deeper place in your file system, create links that point to your index.php, but add a parameter that tells the script the (relative) folder. Beware that you have to verify that only files can be shown that you actually want to make public (i.e. no files above your "entry" directory).