Is is possible to do force directed edge bundling in gephi? I see a GSOC project completed in 2013 but I want to know if it is packaged with the standard release now. If yes, how to use it?
Thanks a lot for the help
It's possible in a demo build only. The project you refer to has been integrated into this demo build (a little over a year old, though). According to the developers, other things have to be addressed first before this makes it into the regular build. There is no estimated ship date.
Related
Fiware Cepheus home page says that its branch is archived and 'read only' now.
https://github.com/Orange-OpenSource/fiware-cepheus
So does it mean:
1. There would be no future support and development in this community?
2. As alternative we should use 'Perseo' as its similar in functionality
https://perseo.readthedocs.io/en/latest/
In general, archiving a GitHub project means that "the project is no longer actively maintained.https://help.github.com/en/articles/about-archiving-repositories
The Fiware Cepheus page also states that "no new features will be added, nor issues fixed by the original team." So this means option 1 is the answer to your question.
There exists 21 forks of this project, so perhaps the community is moving over to one of those?
I am not familiar with 'Perseo', so I cannot tell you if option 2 is a good solution or not.
Yes, further information can be found in the FIWARE 7.4 Release Note
As announced at the Porto Global Summit 2018, five generic enablers
were placed under analysis and have subsequently been removed:
Proton, 3D-UI, FiVES, Cepheus, Aeron IoT Broker
Perseo is the now the
preferred generic enabler for complex event processing, replacing
Proton and Cepheus. 3D-UI. FiVES and Aeron are no longer seen to be a
good fit with the FIWARE project.
If you want to use Complex Event Processing you are left with two choices:
Convert your project to use Perseo and continue to enjoy community support and development.
Continue to use an archived CEP processor, fork it and make further bug fixes on your own.
I'm interested in using Rubberduck primarily for it's Github source control feature. However, from looking at the Github site for the project I can see that in the most recent versions that feature is not so stable. My question is, what version should I use? For now all I really care about is to have the most stable source control feature. Should I go back as far as v1.4.3? Or is there another 2.X version that was more stable before things recently got worse?
EDIT: As per Vogel's comment
This answer is outdate since a few months: Source control has been
removed completely in the PR #3782 on Feb 26 2018
Even so...
I'd definitely recommend trying out Rubberduck; the unit testing, code inspection and other features are awesome... also the guys involved are generous with sharing their time and knowledge - but IMHO would shy away from using an old version to gain access to the Git features (it has been disabled for a reason).
You can enable it as an 'Experimental Feature' under the menu system > Rubberduck > Settings > General Settings (scroll down)
If you really need something ASAP perhaps look at VBAdiff (http://vbadiff.com/) or this project https://github.com/spences10/VBA-IDE-Code-Export
The bulk of the efforts of the past couple of months went to perfecting the parser and resolver, which impacts overall performance and all inspections and refactoring features; eliminating inspection false positives and making sure no quickfix or refactoring wrecked our users' code has been the top priority, leaving the borked source control panel under-loved - so much that we recently outright disabled it by default, until we git it under control.
Teams mean to grow, and a new contributor joined the project and started working on the source control panel issues.
A pull request was merged recently,
and since every merged PR gets a prerelease CI build published, v2.1.0.2257 is now available for download.
This fixes an IoC registration bug involving an abstract factory interface that the SC panel uses, and it just so happens to apparently fix the exceptions with GitHub authentication, so pushing should now work fine.
More fixes on the way, v2.1 "green release" will likely have a pretty much stable source control feature =)
I am looking for documentation for Ace to do "Floating UI" , i want to to like facebook "Chat Heads". So far there is no documentation only mentioning coming soon , which means avaliable but undocumented right?. Is it already available in github latest master?
They decided to close the support for this project:
As of December 2016, this project is no longer maintained by Microsoft. We built ACE to provide developers with an “escape hatch” to access native code from within JavaScript. After nearly a year in production, we learned that most developers are satisfied with the access granted by Cordova’s Plugin Model. Thus, we’ve discontinued active development. We appreciate your interest in the project and hope you found it exemplary of Microsoft’s commitment to experimentation and open source software. if you're interested in continuing this project, please feel free to fork it. As of December 2016, we will no longer monitor or respond to open issues. You can keep up with other projects from Microsoft’s Cordova team by visiting http://taco.visualstudio.com. Thanks for your support!
I was also looking some plugin to implement "chat heads" in Cordova, without any luck :(
I have used Symfony 1.4 since it's release, but I now have the option to upgrade to Symfony2 for my next project. Does anyone have any experience? Is anybody currently building a production app on Symfony2 or have in the past few months?
EDIT: yes, Symfony2 website has been put up with a clear message saying the framework will be released tomorrow! There is no 'beta talk' but it does clearly state on the installation page that you should use 1.4 for new projects.
EDIT: somebody voted to close because this question is apparently 'too localized'. Is that not what tags are for?!
Symfony2 should be released in March and I'm guessing it should be in the next few days. The Preview Release always had a note next to it that it is not ready for production. I cannot tell how much is that really true and how much is that just the usual "beta talk".
If you've noticed, they changed the symfony2 page that now doesn't go to the preview page but to the symfony.com instead. Also some new tutorial(s) came up. And the download page shows a promising "Will be available tomorrow" message!
I tried out playing around with the symfony2 sandbox but before porting my application to it, I've decided to wait for the release version. If your project is not pressing, I'd suggest the same. Should be around the corner.
Just my two cents ;)
EDIT: Btw, if you look in the blog, you can see that
The public API of Symfony2 will be
frozen in just a few days. Therefore,
this week developers committed some of
the last big impact changes to the
code repository: the Response was
removed from DIC, CompatAssetsBundle
was removed in favor of AsseticBundle,
and the boostrap files were also
removed.
This can only mean a stable version out soon!
I would say yes, as long as you're aware that it's a preview release and take the necessary precaution i.e. keeping an eye on the error logs.
There are alot of sites using symfony2 in production including the VPS control panel at ServerGrove and OpenSky (developed by the creator and main contributor to doctrine orm and odm projects).
The Release Candidate comes this month sometime, which signifies the API becoming stable! Hooray!
This link from the Symfony2 blog outlines the road map for the Symfony2 release.
There's also the Symfony2 Bundles site which is a collection of bundles that already exist for Symfony2
They said it will be available soon.
But you already can download it from github and start learning it and migrating to it. I've been doing that since December last year and the only problem was changes in API. But now it must be more stable and it's safe to migrate to it.
The 'is not ready for production' note meant no support and no guarantees that everything works and tomorrow something won't change. And if it changes, it was your problem to find out what and how.
While the original plan was to release a stable release candidate last week around the Symfony Live conference in Paris, it was announced there that it would be delayed for what I guess should be at least a couple of more weeks, which I agree is a good thing.
That means that the API is not stable yet and might change, and that those changes might break BC. The standard package which is now available for download on the new website is a PR like the previous releases were.
The accepted answer to this question suggests using an SVN revision number as part of the version number when building a release. I want to do something similar using Team Coherence, which doesn't do revision numbers quite the same way.
For Delphi 2009 how can I set up a build script so that every release automatically includes a number or tag linking it to a specific Team Coherence check-in or version label? Just a way to access the current version label would be great, though a solution that automatically updates it would be even better.
I don't know how to do this (though I'm interested in the answer, I use TC myself) - but have you emailed Ewan at QSC about it? On the few occasions I've needed some help doing something like this he's replied very quickly and if he doesn't know how to do it, well quite honestly you probably can't - he's the TC developer! :-)
support#teamcoherence.com
QSC web site