DOCSLIB.ORG

Abstract Classes, 114, 150 Abstract Syntax Tree

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Gamma-Beck.book Page 381 Tuesday, October 14, 2003 7:27 PM Index A APIs Abstract classes, 114, 150 abstract-based v. interface-based, 114 Abstract syntax tree (AST), 319–323 compatibility, preserving, 143 Accessibility, 261–262 Debug Model API, 357 Actions Defensive API Rule, 266 bookmark, 351–352 Explicit API Rule, 266 Command pattern, JFace, 342–343 ground rules, 272 context menus, creating, 121–123 plug-ins, publishing, 263–264 contributing, 127 Program to API Contract Rule, 117 ExcludeTestAction, 224–227 subclassing, 329 filtering, 128, 354 Architecture global, 216 contributions in, 15–16 invoking, 26 overview of, 5–7 menu items to run tests, 39–44 Arguments, passing to builders, 159 repository, 346–347 Arrays, configuring builders, 155 run, 347 assertEditor() helper methods, 211 set apart associations, 228 AST (Abstract syntax tree), 319–323 sets, 23–24 ASTVisitor, 321–323 Shared ActionContributor, 220 asyncExec() method, 209 submenus, 57 Attributes, markers, 131–134 Active help, 255 Auto-test properties Adapt To IResource Rule, 353 controls, adding, 165–168 AdapterFactories, 289–294 dialog implementors, finding, 166 Adapters forward pointers, 170 factories, 288–294 overview, 161, 169 IAdaptable. See IAdaptable property pages, 161–164 pluggable, JFace, 336–340 run-time workbench, 168–169 resources to Java elements, 308–309 AutoTestBuilder, 179, 375–377 SelectionAdapter, 212 Auto-testing workbench-provided, 353–354 builders, installing, 154–159 Add CVS Repository, 346–347 editors, excluding tests with. See Editors, Anchors, 250–251 excluding tests 381 Gamma-Beck.book Page 382 Tuesday, October 14, 2003 7:27 PM 382 Index Auto-testing, continued Circle Three help, 250–251 defined, 5 natures, 154–159 overview, 281–282 AutoTestPropertyPage, 173 Circle Two closing, 275–280 defined, 4 B introducing as new feature, 104–106 Basic widgets, 326, 328. See also Standard overview, 93–94 Widget Toolkit (SWT) test-driven plug-in development. See Batching resource changes, 302–305 Test-driven plug-in development Beeping plug-in, 277–278 Circle Zero, 4 Binary projects, 11–14 Class creation wizard, 110, 117 Bindings, AST, 318–319 Class loaders, 54–55, 265 Black-box reuse, 342 Class path files, 307 Bookmarks Classes externalizing strings from code, 258 action invocation, 26 IResourceAdapter, 351–352 contributor implementation, 224–227 view, 194–195 exporting, 264–265 Bridge file-system resources, 296–299, 310 IAdaptable, 286 Browsing, Eclipse source, 12–14 loading, 16 Bruce Anderson’s Architecture Handbook plug-in, 40 workshop, 3 Classpath, 26–27 Bugzilla, 359 Code assist engine, 318–319 build. properties, 20 Collector views, 221 BuildCommand, 153 Colors Builders changing, 113–118 configuring using natures, 154–159 listening to testing progress, 111–113 forward pointers, 159 resetting, 235–238 marker resolution, 186–187 testing, 231–232 order dependency, 152–154 view contribution, 107–111 overview, 151 Commands passing arguments to, 159 BuildCommand, 153 resource listeners v. builders, 152 JFace actions as, 342–343 results, collecting, 317–319 Committers, 2 Bundling Plug-Ins into features, 83–86 “Common State,” 131 Compact maps, 132 Compare component, 358 C Compile errors, 129–130 Caches, Java element, 311–312 Composite Change Method Signature, 135–136 Eclipse components using, 355 changeColor() helper method, 209–210 Java element trees, 313–314 Circle One Standard Widget Toolkit (SWT), 326–330 closing, 89–90 workspace, 300–301 defined, 4 Compound widgets, 326, 328. See also Stan- overview, 33–34 dard Widget Toolkit (SWT) Gamma-Beck.book Page 383 Tuesday, October 14, 2003 7:27 PM Index 383 Configurers, 2 Core v. user interface (UI) functionality, 268 Conformance Rule, 26, 48 Core workspace Content providers accessing file-system resources, 296–299 ContentProvider, 232–233 batching changes, 305–306 outlines, 228 composites, 300–301 TableViewer, 195 Execute Around Method, 302–305 TestReportContentProvider, 204–210 overview, 295 Context menus resource changes, tracking, 302–305 creating, 119–124 resource trees, traversing, 301–302 extending, 124–128 CoreException, 172–173, 188–190 forward pointers, 128 createImage() helper method, 226 targeting, 126 createPartControl() view method, 200 Context-sensitive help, 251–255 CVS Repository, 346–347, 358 Contributed actions, UI workbench, 346–347 Contributed classes, 276 Contribution Circles D Circle One, 4, 33–34, 89–90 Debugging Circle Three, 5, 281–282 components, 356–357 Circle Two, 4, 93–94, 275–280 options, 179–183 Circle Zero, 4 perspectives, 241 closing, 355–360 Declarations completing, 9, 33 Auto-test properties, 162–164 defined, 3–5 Declaration Definition (manifest), 17 Contribution Rule, 15, 247 extension points, 69–71 Contributions implementation/declaration split, 16 actions, 57, 127 Defensive API Rule, 266 context menu extensions, 124–128 Deltas, resource contributors, 224–228 listeners v. builders, 152 declaration/implementation split, 16 resetting colors, 235–238 Eclipse architecture, 15–16 tracking Java element changes, 316–317 editors, 219–223 tracking resource changes, 304–305 extending, 2–3 Der Plan, 35 Hello button, 15–16 Design patterns. See Patterns, design invitation to make, 359–360 dev.eclipse.org, 359 JUnit plug-ins, testing, 100–103 Dialog implementors, 166 Lazy Loading Rule, 16, 44 DirtyListener, 234 menu. See Menu contributions Diversity Rule, 67 objects, 40, 125, 353 Doc.zip files, 255 overcoming inertia in making, 9 Domain objects, 207 plug-ins, publishing, 86–88 Dynamic enablement, menu item behavior, 57 precision, 45 Dynamic registration, listeners, 263 Relevance Rule, 43 RunTestAction, 254–255 submenus, 57 E views, 107–111 Eclipse Core runtime, 283–287 architecture, 5–7 Gamma-Beck.book Page 384 Tuesday, October 14, 2003 7:27 PM 384 Index Eclipse, continued Error dialog, 173–175 basics, 3 Events, JFace, 210–215 design principles, 4 Exception handling feature structure, 84 CoreException, 172–173 host, 94–95 error dialogs, 173–175 Java development tools (JDT), 5–7 IStatus, 172–173 JUnit. See JUnit logging errors, 175–177 learning about, 3–4 overview, 171–172 levels of applying, 1–3 ExcludeTestAction, 224–227 plug-in activation, 75 Excluding tests. See Editors, excluding tests plug-in architecture, 5 Execute Around Method, 302–305 Plug-In Development Environment (PDE), Explicit API Rule, 266 5–7 Explicit Extension Rule, 66–67 Run-Time, 94–95, 100 Extenders, 2 startup times, 89 Extensible Markup Language (XML), 16–17 test-driven plug-in development. See Extension Interface, 285–287, 294 Test-driven plug-in development “Extension Interface,” 285 user programming, enabling, 1 Extension Object, 285–287, 294 viewing test results. See Viewing test results Extension point schemas, 197–199, Editors 268–272 Rerun Marker Resolution, 187 Extension points, 74–75 test cases, 210–212 declaring, 69–71, 355 user interface (UI) workbench, 350–351 defined, 5 workbench, saving, 187, 192 Diversity Rule, 67 Editors, excluding tests explicit declaration, 355 contributing contributors, 224–228 Explicit Extension Rule, 66–67 contributing editors, 219–223 Fair Play Rule, 66 forward pointers, 228–229 Invitation Rule, 65–66 overview, 217–219 listeners, 68–69, 71–74 User Arbitration Rule, 222 loading, 71–74 views v. editors, 221 markerImageProvider, 142 Element trees overview, 65 composite, 313–314 property pages, 162 Extension Point, 270 publishing, 268–272 Grammar, 270 searching for, 40–42 scalability issues, 310 team component, 358 storing resource information, 299 Extensions Elements, Java context menus, 124–128 (virtual) proxies, 309–313 contributions, 16 Adapters, 308–309 defined, 5 filtering, 341–342 IExecutableExtension, 75 resources, 308–309 instantiation, 74 ResultView changes, listening to, 232–233 notifying, 77–78 tracking changes using Observer, 316–317 perspective, 241–244 trees. See Element trees test report view, 197 Enablers, defined, 2 Externalize String Wizard, 259 Gamma-Beck.book Page 385 Tuesday, October 14, 2003 7:27 PM Index 385 F Test Report View, 215–216 Factories test results, displaying, 63 adapters, 288–294 tracing, 179–183 IElementFactory, 350 Fragments, 260 Failed tests, 129–130. See also Markers FTP Plug-Ins, 88 Fair Play Rule, 66, 120, 122 Feature Plug-Ins, 88 feature.properties file, 280 G Features getAdapter() method, 287–288, 292 bundling plug-ins, 83–86 Global actions, 216 publishing plug-ins, 86–87 Good Fences Rule, 77–78 File-system resources, 296–299 Grammar, element, 270–271 FileWithProperties, 289 Granularity, 152 FillLayout algorithm, 332 GridLayout Filters algorithm, 332 actions, 128, 354 auto-testing property pages, 167 elements, 341 defining SWT layout strategy, 331 IActionFilter, 354 Resource Navigator, 341–342 test result view, 215 H tests, 218–219 Handles Finding tests, 147–150 resources, 296–299 Fixtures, creating with TestProject, 98–100 virtual proxies, 309–310 Flexibility v. performance, 355 Handling events. See Events, JFace FormLayout algorithm, 332 Heartbeat, 152 Forward pointers Hello button accessibility, 262 action implementation, 25–26 adding button to toolbar, 31 action sets, 23–24 auto-test properties, 170 Conformance Rule, 26 builders, 159 default implementations, 27 context menus, 128 forward pointers, 31 editors, excluding tests with, 228–229 Lazy Loading Rule, 29–30 extension points, defining, 74–75 manifest file, 21 final, 354–359 overview, 15–16 help, 255 plug-in project, creating, 18–20 instrumenting, 179–183 proxy actions, 29–30 Internationalization, 262 run-time workbench, 22–24 linked v. copied contents, 14 Sharing Rule, 23–24 marker resolution,
Recommended publications
  • Content Moderation Help Card

    Content Moderation Help Card

    Content Moderation Help Card Content Moderation Content Moderation allows you to approve or decline content before it is posted to your website. Click Content Moderation and select Moderated Groups to begin the setup process. You can configure Content Moderation two ways. 1. Choose workspaces that are always moderated (e.g., sections, site homepages). Content added to workspaces specified in a Content Group will require approval for all editors when you activate the Moderate All Editors checkbox for the Content Group. 2. Set combinations of workspaces and editors requiring moderation (e.g., the PTO section and user Eric Sparks). Creating Content Groups Adding Moderated Users You use Content Groups to define workspaces subject to Content Moderation. If you only wish to moderate some editors, you will need to add them as To create a Content Group... Moderated Users. Whenever a moderated user edits content in a workspace 1. In Site Manager, select Content Moderation from the Content Browser. specified in any of the Content Groups, that user will only be able to send 2. Select Moderated Groups. content for approval. 3. On the Content Groups tab, click New Content To add Moderated Users... Group. 1. In the Moderated Groups workspace, click Moderated Users. 4. Add a Name and a Description for your group and click 2. Click Add Group or Add User. Save. 3. Use Search to locate groups or users you wish to moderate. You can To add workspaces and moderators... filter groups by category. 1. Click on the name of your Content Group. 4. Click Select to the right of each group or user name.
  • United States Patent (19) 11 Patent Number: 5,854,629 Redpath (45) Date of Patent: Dec

    United States Patent (19) 11 Patent Number: 5,854,629 Redpath (45) Date of Patent: Dec

    USOO5854629A United States Patent (19) 11 Patent Number: 5,854,629 Redpath (45) Date of Patent: Dec. 29, 1998 54) ENHANCED SCROLLING TECHNIQUE FOR OTHER PUBLICATIONS CONTEXT MENUS IN GRAPHICAL USER The ABCs of Microsoft Office for Window 95 by Guy INTERFACES Hart-Davis, Copy right 1996, ISBN: 0-7821-1866–6. Primary Examiner Raymond J. Bayerl 75 Inventor: Richard J. Redpath, Cary, N.C. Assistant Examiner-Cuong T. Thai Attorney, Agent, or Firm-Gregory M. Doudnikoff 73 Assignee: International Business Machine 57 ABSTRACT Corporation, Armonk, N.Y. A technique is provided for permitting only a predetermined number of panes of a context menu to be displayed and the 21 Appl. No.: 774,560 Scrolling of the context menu for undisplayed panes. Before 22 Filed: Dec. 31, 1996 a context menu is displayed in a graphical user interface, it is determined whether the total number of panes or options (51) Int. Cl. .................................................. G06F 3/00 in the context menu exceeds the number of panes or options 52 U.S. Cl. .......................... 345/341; 345/123: 345/343; to be displayed at One time. If so, upon displaying the 345/973 context menu, a Selectable mechanism is displayed along the bottom edge of the context menu. User Selection of the 58 Field of Search ..................................... 345/123, 341, Selectable mechanism causes the context menu to Scroll up 345/343,973 to display previously undisplayed panes or options. When it is determined that panes logically exist above the top most displayed pane, a Selectable mechanism is displayed along 56) References Cited the top edge of the context menu, Such that user Selection of the top mechanism causes the Scrolling of the panes down.
  • MATLAB Creating Graphical User Interfaces  COPYRIGHT 2000 - 2004 by the Mathworks, Inc

    MATLAB Creating Graphical User Interfaces  COPYRIGHT 2000 - 2004 by the Mathworks, Inc

    MATLAB® The Language of Technical Computing Creating Graphical User Interfaces Version 7 How to Contact The MathWorks: www.mathworks.com Web comp.soft-sys.matlab Newsgroup [email protected] Technical support [email protected] Product enhancement suggestions [email protected] Bug reports [email protected] Documentation error reports [email protected] Order status, license renewals, passcodes [email protected] Sales, pricing, and general information 508-647-7000 Phone 508-647-7001 Fax The MathWorks, Inc. Mail 3 Apple Hill Drive Natick, MA 01760-2098 For contact information about worldwide offices, see the MathWorks Web site. MATLAB Creating Graphical User Interfaces COPYRIGHT 2000 - 2004 by The MathWorks, Inc. The software described in this document is furnished under a license agreement. The software may be used or copied only under the terms of the license agreement. No part of this manual may be photocopied or repro- duced in any form without prior written consent from The MathWorks, Inc. FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation by, for, or through the federal government of the United States. By accepting delivery of the Program or Documentation, the government hereby agrees that this software or documentation qualifies as commercial computer software or commercial computer software documentation as such terms are used or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern the use, modification, reproduction, release, performance, display, and disclosure of the Program and Documentation by the federal government (or other entity acquiring for or through the federal government) and shall supersede any conflicting contractual terms or conditions.
  • Eclipse Project Briefing Materials

    Eclipse Project Briefing Materials

    [________________________] Eclipse project briefing materials. Copyright (c) 2002, 2003 IBM Corporation and others. All rights reserved. This content is made available to you by Eclipse.org under the terms and conditions of the Common Public License Version 1.0 ("CPL"), a copy of which is available at http://www.eclipse.org/legal/cpl-v10.html The most up-to-date briefing materials on the Eclipse project are found on the eclipse.org website at http://eclipse.org/eclipse/ 200303331 1 EclipseEclipse ProjectProject 200303331 3 Eclipse Project Aims ■ Provide open platform for application development tools – Run on a wide range of operating systems – GUI and non-GUI ■ Language-neutral – Permit unrestricted content types – HTML, Java, C, JSP, EJB, XML, GIF, … ■ Facilitate seamless tool integration – At UI and deeper – Add new tools to existing installed products ■ Attract community of tool developers – Including independent software vendors (ISVs) – Capitalize on popularity of Java for writing tools 200303331 4 Eclipse Overview Another Eclipse Platform Tool Java Workbench Help Development Tools JFace (JDT) SWT Team Your Tool Plug-in Workspace Development Debug Environment (PDE) Their Platform Runtime Tool Eclipse Project 200303331 5 Eclipse Origins ■ Eclipse created by OTI and IBM teams responsible for IDE products – IBM VisualAge/Smalltalk (Smalltalk IDE) – IBM VisualAge/Java (Java IDE) – IBM VisualAge/Micro Edition (Java IDE) ■ Initially staffed with 40 full-time developers ■ Geographically dispersed development teams – OTI Ottawa, OTI Minneapolis,
  • 1400.0 Nrcs Minnesota Workspaces And

    1400.0 Nrcs Minnesota Workspaces And

    NRCS MINNESOTA WORKSPACES AND CUSTOMIZATION 1400.0 The Civil 3D software utilizes workspaces to control the display of the work area, including drop-down menus, placement of toolbars and commands included in toolbars. Available Workspaces are selected from the drop-down list on the Workspaces toolbar. Several standard workspaces will be provided when the program is installed, and the procedure for configuring customized workspaces is covered below. 1. Customizing workspaces a. To make changes to a workspace, select the Customize command from the drop-down menu on the workspaces toolbar. b. This will bring up the Customize User Interface window. Selecting a workspace from the available list in the top left hand pane will display all of the setting that can be modified in the Workspace Contents pane in the upper right hand side of the window. A listing of all of the available commands is included in the lower left hand pane. Click on the Customize Workspace button in the Workspace Contents pane to begin modifying the selected workspace. Civil 3D 2012 1 Rev. 1/2013 1400.0 WORKSPACES AND CUSTOMIZATION NRCS MINNESOTA 2. Partial customization files a. Additional customization files can be loaded as partial customization files, which gives you access to additional commands and menus. You can add partial customization files by clicking on the Load partial customization file icon next to the customization file drop-down list. This icon will be inactivated if you are in the process of customizing a workspace, so you will need to click on the Done button in the Workspace Contents frame (see above) to exit the customization mode before you can load a partial customization file.
  • User-Directed Screen Reading for Context Menus on Freeform Text

    User-Directed Screen Reading for Context Menus on Freeform Text

    User-Directed Screen Reading for Context Menus on Freeform Text Ka-Ping Yee Group for User Interface Research University of California, Berkeley [email protected] ABSTRACT CONTEXT MENUS This paper proposes a variation on existing screen-reading A widely used and effective user interface technique is the technology to help sighted users automate common context menu. By clicking on a GUI object on the screen, operations. When the user wants to perform an operation the user can bring up a menu of commands relevant to the related to some displayed text, the user can direct the object. This interaction embodies an object-oriented model window system to read text near the mouse pointer and by enforcing that the noun (object) be selected first, then offer possible actions. This can be considered an extension the verb (method). Among its advantages are the ease of the context menu applied to freeform text instead of with which it lets the user ask “What can I do?”. GUI objects. The proof-of-concept implementation of this However, this kind of interaction is typically available only technique helps the user make appointments based on for objects that are discretely identified within the software dates and times mentioned in e-mail. system, such as icons, hyperlinks, or window regions. It is Keywords interesting to consider how we might apply context menus Screen reading, context menus, group scheduling, to conceptual objects that do not yet have a distinct Hotclick, Smart Tags. representation in the software system, particularly infor- mation mentioned in freeform text. Here, we experiment INTRODUCTION with using string pattern matching to determine the target A significant part of the work we do on computers consists of the action.
  • Workspace Desktop Edition

    Workspace Desktop Edition

    Workspace Desktop Edition 8.5.124.08 9/27/2021 8.5.124.08 8.5.124.08 Workspace Desktop Edition Release Notes Release Date Release Type Restrictions AIX Linux Solaris Windows 02/28/18 Update X Contents • 1 8.5.124.08 • 1.1 Helpful Links • 1.2 What's New • 1.3 Resolved Issues • 1.4 Upgrade Notes Workspace Desktop Edition 2 8.5.124.08 What's New Helpful Links This release contains the following new features and enhancements: Releases Info • The rich text email editor Font menu now displays the full list of fonts • List of 8.5.x Releases available on the agent workstation. Previously, only one font per font family was displayed. • 8.5.x Known Issues • Screen Reader applications can now read the names of colors inside the email Rich Text Editor color Picker control. • Agents can now press the Enter key to insert a selected standard Product Documentation response into an email, chat, or other text-based interaction. Workspace Desktop Edition • It is now possible to sort the content of an 'auto-update' workbin based on a column containing integer values. For that purpose, the key-value pair 'interaction-workspace/display-type'='int' must be specified in the annex of Genesys Products the Business Attribute Value corresponding to that column in the Business Attribute "Interaction Custom Properties". Previously those columns were List of Release Notes sorted as strings. • On an Alcatel 4400 / OXE switch, a Supervisor can now fully log out of the voice channel when exiting Workspace if the value of the logout.voice.use-login-queue-on-logout option is set to true.
  • Devexpress Wpf Spreadsheet Disable Context Menu Items

    Devexpress Wpf Spreadsheet Disable Context Menu Items

    Devexpress Wpf Spreadsheet Disable Context Menu Items Tod remains dopey: she optimizing her tropopause glazed too mockingly? Rocky serpentinizes his defenselessness etherize staring or nasally after Markos overdramatize and quarreled predominantly, epithelial and adventurous. Graphological Fremont inters consecutively. Creating applications and disable them your needs of devexpress winforms spreadsheet document page break within a context menu that. See another list on nuget. It not contain constants, print and edit. Download rtf is used to disable, wpf devexpress wpf spreadsheet disable context menu items with a spreadsheet control contains messages received a data streams and winforms control. The context menu items added tables can get started with the corresponding value are. In outlook when it if this is a sequence with this image shows you leave a devexpress wpf spreadsheet disable context menu items by taking something like before we last step. Datagrid row or runtime and remote control suite of a number being made to pdf sticky notes to a new box becomes very basic. When one add the depth you hostage to clump into for solution people will be prompted to feature other components, we almost found ourselves lacking direction thus to taken how. Heat map Large heat map Tile map, and website in this browser for now next city I comment. Subscribers to disable displaying data needs of devexpress wpf spreadsheet disable context menu items and disable any. Start with another button in devexpress wpf spreadsheet disable context menu items and disable button programmatically start and. Add items in excel users want to disable displaying data. Or, start the spreadsheet has been improved the custom painting of junk property history search panel and there.
  • Infobar A01 Basic E.Pdf

    Infobar A01 Basic E.Pdf

    June 2011 Edition as35_ue.book ii ページ ２０１１年７月２０日 水曜日 午後２時２６分 Preface Before Using an au Phone Thank you for purchasing the INFOBAR A01. • You cannot receive or make calls in a location where the signal Before using your INFOBAR A01, be sure to read the Basic Manual cannot be received, even within the service area. Calling may not be (this PDF manual) to ensure correct usage. After you have finished available in a location where the signal is weak. If you move to a reading this manual, store this PDF manual and the printed manuals in location where the signal is weak during a call, the call may be safe places so you can retrieve them whenever you need them. If the interrupted. printed manuals are lost, please contact an au shop or Customer • The au phone is a digital cell phone and can maintain a high call Service Center. quality until the signal weakness reaches its limit. Therefore, once Basic Manual (this PDF manual) describes basic operations of major functions the limit has been reached, the call may be disconnected suddenly. of the INFOBAR A01. For detailed descriptions on various functions, refer to the Instruction Manual • Note that the au phone uses signals which may be intercepted by a (Japanese). third party. (However, the CDMA/GSM system enables highly Downloading Manuals confidential call communications.) You can download the Basic Manual (this manual) and the Instruction Manual • The au phone is a wireless station which is compliant with the Radio (Japanese) in PDF format from the au homepage. Act, and may be subject to inspections regulated by the Radio Act.
  • Citrix Workspace

    Citrix Workspace

    Citrix Workspace Citrix Product Documentation | docs.citrix.com July 13, 2020 Citrix Workspace Contents Citrix Workspace 3 What’s New 6 Get Started with Citrix Workspace 7 Citrix Workspace app and Citrix Receiver 11 Configure workspaces 16 Aggregate on-premises virtual apps and desktops in workspaces 36 Enable single sign-on for workspaces with Citrix Federated Authentication Service 46 Optimize connectivity to workspaces with Direct Workload Connection 57 Secure workspaces 66 Manage your workspace experience 73 Citrix Assistant 80 © 1999-2020 Citrix Systems, Inc. All rights reserved. 2 Citrix Workspace Citrix Workspace May 28, 2020 Citrix Workspace is a complete digital workspace solution that allows you to deliver secure access to the information, apps, and other content that are relevant to a person’s role in your organization. Users subscribe to the services you make available and can access them from anywhere, on any de- vice. Citrix Workspace helps you organize and automate the most important details your users need to collaborate, make better decisions, and focus fully on their work. For a complete description of each Citrix Workspace edition and included features, see the Citrix Workspace Feature Matrix. Get started Citrix Workspace includes a step-by-step walkthrough to help you deliver workspaces quickly. Each step guides you through the Citrix Cloud console with simple instructions for tasks like configuring your identity provider, selecting your workspace authentication, and enabling the other services that come with Workspace. The walkthrough also provides quick access to the technical information you’ll need when you’re assembling your deployment team and configuring your infrastructure and resources.
  • Rich UI Only)

    Rich UI Only)

    Menu Overview The menu widget is used to create navigation or context menus. Menu options are populated using the 'choices' and 'choice values' properties, and the user's selection is received in the application using the 'menu response' property. The menu widget is a control that is placed within an application screen and the user's selection is processed by the application itself. The menu widget is not, by itself, a device for calling other programs directly. For a menu system that is designed to call programs when the user makes a selection, see Atrium. Field Binding Dialog (Rich UI Only) Please visit the Field Binding page. Menu Options The menu options are specified using the 'choices' and 'choice values' properties. 'choices' specifies the option display text, and 'choice values' specifies the option return value. To specify multiple options, both properties accept a comma-separated list. To create sub-menus, items can be prefixed with a dash ('-') or multiple dashes to indent the items. For example, to create a menu as shown in the screenshots above: In Rich Display Files, the 'choices' and 'choice values' properties can be bound for dynamic options. If 'choice values' are not specified for each 'choice', then the 'choice' text will be returned to the program as-is. If more options are specified than will fit in the widget, scroll bars will appear as necessary. The scroll bars can be disabled by setting the 'overflow x' and 'overflow y' properties to 'hidden'. Mouse-over Animation By default, the mouse-over effect is animated, set the 'animate' property to 'false' to disable this behavior.
  • Get to Know Grants.Gov Workspace

    Get to Know Grants.Gov Workspace

    GET TO KNOW GRANTS.GOV WORKSPACE This guide provides an overview and some tips for using Grants.gov Workspace. It is not intended to be a step-by- step walkthrough that covers all aspects of submitting an application. Though switching from Coeus to agency systems marks a new business process for JHU, Workspace is not a new system. Once you’ve logged it to check Workspace out yourself, you’ll be surprised by how familiar the forms are and how intuitive the system is. In this guide, “Workspace” refers to the system and “workspace” refers to your workspace application. If have questions and want to learn more, we’ve added a list of resources and a FAQ to the end of this document. OVERVIEW GENERAL • Only use for Workspace for submissions to agencies that do not have a dedicated submission portal (e.g. CDC, HRSA, DOD, etc.) • Files cannot exceed 200MB. • Do not use the Adobe attachment function (the paper clip in the taskbar) to upload files. You must use the in-form “Add Attachment” option. Not using the in-form options will cause errors. • Disable pop-up blockers for the Grants.gov site. Some confirmation boxes appear in pop- up windows. • Available and required forms vary by FOA and agency. Always read the application instructions carefully. • Like the Adobe Legacy forms, completing the SF424 R&R form will populate some fields in the rest of the package. ACCESS AND OWNERSHIP • You can only create a workspace if you have a Grants.gov account with the “Manage Workspace” role. • The person who creates the workspace is workspace owner and can grant other users access to the workspace.