lordexod

I have no access to the official NI NXG 2.0 forum, so I will write here.

1. In "NationalInstruments.NIWebBrowserSupport.dll" - instead of the external library "CoherentUI (CEF)" could by use the "WebBrowser" control from "PresentationFramework.dll" https://www.dotnetperls.com/webbrowser-wpf

2. In C Node - Instead of compiling the code in c using CVI, could by use the Ch interpreter and SDK https://www.softintegration.com/products/ .

This may the next version of NXG 3.0 will make it on Windows MR (MixedReality)?

.Net is open source, apart from the WPF platform, to ported NXG to other systems, writing again the WPF native components such as: MilCore and compiler DFIR to LLVM instead of lvffrt.

Personally, I would never ever implement a hundredfold shitty avr in fpga.

I would prefer something more interesting and useful like this: http://bar.eecs.berkeley.edu/projects/2014-rocket_chip.html

11 hours ago, DTaylor said:

Is this speculation about something that you think we should be able to do in NXG, or is this functionality that you've heard is actually planned?

How very you want you can do it XNode abstraction layer.

I personally prefer LV NXG from LV TG because I have 100% influence on what is implemented and for my future implementations.

For example, adding a Lattice FPGA platform because it has good and cheap FPGA ECP5.

Or simplify the implementation to XDiagram and XComponent so that I can create any diagram behavior for any component.

In LV NXG you have more capabilities than you had in LV TG because you can make abstraction layer for XNode, XDiagram, XTunnel, XWire, components as native plugins.

As for "Web UI Builder" it should already be open source.

One can launch without a browser.

Download: uibuilder.niwsc.com/webuibuilder/WebUIBuilder.xap

After installing Silverlight set system variable PATH= <Disk>:\<Path> to sllauncher.exe and launch   sllauncher /emulate:"WebUIBuilder.xap" /origin:"<Disk>:\<Path>\WebUIBuilder.xap" /overwrite

"Node Red" is just HTML+JS+CSS and Python's dick for the RPi is like a fart in comparison to LV NXG1.

I am most pleased with this most useful feature which will be never in the standard Labview.

I like it too LVNXG graphical interface and creating native plugins (Examples: https://github.com/ni/nidevlabs).

I just don't get why they cut out this version of LVNXG1 (4.9.1.57948), earlier version 4.9.1.56780 is full.

Instead of reading the idiotic posts of users "Jacemdom, rolfk".

It may be interesting and useful:

1. Next Generation Labview Interactive (html) VI Instruments.

https://github.com/elijah286/NIWeek-2016-Keynote/tree/master/WebVI/WebVI and Tag Keynote/Interactive/Component

https://github.com/joshuaprewitt/crio-temp-logger-webvi/tree/master/cRIO Temp Logger/Builds/Web Server/Default/WebApp

https://github.com/joshuaprewitt/webvi-plugin

https://github.com/joshuaprewitt/data_logger

https://github.com/joshuaprewitt/crio-logger-webdashboard/tree/master/Interactive/Component

https://github.com/joshuaprewitt/hackathon/tree/master/Interactive/Component

https://github.com/joshuaprewitt/simplelvplugin

https://github.com/prestwick/wind-turbine-demo/tree/master/Interactive/Component

https://github.com/prestwick/HackathonWebVI/tree/master/HTMLVIDeploy6

2.VI Parser

https://ni.github.io/VireoSDK/

https://github.com/ni/VireoSDK/tree/incoming/source

On 7.04.2017 at 6:11 PM, NI_Eagle said:

I'm not sure what posts or issues you're referring to, but if you contact me directly, I'll help you take care of it. 

jeffrey.phillips@ni.com 

I sent and I wait for the answer.

It's good that this is not an NI official forum.

There are my posts is deleted in a few minutes.

Due to the lack of any secret license.

It's not about that to publicly respond, just to fix it.

This is NI internal "super secret private special" support service question.

Maybe if I ask on the public forum maybe someone will wake up and fix it.

Applies to server administrator "Store API Service - ...conduit.ni.com....".

Move your ass and configure this server, because I can't download new labview.

To generate and compile the Labview FPGA for other hardware with Xilinx FPGA, just create a XML file (*.xml) in <lvdir>\Targets\NI\FPGA\<hardware> and create a few files .ucf and .vhd in <lvdir>\Targets\NI\FPGA\<hardware>\FPGAFiles\ .

example: LV2015DIR\Targets\NI\FPGA\MT-P160\MTresource.xml , LV2015DIR\Targets\NI\FPGA\MT-P160\FPGAFiles\

The rest is the additives used for data transfer and programming.

Update

Relabelizer.llb

The error occurs only in vertical wires.

On 14.06.2016 at 2:56 AM, bbean said:

Some self promotion here, but have you tried or seen this:

 

New non-xnode update for "Re-Label Wire Xnode" popup plugin Relabelizer.llb , copy to ..\LabVIEW <version>\resource\plugins\PopupMenus\edit time panel and diagram.

3 hours ago, rolfk said:

NI's stance on such things (and basically any company in the US and most other places) is: We do not comment on internal developments, plans for development or lack thereof or whatever, unless we are at a stage with it that it is ready for prime time.

It may sound dissatisfactory for us mere users, but reality is that there are simply to many legal and other implications in our modern system, that speaking before the fact can have far reaching consequences. Basically every employee knows that commenting on unreleased products or technologies without approval from higher management might be the signature under a resigning letter that has no possibility for reappeal.

So you can hope for a reaction from someone from NI about this, but unless they have it ready to be announced at coming NI week you can keep waiting until the hell freezes over. Even then it is not likely that they will react here.

The management shall be granted in this topic.

Provides information about product content, which is not yet officially available.

So it does not hurt to ask for things that already are in the products.

19 hours ago, hooovahh said:

I'm not NI, and this is slightly off topic, but in the past NI's answer has been that technical limitations came up when with the licensing of XNodes for public use which caused NI to stop looking into making it open.  It sounded like NI (or some within NI) saw that this was a niche group of developers that would want this, and figured it wouldn't hurt to open it up, but ran into issues which were not easily overcome.  With little reason to continue looking into fixing these issues, and with such a small group of developers who would use it, it sounded like NI wanted to invest in other areas instead.  Being part of this small group I certainly am not happy with the decision and hope it changes, but understand why NI hasn't continued to work on opening it up as far as I know.

I know you're not with NI.

I was hoping for the answer of someone with NI, who appeared recently in this topic.

Finally, the right man it is in this forum.

So I ask (without the participation of lawyers) , when will the official (unofficial) support to the "XInterface Component" and "DFIRtoCPP".

VI Macro technology update :

Simpler XNode .

XMacro.zip

Instead replace vi to vim.

Macroizer.llb copy to "..\resource\plugins\PopupMenus\edit time panel and diagram" and right-click on subvi and "Convert To Macro".