http://docs.structuremap.net/ seems to have very old examples that use deprecated members.
Is there a place where I can find up to date StructureMap doco ?
I seem to have found some of the newest documentation for version 3.1 at
http://structuremap.github.io/
It looks like it has most of the basic information is there. Some of the other pages don't seem to be fleshed out yet. But it still looks very helpful.
There is no new development. Latest version on NuGet is 2.6.4. So all these examples are the best you can get right now.
We are using it for some years, and because principles are the same, it is (as a concept) still up to date...
Related
http://neo4j.com/docs/java-reference/current/
... seems old.
Section 4.2 points to a dead link.
Starting with version 3.0, I can't find examples on github.
https://github.com/neo4j/neo4j/tree/3.0/community
Where are they?
The first link to the java reference should be current for 3.1. As far as the broken link, there's a /manual/ part of the path which really shouldn't be there, try this instead.
I'm new to emgu, and found people are using Emgu.CV.CvEnum.IPL_DEPTH.IPL_DEPTH_32F in their implementation. In my program, I don't know why I can not use it. However, I found that I could use Emgu.CV.CvEnum.IplDepth.IplDepth32F. I'm guessing they are the same thing, but I'm using a different version of emgu from other people. I'm using emgu.cv.dll version 3.0.0.2157. I tried to find which version uses Emgu.CV.CvEnum.IPL_DEPTH.IPL_DEPTH_32F as other people are using, but didn't get any luck. I probably referred to the wrong place. Can any one tell how to figure out such problems?
Usually when faced with something like this I go to the Emgu.CV web site and look in the API documentation. I checked v2.4.10 and that version uses IPL_DEPTH_32F. If they are using 2.4.10 then you are fine.
I will let you check other versions if necessary.
Doug
I love OSS contribution but trying to get involved into OSS contribution. Recent I give a try to rails 4.2.4.rc1 with rails 4.2.3 and got failure for testcases.
The app works perfectly with rails4.2.3 and in the latest release candidate it's throwing some errors. I'm trying to figure out the issue.
could anyone help me to find the change from 4.2.3 version to 4.2.4.rc1 in main rails repository? I feel that will help me to resolve the bug.
How I can find the difference from github.
Note: changeLog only contains the error message not the commit details.
I am not sure that I grasp your question.
You are speaking about tests from rails but also about an app that works.
If you want to try different rails versions for your app, I would use rvm and gemsets. Official documentation, but you will find imho nicer tutorials about that elsewehere. Actually, I would always use rvm and gemsets :) .
Changes between two versions can be seen on the github webpages, e.g. for rails - coming from the small green two-arrow-button to create pull-requests. Or you do it on the commandline git help diff, plus there are various graphical tools which I rarely resort to use (I am happy with gitk but there are probably fancier alternatives).
The last Type Provider I wrote just after F# 3.0 was released, and I used the ProvidedTypes.fs(i) files that came with the sample pack.
These files are quite old by now, and I wondered if there are more recent versions.
By googling alone I came up with six different versions. Where can I find the current, official version of ProvidedTypes.fs and ProvidedTypes.fsi?
Moreover, I heard that generated types are now easier to implement. Is this funtionality already inside newer versions of those files?
As requested by Nikon, here is the comment promoted to an answer :)
The starter pack is maintained at https://github.com/fsprojects/FSharp.TypeProviders.StarterPack
When I take a look at the great looking Grails Reference Documentation (http://grails.org/doc/latest/) and compare it with my lousy gdoc documentation, I wonder what makes the difference?
is it just a different style sheet?
or do they use another tool?
How do I get these great looks for my own project without having too much to do?
The easy way to get the new look is to upgrade to 2.0M1 which uses the new look and feel. Peter Ledbrook created the current 1.3.7 docs with the new approach but I'm not sure how easy it'd be to do for a regular Grails application. And there are obviously many reasons to upgrade to 2.0.
You might want to wait a day or so - we're planning on releasing M2 this week. But upgrading from M1 to M2 will be trivial. The real work will be upgrading from 1.3 to 2.0, which isn't that bad.
They use the same exact documentation building tool. It's clearly customized CSS but nothing else. You can read more about it in the reference documentation itself.
Since Grails 1.2, the documentation engine that powers the creation of this documentation is available to your Grails projects.
From the documentation itself.