Is JColibri functional yet? - system

I am building a case-based reasoning system in Colibri Studio, but I keep running into build errors. The documentation is sparse - does anyone else successfully get Colibri Studio to properly build in Eclipse? It is currently in beta 0.9, but it seems to be a little behind beta.
I was thinking that it may be my data, but I don't have a solid way to check this.
Colibri Studio is from GAIA, link here:
http://gaia.fdi.ucm.es/research/colibri/jcolibri
It is supposed to be highly useful, but I have just been frustrated by the whole process. If it is confirmed that the Studio version can successfully build, I can follow up with more questions about how to successfully get it to compile and execute.
Note, this differs from JColibri 2.3, which apparently is a functional Java program that lacks a GUI.

Related

LWIP library files not building on Atmel 7.0 when setting NO_SYS=1

I've got a strange question that I can't seem to find any answers for. I'm building a quite simple application for sending/receving data from/to a PCB, and the application itself builds, but when I exited Atmel Studio (Version 7.0) and reopened the project, the library files no longer built. At least that's what I think happened. I didn't change any code between building the project before and after restart of the program. It has happened before, and that time I solved it by creating the project from scratch, but I'd really like that not to be the only solution. I've also tried restarting the program again, as well as the computer. I also removed and re-added the library.
Has anyone encountered the same issue? If so, any help in the right direction would be greatly appreciated. Information on my system and error messages below:
I'm building for the ATSAMV71N21B board, with Atmel Studio 7.0. I've imported the lwip library trough the ASF wizard, and these files built before the program restart.
These are the files that won't build:
The 122 build errors mainly consists of "expected expression before 'struct'" and undeclared functions and variables, even though these clearly are defined in the various files in the library.
It ended up being because of my NO_SYS setting being 1. When I switched it to 0, everything built, (except for sys_check_timeouts(), but I think I'll find another answer for this). Keeping this here for reference if anyone needs it one day.

What is the upgrade path for C# MSBuild Tools to be?

We are using Bamboo to compile our C# projects and recently enhanced our build AMIs to have the MsBuild 15 Build Tools so devs are able to use C#7. With the advent of C# 7.1, Microsoft state they are "increasing the cadence" of language releases and I've been trying to find out what the upgrade path for MS Build Tools and how to keep it updated with the latest version.
At the moment it appears that the Bamboo admins would have to always be one step ahead of the devs (who update their IDE to use the new language release) to enable clean compilations.
I can't find a decent way of automating this (other than though something like Chocolatey) - I'd be interested to see how other people get round this or ensure their Build Tools will always up to date.

How to install Visual Paradigm on Netbeans?

I'm following the instructions here but it seems not to work. I'll contact the developer, but wonder if someone has been able to make it work somehow.
The installation process is completed, but Netbeans doesn't see the plug-in. I assume it is deployed incorrectly.
Not sure how it got fixed but suddenly upon starting the IDE an update for the plugin showed up and it started working afterwards.

Grasp simulation tool

I want to do some grasp motion planning experiments, but I failed with compiling the GraspIt! using VS2010 on Win7. Is there has other grasp simulation tool like GraspIt! that can be used in Win7 and VS2010 environment? Thank you!
I had been trying to install Graspit for Windows 7 too, but failed somehow and then switched to OpenRAVE. OpenRAVE is open source and provides an environment for testing, developing, and deploying motion planning algorithms in real-world robotics applications. The installation guide for Windows can be found here. There are a lot of quick start examples, which cover topics to help you get started with Inverse kinematics, testing a grasp, implementing planners and controllers. You could also work in a MATLAB, Octave or Python interface.
You can also find lots of relevant information on the OpenRAVE user mailing list, or ask questions when you need help.
I am running OpenRAVE on Ubuntu 12.04 though, and the installation was fairly easy.

What technical steps should I take before publishing my new software?

I am about to publish my first small piece of software. The software is in VB.NET and I have used Visual Studio 2013 as my IDE.
What are the steps I should think about before publishing and do you have any suggestions on how to complete each successfully?
Here is an incomplete list of the steps that I have thought about so far. But I don't know if I may be missing other important steps
Create an installation package (Status: I have created one using WIX)
Obfuscate the code (Status: I have obfuscated it using the built-in obfuscator in VS 2013)
Have a T&C that doesn't make me liable if my software causes problems (Status: I haven't looked into this yet)
Create a demo and a registration mechanism (Status: I don't know how to do this yet)
Please let me know if my list is pretty complete or if there might be other things that I haven't thought about and that might cause problems for me down the road.
That sounds probably obvious but:
Try to install/update the software on every supported platform
Install and test the software on a different machine than your development machine to find dependencies that users may not have
Ensure that Logging is working as expected and that it gives you the information that you will need to fix issues
Test how you will fix issues (integrated update, ...)
List all 3'rd party libraries you have used with their licenses
Create a Help/FAQ or Documentation
Figure out how to licence the application and how this behaves when uninstalling etc.
A good list can also be found here.