I'm developing with National Instruments' CVI LabWindows platform. It's a very old IDE and they don't seem to have any plans to update it.
debugging one of my LabWindows projects
I'd love to use VS Code to do my development, which I could since LabWindows is pure C language with added proprietary hardware libraries, and a binary GUI editor layer.
But it would be cool to compile and debug inside VS Code too. Assuming I have a paid license for LabWindows, and that their command line tools for their debugger is feature rich enough, how do I get started making an extension?
I want to know is it possible to run pyqt5 on micropython(pyboard),I think micropython library is too small.
pyQT is not an option here. Read following discussion here to find and choose suitable GUI lib for your micropython project.
From my personal experience- my choice was LVGL library for small ILI9341 touch screen.
My university has a total headcount license that covers all major add-ons. I was able to install it, alongside the two add-ons I need (Image Processing Toolbox and Computer Vision System Toolbox) at home with the install wizard.
However, in the lab when I try to add these add-ons to my matlab environment (even when logging in) via the 'Get Add-Ons' option in the menu (Add-On Explorer), I am forced to 'Buy' each toolbox. i.e. I am not offered the option to download it, despite it being covered in my license. Any idea how to get this working/ alternative method?
I should also note, it's not possible to reinstall Matlab as I do not have the permissions required.
For anyone who arrives here after me, just use Matlab Online. Bit of an workaround but it's the only solution I found.
https://matlab.mathworks.com/
This does not exactly answer the question, but nowadays it is not essential to stick to Matlab. Python with OpenCV and Numpy, R are basically free options with no license hassle and lots of support. Plus, you will be able to use your code after graduation :o)
I have found that there are plenty of frameworks for browser plugins.
my first question:
which one of the following frameworks specified for plugins and which one is not specified for plugins:
FireBreath, OpenForge, Kango, BabelExt, Nixysa project, JUCE project, QtBrowserPlugin project .
my second question:
Is there another popular plugin's framework other than those mentioned?
my third question:
What is the main differences of these popular plugin's frameworks?
Indeed is there any comparison of these frameworks, the comparison could be in each of following terms:
usability (for a page as a NPAPI plug-in or for a browser as an
add-on extension),
simplicity (in developing),
speed (on execution),
extensibility (of developed add-on),
availability (in Windows 86x and 64x, Unix, Linux, mac and other
platforms and also mobile platforms specifically android, ios, ...),
flexibility (for new technologies),
reliability (in terms of security),
accessibility (open source or not),
portability (in Fire-fox, chrome, IE, Safari, Opera, ...),
applicability (in drawing, communicating, calling from external
server, threading, network accessing, etcetera),
stability (in changing the policies, for example in deprecating
NPAPI)
Also I have read Cross-Browser Extensions API? which I think it is about extension's framework (not plugin's framework)
I'll be honest -- this seems like something you should be able to answer with some google searching. I appreciate that you're at least trying to apply suggestions on how to better ask questions, though, so I'll respond on the few that I know something about.
FireBreath is a C++ framework for creating browser plugins, not extensions. It works as an NPAPI plugin for browsers supporting NPAPI plugins (previously this was all but IE, but Chrome dropped support for them this year and Firefox plans to at the end of 2016) or as an ActiveX control, giving it equivalent functionality to a browser plugin in Internet Explorer. FireBreath 2, which is working but poorly documented so far, changes the APIs from being synchronous between the browser and plugin to being asynchronous and adds an emulation layer to let them work with Google Chrome using Native Messaging. It's the most complete and up to date of the plugin frameworks, as far as I am aware. I am its primary author, so feel free to get your own confirmation of that.
Nixysa is a tool that takes definition files and outputs code for a NPAPI plugin. I haven't used it, so I can't tell you exactly what it's capabilities are. It hasn't been updated since 2012, when PPAPI support was added; this is unlikely to be useful, though, since PPAPI has changed significantly since then, and also since the only PPAPI plugins that can run without special command-line flags to chrome are ones specially blessed by the Chrome team.
JUCE is a GPL library with a commercial licence available which has some support for creating browser plugins. I have no idea as to how powerful it is these days; it seemed well written when I last looked at it, and takes a much more minimalistic approach than FireBreath does; FireBreath gives you a framework and tries to make everything Just Work, whereas JUCE seems (I could be wrong) to be more of a "provide the building blocks, but don't try to make everything look the same" type of thing.
QtBrowserPlugin is a defunct unmaintained project which at one time allowed creating browser plugins (probably just npapi, but not certain) with QT. Indications are that it probably doesn't work anymore.
I have no idea what the other projects are. If I were you, I'd try doing some research. Google is your friend.
After watching some videos on how to use variant subsystems in a design, I was able to get variants working.
But this video tutorial (Managing Design Variants) from Mathworks mentions a Variant Manager which I have been unable to find in my version of Simulink. I am running version R2011b.
My View menu is different form the one in the tutorial, but it shows tabs for the Library browser, the Model Explorer and the Simulink Project. But I don't see any sign of a Variant Manager. I checked the other menu tabs with the same results.
Documentation help doesn't find anything on Variant Manager either.
Is the Variant Manager something introduced in a later version? Which one did it start in?
Or is there something I can configure to in order to use it?
The Variant Manager was introduced in R2013b, see the release notes (under R2013b, Component-Based Modeling).