-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify Project name and path #139
Comments
Can project path be any path anywhere? yes, but keep in mind that if it's outside of the OF folder, the project may use fixed paths, so that if you move the project or OF the paths may break. If it's inside of the OF folder, the paths will be relative. Should project path stick to the general practice of being ../../../ away from the root? any distance away from the root should be fine... ie, ../../ vs ../../../../ is ok. Will project name generate a new folder for me as well (in which case do I have to point it to ../../ away from root)? Or will it just dump files into a folder I make and then point the project path at that folder? not sure I undestand this question. if you make project name blah, with path: /Users/zachlieberman/Desktop/of_v0.9.3_osx_release/apps/myApps it will make a folder called: /Users/zachlieberman/Desktop/of_v0.9.3_osx_release/apps/myApps/blah with a project (xcode project file) called blah inside it that makes a bin named blah. |
Makes sense, some of that is new information to me. Re: the last question that was a bit convoluted, I was asking if instead of what you mentioned it did, if it did something like: I would make a folder called: Then I'd set project name to blah. I would expect it to dump project files in: and not: I guess my overall concern/confusion is what would be your suggested/preferred design path? Like if this was the first thing someone was using in oF was the project generator, what would you want them to do. I don't think that direction/best practice is present currently, which for some people may be ok, but I think for some people it could lead to confusion and frustration. I think the solutions I mentioned above, any of them could work. Thoughts? |
i've always found the separation between path and project name confusing too but then most ides do the same or even more convoluted. perhaps something that would make it clearer would be to check if the name of the project is the same as the last part of the path and in that case don't create the extra folder. I actually thought we were already doing that |
I think maybe we can simply rename "path" to something like "containing folder" ? I think it's helpful to think of path more like that -- a folder which contains your project -- rather than to add auto smarts (I can think of instances where I might want the containing folder and the project folder be the same, ie, blah/blah/blah.xcproj) |
makes sense, also what @elburz suggested initially, having some kind of help tooltip that shows the short explanations you've posted here would be really helpful |
Context: Have experience with oF, use VS2015 with the oF plugin normally , new to using the project generator.
Problem: I find the project name and path combination confusing
Questions I ask myself that I can't easily answer:
Possible solutions:
The text was updated successfully, but these errors were encountered: