Is there any easy way to sync the group structure inside Xcode 4 and the actual folders structure in the filesystem?
I have read that some people create new folders on Finder and them drag-and-drop into Xcode, but that sounds like a hack to me. I wish there were a configuration/setting where I could set to make logical (groups in Xcode) and physical (files in filesystem) structures match so that I would not have images, my code, external code, plists, pch, lproj, etc. on the same messy folder.
I also tried changing the location on the Identity and Type panel in View -> Utilities -> View File Inspector and it just made me more confused.
Unfortunately not, the way you mention is what I do.
Its not great but it works.
Just place the file in the folder and then logically group it in XCode.
Automatic Folder Content Inclusion
For automatically inclusion of files and folders, add a folder reference.
You'll see this as a blue folder in your project and now anything you place in there is automatically added to the project.
Related
In a LabVIEW project, when should I use virtual folder and when should I use auto-populated folder? Why?
You don't have to use either. Your project could just have a main VI and have everything else handled automatically as a dependency.
Personally, I would suggest viewing the project window as a logical organization tool for your work and say that you should only put the things you actually need or want to access from there.
The conclusion from this is that you should generally not use auto-pop folders, as you don't need that. If you want to see the disk hierarchy, you can go to the files tab in the project window.
You can use virtual folders for your logical organization. For example, you might want to have support files for your builds (like an icon for the EXE) and putting those in a folder cleans up the project. Another example might be that you have a library (like a class) and you want to group subitems in that library into some logical groups. You can create virtual folders inside that library.
The one place where I do use auto-pop. folders is if I have some dynamically loaded VIs or another list of files which are placed in the same folder. Adding that folder to the project as auto-pop allows it to be handled cleanly.
It is your choice. How do you want to manage your files?
For myself, the answer is “never ever use auto-populating folders.” Those folders do not play well with libraries or classes (by design, not because of a bug), and they make it hard to remove items from a project but keep the files around (because deleting from the folder is automatically deleting from disk). There are plenty of others who agree with me. But they are nice for simple apps that don’t use any modern software design tools.
the thing is, I want to open folder from "hellobill-retail-service"
and "hellobill-retail-web/view" at one go
is it any command to do it? as long as I know it can only select multiple folders from same hierarchy...
I know I can do it separately, but can it done with one go? I dont want to make my project folder histories dirty because it contains all my important projects
or, alternatively, can we some kind like, bookmark projects (along with all opened files) because file/reopen project is like temporary right?
Here is my htdocs folders...
here is inside my hellobill-retail-web folders
selecting multiple folders from same level
one of my projects
There are several project packages (e.g. project-plus or project-manager) that can save and restore your current projects, even when consisting of several folders.
I opened a project "ProjectOne" in atom and then added another project folder "ProjectTwo". When I cmd + t to look for a folder, it always looks through ProjectOne even though I have that folder tree folded and ProjectTwo tree opened. How do I look through ProjectTwo and switch back and forth between the two projects?
Each Atom window has currently has one project. If the two folders are added to the same project (that is, they are both added in the same Atom window), then the file fuzzy finder will search through files in both of them (because the fuzzy finder searches through the entire project, not just individual folders added to the project).
For now, if you want to search through individual root folders, you'll need to either open them in different Atom windows, or use a plugin that behaves the way you want it to.
I've been importing a number of project folders into Apatana 3 and some of them are stored on disk in folders with identical names. It's not really easy for me to change the names of the folders themselves, as they are the same project on different servers (one is a local copy, the other a copy on a development server).
I tried importing the folder as a project and setting the name of the project to FOLDERNAME - local or FOLDERNAME - dev (depending on the location) but all that seems to do is create a new folder with the project name, rather than importing the specified project!
Is this normal behaviour and is there a way around it?
After a bit of fiddling I managed to find a solution, hopefully this will help anyone who comes across the same issue:
When the Aptana workspace is set to the parent directory of a project, Aptana renames the project folder to match the project's name. By setting the workspace to a different folder the project can be renamed without altering the folder name on disk.
I'm not entirely sure why Aptana does this, but changing the workspace does seem to solve the issue.
You should just be able to import the project, right-click on it and rename it. The project name does not have to match the folder name. It may be how you are importing them...please follow the steps here: https://wiki.appcelerator.org/display/tis/Importing+an+Existing+Project
I noticed that Eclipse (Flex Builder) generates hundreds of metadata files. Should I check them into my source control? They seem necessary, because if I delete them Flex Builder just opens up an empty workbench...
Some of these files plainly do not belong in source control (like .history files and some cache files). If I delete them my project opens up again without a hitch. But the list is long and there seem to be no clear separation between folders that contain files that belong in source control and those that do not.
I can't just shove them all into svn, even if I were to ignore the inefficiency, because Eclipse generates new ones constantly, with different names, which in turn also seem to be crucial for the project to load.
Can someone please enlighten me?
Don't check in the hundreds of metadata files. If you want to be able to check out the project in a way that it can just be imported, then check in:
.actionScriptProperties
.project
.flexProperties
And "html-template" and "libs". As Christian says, any resources you depend on. I usually keep those as separate Flex Library projects though.
I generally put all of my source code under src, and I check in src and all of its descendents. If my project relies on any external dependencies (e.g., the Cairngorm SWC, as3corelib, etc.), Flash/graphical assets, stylesheets, or resource files, I check those in, too. But I don't check in any generated (bin-*), intermediate or IDE-specific stuff, because having that stuff in source control doesn't seem to provide much practical benefit, and in my experience has only caused me headaches; in general, I check in the most minimal set of whatever I'd need -- given a clean FlexBuilder installation (or none at all -- for example, if I were compiling instead with mxmlc or compc) and an empty project -- to build the project successfully.
Most of the eclipse project files, like .project, .properties, everything in .settings, can go into your source control. As long as the files don't have user-dependent settings like file paths or local urls, you should be fine.
One method we use is creating local property files that don't get used in SCM, but are included in the ones that do. I.E an ant build file including a local.properties file which has local metadata.
What if the .actionScriptProperties, .project, or .flexProperties have user-dependent stuff in them? Typically this will be url or path information. What's the best practice way of externalizing this? I tried creating path variables, but this only works obviously for paths. Not for things like hostname, etc.