I am working with the deployment feature to easily upload files to a server. So opening a specific project folder for which I have already set up deployment gives me the opportunity to work with the project files instantly and also upload them without any problems.
The problem is with opening the right folder. When setting up deployment for a project you choose a folder as the 'root' folder for this one project and when one wants to load this settings he has to choose the right folder when opening a project. Sometimes there are some differences which folder is chosen as root (most of the time the folder is 'domain', but sometimes it's another folder).
When I now want open a project folder to work with the files and have the deployment ready, I can not recognize in the popped up window which folder is the right one. Friends of mine (win8/Linux) tell me that they have a phpStorm icon instead of the standard folder icon.
On the other hand I told OSX to show me the hidden files on my system which results in following:
As you can see Finder shows me the .idea file, so at least I know the folder I am at right now is the project folder. But I in the future I don't want to check first in Finder, which folder the right one is and then open phpStorm to open it there.
I hope anybody understands my problem :). Thanks for any tips, really annoying topic.
Update:
Maybe the problem comes with the fact that phpStorm on OSX uses Finder as the explorer when trying to open a project folder. The explorer on Windows looks similar
I posted on the jetbrains helpforum, the 'answer' was:
Relates to: https://youtrack.jetbrains.com/issue/IDEA-100279
Duplicates: https://youtrack.jetbrains.com/issue/IDEA-131303
Nothing anybody could have find out themselves, there does not seem to be a better answer than "give the folders related to PHPStorm the right icon, manually".
I have made a .dmg file for my application but, when I open up my .dmg file it opens with the sidebar included. It most of the applications I have seen, the .dmg file opens up a new Finder window without the sidebar. How would I acheive this?
You can control that by creating a .DS_Store - This is a "Directory Services" Store file, which is used by Finder to setup the position of the various icons in the folder, etc. The problem is, the format is very poorly documented. However, there is a workaround: Open up your to-be-in-DMG folder prior to packaging the DMG, make it so that the sidebar is hidden, and then create the DMG. When the DMG is created, it will contain the .DS_Store hiding the sidebar. You can see a bit more on this in https://apple.stackexchange.com/questions/69467/consequences-of-deleting-ds-store
The easiest way to do this is just to pay for one of the utilities out there that builds disk images for you.
I use dropdmg, but there are plenty of others. (I'm not affiliated to any of them)
I added a folder to my project in XCode and called it Themes, which will be used to store themes for my iPad app. Under that I have Red,Blue, and so forth.
They show up in XCode. But when I look at the physical folder, there is no Themes directory (and obviously anything under it).
Why not? Where did it go? How can I store images (which may have same names) under different paths (themes)?
Thanks in advance
XCode does not create "folder", it creates "groups". Groups are logical organization of your files, independent of the file system organization underneath it
If you want to actually have a folder, easiest way would be to create one on the file system first (through Finder), and then drag it to XCode's project navigator. When a confirmation window pops up, leave the default settings ("Copy items into destination" and "Create groups for any added folders")
This will import the folder and all the files in it, however it will not auto-import newly added files to the folder after this (you'd have to manually add them).
If you do want to auto-import newly added files from the file system's folder to this group in XCode, instead of using "Create groups for any added folders", change to "Create folder references to any added folders"
When I started my project I was happy to use Groups in Xcode rather than literal folders: Since I'm using the browser in Xcode to access everything, stuff was nicely organized and I was happy.
However, now that the project is about to be shared for version control, the project folder itself is a horror show for those trying to scan it via a terminal, about 300 files, over half of which are graphics.
I'm trying to now reorganize things, creating real folders and importing them into Xcode. Unfortunately Xcode doesn't let me work with them the way it does with groups. For example, if I right-click on an actual added folder (blue, not yellow) and choose to add existing files, it doesn't actually put them in that folder, it puts them in its root.
Similarly, I can't move a file from a faux-folder (a group) into a real folder: Xcode doesn't consider the real folders to be valid places to move stuff to.
What am I missing? How can I convince Xcode to let me use the folders the way I use groups? There's an answer here to a somewhat similar question, but it doesn't actually solve my problem since I'm working with existing files.
A modern (and dead simple!) approach for 2017 (Xcode 6, 7, 8, and sometimes 9, since it does it automagically some of the time):
If you're moving a bunch of files into a new folder and are keeping the child hierarchy, it's actually a lot easier than moving each file individually:
Create new groups in the Xcode folder tree and organize your files into them however you like.
Create a matching physical folder tree in Finder and organize your physical files into them to match what you did in step 1.
All the references in Xcode should now be red (that's OK!).
From the Identity and Type manager, select the Group in Xcode that you want to relocate, then click the folder icon from the info pane:
In the Finder selection dialog, locate the equivalent new folder you created for this group in step 2. All the files inside that group will now be automagically rediscovered!
Isn't that nice? At most you'll have to repeat these 5 steps once for each new group you've created (which beats relocating each file individually!)
Bonus Points!
Say you accidentally screwed up the move and now a bunch of your files are red and can't be found: select multiple files that are broken, and using the same folder icon in the screenshot from step 4, find the correct folder that contains these files and they'll automatically resolve the missing paths.
FURTHER EDITED JUNE 2017: Xcode 9 does this automatically, no special effort required. This answer and Brandon's only apply to Xcode 8 and earlier.
EDITED DECEMBER 2016: Brandon's answer below is a better solution now. Back when this answer was created in 2010 this was the only option I could find. I now suggest Brandon's answer, below.
It turns out that moving files into real folders is certainly possible, though not as simple as it should be.
I got the basic information from a question here, Xcode organising files and folders (core data model objects - iPhone), but learned important things along the way.
##The Process
Moving the files is a two-step process with multiple sub-steps:
Tell Xcode where you want the files to be:
Right/Control-click on the file or file group that you'd like to move and choose Get Info from the contextual menu that appears. The Group Info or File Info window appears.
Click the Choose button on the far right side of the window in the Path area. A dialog box appears.
Navigate to the folder you want the files to be moved to. Create a New Folder if needed. Click the Choose button in the bottom-right corner of the dialog box, then close the Group Info/File Info window.
The names of the file/files in the group will turn red to indicate that Xcode can't find them in the place you specified.
Move the actual files
In the Finder (or Git) move the files you selected in step 1 into the actual folders you want them in.
Switch back to Xcode. The files/groups should all have turned black again. If any are still red then you've missed moving something to the right folder.
##Tips
I learned a couple of important things while adjusting the ~300 files in this project:
Some files refuse to move this way; that is, when you navigate to the new destination the Choose button is disabled, as is the New Folder button. The solution, though I don't know why it makes a difference, is to first use Xcode to put those files in a Group (right/control-click the files and choose Group, and give the group a name) and then move the group to the new location. After you're actually moved the files in the Finder you can remove them from the group (by dragging them into the new parent group/folder and deleting the group).
Stop and build every few minutes, after completing step 2 for a number of files. The build will tell you if you've screwed anything up so far, making it easier to go back and fix it before you've done too much damage.
If the files won't move to where you want them to — I had a devil of a time moving some files that had been created early-on in the Classes folder — you can simply drag them out of their old place in the finder to someplace handy like the desktop, delete references to them in Xcode, and then re-import them via the right/control-click Add Existing Files option.
If in the past you've used Xcode to delete references to files without also moving them to the trash in this project, you'll find files that don't have to be moved but at just sitting there. Be careful that you don't do what I did, confusing the names of a current group of files I was moving and the older, no-longer-linked files, insisting that Xcode import them because you thought it was being dense.
In Xcode 5 or Xcode 6:
Create the folders that map to your Groups in Finder
Move the files into those folders in Finder
Select each file that is red in the Xcode sidebar on the left
Click the button "Show/Hide Utilities" to reveal the right sidebar (see figure)
In "Identity and Type", click the tiny button and select the file location (see figure)
Cheers.
I've found the most reliable way to work around XCode's appalling design here is to organize ALL your files in Finder, for two reasons:
Finder doesn't make "mistakes", unlike XCode's GUI
Once things are organized in Finder, you can drag/drop entire Finder folders into XCode, and ... it does exactly what you wanted, with no effort
Even when moving existing XCode files around, it is quicker to do this:
Select the files in Finder
Create a folder in Finder for them
Drag/drop them to the folder (automatically Moves them)
Drag/drop the Finder folder into Xcode (automatically: creates the Xcode folder, adds every file in the Finder folder)
cmd-select every "red" file you now see in Xcode (because you moved them) and hit the delete key
NB: I never use the "create dragged folders with sub-groups" option, because in XCode 3 that was often hopelessly buggy and could corrupt projects. Apple clearly (IMHO) does NOT use this feature internally, otherwise it would never have been allowed to be so buggy; if Apple doesn't use a thing, it's generally not safe to use it either - they aren't good at testing :)
There is a simple to setup and use Command Line Tool - "synx"
available in github that do exactly what is needed here.
It reorganizes Xcode project folder in finder to match Xcode groups in project.
You can find it here:
https://github.com/venmo/synx
UPDATE:
XCode 9 supports this feature by default. So, no need to use other tools anymore!
Xcode 9
It seems Xcode 9 now supports it by default. When you move files from a group to another, the file will also be moved from the old folder to the new folder. This was announced in WWDC 2017.
I used the following tool to achieve it.Organize Folders in Groups Xcode
--no-default-exclusions
I'm usually move files to the directory directly in the Finder, then fix the files with red-color names in XCode in their "Get Info" dialog: click the "Choose..." button and select file's new locatoin. That's the first response when I want to move files in XCode, and it works.
As of Xcode 4.5 when you drag in a folder structure it is automatically turned into nested groups in the Project Navigator. Then, if you look on disk (e.g. right click and choose Show in Finder), the folder structure has been retained.
I found trying to fix things from an older project was just a pain. It turned out much easier to just delete these files and drag them in again.
To move a folder in xcode 4.5 I just...
Delete the files/groups from xcode and select "Remove Reference".
Go into finder and move the folder/files as needed.
Once done I go back into Xcode and choose File->Add Files to {ProjectName}.
Make sure "Copy Items into Destination Group's folder (If needed)" is checked
Make sure "Create Group for any added folder" is checked
Make sure "Add to Target" is checked for your project
Easiest technique for XCode 8....
Assuming you have files A,B,C in a logical group, but want them moved into a folder on your hard drive.
Create a destination folder via Finder
Add the folder in XCode (File -> Add Files ) using the Options pane to select a Folder Reference (not a group)
Drag files A,B,C from the (old) group to the (new) folder reference in the project navigator. XCode will move the files into the folder, both in the the project, and on disk.
Done.
On XCode 11 (I just validated this on XCode 11.6), you can select the files you would like to move under the project navigator, right click on the selected files, and click "New Group From Selection". This will create a folder on disk and move the files appropriately.
I was testing an application called iTrash during which it seems like i have deleted the
"Contextual Menu Items " folder as its no longer present and i can no longer right-click
anywhere on my Snow Leopard. I don't have any backups. Can someone tell me how i can recover
that folder or if i can download the files needed to have in that folder (just the original
ones) to regain the Right-click again?
I managed to get around the problem by reinstalling the 10.6.3 update and also by replacing the Track preference file .plist using an app called Pacifist which allows you to look into MacOSX installation Disk or image and search and extract individual files, in my case the default .plist file for the System Menu Trackpad. glad to see the back of this bizarre predicament.