What happened to the chorddiag package in R? - chord-diagram

While working in Rstudio, I cannot seem to find the chorddiag package. Does it still exist? I've restarted Rstudio in 3.3, 3.5, and 4.0 versions of R, and each seem unable to find the package using either devtools::install_github("mattflor/chorddiag") or the install.package tools. Moreover, after installing devtools, it cannot be found. I'm still learning R, so I'm probably doing something wrong. But I can't figure out what it is.

I was able to complete the install and load the library doing the following:
install.packages("devtools")
devtools::install_github("mattflor/chorddiag", build_vignettes = TRUE)
library(chorddiag)
I'm using R version 4.0.3 (2020-10-10) on Windows 10 via Rstudio.

No one seems to have an answer. So I've gone to the raw html and css to adjust the diagram. It's painstaking work, but worth the effort. I'm leaving copyright claims in place within the code.

Related

DNN 9 Persona Bar not visible after login

I am using DNN 9. I recently upgraded DNN from version 9.1.1 to 9.3.2. When I Login, the left side of DNN disappears with only the logo od DNN. Other options like settings,edit etc are not seen. Any Idea as to what the issue might be?
If you search the forums at dnnsoftware.org, you'll probably find the solution. I'm afraid that I don't recall what it is.
I think, though, that upgrading to 9.4.4 will fix it, too. You'll want to do that in a test environment to make sure that your upgrade will work. There may be some third party modules that need to be upgraded before you upgrade to 9.4.4, so check with module vendors.
As an addition to Joe's answer: There were Problems with the Newtonsoft JSON versions. Maybe this thread is helpful: https://www.dnnsoftware.com/forums/threadid/543186/scope/posts/persona-bar-not-displaying-completely
"...so check with module vendors": There are known issues with DNNSharp modules. See https://dnncommunity.org/forums/aft/748 - but better check with all vendors of third party extensions, if you use any.
Read a few things, tried this and it worked. Delete all from the Bin directory, grab and copy all from another bin directory from a currently working site with the exact version. You may need to install a demo/test site and spin it up to get a good working copy, but this worked for me.
Restoring the bin folder was the solution for me

Twitter-Bootstrap 3.3.7- Getting Started

I'm stumped. I cannot understand the getbootstrap.com Getting Started info. I'm running on Windows 7 Pro. I would like to use Pingendo - which I'm new to - to create my website.
I downloaded the distribution version bootstrap-3.3.7-dist.zip (pre-compiled) and unzipped it. Then I came to the MaxCDN code. Where do I put that code??
For the source code version, I see references to things I don't know about: Bower, npm, Composer, Grunt, Less, and SASS. All these appear to be Linux based tools - from the command lines shown. How does one accomplish the same thing under Windows without installing yet more tools? Do I even need to compile this code to use the greater features?
You can either add the downloaded bootstrap css and js files to your project and reference them or you can just use the cdn which is just the same files hosted on a server. You do now have to know about any of those to get started with Bootstrap. They are just additional ways to install it, and different preprocessors that you can leverage.

How to install RMySQL package [duplicate]

I tried to use RMySQL package but i get this error doing:
install.packages('RMySQL')
Warning in install.packages :
package ‘RMySQL’ is not available (for R version 2.14.2)
What can I do to use MySQL with R?
Thank you!
There is not a windows binary available for the package RMySQL. This means you will have to install this package from source and build it yourself.
At the CRAN RMySql page you will notice there is no binary available, with a link to Pre-compiled binary packages for R-2.14.x for Windows
From this page:
Packages related to many database system must be linked to the exact
version of the database system the user has installed, hence it does
not make sense to provide binaries for packages
RMySQL, ROracle, ROracleUI,
although it is possible to install such packages from sources by
install.packages('packagename', type='source')
after reading the manual 'R Installation and Administration'.
So, read the manuals, in particular R Installation and Administration, install RTools, and then use:
install.packages('RMySQL', type='source')
After installing Rtools, from the RMySQL CRAN page grab the source from the Package source: link to ensure that you have the latest version. Then read the information in the INSTALL file that comes with the package (or find the same info at the Installation: link on the aforementioned CRAN page).
The main problem that most people have is following outdated information on the internet that pertains to older versions of RMySQL rather than using the instructions that come with the package itself.
After spending 10Hours,I followed Arne's instructions and Willem's comment from here:
http://www.ahschulz.de/2013/07/23/installing-rmysql-under-windows/ and it worked like magic.
I experienced some difficulty with installing RMySQL package in R, twice this year. I haven't used it, yet. To help me in getting around the known additional problems, I followed the steps I found in these two articles:
Installing RMySQL under Windows
Vanderbilt University RMySQL page
First you need to download, install and configure MySQL to work with Windows. Next, you will have to create or edit a file called Renviron.site, and add the variable MYSQL_HOME to your default environment, and other tricky tweaks that may have worked for other people, but have not worked for me.
It appears that running RMySQL on Windows is not advised; there are other packages that you can use to get R to work with MySQL. I've been checking out R bloggers, R Studio Support and the R Help Mailing List, for ways to get around the problem.
Although they're useful resources, there is no guarantee that the troubleshooting steps will work for everyone. You can try following them to install RMySQL package, and if they work you should be able to use the package with R.

What happened to ManagedSpy?

ManagedSpy is supposed to be the .NET equivalent of Spy++, but somehow the download page is now not availeble any more.
Anyone who knows why?
Anyone that knows a replacement?
--jeroen
I've cloned the original ManagedSpy source code and maintaining the code in modern environments (for example, ported it to .NET4).
See project on GitHub.
You can still download it here, but the original website seems to be gone. There is however still an article in MSDN (from 2006) about ManagedSpy.
I've cloned the ForNeVeR's ManagedSpy source code and changed a bit to support 64-bit process. see https://github.com/slimzhao/ManagedSpy
Is there a newer equivlent tool? ManagedSpy fails completely on .NET 4.0 enabled machines because Native Images existing under \Windows\Assembly* and it tries loading those as .NET assemblies and fails.

DbLinq and Mono 2.4: Working Together?

Hopefully this is a silly question and there's really a simple solution somewhere out there but...
Has anybody successfully gotten DbLinq to play nicely with Mono 2.4 on Mac OS X 10.5?
I've got my SQLite database ready but for the life of me, I can't find sqlmetal to generate my objects.
I'm guessing I might have to download a previous version of Mono that included sqlmetal, build and install it, and then just use the code generated from that version on Mono 2.4...but I'm hoping to avoid it at all costs.
I'd avoid using DBLinq for production code... many of Linq-To-SQL's features aren't implemented, and walking through the source code shows a low level of maturity... many of the methods are not implemented or marked as "unterminated".
...you've been warned!
Using the pre-compiled binary in this case just doesn't work.
To get a properly generated DbLinq data layer, you have to use the sqlmetal tool included with Mono (but, apparently, not with the pre-compiled binaries for OS X). You have to pull down the Mono trunk (along with all the dependencies) and build Mono from the source.
Once you build and install Mono from source, you should have the sqlmetal tool. Once you generate your code, it's as easy as including the generated *.cs file and importing Mono.Data.Sqlite.
Mono 2.6 will include for the first time a preview of DbLinq with Mono. You can take it out for a spin today if you install DbLinq on your own side-by-side with your current Mono setup.