会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 3. 发明授权
    • Modular user interface
    • 模块化用户界面
    • US07389417B1
    • 2008-06-17
    • US10766082
    • 2004-01-28
    • Alice SteinglassYasser AsmiRoxana Arama
    • Alice SteinglassYasser AsmiRoxana Arama
    • G06F17/24G06F9/24G06F9/312
    • G06F9/451
    • A modular user interface (UI) with consistent sensory interactions across a plurality of selectable UI features that involve user interactions with a computing device. A controlling program invokes one or more functional UI modules each of which performs a data function of the corresponding UI feature. The data functions do not involve any sensory interaction with the user. Instead, a UI plug-in implements sensory interactions with the user, such as displays, sounds, animation, data entry, etc. The sensory interactions are based on the data functions and a skin file of visual, audio, layout, and other sensory data. The skin file, the UI plug-in, and the functional UI modules can be independently modified or replaced at any time to change sensory and/or functional aspects of the UI features. A UI engine manages computing resources and acts as a common communication gateway between the controlling program, functional UI modules, and UI plug-in.
    • 模块化用户界面(UI),其跨越涉及用户与计算设备的交互的多个可选UI特征具有一致的感觉交互。 控制程序调用一个或多个功能UI模块,每个UI模块执行相应的UI特征的数据功能。 数据功能不涉及与用户的任何感觉交互。 相反,UI插件实现与用户的感觉交互,例如显示器,声音,动画,数据输入等。感官交互基于数据功能和视觉,音频,布局和其他感觉的皮肤文件 数据。 皮肤文件,UI插件和功能UI模块可以随时独立修改或替换,以更改UI功能的感官和/或功能方面。 UI引擎管理计算资源,并且作为控制程序,功能UI模块和UI插件之间的通用通信网关。
    • 6. 发明申请
    • RESOLUTION OF RESOURCE OVER-ALLOCATIONS IN PROJECT PLANS
    • 资源分配在项目计划中的分配
    • US20090307035A1
    • 2009-12-10
    • US12132629
    • 2008-06-04
    • Alice SteinglassBonny LauRaju Iyer
    • Alice SteinglassBonny LauRaju Iyer
    • G06Q10/00
    • G06Q10/06G06Q10/06312
    • Architecture that introduces a new default leveling algorithm related to a leveling order that uses one or more of task identifier, start dates, and existing priority field, such that users do not need to define an explicit priority value for each task before using leveling. The architecture allows the user to reschedule only a specific task based on availability, without changing other tasks in the schedule. Users can select a single over-allocated task and the architecture looks at all other tasks in the overall schedule to find the next open timeslot when the assigned resources have capacity. The architecture further allows a user to selectively level a subset of tasks in a project. The user can choose to level only tasks that are relevant and the application only resolves over-allocation within the selection and excludes all other unselected tasks in the project.
    • 引入与使用任务标识符,开始日期和现有优先级字段中的一个或多个的调平顺序相关的新的默认调平算法的架构,使得用户在使用调平之前不需要为每个任务定义显式优先级值。 架构允许用户根据可用性重新安排一个特定的任务,而不需要改变进度表中的其他任务。 用户可以选择单个过度分配的任务,并且架构在整个调度中查看所有其他任务,以便在分配的资源具有容量时查找下一个打开的时隙。 该架构进一步允许用户选择性地对项目中的任务子集进行分级。 用户可以选择仅对相关的任务进行分级,并且应用程序仅解析选择内的过度分配,并排除项目中的所有其他未选择的任务。