General user interface items

This question was posted in response to the following article: http://help.adobe.com/en_US/aftereffects/cs/using/WSB8DDC87E-577E-4099-A5D0-B266E9543E09a. html

How do I turn of all anti-aliasing on the After Effects User Interface within Mac OSX? I've got LCD Font Smoothing turned off in the System Preferences > General, and increased the minimum size of smoothing to above 12 points, and think that the interface fonts are surely smaller than 12 points, but they're still being anti-aliased.
For me, and I might be alone in this, I really like clear, pixel edged fonts, and this is especially true on the new Retina Macbook Pro when running in native 2800x1800 mode.

Similar Messages

General User Interface Data Flow Problem (LabVIEW 2012)

I am having problems reading & checking user input to a tabbed panel (see the tab "Test Parameters" in the attached example).
In essence I need to set and test many parameters.
In the example I need to create a binary mask from four select switches. On its own the scheme works a treat but in the context of
the tabbed panel the switches are never "reached". I tried to put a while structure around the switches (which works ex-vivo,
see attached "channelselect.vi") but the switches are never reached when I step through the code. Basically, I do not want to
leave the pane until all parameters have been set and verifyied.
I tried case structures (by group), flat structures (group by frame), Event Structures (event by nutton change)
I anticipate the same problems with the other sets of parameters. I need to change - set - check, in any order.
Understand the "setting" mechanism is tied to a sub-vi/class method where the parameter is tested, set and verified.
This is a long winded approach to ask the basic question "how would you lay it out"? I am sure this is a basic misunderstanding
on my part of the dataflow paradigm. I am not looking for anyone to do my work for me but I am looking to understand how this
works so I can get on with my day.
Thanks in advance for any help you can proffer.
Solved!
Go to Solution.
Attachments:
playUI.vi ‏96 KB
channelSelect.vi ‏12 KB

You can still have the tab control. You just don't need to do all of your processing when the user changes the tab. You can make event cases on the button presses as well. Treat the VI as an entire VI, not individual tabs that you have to manage.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
playUI.vi ‏82 KB

Use Group Policy to disable user interface items and shortcut keys in IE

Hi,
We are creating a kiosk mode of IE with full restriction to the machines drives and other applications. For that we need to disable all the shortcuts keys like ctrl, shift, alt and combination of these keys. Can anyone help me on this. i want to done this
through GPO. Client machines are windows 7 and we are having windows server 2008 R2 (AD server).
Thanks,
UdayaKumar S

I need to disable the ctrl, Alt, and shift keys and combinations of these keys with other keys as for example, cltrl+H, Ctrl+o, ets., and most important thing is, we need to apply it only through GPO not by using any other tools/ applications.
I'm not aware of any GPO-only methods to achieve your goal (hence my other suggestions), sorry.
Others might comment here with their thoughts/suggestions/experiences..
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

User Interface Fonts (CS4)

My wife just got a new PC and a 23.5" widescreen monitor. It's great, but with the high pixel density of the screen (1920x1080), DW CS4's fonts in the menus and other user-interface items are really small and hard for her to see. Windows 7 has a way of setting on-screen fonts to a larger size, which works in most programs, but (unsurprisingly) not in DW.
I think from past discussions that I recall that this is pretty much a lost cause, but since we're thinking of upgrading to CS6 when it comes out, I'd like to know if this situation has been remedied even in CS5 or CS5.5?
With the increase in screen densities this is getting to be a real issue, and it's just not good practice to render these fonts at what is essentially a fixed pixel size. We're also not getting any younger (I'm in my 60s), and it's not fun to have to strain to see what's on the screen.

User Interface (GUI) fonts like menus and such are set in Windows in the advanced Display settings, even in Windows 7.
That won't (or it may - I don't know) increase things like items in the Files panel, but you can set a larger size and different font for other menus.
The Code panel can be adjust infinitely in the DW preferences.
I work on a 1024X600 netbook and a 1440X900 19" monitor, but I still keep the resolution as high as I can get it, even though I need my glasses to see it.

Disable Items in User Interface - Custom

I have been looking through the Control Identifier/Policy ID number from the spreadsheets below.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=6627
I have been unable to find the following item in order to remove it using group policy. Can someone tell me definitively if it does not exist and if it does what is the correct ID in order to disable it through User Configuration->Administrative
Templates->Microsoft Outlook 2010->Disable Items in User Interface->Custom.
Under Tasks, New Task, Assign Task there is a check box next to "Send me a status report when this task is complete" that I want to remove.
Thanks,
-Ethan

Hi Ethan,
>>Under Tasks, New Task, Assign Task there is a check box next to "Send me a status report when this task is complete" that I want to remove.
Sorry, based on my knowledge and test, there is no corresponding policy ID to disable this checkbox.
In addition, I searched around and found that this setting should correspond to the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\options\Tasks
AddToUpdList
Regarding this point, the following article can be referred to for more information.
Task Options not in Outlook Object Model - Registry Workaround
http://www.outlookcode.com/threads.aspx?forumid=4&messageid=32320
Please Note: Since the website above is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best regards,
Frank Shen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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

Nokia's user interface and software A terrible e...

(hope this is in the right section, here goes)
I got my E63 about a month ago. I thought it only fair to list my grievances with the phone so far, because I am really close to selling it and buying something else, and I think Nokia deserves to know the reasons why, and will hopefully improve in the future.
I will start off with what I love about the phone, because I do in fact, really like it. The slim size, excellent keyboard, great connectivity like 3G and Wi-fi, and the reasonable battery life, make it a great phone, but its in the user interface, and actual usage of the phone, where things really start to fall flat.
The user interface is very disorganized and difficult.
Why is everything so hard to find and use? For example, if I want to change the applications that appear on my home screen, I need to navigate the following directory tree:
Menu > Tools > Settings > General > Personalisation > Mode Settings > Home Screen Applications > Application Shortcuts > Shortcut 1
and then, when I finally get to the list, the items arent even in any order!
You must be joking, what a horrible menu! Its insane. As a user, I feel like its a terrible experience.
But thats not all. Why are there 2 notes applications on my phone? There's notes, and active notes. Why does Nokia OVI store exist twice, once in the main menu, and once under installations? Why do I have Contacts, and OVI contacts on my phone? Why can't my phone have just one app that works well, instead of 2 that differ slightly.
Why is email setup in the installations menu? Why isn't it under email, where mailboxes get set up? Its just sitting there cluttering up Installations, when its something you only use once or twice.
Not to mention the fact that the configuration settings are all over the place, i.e. there is an Email Key setting in Menu > Tools > Settings > General. Its all on its own, not near anything. Why isn't it in the same menu where the other shortcut keys get set? Or even in the email app settings?
I am not naive, I know that the E63 is on the cheaper end of the scale, so I can't expect it to be the fastest phone in the world, but scrolling through my email in HTML mode is so horribly slow, and the view tends to jump from left to right on some emails, I hardly even use the phone to check my email anymore, which is sad because that is the reason I chose the E63.( for the nice keypad and email syncing)
These are just SOME of the things that I have noticed. So please Nokia, PLEASE PLEASE PLEASE! Spend some of your R&D money on user interface and user experience!
If there is anything you take away from this letter, let it be this:
Doing anything on the phone just feels like hard work, it makes me not want to use the phone.
Your phones should be simple and easy to use, even without the mass of Help files that appear in a lot of the menus.
I know, some people may say that if I want a better experience, I should be willing to buy a more expensive phone. Well, I can say that if I do spend more money on a phone, the chance is very slim that it will be a Nokia.
Really, I am not being nasty, just trying to be honest. I know that Nokia is run by human beings like myself, so I tried to be polite, and I dont intend to hurt anyones feelings.
I am quite willing to answer any questions you may have. Its a bit of a pipe dream, but I would love to see Nokia release an entirely new version of the phone software, with everything re-organized and re-done. The sad truth is that will probably never happen, and I will end up swopping my E63 for something that is easy and pleasant to use.
So please, let me know if there is anything I can do to change the situation, or help you guys in making this better for everyone.

"If your not used to symbian you'll learn it quick enough, compared to android it's childsplay."
On the contrary, Ive been using Nokia phones for the last 8 years, and for the last 2 years Nokia exclusively, and the UI has just got worse.
The fact that "you'll learn it" is of no comfort. Why should I have to spend hours learning how to use a cellphone? Whenever I want to do something I havent done before, I have to spend time digging through obscure menu options. That is absurd.
"What phone do you have in mind to replace the E63, that would help us users alot more then telling us what is wrong with your phone. Although over all I like my e63."
I don't have any specific phone in mind, Im just going to ask and look around until I find something with an operating system that is organised in a logical manner, and that allows me to access and read my email quickly and easily.
I put this here hoping that other users would come forward with UI related things that they were unhappy about, and then Nokia would take notice. I could easily have just gone out and changed phones, but I chose to do something different.

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

FAQ: 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) 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! [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)_ |http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf]
Edited by: Zhaojie Liu on Jun 10, 2009 10:08 AM

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

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

Illustrator CC 17.1.0 crashes when editing preferences, user interface. Running on MacBook Pro i7 OSX 10.9.5

Illustrator CC 17.1.0 running on MacBook Pro i7 OSX 10.9.5 - crashes when editing preferences, user interface. Also crashes when quitting application. Anybody any ideas?

While 2 GB is the absolute minimum to install Mavericks, if you want to do anything with the Mac you need more then that. Upgrade your RAM.
Until you upgrade the RAM seriously consider shutting down the Mac nightly. You should also seriously review the items in the User Login Items to see if there are any there that you really don't need to have startup with your login to reduce the amount of RAM you are using.

Not able to change user interface setting screen (SMCR) in solman 7.1sp3

Hi,
I am trying to change the change advisory board to Developer in request for change(SMCR) screen in General data navigation bar.
So i changed in partner schema -> define partner determination procedure ->SMCR0001(change request) ->user interface settings, like SAP solution manager 7.0 EHP1 version. not working
But solman 7.1 mapped to CRM UI using Business role SOLMANPRO using logical link and direct link group.
Plz help to change the user interface settings in SMCR screen?
Rg,
Karthik

Hi Andy,
Please check the below link
https://websmp102.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000311362008E
It help to change the Label in SMCR screen. if you face any issue post it.
After changing the Label , how to change the partner function in
background for particular field.
Ex. I have changed Change Advisory to Developer, but Parties involved
shows only CAB partner function.So how to change the partner function
after change the label for particular field.
Any idea?
Rg,
Karthik

User Interface (UI) Too Small on InDesign and CC Suite

I have a 27″ IMac running Yosemite 10.10.2. Its native screen resolution is 2560×1440.
When I opened CC Indesign 2014 for the first time I was shocked to see that the tools and rest of the user interface were SO SMALL that I was having tremendous difficulty seeing them clearly. I'm talking 5 and 6 point type!!! And the icons... minuscule!
I lowered the resolution of the display, but type then becomes fuzzy. I searched the web and found that there were others who were having the same problem.
I find it hard to believe that a company specializing in software for the design/creative community would overlook something as CRITICAL as size of the graphical user interface and its customization to work optimally on different platforms and with different display sizes and to satisfy the particular needs of each user.
The UI obviously greatly impacts our working speed and facility.
I called Adobe and their tech support could not help. I called Apple and got the same.
I've been a graphic designer for over 20 years. Frankly, at this point, I find the suite UNusable (I took a quick look at Photoshop and Illustrator and the same issue applies).
This is just unbelievable! Anyone out there have an answer?
Someone suggested we should repeat our complaints INDEPENDENTLY in the general forum instead of them being buried on one thread. GREAT IDEA!!

CC 2014 has a Expermental Preference you can use to increace the UI size 200% for High resolution displays

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 <b>about:config</b> 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 <b>about:config</b> 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/

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

General user interface items

Similar Messages

Maybe you are looking for