I currently began a new project with processing and first started with the
processing-ide that comes together with the installation.
Is it possible to structure the project into subdirectories instead of having to put all classes into the single sketch folder? I looked at the documentation at https://processing.org/ but didn't find any useful information about how to divide projects into manageable source subdirectories. Your help is much appreciated :)
No the default Processing IDE does not support this.
Before switching to another IDE for Processing, keep in mind that Processing 3 will highly focus on creating an entirely new IDE, which "might" add this functionality.
Related
I'm working on a c# Visual Studio project I've taken over and one thing that is causing me a problem is that a package Castle.Components.Validators is installing every single resource file it has when I build for every single language it knows about. This means that in my eventual program directory I have folders for about 12 different languages. I don't want all those as it clutters things up and tbh I don't use the Validator resource files. How can I stop it including all those resource files?
Cheers,
Neil
there might be a more elegant way to deal with this Problem, but an easy one that'll work would be to add a post-build-script to your project, that deletes all the unnessecery files and folders.
Greetings
Juy Juka
Is there a list of all (or nearly all) possible issues that could stem from maintaining multiple solution files for the same set of projects? The only reason for doing so is different versions of Visual Studio.
I'm aware of the glaring issue where new projects are added in one solution file, that haven't been synced to the other. What are some others?
disclaimer: my current company is still entrenched using VS10, for mainly political reasons. so please, save the preaching about the need for having a single solution and how this is not the optimal "solution".
I've seen this done all the time, for the most part it is perfectly fine other than what you mentioned, any files added would have to be added to all of the projects. However, I would recommend you go with a make file of sorts, CMake is a very robust version but there are plenty of others. The way they work is basically, you write one script that defines how the project is to be made, then the end-user runs CMake.exe on it. It will take that script and generate the proper solution and project files for your entire project in the version of VS you want, it also supports generation of types like XCode and Eclipse solutions etc so it is very multi-platform.
I have created three different solutions for three different clients, but those solutions are for an app that have the same features, classes, methods, resolution, except for the images, XML resource files, and a web service reference, that are specific for each one.
I would like to have just one solution for all those apps, that I could open in VS2010 IDE for edition, without errors. So, when I need to build or publish an specific app, I just set the client which one I need to, and go ahead to building or publishing.
It is important to consider that XML file names will be the same, as classes and images names too. The difference will be the content, but the name will always be the same.
My intention is to reduce my effort to maintain many solutions, having just one solution to work with.
In my company, we will have more than those three clients soon, so I am worried about how to maintain that. The best way will be have just one solution and when I need to generate a new app for a new client, I have just to change/include a few things (like some resources and images) and compile to a new client folder.
Is it possible? If so how?
One option would be to have a master solution which had the following
A "Template" project that contained your actual application and all of the shared code
Projects for all of your clients
In the projects for your clients, you could have links to the files in your files that come from your shared project. Then, in each of those projects, you could add the files that are only specific to them.
With this kind of structure, whenever you made a change to your Template project, all of the client projects would be updated as well because they just have pointers back to the Template project.
A good reference for this kind of setup would be the Json.Net Code Base. There he has a solution and project for all of the different configurations, but they all share the same files.
In terms of ensuring that the xml files are named properly, you might just want to put some checks into your main application to ensure that it has all of the files needed or potentially add a check into your build process.
There are many ways you could look to tackle this.
My favorite would be to run some sort of pre-build step - probably outside of Visual Studio - which simply replaces the files with the correct ones before you do a build. This would be easy to automate and easy to scale.
If you are going to be building for many more than three customers, then I think you should look to switch from Visual Studio building to some other automated build system - e.g. MSBuild from the command line or from something like TeamCity or CruiseControl. You'll find it much easier to scale if your build is automated (and robust)
If you don't like the file idea, then there are plenty of other things you could try:
You could try doing a similar step to above, but could do it inside VS using a pre-Build step.
You could use Conditional nodes within the .csproj file to switch files via a project configuration
You could look to shift the client-specific resources into another assembly - and then use GetResourceStream (or similar) at runtime to extract the resources.
But none of these feel as nice to me!
I'm using XNA 4.0 with VS 2010. When I start a new project, a decent amount of the resources have broken links; other sites where people have encountered this problem suggest manually fixing the file paths, which works but is bothersome when I'm creating several new projects (I'm following various tutorials to learn my way around XNA). Does anyone know if there is a way to fix the underlying problem, rather than changing the file paths for each new project?
Are you trying to use Contents of other project in one solution ? Than you add to your Content Project Reference's the external Content you want to use. Jon's answer is already works fine, I already prefer Jon's answer :)
If you put your resources in the Content directory, then copy the Content directory to your new project, it should retain all the files and the links should still be good.
Not sure what the problem is exactly, possibly provide more information on the problem so that we can get a better idea of what is wrong.
I'm pretty new to Sphinx, documenting my project on a server. Now a co-worker sees what I've been up to and she wants to do the same thing--document her project on the same server.
The projects are not related (they don't belong in a single TOCtree) and I don't know how to help her. Can I configure sphinx to build separate document trees? Is it as simple as making two copies of the Makefile and have it set different source/build directories?
thanks,
--Tim
Yes, I think you want to treat them as separate projects. For that you should just copy the current build tree as you stated, and edited the config.py file. The other options is just to start from scratch by running sphinx-quickstart.
Also, keep in mind that you can reference topics between the two documents by using the Intersphinx plugin.