Patent application number | Description | Published |
20090307586 | USER INTERFACE (UI) DIMENSIONING - Determining a total dimension of items in computer-based user interface control (e.g., non-uniform items displayed in grid-view), may be accomplished by determining an estimated dimension value (e.g., for all items in a series) and combining (e.g., multiplying) that value with a total number of items (e.g., items in the series). If a viewport offset value and viewport item value is known, and/or a previously realized dimension and previously realized item value is known, the estimated dimension value may be determined by combining one or more of these values with values for realized items. Otherwise, the estimated dimension value can be determined by dividing the realized items dimensions value by the number of realized items. A total dimension value may be used by a user interface element, for example, to calculate an appropriate size and location of a scroll bar display. | 12-10-2009 |
20110125733 | QUICK ACCESS UTILITY - Users are enabled to perform tasks such as creating new content, searching for items, communicating with other users through a simplified access interface, at the same time defining a location for the access interface. A user may begin typing at any location on a canvas. The system ranks possible outcomes, suggesting one as the best match, where the user can override that choice upon which the resulting action is displayed at the point the input was initially placed. The user may be provided options to select among available tasks and the tasks may be performed without selecting an application. | 05-26-2011 |
20120158863 | HASH TAG MANAGEMENT IN A MICROBLOGGING INFRASTRUCTURE - Architecture that provides enhanced tag telemetry in a microblogging communications infrastructure. The architecture provides efficient discovery and tracking of topics that are of interest to a specific user by enabling users to follow (track) hash tags (#tag) and to receive and view all messages tagged with the hash tag appear in the user's personal feed. Each hash tag has a persisted tag page that aggregates all the associated activity, and includes a list that includes, but is not limited to, the tag followers, the most frequent user (uses the tag the most often in a specific time frame), a description, related tags, for example. The user can receive all the updates in the user's personal feed, and see an aggregation of all the messages and conversations associated with the tag in single place. The user can also mute the tag to prevent the receiving of tag information. | 06-21-2012 |
20120209850 | AGGREGATED VIEW OF CONTENT WITH PRESENTATION ACCORDING TO CONTENT TYPE - Architecture that facilitates the discovery of interesting and relevant content by a user in a serendipitous way on a microblogging site. For example, relevant content can be defined as connected to the user, the user's work, and user interests, while interesting content can be defined as content that does not directly affect the user, yet the user chooses to obtain (e.g., for viewing, interacting, etc.). The content can be presented as a tile cluster, where each tile is a specific content type (e.g., image, link, post, user recommendations, tags, etc.). Additionally, the content can be obtained and presented relative to a specific temporal setting such as the latest content. The different content types are visually distinguished such that one type of content looks and behaves differently from another content type. The user can also drill into content details from the top content. | 08-16-2012 |
Patent application number | Description | Published |
20080281885 | Interleaved garbage collections - An automated memory management or garbage collection routine uses a first garbage collection routine to perform garbage collection on new objects, and a second garbage collection routine to perform garbage collection on old objects. The two garbage collection routines are operated concurrently, with each routine separately marking objects to be reclaimed. The second routine may operate in a background mode by traversing a tree of objects from a copy of memory, while the first routine may operate on actual memory. | 11-13-2008 |
20130091186 | WORK STEALING OF PARTIALLY-MARKED OBJECTS - A process may utilize multiple garbage collector threads, each having the capability to steal partially-marked object references from an accessible mark stack having additional work that has yet to be processed. A partially-marked object reference may be represented as a pair of entries on a mark stack. A garbage collector thread may utilize an atomic operation to access the pair of entries in a prescribed manner to steal an unprocessed partially-marked object reference. In this manner, the workload of an overloaded garbage collector thread is offloaded to another garbage collector thread that may be idle thereby balancing the workload more evenly among multiple garbage collector threads. | 04-11-2013 |
20130159122 | OPTIMIZER AS AN APPSTORE SERVICE - Delivering applications to devices. A method includes receiving, at an AppStore, developer provided application code. The method further includes determining anticipated usage of an application based on the application code at end user devices. The method further includes using the determined anticipated usage, optimizing the developer provided application code at the AppStore to optimize for the anticipated usage. The method further includes delivering the optimized application code from the AppStore to an end user device anticipated to use the optimized application code according to the anticipated usage | 06-20-2013 |
20140317641 | CONTROLLING RUNTIME ACCESS TO APPLICATION PROGRAMMING INTERFACES - The present invention extends to methods, systems, and computer program products for controlling runtime access to application programming interfaces Embodiments of the invention allow library developers to more precisely and easily control which of their libraries' APIs can be called dynamically. Thus, their servicing and versioning burden can be more appropriately controlled. Further, application developers can control which such APIs to further exclude from dynamic calling scenarios, to minimize the runtime support overhead (e.g., preventing generation of metadata). | 10-23-2014 |