We have numerous developers and we all tend to have a slightly different version of the JDK (whatever was latest when we last updated). We're all 1.8, but the x in 1.8.x.x is all over the place.
Is there a way we can define the JDK to use in our project so it is defined in files that are not part of the project and therefore not checked in? And more importantly, are not overwriting our individual choices when pulling the latest?
Just name your project/module JDK 'JDK', everyone then can point it to wherever they want.
Related
My application is compiling against Windows Creators Update (15063), but is supposed to run on a minimum version of 10586; however, some colour resources we used seem to be missing on old versions.
The exact whereabouts of failing resources are unknown (as the incompatible resources are), so temporarily, I want to give a global fallback value to eliminate crashes on old SDKs.
Is there any programmatic C# or automatic XAML way I can do it?
You could check whether certain features are available at runtime. There are many ways how to achieve that. You can read more about how to write version adaptive code for example here and here.
In eclipse I had all of my projects located in the sidebar by default.
Here's what I have:
Here's what I would like:
I find it hard to believe that you can't have more than one project in your sidebar but I can't find away to add multiple projects.
Try this
https://plugins.jetbrains.com/plugin/7897
a plugin for intellij idea which will allow you to work on multiple projects.
#sai rao gutta has a neat suggestion here, I'll have to look at that plugin.
I recently made the switch from Eclipse to Idea and this was a stumbling block for me as well. The way I came to understand the Idea paradigm was to consider an Idea Project similar to a Workspace in Eclipse, and a Module in Idea similar to a Project in Eclipse.
Some of the projects I work on are libraries (usually sandbox type projects) where I want to see instant use of Project A as a dependency on Project B without having to run builds and whatnot. Or, sometime I just want to use Idea as I did Eclipse and just keep a few random projects available. I created an Empty Project in Idea, then added Modules within. The end result gave me the ability to sandbox a library project and a consuming project in one space in a simple way, as well as give me a space to work with whatever random projects I had in Eclipse.
We know all that JGraph is a very powerful graphic library and now we are in version 6 (JGraphx).
Me I have an application (by the way I am newbye in JGraph) coded in JGraph 5 and I want to migrate it to Graphx.
Is there any tut to know what is the main differences between these two versions?
That migration, is it easy to do (in general)?
JGraph (the last version of which was version 5) and JGraphX (which was originally going to be called JGraph 6) are completely different code-bases. JGraphX was a complete rewrite from scratch, which is why we made the naming change to avoid the idea you could upgrade from 5 to 6.
So no, there is no migration route, you'd need to re-write your part of the application that interfaces with JGraph(X).
Just downloaded and installed netbeans 6.9. At the first run, it asked for importing settings from netbeans 6.8 (which is nice). But after using it for my current PHP project for a while, I found this new version sucks. Here are some problem:
"Refactor->Rename" always gives me "The Rename Refactoring cannot be applied
in this context". If I press the Ctrl+R, the whole IDE halt!
Most of the time it shows "Checking for external changes" in the status bar.
Some plug-ins that exist in version 6.8 are not available in version 6.9
Anyone encounters the same problems and know how to deal with them?
I've got all the issues you wrote about. I had to split my project into 3 different projects just to make it work reasonably fast (too many files kills 6.9 apparently).
Also, the auto-formatter sucks. Half of the options don't work at all.
And who thought it would be a good idea to add a spell checker to a &^(%£ code editor?!?!?! Worst. Idea. EVER.
I've been using Eclipse for the last 2 days.
+1 to version 6.9 being total trash.
I'm running 64bit Netbeans (PHP) on a Mac.
Yes to number 1. Selected from the menu and keyboard.
No to number 2. It does state that once in a while (as in rarely).. though that might depend on the project really.
Number 3; which plugins you looking for?
I want to update/upgrade the standard Leopard install of Sqlite3 to >3.5 to use the new sqlite_xxx_v2 methods from a Cocoa project.
I can't seem to find any information on how to do this. Does anyone have any tips or a site that outlines the update procedure.
Also is 3.5+ supported on the iPhone. I understand it's embedded so shouldn't be an issue...
What you want to do is grab the amalgamation sources from http://sqlite.org/download.html . Then just compile that into / add it to your project. You don't want to replace the system sqlite- that'll have unintended consequences in other applications. Plus, I'm pretty sure the system sqlite isn't a stock sqlite... Apple has probably made their own modifications to it that core data relies on.
You can read up on the amalgamation stuff here: http://sqlite.org/amalgamation.html , but in short: '''The amalgamation is a single C code file, named "sqlite3.c", that contains all C code for the core SQLite library and the FTS3 and RTREE extensions'''
I'd also suggest not using the sqlite calls directly, they weren't designed to be used that way (says the author of sqlite). Instead, there are a number of cocoa wrappers out there, including fmdb: http://code.google.com/p/flycode/source/browse/trunk/fmdb/ (which I wrote) :)
-gus
You don't really want to upgrade the system version of SQLite on Mac OS X. The reason is that all Mac OS X software is qualified against the versions of the packages that it includes, as built by Apple's build process. Installing a different version of a package, or even building the same version yourself but doing so slightly differently than Apple does, may result in a system that behaves unexpectedly.
Finally, if you embed a newer version of SQLite — or any Open Source library or framework included with Mac OS X — into your own application, you should be sure to integrate the Darwin changes for it from Apple's public source site. That way you can be sure you'll get as close to the same behavior as possible from the library you've built yourself as the version Apple ships, which is especially important when it comes to functionality like file locking in databases.
I don't believe i've updated my version, but it's currently at 3.4.2, and i'm able to use the new methods with the current version.
And i'm running 10.5.5 with the latest (public) iPhone SDK.
It would likely be easier to just drop the library into your project and link it in from there.