Book recommendation - user interface hardware

Hi all,
Could you please recommend me a book related to user interface design and hardware related knowlege? That will also be helpful.
Thanks
Need recommendation for hardware and software
Hi all,
I am doing a project related to current control.
The purpose is to keep the current at constant. So I measure the current and get the value; and send a analog signal to tell our machine to discharge or to charge in order to keep the current at constant. I need to write the program to give analog signal to machine based on the current input.
Also, the machine can communicate with user. User can monitor the machine operation statuse and current level, etc.
I want to use LabView to program, since it doesn't cost a lot of time. I saw there is LabView RT LabView FPGA, etc. I am confused whether all of these are just diffrent function for LabView or different software. Which one I should use?
For hardware, I have no idea what is compactible with LabVeiw. What I should use?
I am totally new to this. I'll appreciate a lot if anyone can give suggestions.
Thanks

Hi,
In terms of books specific to GUI design there was one written by David Ritter, LabVIEW GUI - Essential Techniques but I'm pretty sure it's out of print. A very good book to get started with LabVIEW is 'LabVIEW for Everyone', by Jeffrey Travis and Jim Kring. This is the one that I picked up when I was plunged into the deep end and had to start building applications in LabVIEW. I still use it now because it covers a bit of everything and is usually enough to point me in the correct direction even if it doesn't have all the answers.
In terms of your other questions, LabVIEW RT is a real-time version of LabVIEW normally used for things like CompactRIO or PXI chassis hardware. The FPGA add on is for programming FPGA's such as the backplane in the CompactRIO device. The big advantage of both of these is that they avoid the need to use WIndows, MacOS or Linux which when dealing with critical rig control or aquisition can be a big plus. The bad side is that the hardware is more expensive and there's an additional software cost. For a simple application such as yours these would be serious overkill unless they're highly critical.
For the applications I run I use the LabVIEW Developer suite coupled with National Instruments hardware and compile executables that run under Windows. This does mean that I have to add in code to cope with situations when Windows decides to crash, or do something odd, but reduces the cost significantly. In your case it appears you have a single station controlling a simple process so the world is your oyster. The lowest cost option would be LabVIEW basic version running on a PC using a USB DAQ - cheapest that can output analogue signals is a USB-6008 but these are quite limited in their capabilities. I tried to use the slightly higher spec version (USB-6009) to run a lashed up test rig for a short period and had lots of problems because I was using the digital ins, outs, counter, analogue ins and outs all at the same time - it appears you can use any one quite happily up tot he stated performance but it complains when you try to use all together.
If your budget permits then the USB-6211 is a better choice in my opinion. You can look up the specs and prices for your location at www.ni.com
If you're a student then you can get LabVIEW at a very much reduced cost.
Hope this helps.
Paul
Regards
Paul
CLD running LabVIEW 2012 32 & 64 bit on Windows 7 64 bit OS.

Similar Messages

User interface hardware

anybody can help me to I find a list of industrial hardware (panels etc, no PC) which I could use to create a user interface in LabView?
It would have to be "rough" but not too expensive. Regula PDA would not be ok
Thanks
Nicola

Try looking at IVC and Suetron. I haven't tried any of them.
Try to take over the world!

Hi all, i'm new and facing a problem while creating a new file for Xcode. I can't select the box "with XIB for user interface" if the subclass is "UIViewController".this problem happen after i upgrade Xcode to 4.6 version.Appreciate for any help rendered.

Hi all, i'm new to Mac book & Xcode. I'm learning and facing problems while creating a new file for Xcode. Before i upgrade the software, i have no issue to create simple steps in apps. After upgrade Xcode to 4.6 version, i'm facing lot's of issue eg.
1) "the identity "iphone developer" doesn't match any valid certificate/ private key pair",
2) can't select the box "with XIB for user interface" if the subclass is "UIViewController"..
Appreciate for any help rendered.

Mikko777 wrote:So what is the best?
I wouldn't judge. I've been to Arch for a week, you know? But as said, it's VERY close to it.
What I dislike after a week is makepkg not handling dependencies automatically (which would be overhead, so probably not appropriate).
Mikko777 wrote:Also theres KDEmod for modular kde, dunno if its for 64 bits tho.
Don't actually need that as said ... I see no real benefit of having that other than not beeing a KDE user or having Gentoos useflags.
Mikko777 wrote:PS:You produce a lot of text and welcome smile
Yeah. Wonder why I'm still employed? So do I ...

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

Issue in the user interface of ICSS application

Hi Experts,
Please find the below description of the issue.
Ours is a migration project of ICSS application from one landscape to another landscape. Both the landscapes are in CRM 7.0 with the same patch levels.
For this migration we have copied the existing track A to the new track B and mapped to the new CRM 7.0 B system.
The XCM setting has maintained in the new B system exactly the same way like the A system
All the related backend code like FMs, Data Dictionary objects etc in CRM 7.0 A system has been moved to the CRM 7.0 B System.
   After this when we tried to run the application B, we are not seeing the same user interface like in application A.
   We are seeing only black font with white background. The color combination, fonts, styles etc like in application A are not visible in application B.
There are no CSS files in the XCM settings in A system. So I have also not maintained in B system.
We have not done any changes in the track. So we have not deployed the application.
I have created the projects for both the tracks A and B and compared the code manually. Everything is same.
Question:
   Please let me know what needs to be done additionally to get the same user interface.
   Is Shopadmin settings has to be maintained. Is this mandatory.
   Thanks in advance.
Thanks and Regards,
Raghu

Hello Waldemar,
Thank you for contacting National Instruments. I would like to apologize for the delay in responding to your support request. We have been on holiday for the past few days due to Thanksgiving.
From the information you have provided here, it sounds like you are on the right track with getting your application up and running with a chinese font interface. I would like to point out an extremely helpful KnowledgeBase that you might use for reference now and any other time you need to localize your user interface:
http://digital.ni.com/public.nsf/websearch/5987FCAFE3FBE8B98625693B0052EBD9?OpenDocument
(This KB was written for LabVIEW 6.0, but is still relevant for LabVIEW 7.0.) Based on this document, you only need "an MBCS-enabled operating s
ystem with an IME for the corresponding language." All 32-bit Windows operating systems are MBCS-enabled. Please see these links from the Microsoft website for more information:
http://search.microsoft.com/search/results.aspx?View=msdn&st=a&qu=mbcs&c=4&s=2
You may also find this tutorial describing localization procedures useful:
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/6d94f90fc9b93aad862568a7007cd4c0?OpenDocument
I would recommend that you go ahead and install the Chinese fonts to your OS (if you have not already), and develop your user interface using the new font. This application should have no problem on any other machine with the Chinese font enabled.
I hope this helps! Let me know if there is anything else I can help with or clarify. Have a great day!
Liz Fausak
National Instruments

How do I fix incorrect resolution for Firefox user interface on Retina display Mac?

I have a 15" retina display Mac (roughly a year old) running Mountain Lion. A couple weeks ago the user interface in Firefox seems have switched from using the normal zoom level of every other application to the native dpi of the retina display monitor. This means that the UI elements are all extremely tiny, etc. Is there anyway to reset this without simply reinstalling or reseting the rest of my configuration?
Currently running Firefox 27.0.

You can try to modify the gfx.hidpi.enabled pref on the about:config page (<=0: disable; 1:all screens same res; >1:enable always).
*http://kb.mozillazine.org/about:config
Try to disable hardware acceleration in Firefox (you need to close and restart Firefox).
*Firefox > Preferences > Advanced > General > Browsing: "Use hardware acceleration when available"
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can set the layout.css.devPixelsPerPx pref on the about:config page to 1.0 and if necessary adjust layout.css.devPixelsPerPx starting from 1.0 in 0.1 or 0.05 steps (1.1 or 0.9) to make icons show correctly.
*http://kb.mozillazine.org/about:config
See also:
*https://support.mozilla.org/kb/forum-response-Zoom-feature-on-Firefox-22
Use an extension to adjust the text size in the user interface and the page zoom in the browser window.
You can look at this extension to adjust the font size for the user interface.
*Theme Font & Size Changer: https://addons.mozilla.org/firefox/addon/theme-font-size-changer/
You can look at the Default FullZoom Level or NoScript extension if web pages need to be adjusted after changing layout.css.devPixelsPerPx.
*Default FullZoom Level: https://addons.mozilla.org/firefox/addon/default-fullzoom-level/
*NoSquint: https://addons.mozilla.org/firefox/addon/nosquint/

No Plug-In specified and not allowed to bring up user interface

Hello,
We have several users here getting an error when trying to sign a pdf with Adobe's digital signature. When they click in the field box to sign the document they are getting the following error,"No plug-in specified and not allowed to bring up user interface for selection." We are using Adobe acrobat 9 standard with the latest updates. I have done a total uninstall and reinstall and recreated the digital signature and still the error persists. I have gone as far as renaming the windows profile and nothing seems to work. Any thoughts?
Aaron

A signature field may have associated so-called "seed values" that specify certain signature properties and restrictions. The document's author can associate "seed values" with an unsigned signature field. One of the "seed values" specifies which external signature plug-in must be used to sign this signature field. If you do not have the required plug-in in the Acrobat installation then you cannot sign this signature field. This is the most likely reason that you get this error message. In some environments this is done to restrict the signing to only signing credentials that reside on hardware modules or signing pads. There might be other reason why the document's author chose to put in this restriction.
Contact the author of the document you are trying to sign and find out whether this is the case and if it is then which plug-in you need and where you get it from.

How to get the value of the global variable of test stand in labview User interface?

Hi.
Can anyone Please share examples and tell me to how access the test stand global variable using labview user interface.
Solved!
Go to Solution.

I'm not surprised that what you are doing doesn't work. The Start Execution UI Message is triggered when the user clicks a button to start an execution. Realize that most executions go through a process model. So you could be looking at the sequence context of the process model and not your client sequence file.
I recommend reading that link I posted above. UI Messages are your best bet but you cannot just piggy back on an existing UI Message like this. They may not be getting sent at the time you need them to be. The only way to ensure you get what you want is to trigger one yourself at the right time.
Regards,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

BPM Workspace Customization & User Interface: Best Practice Question

Hi All,
This is our first BPM Project in house and we are on Oracle BPM 11g.
The business process involves request for approval for a permit from a public user and internal users need to approve/reject the same. Pretty simple and straightforward so far.
But we are now having lots of questions wrt to user interface.
1. Work Space Changes.
If we develop this application completely in Oracle BPM, the outside user (general public) will also see the 'workspace' with its current interface. It would be impossible to handle user training on this interface for a simple Joe Bloe, who may not be computer savvy) So the requirement documents demand that the look and feel of the outside users should be totally different than what the workspace provides. They want this to be customized in such a way that iit would strip all of the default lay out (left navigation bar, and get rid of the upper section completely. with its list of tabs) and also to modify the task list that appears below).
We have figured out how to achieve this (by modifying the workspace .jar files and recompiling the same), but is this a good approach? What happens if we are developing a brand new application on the BPM in our shop? This change will affect that application as well, as the workspace is shared and common to all the apps? I want some of you experts to let us know, your thoughts on this. If this is not a recommended practice, what would be best way to achieve what we want using Oracle BPM? (Where we want a simple intuitive user interface, without the default add ons that comes with the work space)...
2. What would be the best method to create a user registration page (where a user creates his own login and password and maintains his account) for an application using the BPM ? Right now we are thinking this should be in either a ADF page/ JSP page or (worst case a PL SQL cartridge) that can be launched on the browser, which will be open and does not require any kind of authentication to access. Is this a good practice or recommended one? Or are we missing out on something within BPM application itself, that we are not aware of and that would let us do this?
3. Also, if we go with an external ADF application for the 'public' user interface developement, then how can we (or can we) leverage the BPM's internal storage for the submitted data from the payload? I understand that it stores this information currently on the server 'soa infra' tables some where? Thru an external ADF app, can we write into these tables (Is this recommended or just sounds plain ridiculous)???
Knowing answers to these questions will help us decide, if this is the right tool for the job at hand.
Appreciate your time and xpertise.
Thanks
SR

Hi All,
This is our first BPM Project in house and we are on Oracle BPM 11g.
The business process involves request for approval for a permit from a public user and internal users need to approve/reject the same. Pretty simple and straightforward so far.
But we are now having lots of questions wrt to user interface.
1. Work Space Changes.
If we develop this application completely in Oracle BPM, the outside user (general public) will also see the 'workspace' with its current interface. It would be impossible to handle user training on this interface for a simple Joe Bloe, who may not be computer savvy) So the requirement documents demand that the look and feel of the outside users should be totally different than what the workspace provides. They want this to be customized in such a way that iit would strip all of the default lay out (left navigation bar, and get rid of the upper section completely. with its list of tabs) and also to modify the task list that appears below).
We have figured out how to achieve this (by modifying the workspace .jar files and recompiling the same), but is this a good approach? What happens if we are developing a brand new application on the BPM in our shop? This change will affect that application as well, as the workspace is shared and common to all the apps? I want some of you experts to let us know, your thoughts on this. If this is not a recommended practice, what would be best way to achieve what we want using Oracle BPM? (Where we want a simple intuitive user interface, without the default add ons that comes with the work space)...
2. What would be the best method to create a user registration page (where a user creates his own login and password and maintains his account) for an application using the BPM ? Right now we are thinking this should be in either a ADF page/ JSP page or (worst case a PL SQL cartridge) that can be launched on the browser, which will be open and does not require any kind of authentication to access. Is this a good practice or recommended one? Or are we missing out on something within BPM application itself, that we are not aware of and that would let us do this?
3. Also, if we go with an external ADF application for the 'public' user interface developement, then how can we (or can we) leverage the BPM's internal storage for the submitted data from the payload? I understand that it stores this information currently on the server 'soa infra' tables some where? Thru an external ADF app, can we write into these tables (Is this recommended or just sounds plain ridiculous)???
Knowing answers to these questions will help us decide, if this is the right tool for the job at hand.
Appreciate your time and xpertise.
Thanks
SR

This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic.

Hi there,
I was wondering whether anyone could tell me which feature in Windows 7 produces this message "This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of
the package to basic." and whether it can be turned off in Windows to prevent this message from appearing when installing certain programs that aren't WHQL certified. At first I thought it was the UAC control that generated this message but found out
that it wasn't and then thought it was the DEP control and found out that it wasn't this either. I'm only seem to be getting this message when installing FileDirector Component Service Version 3 on a few of our workstations which is an add-on that allows file
integration with Office and is part of FileDirector WinClient Version 3.
Your help would be much appreciated.
Many thanks,
RocknRollTim
P.S. I know of a way to bypass this message but would ideally not like to have the feature turned on and for the message not to be appear for non WHQL certified program installations in order to make non WHQL certified program installations in the future much
easier, more simpler and straightforward to carry out. I was redirected by a moderator off the Microsoft Community Forum.

Hi,
You can try following options to disable this prompt, but we don't recommend you to do so since this feature helps you to protect your computer.
Option 1: Run command as admin:
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Restart your computer to apply changes.
Option 2: Disable in GPO:
1.Type gpedit.msc in the Run dialog and press Enter.
2.In the Group Policy Editor, navigate to User Configuration → Administrative Templates → System → Driver Installation.
3.Double-click on Code signing for device drivers in the right-side pane as shown above.
4.In the windows that opens, choose Enabled. In the Options, choose Ignore as shown. Then click on the OK button to save the settings.
Restart your computer to apply changes.
Kate Li
TechNet Community Support
Unmarked as Answer based on OP's request.
https://social.technet.microsoft.com/Forums/en-US/35ab1279-c3a1-46be-9f7d-45e8606c1410/this-advertised-application-will-not-be-installed-because-it-might-be-unsafe-contact-your?forum=w7itproappcompat
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

How to get to learn using TestStand User Interfaces

I am starting to work with TestStand and I was looking into using the User Interface. I know that a couple of examples are provided and that there is a couple of sections of literature on the subject, but there does not appear to be a very helpful (get started from scratch) type of documentation that I can find. Does such a thing exist? If not, what is the best way to get started?
Solved!
Go to Solution.

You can currently do this in the Full-Featured UI without any modifications. It's kind of a hack though:
So assume that an execution is running. The user clicks the Break button and wants to rerun a step with different parameters. So now your execution is paused somewhere below the step. Right click the step and select: Set Next Step to Cursor. Now in the Variable window look for the variable that is being passed as a parameter to that step. Say for instance Locals.Foo is being passed to your VI. Change the value of it and click the Resume button. This also assumes that you are passing either Locals or FileGlobals to your VI. You may have to have Administrator privileges to do this.
If this isn't good enough then there are ways to accomplish what you want in a cleaner manner.
One way is to build your sequence file such that if a certain condition occurs then retry with new values or values from a file which can be changed by the user. This is what I would recommend because it will be the cleanest and the easiest.
Another way is to build into your UI like you are asking about. The problem with this is at a certain point the user will click Break or a Stop button that you have put on there. This will stop the execution at some point (who knows exactly what point unless you write code to specify a point). Then they would have a pop up or something that would allow them to select a step. Then for each step you'll have to have some code or a parser or something that will determine the parameters and valid values they can be and ask the user for those. This is all doable but would be quite a task. You will have a long ways to go in understanding the TestStand API in order to accomplish this. In fact there would be so many API calls with numerous ways to attack this problem.
Whichever way you choose to go you will always have the TestStand forums or NI support.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Calendar User Interface (X7)

I'm a new X7 owner, fighting my way through a confusing user interface. On my second call to my telco, I got sent the PDF of the user manual for my phone. It answered some questions, but nothing for the calendar.
It tells me to fill in the fields. Not a single word on what the fields mean! So what DO these fields mean? When I click through into the data entry for an icon, it should add a title for that field.
I'm in edit mode for a single-shot appointment. I have an icon of a calendar page with a right-pointing arrow in the lower right. I have an icon of a calendar page with a right-pointing arrow in the lower left. I assume that these are controlling the repeat characteristics of the appointment. But this is a no-repeat appointment as indicated further down the page as "circle-arrow Not repeated". If that's what these fields are, why are they shown before selecting repeat?
What does private or public syncronization mean?
Is there any way to link the phone book to my appointments? I already have my doctor's address in the phone book -- why should I re-enter it here? If I want to phone him to modify my appointment, can I click through from the calendar? Why not in the twenty-teens? My doctor has a nice dozen-character Polish name -- shouldn't I be able to right-click (oops -- long-press) his name in my phone book and choose "schedule meeting" from there, rather than typing in a name and address all over again?
I discovered 1-for-AM, 2-for-PM by experimentation. Shouldn't this be in the user manual?

In calendar interface, standard is 30, but if you need 15 etc you need to a modification etc, use the normal interface with clock times or in details screen you can enter clock times enable fore the cats profile using CAC1 http://scn.sap.com/thread/3678682

Flex User Interfaces

I'm new to Flex. I've seen some great apps with great user
interfaces done in it. I have this question:
Is there ANYWHERE that helps one think about appropriately
laying out the Flex user interface? A book, a PDF, a style guide,
etc.? This would include, particularly, when to use container type
X vs container type Y, etc. Even a description of the best use of
all the containers and controls would be useful.

Katie, I see what you mean, something in this vein but for
Flex:
Apple Human Interface Styleguide
http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/OSXHIGu idelines.pdf
Let's ask guys at Adobe and Adobe Consulting to write such a
document.

User Interfaces: Is the ain~ui~mobile Package in AII 2.1 still available?

Hello!
During my studies on the outbound scenario script, I found out that there must exist an ainuimobile WebDynPro application for tagging and packing via mobile reader.
This application is mentioned nowhere in the documentation. Just the obviously older process script uses a link to this application. I didn't found an entry for ainuimobile in the Web Dynpro Content Administrator screen. There is just the ainsodesktop package available. When I try the /MobileReaderApplication on the ainuimobile package, I get a lot of errors. Even when I try the /MobileReaderApplication on the ainsodesktop package, I get errors.
My question is: Is the ainuimobile package or something similar in AII 2.1 available? Has it been removed from 2.0 to 2.1? If this ships with AII 2.1, why isn't it installed with the standard installation?
Thanks in advance,
Johannes

Hi Haakon,
single component export/import is only supported for application which are identical on the source and target system. It relies on the fact that other referenced components (for example user interface, templates, ...) use the same IDs on body systems.
Because of the APEX 4.2 upgrade, that's not the case anymore. As part of the upgrade, several new components had to be created on the fly which do now have different IDs on dev and prod. That's why the single component export/import doesn't work anymore.
If the single component export/import is used to patch applications, it's recommended to do a full export of the app on dev and import it into prod after upgrading to a newer version of APEX to make sure that body systems are using the same component IDs. After that your single component deployment should work as before.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Suitable user interface application for a billing system

I am seeking an appropriate friendly user interface application that is appropriate for a billing system to interact with an oracle 10gr2 database.
Thanks

I'm not sure I understand the question.
If you have a billing system, presumably the billing system has a user interface. It's not like you could just bolt a new user interface over the existing one without a tremendous amount of effort.
Are you looking to purchase a new billing system with a user-friendly interface? If so, it seems odd to post that here. Presumably, you'd want to create an RFP that vendors of billing systems could respond to.
Are you looking to build a new billing system? If so, there are dozens of languages, frameworks, and APIs that could be used. Without more information, no one could possibly provide any useful recommendations.
Justin

Book recommendation - user interface hardware

Similar Messages

Maybe you are looking for