Flex vs YUI (Yahoo! User Interface Library)

I just completed an overview and shallow dive into a variety
of Web 2.0 technologies, and one result is that I decided to take a
deep look at YUI, Yahoo's AJAX library and compare it to Flex.
Check out my blog entry on beginning this comparison, and
stop on by the blog from time to time over the next six months to
see how my comparison progresses.
I love Flex, but have been wanting to see how AJAX compares.
Don't think I'll be disappointed.
FLEX vs AJAX - Taking
a Look at YUI

I just started, so I have no articles or links, but as I do
my comparison I'll be sure to post any. I'm pretty much just going
to approach it from the perspective of someone not knowing anything
about it trying to learn it. So I might try to avoid reading other
articles, just see what my experience is like.

Similar Messages

Graphical User Interface Library

I begin to develop a graphical user interface (which can be an applet or an application) whose main purpose is to display graph with nodes. I would like to use a powerfull graphical user interface library (even not free) but I don't know any. Someone's got an idea ?

Good god my writing is awfu! edit:
When something slows down a programme then in most cases algorithms are the source for the lag, try using better designed algorithms using less iterative content if you want some fast programmes.
Anyways concerning portablility and avalability on the internet there is always a price you pay and in most cases the price is speed.
Another concern is when using third-party libraries with Applets most users will have to download these to run your Applet, which of course takes it's time.
Maybe you want to think about your position against AWT and Swing - I don't want to promote them in any way - but speaking of applets there is nothing that I know could circumvent additional downloads.
Greetinng,
.o0|LIQID|0o.
ain't got time to loose.

CVI2009 general protection fault in user interface library commands

I have a program which we have been using and updating since 1999. We have updated it in various versions of LabWindows/CVI and had no problems. We recently updated it and compiled it in CVI2009 and now we get general protection faults. The faults are occurring in commands from the user interface library and not always in the same command. Sometimes it will process the commands properly and sometimes not. PlotXY, PrintCtrl, SetMouseCursor, and DiscardPanel have each caused the faults. Any suggestions?

Hello -
My initial guess is that you are running into the issue described in this KB. What is the version of cvirte.dll in c:\windows\system32? If it is 9.1.0.427, you need to upgrade to version 9.1.0.428, which is linked in the KB.
Let us know if that does not resolve it for you!
NickB
National Instruments

Yahoo! UI Library in IC Webclient

Hi,
I'm about to develop an own view, for a contact subject input in IC Webclient. The subjects (reasons) are arranged in four layers (Layer 1 'til Layer 4). Every subject consists of the catalog, codegroup and code. Together the build, in the first Level, the contact reason, in the second level, the first result, in third comes the second result and finaly media.
I considered for a long time back and forth, and came to the result, that there is nothing in the SAP library to be sufficient enough, to display this subject combination. Travelling through the web, I found the
<a href="http://developer.yahoo.com/yui/">Yahoo! UI Library (YUI)</a>, which, I thought, fits me needs. I immediatly built a page with flow logic and implemented the YUI. The result was perfect. I had a menu widget, just like the start menu of Windows XP.
But when I try to put the code into a IC Webclient view, I always get a JavaScript error.
Long speech, short sense, my question is: where do I have to include the JavaScript to get full use of the YUI?
Of course I will revard points for an answer
If I found it out in the meantime, I will surely post the solution.
Regards
Mathias
Oh, I forgot, I'm using CRM 5.0
Message was edited by:
        Mathias Schneider

Mathias,
I see the script files location as :
<script type="text/javascript" src="yui/yahoo/yahoo.js"></script>
<script type="text/javascript" src="yui/event/event.js" ></script>
<script type="text/javascript" src="yui/dom/dom.js" ></script>
<script type="text/javascript" src="yui/container/container.js"></script>
This is due to missing libraries hence you would be getting "Object expected" or "Object is undefined" errors.
You need to include these files before the Yahoo layout code is processed.
For ex: in the standard view "Workviewset.htm" you could copy all these scripts.(Don't modify it, rather copy it in your own BSP application)
After that, have you created following folders in mime :
1. yui/yahoo    (then upload file "yahoo.js" into this )
2. yui/event     (then upload file "event.js" into this )
3. yui/dom        (then upload file "dom.js" into this )
4. yui/container (then upload file "container.js" into this )
A sample to create "yui/yahoo" is :
Create folder "Yui" in you applications mime. Then in folder "Yui" create folder "yahoo".
Repeat this process for all scripts and then try running.
Let me know if you are comfortable copying and replcaing standar view (Its there in ICWC Cookbook) & any other isse you face.
Till then...
Cheers,
Ankur

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.

Re: Explorer like user interface

Re: Explorer like user interface
You'll want to use the geometry management features in Forte.
These can be controlled using the WidthPolicy and HeightPolicy
attributes on FieldWidget (see p 160 of the Display Library manual).
You can set these in your code, or using the 'Size Policy' dialog
off the widget property sheet.
Do the following:
Create a Window class, get into the Window Workshop.
In the Window property sheet, set the Window Style to Resizable,
set Autosize Enabled.
Create your TreeView and ListView, group them into a GridField.
In the TreeView and ListView Property Sheets, under Size Policy,
set the Width Policy and the Height Policy to Parent for both
the ListView and TreeView. Also set a minimum size for each (in mils)
the minimum size will prevent you from getting too small a window.
For the GridField, also set the WidthPolicy and HeightPolicy to Parent.
You may also want top set the Column Weight to the ratio you want for
the sizing of the Tree and List, say 2:3.
Now the sizing will work. You'll just have to write the code
to get data in you TreeView and ListView. Looking at
the examples for outline field:
$FORTE_ROOT/install/examples/display/soutline.pex
is a good place to start, if you haven't done it before.
Good luck!
Thanks, -Mark
X-Originating-Ip: [40.33.1.12]
From: "Ramarao P" <[email protected]>
To: [email protected]
Subject: Explorer like user interface
Date: Fri, 19 Jun 1998 11:50:08 PDT
Sender: [email protected]
Reply-To: "Ramarao P" <[email protected]>
Hi,
I would like to design a window which is similar to Windows Explorer.
Treeview in the left side, listview in the right side. I should be
able to drag and expand the size of the treeview. How is this possible
in Forte? I tried to use STATE attribute of widgets, but did not
succeed. Could anyone suggest me how to go about it.
Thanks in advance,
Ramarao
International Business Corporation-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Just to complete, here is a little sample in R3.F.2.0 done with
Treeview and listView.
Be aware that to give the user the possibility to resize the left
part, you should manage it yourself. If you use an outlinefield
instead, you can put WidthPolicy to seleted and then use FS_ROUTE
state to enable the user to resize it. But this occurs a bug with the
resize of the window. If you try this with the treeview, it will
be converted to FS_SELECTONLY which is nonsense here.
Also, don't forget that ListView only does Ascending Sort (Microsoft
does Ascending and Descending). So you should need to manage sort
yourself too.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
Mark Wallace wrote:
>
Re: Explorer like user interface
You'll want to use the geometry management features in Forte.
These can be controlled using the WidthPolicy and HeightPolicy
attributes on FieldWidget (see p 160 of the Display Library manual).
You can set these in your code, or using the 'Size Policy' dialog
off the widget property sheet.
Do the following:
Create a Window class, get into the Window Workshop.
In the Window property sheet, set the Window Style to Resizable,
set Autosize Enabled.
Create your TreeView and ListView, group them into a GridField.
In the TreeView and ListView Property Sheets, under Size Policy,
set the Width Policy and the Height Policy to Parent for both
the ListView and TreeView. Also set a minimum size for each (in mils)
the minimum size will prevent you from getting too small a window.
For the GridField, also set the WidthPolicy and HeightPolicy to Parent.
You may also want top set the Column Weight to the ratio you want for
the sizing of the Tree and List, say 2:3.
Now the sizing will work. You'll just have to write the code
to get data in you TreeView and ListView. Looking at
the examples for outline field:
$FORTE_ROOT/install/examples/display/soutline.pex
is a good place to start, if you haven't done it before.
Good luck!
Thanks, -Mark
X-Originating-Ip: [40.33.1.12]
From: "Ramarao P" <[email protected]>
To: [email protected]
Subject: Explorer like user interface
Date: Fri, 19 Jun 1998 11:50:08 PDT
Sender: [email protected]
Reply-To: "Ramarao P" <[email protected]>
Hi,
I would like to design a window which is similar to Windows Explorer.
Treeview in the left side, listview in the right side. I should be
able to drag and expand the size of the treeview. How is this possible
in Forte? I tried to use STATE attribute of widgets, but did not
succeed. Could anyone suggest me how to go about it.
Thanks in advance,
Ramarao
International Business Corporation-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Error in report builder wizard user interface

I am getting error 'REP-31954: Error in the Report Builder Chart Wizard user interface'.
The help subsystem states that I should make sure that the Chart Builder Wizard libraries are properly installed.
I am sure they are because all other wizards work fine, along with the Forms, Reports, etc.
I searched using Google and found two messages that indicate this is a bug in the program and not library installation related.
Does anyone know if this is indeed a bug that has not been resolved, or do I need to troubleshoot more on my end.
I re-linked Oracle graphics and checked the env variables, but nothing gets the Chart Wizard to work within Reports or Forms.
Any help/advice would be greatly appreciated.
Thank you.

Hi.
I am running developer 6i on my home machine (with Oracle 8i, v 8.1.7). I am at work at the moment, and I can't recall what the Reports version is. The same error occurs with Forms.
The filename that I downloaded is called 'd2k6irelease2.tar'.
I downloaded the version that is currently on Oracle OTN's download site, so I presume that is the latest version that should contain all patches, updates, etc.
Thank you for responding!

A more successful experiment in creating compositable user interfaces for Config Dialogs

A couple weeks ago I posted an experiment in creating compositable user interfaces using transparent subpanels. The approach might best be described as, "It at least was notable for being novel."
Today, I'm posting another attempt, this one along more traditional lines, and far more successful. Particularly notable: this one can do all the arbitrary composition of the last one AND it solves the TAB order problem.
This solution uses a picture control and renders N copies of a control. When the user tabs to a control or moves the mouse over the control, a real control slides into that position to be able to catch the events (update mouse over draw state, highlight for keyboard focus, handle typing, etc). When the Value Change occurs, a master array of data is updated and the picture control is updated.
This is something that has been attempted in various forms in the past, but there are two aspects of this particular implementation that make it nice:
its programmatic interface for specifying the behavior of the various objects should make it fairly easy for a user of the framework to programmatically generate their dialogs
it handles the TAB problem without flickering, something I haven't seen in other attemps
This idea spawns out of conversation about the previous experiment -- thanks to those of you who posted on various forums, e-mailed me, or, in a couple cases, showed up at my desk. That last one is not something I'm encouraging unless you work at NI... just saying. :-)
Now, this experiement has already yeilded some interesting conversation. We note that as long as controls are instantiated independent of each other -- that is, no property of one control depends upon the property of another control -- this dialog system scales nicely. But in this experiment, I implemented Radio Buttons, which interact with each other -- when one is set True, the others go False. As soon as controls start interacting with each other (such as graying out one control when a checkbox is toggled, or having expandable sections, or really complex cases like updating a graph as some options change, like happens in some Express VI config dialogs) then we start needing ways to refer to the other controls. This rapidly moves us in one of two directions: naming controls or creating references. The naming approach is definitely my preference as it fits better with dataflow and I can do some interesting effects with breaking apart some of the tree. But all of this quickly starts sounding like "Please implement a XAML parser in LabVIEW." For those of you unfamiliar with XAML, in the world of UI design, it might very well be the coolest thing since sliced bread. A XAML string would indeed fit with dataflow, and we could start building that up. I hesitate to head down this road for two reasons. One, as many have noted, there's really not a good XML parsing library written in LabVIEW that can give me a useful DOM tree. Two, that's a huge project and my gut sense is that you'd have to complete a fairly large chunk of it before you'd start seeing any return on investment. But it is worth thinking about -- I might be wrong. Wouldn't be the first time. This code that I've posted today can at least get you started on the generation side if one of you decides to become industrious.
I'm turning my attention away from this project for now... coding in G is lots of fun, and I wish I could spend more days doing it, but this has been a side project and it's time to get back to my assigned projects in text programming. Building a powerful platform for automatic UI generation in LabVIEW would be really useful -- I see lots of requests for this sort of thing, and other languages are pulling ahead of us in this domain.
[UPDATE 5/17/2012 - There is an improved version.]
Solved!
Go to Solution.
Attachments:
ConfighThroughCtrlCreation.zip ‏558 KB

Elijah K wrote:
Thanks for posting this Aristos. I would normally be one of those to go bug you at your desk, but in case I'm not the only one with this question... which particular flickering problem are you referring to? The act of switching tabs? In all honesty, I've never noticed...
When you move controls around on the screen, normally you try to Defer Panel Updates while you do that. But Defer Panel Updates has an effect on control's abilities to catch certain mouse clicks, so when you're trying to move a control to catch the mouse, you have to work a lot without Defer Panel Updates, so if you're adjusting captions, etc, to match the new location, you can see flicker as properties adjust. You can move the control off-screen, as long as you have already updated the picture control to reflect the changes. It took a while to catch all the ways that the flickering can crop up. I think I got 'em all.
Attached are the VIs saved for LV 2009. Actually, they're saved for LV 8.6, but it doesn't work in 8.6 because of a bug in the picture control that existed back then.
Attachments:
ComposableUI_LV2009.zip ‏391 KB

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.
==============================================

User Interface Guidelines for CRM 2007 are now available

The CRM UI Concept Team has made the [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/302d8152-002b-2b10-34bd-9ff3c712dd4b] available to the BPX community:
This document provides an overview of the on-premise as well as the off-premise versions of the SAP CRM Web Client User Interface (UI). It contains the properties and principles of the SAP CRM Web Client UI that are already committed and available. For planned features, refer to the corresponding specification documents.
The information in the guidelines starts with general topics, followed by details. The sections are organized with high-level topics like Page Types and Navigation Schema first, followed by the consecutive sections describing which building blocks and elements of the UI populate the various pages. A section typically starts with one or more screenshots of a central UI element with a generic explanation. The subsequent sections explain the detailed aspects of each element.
We hope that you will find this information useful.
Enjoy the new CRM UI!
Feel free to provide your feedback.
Edited by: Florian Weigmann on Jul 17, 2008 9:14 PM

Hi,
not sure why your download stops.. you can also try to download via this link: [http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf|http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf] (Document is 17,4MB of size)
Here the guidelines also have been posted together with an article about the CRM 2007 Web Client UI.
Hope this helps
Best regards
Ingo

Select-options in WDJ user interface

Hi Experts,
I would like to know why select-options found in SAP GUI screens is not available in WDJ. WDA however has provided this. Is there a possibility that this might be added sometime soon? Or may I please know the reason for omission.
Warm Regards,
Abdullah

no, what I mean is the select-options user interface component. Where in you can specify a range. For example: I can enter a range of employee numbers to be selected for a particular report. In that same control, I can omit some of the employees that I dont want. You can also check the following link for the select-options feature in WDA.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09fec07-0dab-2a10-dbbe-c9a26bdff03e

Row currency has changed since the user interface was rendered.

Hi All,
we have developed and deployed an Application in Production, before four months,
Suddenly for the past two days we are getting an error after the page being idle for 2- 3 minutes.
Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[3259 ]Once we get the error, the session scoped beans are resetting the values, and all the vo's cache are getting cleared(All the buttons in the page will get disabled and the menu will disappear).
but the same EAR is working perfectly in UAT and QA environments.
We have changed the "Enabletokenvalidation" as false and tested again, but the page itself is not loading after the change .
We have checked the Production and UAT weblogic server settings , but didn't find anything wrong.
WebLogic Server Version: 10.3.3.0
Studio Edition Version 11.1.1.2.0
if any ideas,
please help us...
Regards,
Ranjith

Hi All,
We have checked the error "Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[3259 ]", we tuned the view objects, we changed the application page flows, and it is found that once we turn off the statevalidation (statevalidation =false), the error is not popping up, but it is getting fired in the server side as
oracle.jbo.JboException: JBO-35007: Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[3259 ]
     at oracle.adf.model.binding.DCBindingContainerState.throwRowNotFoundException(DCBindingContainerState.java:318)
     at oracle.adf.model.binding.DCBindingContainerState.validateIterator(DCBindingContainerState.java:341)
     at oracle.adf.model.binding.DCBindingContainerState.validateStateFromString(DCBindingContainerState.java:482)
     at oracle.adf.model.binding.DCBindingContainerState.validateStateFromString(DCBindingContainerState.java:492)
     at oracle.adf.model.binding.DCBindingContainerState.validateToken(DCBindingContainerState.java:602)
     at oracle.adf.model.binding.DCBindingContainer.validateToken(DCBindingContainer.java:4852)
     at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.prepareModel(PageLifecycleImpl.java:117)
     at oracle.adf.controller.v2.lifecycle.Lifecycle$2.execute(Lifecycle.java:137)
     at oracle.adfinternal.controller.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:192)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.access$400(ADFPhaseListener.java:21)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.startPageLifecycle(ADFPhaseListener.java:231)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$1.after(ADFPhaseListener.java:269)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.afterPhase(ADFPhaseListener.java:72)
     at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.afterPhase(ADFLifecyclePhaseListener.java:54)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:364)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:160)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)No Difference in server side configurations of prod and UAT
we are not using back button press or any other rowItearation in these pages and we are not changing the row key through code.
Simple Master page, with inline edit , add and delete with thousands of records.
Error is popping up after the page is being idle for 2- 3 mins. on the next request after the idle time, the error will pop up .
once the row currency error came, the current state of the view objects will get reset to the initial state(First row).
we don't know how to fix this issue, this issue is coming in production server only...
if any body comes across such an issue, please help us to resolve this issue..
Regards,
Ranjith C

Re:error in report builder wizard user interface

I am getting error 'REP-31954: Error in the Report Builder Chart Wizard user interface'.
The help subsystem states that I should make sure that the Chart Builder Wizard libraries are properly installed. I am sure they are because all other wizards work fine, along with the Forms, Reports, etc. I searched using Google and found two messages that indicate this is a bug in the program and not library installation related. Does anyone know if this is indeed a bug that has not been resolved, or do I need to troubleshoot more on my end. I re-linked Oracle graphics and checked the env variables, but nothing gets the Chart Wizard to work within Reports or Forms. I am running developer 6i on my home machine (with Oracle 8i, v 8.1.7). The same error occurs with Forms. The filename that I downloaded is called 'd2k6irelease2.tar'. I downloaded the version that is currently on Oracle OTN's download site, so I presume that is the latest version that should contain all patches, updates, etc.
Any help/advice would be greatly appreciated.
Thank you for responding!

Hi Adrian,
Got the following when grepped through the web. You can give a try and see whether it works :
1) Open the report in the Builder. In the properties for the graphic image, change to the proper UNIX path. Also, ensure the .ogd file which is referenced is also placed in the proper UNIX directory, so that the new path is reflected accurately.
2) Ensure that your environment have the ORACLE_HOME set properly and then try re-linking with Graphics.
Thanks,
Vinod

CS5/CS4 GUI User Interface Design

I have always been very unimpressed with the user interface design on Adobe CS4. It's riddled with problems and changes that make no sense and offer no advantages.
For example, there is no longer a normal Windows title bar in many of the CS4 apps. This makes it much more difficult to maximize/restore applications since normally a Windows user could simply throw the mouse to the top edge of the screen and double click the title bar. In fact, doing this with CS4 apps has ZERO function (it doesn't do anything). One would think that by moving the menu commands to the top bar of the window chrome, Adobe would make these menus accessible from the top-most edge of the screen in order to increase usability. Unfortunately this is not so and clicking the top most edge of a maximized window does nothing.
Two other very important parts of an application user interface are the upper left and upper right corners. Normally when a Windows application is maximized, throwing your pointer to the upper right corner and clicking will close the application. Throwing the pointer to the upper left corner and clicking will reveal the application window menu. This happens in ALL applications... EXCEPT for Adobe CS4 programs. These two extremely important application window command locations have been completely disabled in Adobe CS4 apps. Clicking the upper most corner pixels in a maximized Adobe CS4 app does nothing.
Then there's the tabbed document window interface. If you float a document window and maximize that, normally you would expect it to become maximized within the application window as it should. Au contraire, in Adobe CS4, the document window maximizes itself ON TOP OF the application window, thus obscuring and disabling any access to the application window's tools/commands. I did report that as a bug during beta, but obviously it was ignored. Seems kind of obvious to me that the fact that a user could accidentally make the entire application completely unusable by maximizing a document window might be a problem.
It still alludes me as to why Adobe changed the CS4 user interface to something that breaks so many Windows UI conventions. Adobe CS3 was a practically perfect user interface design on Windows. It was very customizable, all of the normal Windows functions were properly in place.
What's the deal with the change?
I thought maybe the file menu was moved in place of the title bar in order to make more room for other UI elements, but it's actually pretty much the same size as the old file menu title bar combination in CS3.
With all these changes and with all the functionality losses, what exactly have we gained in the CS4 GUI? Seriously, I'm asking.
Anyway, I hope Adobe starts reading the Windows User Experience Guidelines (http://msdn.microsoft.com/en-us/library/aa511331.aspx) and brings CS5 back to the way a Windows application should behave. Proper theme adherence would be nice too.
Which brings me to Windows 7. I love love love the way Windows 7 groups application document previews in one taskbar icon and allows aero-peek for open windows. Adobe CS 4 obviously does not support this since it does not have normal document windows. I hope CS5 does because it is a great feature. I also hope Adobe CS5 implements the Windows 7 jumplists and maybe even a more touch/multi-touch friendly interface. I've become pretty good at processing photos in Bridge using the touchscreen, and it's very cool, but it could use some improvements.
For an example of great user interface design, has anyone tried Office 2010 on Windows 7 yet? http://www.istartedsomething.com/20090512/screencaps-office-2010-technical-preview-teched- 2009-keynote/
The faded transparent title bar and tabbed ribbon interface is absolutely gorgeous.

@Adam:
I agree with your comments! So well said!
And there are other issues, too -- by the color of the app window, you don't know if the window is active or inactive (focus or not in focus). Titles of panels which are inactive, are dark text over dark background -- hardly readable at all... And many more.
I really hope Adobe are listening...

Best way to create user interfaces

Hello Everyone,
So far my work with sap NetWeaver development was on the background processes but now i need to create some user interfaces, i read there are more than one way to do this like jsp, HTMLB , WebDynpro , and some others i think.
Can you give me some advises (and guides if it's possible) about what can i use?
The user interfaces must have the same look and feel as the SAP modules. I need to include some uploadcontrols, table views with sorting and paging features, buttons, list box, options buttons, check buttons, etc.
Also i need to send emails on demand and a task scheduler to send remaining by email.
Is there a user interface designer like dreamweaver or something like that to create user interfaces?
Hope you have some time to help me.
Regards.

Webdynpro java is best solution in userinterface devlopment
check the below links.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40239f38-a94a-2b10-c583-9b89187c3856
Send Email in webdynpro for java
http://help.sap.com/saphelp_nw04/helpdata/en/91/9c2226df76f64fa7783dcaa4534395/frameset.htm
SDN RSS Feeds spider using WAS Timeout Service
webdynpro sample tutorials
Now it is located under the link https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/web%20dynpro%20sample%20applications%20and%20tutorials.htm.
Koti Reddy

Flex vs YUI (Yahoo! User Interface Library)

Similar Messages

Maybe you are looking for