Patent Grant
10185703
The present invention relates to the building of online visual design systems generally and to dynamic layout in particular.
Current visual design systems use a WYSIWYG (What You See Is What You Get) metaphor to provide a convenient, high-productivity and easy to use environment for the creation and editing of graphical applications and creations. Such creations or applications can include web sites, catalogs, presentations, e-shops, flow diagrams and as well as other application categories. These creations are deployed to systems which display them on a display screen, or to systems which print them.
A visual design system may integrate both static and dynamic content into the applications created in it. Static content may be stored locally and dynamic content may originate from a number of sources such as from the application itself, a database, an external dynamic data sources (or streams) such as a RSS feed or content generated by other users of the same system.
Visual design systems may be standalone systems (such as the Microsoft Visio diagram editor or the Microsoft PowerPoint presentation program), or may be embedded inside a larger editing system (such as the Microsoft Word AutoShape editor).
A designer using such a system may design a new application from scratch (starting with a blank screen), or may rely on predefined templates created by the application designer, by the system creator, or by the designer community. When a template is provided, the designer can customize it at will, adding, removing or modifying all elements of the template to create his or her version of the template.
Such applications generally consist of multiple pages. An application can include any number of pages and pages can typically be added or removed by the system designer and/or the end-user as required. Pages contain components which can be further classified as either atomic (those that cannot be broken down into sub-components) or container (which occupy a given screen area and can contain one or more further sub-components). Components may be fixed in shape and content, may be based on a content management system or may be based on user specified content such as a text area into which the designer enters text. Dynamic components can be based on external information (static or dynamic), such as a RSS feed displaying information from an external data source or the content of a given internet page.
Container components can be nested to a number of levels and can contain components of multiple types. Some containers are also limited to contain specific classes of contained components such as a photo album container which may only hold picture components. Component appearances and screen areas can be modified by moving, resizing, rotation and similar operations. Their appearance and behavior can also be modified by various modifiers, such as blurring and animation (e.g. the component has blurred edges, or appears on the screen by expanding from a single pixel, etc.) During the application creation and editing process, the content of a component may be entered and modified in a number of ways.
In visual design systems, typically the pages (containing the components) as well as the components themselves (container and atomic components) are often rectangles whose sides are parallel to each other and to the sides of the display screen. They are also parallel to the X and Y axes of the system on which the pages are being displayed or printed. In some cases, the components themselves are not axes-parallel rectangles. They may be a rotated rectangle, a combination of attached rectangles, or have a different shape altogether. In these cases, visual design systems (and their layout management element) typically handle the components using a per-component minimal enclosing axes-parallel rectangle which contains the irregularly-shaped component.
Components do not have to occupy mutually exclusive screen regions, and may in fact geometrically intersect each other. A component may also be situated completely within the boundaries of another component. The screen area overlap may be coupled with logical containment (i.e. the component “belongs” to a given container—and moves with the container wherever it goes), or be a mere geometrical overlap which is not based on any containment relationship. Whenever components intersect, a display priority attached to each component controls which component is displayed on top of which component. A visual design system typically employs a layout manager which manages component places, sizes, display order and related issues.
Visual design systems can be often be classified as absolute position or relative position systems (described in more detail herein below). In absolute positioning systems, the focus is on exact component positioning. The location of the components is defined as an absolute position value (x, y) relative to the containing entity, be it relative to the page itself or to a container containing the component. The position is typically expressed as an offset between the top left corner of the containing entity and the top left corner of the component.
In relative positioning systems, the focus is on the concept of flow or natural order. The system arranges components along a logical content flow, which typically corresponds to the reading order of the components whenever such an order is applicable. For example, an English language word processor is essentially a layout system for characters (and words) which uses the natural reading order of the English language (top to bottom and then left to right) to arrange the displayed characters and words. Another example is a blog editing system (such as the Wordpress blogging platform commercially available from wordpress.org), which arranges page elements (blog entries, talkbacks etc.) on a page according to a natural reading flow.
Thus, in a relative positioning system, the components are positioned relative to each other, so a component is displayed after (position-wise) the display of a previous component ends. Existing absolute and relative positioning systems both define a default screen or page size, which is used for all displayed pages. All relative positioning systems (and some absolute positioning systems) can increase this size as required to accommodate the addition of content to the page.
Visual design systems which use absolute positioning are best suited for exact layout and design of the displayed page. Such exact placement allows components to be properly sized, positioned and aligned on the displayed screen. For example, as illustrated in
There are also two main types of absolute positioning systems, constraint based systems and anchor-based systems. The types are not mutually exclusive and systems can contain elements of both systems. In visual design systems, constraints and anchors can be specified explicitly by the designer (through the system user interface) or inferred automatically by the system based on existing component layout and information. In a constraint-based system, the designer defines dynamic mathematical constraints on the relationships between the components residing on the screen. In anchor-based systems, the dynamic layout is defined in terms of anchors set between components and framework elements, as well as between the components themselves.
Dynamic layout, the automatic adjustment of components according to their content to fit on a page, is known in the art. In existing systems, dynamic layout is typically present in relative (rather than absolute) positioning systems. Current methods available provide both manual and automatic solutions using standard methodologies such as anchoring. Dynamic layout involves the moving and resizing of components on the screen based on dynamic layout triggers. These triggers may include content changes, multiple target platforms (display of the application using different technologies on different viewing platforms), multiple screen sizes (display of the application using a number of displays which have different sizes and resolutions), dynamic data (use of components containing dynamic data which changes over time), end user changes and application initiated layout changes. Component moving and resizing may also cause dynamic layout changes (i.e. act as a trigger), although the system should provide a way to move and resize component without triggering dynamic layout (e.g. by providing separate visual editing modes with and without dynamic layout triggering).
Reference is now made to
U.S. Pat. No. 5,796,401 to Wiener together with U.S. Pat. No. 7,554,689 to Tonisson and U.S. Pat. No. 7,634,725 to Nishikawa are believed to be representative of the prior art regarding dynamic layout.
There is provided in accordance with a preferred embodiment of the present invention, a system for implementing dynamic layout on a website. The system includes a receiver on a server to receive events caused by dynamic layout triggers from at least one client and a coordinator on the server to coordinate dynamic layout updates between the server and the at least one client according to the events and associated dynamic layout rules stored on the server.
Moreover, in accordance with a preferred embodiment of the present invention, the system also includes a database to store elements of the website, the associated rules and dynamic layout information.
Further, in accordance with a preferred embodiment of the present invention, the coordinator includes a pre-processor to preprocess for specific targets and un-displayed areas.
Still further, in accordance with a preferred embodiment of the present invention, the coordinator includes a dynamic data aggregator to aggregate and limit dynamic data.
Additionally, in accordance with a preferred embodiment of the present invention, the rules define the relationships between the web site elements and at least one other secondary website element.
Moreover, in accordance with a preferred embodiment of the present invention, the relationships are at least one of: explicit anchors, automatic anchors, semi-automatic anchors and gate conditions.
Further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the website elements and their content.
Still further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships_between the parallel edges of adjacent website elements along a primary direction.
Additionally, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the edges of the website elements with the matching edge of a secondary website element.
Moreover, in accordance with a preferred embodiment of the present invention, the information includes at least one of: the anchor information, the anchor creation history, the original position and size of the elements and designer and end-user parameters.
Further, in accordance with a preferred embodiment of the present invention, the updates include the manipulation of the website elements according to the event and the associated rules.
Still further, in accordance with a preferred embodiment of the present invention, the website elements are at least one of a component and a framework.
Additionally, in accordance with a preferred embodiment of the present invention, the at least one client is at least one of an editor client and a viewer client.
Moreover, in accordance with a preferred embodiment of the present invention, the triggers include at least one of component size and position changes, content changes, content formatting change, components having multiple configurations, multiple target platforms, multiple screen sizes, dynamic data, end user changes and application initiated layout changes.
Further, in accordance with a preferred embodiment of the present invention, the rules are at least one of: user defined and system defined.
Still further, in accordance with a preferred embodiment of the present invention, the website is viewable via at least one of: a regular browser, a specialized web browser and a non-browser client access application.
There is provided in accordance with a preferred embodiment of the present invention, a system for implementing dynamic layout on a shared website. The system includes a receiver on a server to receive events caused by dynamic layout triggers from at least two clients editing the shared website and a database communicating with the server to store elements of the shared website, rules and dynamic layout information associated with the events.
Moreover, in accordance with a preferred embodiment of the present invention, the rules define the relationships between web site elements and at least one other secondary web site element.
Further, in accordance with a preferred embodiment of the present invention, the relationships are at least one of explicit anchors, automatic anchors, semi-automatic anchors and gate conditions.
Still further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the website elements and their content.
Additionally, in accordance with a preferred embodiment of the present invention, the anchors define the relationships_between parallel edges of adjacent website elements along a primary direction.
Moreover, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the edges of the website elements with the matching edge of a secondary website element.
Further, in accordance with a preferred embodiment of the present invention, the information includes at least one of: the anchor information, the anchor creation history, the original position and size of the elements and designer and end-user parameters.
Still further, in accordance with a preferred embodiment of the present invention, the website elements are at least one of a component and a framework.
Additionally, in accordance with a preferred embodiment of the present invention, the triggers include at least one of component size and position changes, content changes, content formatting change, components having multiple configurations, multiple target platforms, multiple screen sizes, dynamic data, end user changes and application initiated layout changes.
Moreover, in accordance with a preferred embodiment of the present invention, the least two clients are at least one of an editor client and a viewer client.
Further, in accordance with a preferred embodiment of the present invention, the rules are at least one of: user defined and system defined.
Additionally, in accordance with a preferred embodiment of the present invention, the shared website is viewable via at least one of: a regular browser, a specialized web browser and a non-browser client access application.
There is provided in accordance with a preferred embodiment of the present invention, a system for implementing dynamic layout on a website. The system includes a coordinator on a client to receive events caused by dynamic layout triggers on the client. The system also includes an updater on the client communicating with a database implemented on a server, with the database storing elements of the website, rules and dynamic layout information associated with the events in order to update the elements, according to the events and associated rules.
Moreover, in accordance with a preferred embodiment of the present invention, the coordinator includes a pre-processor to preprocess for specific targets and un-displayed areas.
Further, in accordance with a preferred embodiment of the present invention, the coordinator comprises a dynamic data aggregator to aggregate and limit dynamic data.
Still further, in accordance with a preferred embodiment of the present invention, the rules define the relationships between the web site elements and at least one other secondary website element.
Additionally, in accordance with a preferred embodiment of the present invention, the relationships are at least one of: explicit anchors, automatic anchors, semi-automatic anchors and gate conditions.
Moreover, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the website elements and their content.
Further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships_between parallel edges of adjacent website elements along a primary direction.
Still further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the edges of the website elements with the matching edge of a secondary website element.
Additionally, in accordance with a preferred embodiment of the present invention, the information includes at least one of: the anchor information, the anchor creation history, the original position and size of the elements and designer and end-user parameters.
Moreover, in accordance with a preferred embodiment of the present invention, the updates include the manipulation of the website elements according to the event and the associated rules.
Further, in accordance with a preferred embodiment of the present invention, the website elements are at least one of a component and a framework.
Still further, in accordance with a preferred embodiment of the present invention, the client is at least one of an editor client and a viewer client.
Additionally, in accordance with a preferred embodiment of the present invention, the triggers include at least one of component size and position changes, content changes, content formatting change, components having multiple configurations, multiple target platforms, multiple screen sizes, dynamic data, end user changes and application initiated layout changes.
Moreover, in accordance with a preferred embodiment of the present invention, the rules are at least one of: user defined and system defined.
Further, in accordance with a preferred embodiment of the present invention, the website is viewable via at least one of: a regular browser, a specialized web browser and a non-browser client access application.
There is provided in accordance with a preferred embodiment of the present invention, a method for implementing dynamic layout on a website. The method includes: receiving events caused by dynamic layout triggers from at least one client and coordinating dynamic layout updates between a server and the at least one client according to the events and associated dynamic layout rules stored on the server.
Moreover, in accordance with a preferred embodiment of the present invention, the method also includes a database to store elements of the website, the associated rules and dynamic layout information.
Further, in accordance with a preferred embodiment of the present invention, the coordinating includes preprocessing specific targets and un-displayed areas.
Still further, in accordance with a preferred embodiment of the present invention, the coordinating includes aggregating dynamic data and limiting dynamic data.
Additionally, in accordance with a preferred embodiment of the present invention, the rules define the relationships between the web site elements and at least one other secondary website element.
Moreover, in accordance with a preferred embodiment of the present invention, the relationships are at least one of: explicit anchors, automatic anchors, semi-automatic anchors and gate conditions.
Further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the website elements and their content.
Still further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships_between parallel edges of adjacent website elements along a primary direction.
Additionally, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the edges of the website elements with the matching edge of a secondary website element.
Moreover, in accordance with a preferred embodiment of the present invention, the information includes at least one of: the anchor information, the anchor creation history, the original position and size of the elements and designer and end-user parameters.
Further, in accordance with a preferred embodiment of the present invention, the method also includes manipulating the website elements according to the events and the associated rules.
Still further, in accordance with a preferred embodiment of the present invention, the website elements are at least one of a component and a framework.
Additionally, in accordance with a preferred embodiment of the present invention, the at least one client is at least one of an editor client and a viewer client.
Moreover, in accordance with a preferred embodiment of the present invention, the triggers include at least one of component size and position changes, content changes, content formatting change, components having multiple configurations, multiple target platforms, multiple screen sizes, dynamic data, end user changes and application initiated layout changes.
Further, in accordance with a preferred embodiment of the present invention, the rules are at least one of: user defined and system defined.
Still further, in accordance with a preferred embodiment of the present invention, the website is viewable via at least one of: a regular browser, a specialized web browser and a non-browser client access application.
There is provided in accordance with a preferred embodiment of the present invention, a method for implementing dynamic layout on a shared website. The method includes receiving events caused by dynamic layout triggers from at least two clients editing the shared website and communicating with a database implemented on the server. The database stores elements of the shared website, rules and dynamic layout information associated with the events.
Further, in accordance with a preferred embodiment of the present invention, the rules define the relationships between web site elements and at least one other secondary web site element.
Still further, in accordance with a preferred embodiment of the present invention, the relationships are at least one of explicit anchors, automatic anchors, semi-automatic anchors and gate conditions.
Additionally, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the website elements and their content.
Moreover, in accordance with a preferred embodiment of the present invention, the anchors define the relationships_between parallel edges of adjacent website elements along a primary direction.
Further, in accordance with a preferred embodiment of the present invention, the anchors define the relationships between the edges of the website elements with the matching edge of a secondary website element.
Still further, in accordance with a preferred embodiment of the present invention, the information comprises at least one of: the anchor information, the anchor creation history, the original position and size of said elements and designer and end-user parameters.
Additionally, in accordance with a preferred embodiment of the present invention, the website elements are at least one of a component and a framework.
Further, in accordance with a preferred embodiment of the present invention, the triggers include at least one of component size and position changes, content changes, content formatting change, components having multiple configurations, multiple target platforms, multiple screen sizes, dynamic data, end user changes and application initiated layout changes.
Still further, in accordance with a preferred embodiment of the present invention, the at least two clients are at least one of an editor client and a viewer client.
Additionally, in accordance with a preferred embodiment of the present invention, the rules are at least one of: user defined and system defined.
Moreover, in accordance with a preferred embodiment of the present invention, the shared website is viewable via at least one of: a regular browser, a specialized web browser and a non-browser client access application.
There is provided in accordance with a preferred embodiment of the present invention, the method includes anchoring the edge of a website element with the matching edge of a secondary website element.
Moreover, in accordance with a preferred embodiment of the present invention, the edge is at least one of a top edge and bottom edge.
The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:
It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.
In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.
Many of the types of visual design systems as discussed in the background are aimed specifically at the design and editing of websites. Websites are typically hosted by a remote server and accessed locally on a client integrated with a browser for access to the layout and content residing on the remote server. Reference is now made to
It will also be appreciated, that in existing systems known in the art, the functionality related to dynamic layout is performed entirely on the editing or viewing software client 30, without involving the capabilities provided by a centralized application-specific server which supports the dynamic layout process. In existing systems, a copy of the website in question may often be held locally for editing. Changes made to a website are stored locally and then later synchronized with the main copy of the website which is stored on website server 10. Such synchronization may occur whenever the designer moves from page to page, on explicit designer requests, over a given time period or using another mechanism.
Applicants have realized that current methods of working with dynamic layout are limiting. There are two solutions that are in common use in absolute-positioning systems for the problems arising when there is insufficient space to display the required content. One common solution is dynamically adding scroll bars (e.g. HTML IFRAME or DIV “scrolling=auto” property) to the component so to enable the application user to scroll over the content (be it text or image). Another common solution is dynamically changing the text font size to fit into the available space (such as. Microsoft Excel's “alignment|shrink to fit” option). It will be appreciated that scroll bars require the application user to scroll to read the full text, or view the full media and that this is particularly bothering to users when there is only a small amount of text which doesn't fit into the allocated space; Horizontal scroll bars may be especially problematic as they require text to be scrolled twice for every line read, and not just when finishing reading the page (as vertical scroll bars do). A similar problem exists with vertical scroll bars applied to components displaying vertical text such as Japanese and Chinese traditional text writing. Scroll bars also cannot be used in print media output, or in situations in which user interaction is limited (such as applications displayed on a data kiosk). Text font resizing is often unacceptable as the text would have to shrink to a size below what is reasonable for a user to view.
As described herein above, dynamic layout, when used in absolute positioning systems, involves the moving and resizing of components on the screen based on dynamic layout triggers. Some examples known in the art for absolute positioning systems which also comprise dynamic layout include: the use of absolute alignment in HTML CSS (with 4 directional margin specification) and the use of anchoring and docking the controls in a graphical user interface (GUI) design for systems running under the Microsoft Windows operating system. Anchoring (described in more detail herein below) entails connecting the edge of a GUI component to the edge of a container, causing the component to be resized or moved when the container changes. Docking entails specifying that multiple GUI components are stacked (based on predefined priority) near a given edge of a container. These options can be found, for example, in the Microsoft dynamic layout controls and in the Telerik dynamic reports system commercially available from Telerik.
Applicants have realized that these simple dynamic layout solutions and systems cannot create complex, high quality web sites (such as e-Commerce store fronts) that integrate multiple dynamic content and dynamic layouts. There are often cases in which components have to be moved or re-sized making it difficult to maintain the preplanned exact layout. This layout can become unstable and incorrect. This is especially relevant when the content is external to the system, and reflects for example, an external product database which is not managed by the design system itself. Dynamic layout is also a necessity for devices such as smart phones and tablets that have smaller display areas than a regular personal computer. Applicants have further realized that the use of a centralized application-specific server combined with dynamic layout principles may allow for concurrent editing of the same website by multiple users on multiple clients, may allow for the integration of dynamic content from multiple sources and may also allow automatic real time modifications due to dynamic data and screen size changes.
Reference is now made to
Server-based system 100 may comprise two main interconnected sub-systems, a client component 110 and a server component 120. It will be appreciated that there may be more than one client component 110, connected to server component 120 at any one time. It will be further appreciated that there may two types of client components—an editor client 110A (used by the application designer) and a viewer client 110B (used by an end user of the application). It will also be appreciated that both the editor client 110A and the viewer client 110B may be implemented either using the same architecture and technology—for example, both are FLASH-based downloaded applications, or both are iOS-based applications—or may use entirely different architecture and technology to the same advantage. A browser based application may also be used, which may be downloaded but combines both client and server side work. Clients 110A and 110B may also have different screen sizes and geometries used for display. It will also be appreciated that both clients 110A and 110B may be personal computers with a full browser and full HTML support, or may be smartphones or tablets, or alternatively may be an application embedded within a social network. The latter may internally limit the availability of HTML and JavaScript which can be used in the application display (e.g. for security reasons or due to limitations of its embedded browser).
Server 120 may comprise a website application 60, a dynamic layout editor 70 and a data repository 80. Website application 60 may also be installed locally on clients 110A and 110B. Data repository 80 may store the pages and templates 65 pertinent to website 60, together with component information as well as rules and parameters pertinent to dynamic layout actions.
Dynamic layout editor 70 may comprise an event receiver 125, a text handler 130, an image handler 140, a component engine 150, a dynamic layout coordinator 170, a pre-processor 155, an updater 175 and a server module 180 as illustrated in
In an alternative embodiment to the present invention, dynamic layout editor 70 may also be implemented on the client side as part of client 110, for example using a locally installed visual design system, a dynamically downloaded application (such as a Flash application) or a browser-based application (which runs inside the client browser using technologies such as HTML5 and JavaScript).
In yet another alternative embodiment to the present invention, dynamic layout editor 70 may be implemented on both server 120 and client 110. For example, system 100 may handle dynamic layout processing based on triggers activated by client 110 and handle dynamic layout processing based on triggers resulting from server-side activities (such as on-line data feeds) on server 120. The division of tasks may also be dynamic, shifting tasks between the two as necessary (e.g. to optimize performance and bandwidth usage).
It will also be appreciated that there may be numerous embodiments for the client component 110. In an alternative embodiment to the present invention, as illustrated in
In an alternative embodiment to the present invention, client 110 may be integrated with a larger software system so to provide a rich media application editing, layout and display services inside the larger software system. This could be through the use of integration technologies (such as Microsoft's ActiveX technology) or by being embedded as a specialized plug-in inside the larger system (for example by integrating the client sub-system as Facebook application). Reference is now made to
In yet another alternative embodiment to the present invention, client 110 may be integrated with a larger software system which provides its own editing and display user interface. System 100 may be used only as a back-end engine to provide content formatting and layout information, but the actual edit-time and run-time display is performed by the larger software system as is illustrated in
It will be appreciated that work may be divided between the client and server components (110 and 120) as required for the specific web site design system (as described herein above) and there may be various embodiments to the combination as is described herein below.
It will also be appreciated that system 100 may also be integrated with the same server infrastructure used to host the pertinent website to end users which use the pertinent web site (and are not involved in its creation). It will also be appreciated that this server does not have to be the same physical server, as such systems typically employ numerous servers in a load-balancing or cloud configuration and these numerous servers may be optimized for specific sub-tasks.
It will be further appreciated that the client-side software does not have to be installed, or otherwise permanently reside on the client computer used by the end user. It may of course be installed on it, but it may also be downloaded on demand, using technologies such as Adobe Flash, browser-based JavaScript or Java.
In accordance with an embodiment of the present invention, system 100 may be built using server assisted dynamic layout. Tasks related to dynamic layout may be performed with the assistance of server 120 which may cooperate with either client 110A or 110B via dynamic layout coordinator 170. The direct actions of the designer or end-user 5 working on the created web site or application may trigger dynamic layout activity. It will be appreciated that such dynamic layout activity may often (but not always) be performed on the client side, so to provide immediate response to designer or end user editing actions and to avoid network latency during visual editing. However, even for such cases, server 120 support may be required in cases involving very low-power end-user machines and reasonable speed communication links to server 120.
In an alternative embodiment to the present invention, certain events triggering dynamic layout, such as changes resulting from dynamic data or from cooperation with concurrent users, do not require instant feedback, and therefore the required processing may be performed entirely by server 120.
It will also be appreciated that system 100 may create and maintain an internal data structure which contains the full dynamic layout information and is persistent across all editing sessions known as stored dynamic layout information (SDLI). This information may be stored in rules repository 80 which may sit on server 120. A copy of the information may also be stored locally on client 110 in cases where end-user 5 is allowed to modify certain aspects of the application (such as the size and position of certain components). There may be multiple versions of the stored dynamic layout information for the same stored application. This information may include anchor information, anchor creation history and the original position and size for each component affected by the dynamic layout as well as any designer or end-user set parameters. It will be further appreciated that website 60 may provide a suitable interface with the designer and/or end user 5 in order to receive such designer or end-user set parameters.
However, since many events that trigger dynamic layout such as changes resulting from dynamic data or from cooperation with concurrent users, do not require instant feedback, server 120 may entirely perform the required processing itself or may be assisted by server 120.
It will also be appreciated that system 100 may also provide server assisted dynamic layout services both at the component and container levels for different pages of the pertinent visual design system. The container in question may be a full page containing components, or it may be a sub-container inside the page or inside a large container as illustrated in
It will also be appreciated that component-level server assisted dynamic layout may include the actions needed to present modified versions of a specific component. The code implementing components in website 60 may run on the client-side software, such as the above mentioned iOS application or a browser based application. Alternatively the code does not have to reside on the client-side system but may still run on it (i.e. through dynamic downloading); it may also be completely server-side in cases where the system is completely server based and uses a very low CPU-power client. Certain elements may have a matching server-side element that implements some of the processing-intensive tasks related to dynamic layout.
Container-level server assisted dynamic layout may include an actual calculation of layout based on the properties of the collection of components which reside inside a single container, the calculation is not related to a single component but to the interaction between the set of components and the area in which they reside.
It will also be appreciated that server assisted dynamic layout may be performed by system 100 at a number of stages during the application editing process: System 100 may perform them fully on-line whenever a page is accessed by client 110 or even while the page is being viewed, whenever a new version of a given page or when the completed application is saved or published. System 100 may also perform server assisted dynamic layout in parallel to regular system functioning, based on collected information and usage patterns gathered from tracking actual application use, and not as response to a given page access or modification. This could be done, for example, during times of lower system load.
Reference is now made to
As mentioned herein above, dynamic layout editor 70 may comprise dynamic layout coordinator 170 which may comprise a text handler 130, an image handler 140 and a component engine 150. It will be appreciated that for text-based components, text handler 130 may handle different fonts, font sizes and text reformatting. For image-based components, image handler 140 may adjust the scaling of the image to a different size or possibly change the amount of details in vector-based images (such as maps). Similar changes may apply to other media types (such as video) as well. For complex components (such as a store front component), an actual change in the structure of the components, including removing or adding graphical user interface elements for the specific component may be dealt with using component engine 150.
It will be further appreciated that the above mentioned operations may typically be performed on-line, with server 120 responding to specific client (110A and 110B) requests. However, server 120 may also cache requests, so the processing done for client 110A using a specific screen size would be immediately useable for additional users of the same application which deploy it on a system of similar size such as client 110B. These cached versions of the components may be stored (taking images for example) using a data structure such as an image pyramid or mipmaps.
It will also be appreciated that the design environment of system 100 may use absolute positioning to provide a high quality website layout (in both the editor 110A and viewer 110B clients) to support automatically generated changes to the designer-defined layout. It may also integrate dynamic layout management as well as dynamic content separate from the design information. Dynamic layout editor 70 may be integrated with both the editing and the viewer components (110A and 110B), so the same dynamic layout rules can be applied to changes in website 60 resulting from explicit design actions (by the site designer), as well as to changes in the web site resulting from changes in the dynamic information included in website 60. These dynamic layout rules are discussed in further detail herein below.
It will be appreciated that there may be different embodiments to system 100 regarding the server 120/client (110A and 110B) relationship when dynamic layout processing is performed. Some of these embodiments are described herein below. In most of these cases, server 120 may modify the stored dynamic layout information data stored on it. This could be the stored dynamic layout information of currently un-displayed pages (which would be loaded when required), or that of currently displayed pages (which would be synchronized with the client-side version of the same information).
Target-Specific Dynamic Layout Processing.
As discussed hereinabove, system 100 may have clients 110 of multiple types accessing the same application. Clients 110 may have different characteristics, and may employ completely different technologies for the display of the application. Clients 110 may further have different screen sizes and geometries used for display. In order to overcome these obstacles, the application in question must be adapted to each of the different display platforms and display screen geometries. In existing systems known in the art, there are two major approaches to this problem of adaptation. One approach is editor-side adaptation—editor client 110A creates multiple versions of the application each time the application is saved, or alternatively when the application is finally published and loaded into a server for access by the viewing clients. Another approach is viewer-side adaptation—editor client 110A saves the application in a generic format (be it a database format, a collection of HTML or XML files or some other method) on server 120. Each viewer client 110B then performs the required adaptation of the application to his own platform and parameters.
It will be appreciated that when system 100 implements dynamic layout, there may be a substantial amount of work involved in the retargeting of the designed screen for all supported target platforms and screen geometries. This may involve position recalculation, re-rendering of text, resizing of images and other activities. It will further be appreciated that for dynamic layout triggered by content editing in editor client 110A, there is no problem, as the dynamic layout is calculated during editing and before the point in which the application is saved and/or published. In such a case, editor-side adaptation would be sufficient. However, for dynamic layout triggered from other sources (such as dynamic data or collaboration), dynamic layout is triggered during application viewing and cannot be pre-calculated by the editing client 110A.
In accordance with an embodiment of the present invention, the processing required for dynamic layout related to multiple target platforms and multiple screen geometries may be performed by server 120. Reference is now made to
It will be appreciated that this method of operation may decrease the workload on client 110A, which may receive a version of website 60 already adapted to the specific client, and would not be required to reformat it. In addition, the work is performed once per target platform, and is not performed repeatedly by numerous clients 110 accessing the application. It will be appreciated that in the way, server 120 may perform the entire dynamic layout work or may partially perform some of the time consuming leaving part of the work for client 110A to perform.
Un-Displayed Area Processing.
It will be appreciated that when end-users 5 (using both editing and viewing clients) browse an application, a single specific application page is typically displayed at any given time. There are numerous sections of the application which are not displayed at any given moment, including (but not limited to) the following: pages other than the current page; hidden areas in the current page, such as occluded areas or off-screen area (to which end-user 5 may scroll or switch) and application pop-up graphical user interface elements which are not displayed currently.
It will be also appreciated that even though these areas are not visible at any given time, they may still require dynamic layout changes. This could be due to changes to the application resulting from external sources (such as dynamic data and collaborative authoring). This could also be, for example, due to designer or viewer initiated changes which affect off-screen areas, e.g. changes to component which are visible from a number of screens (such as a large e-Store object which is visible from multiple screens in the application). These areas may be disjointed dynamic-layout wise—from the currently displayed areas, e.g. separate application pages which do not interact with the currently displayed page. They could be, however, areas which would interact with the currently displayed area when they would be displayed, e.g. the un-displayed areas of components which may provide additional information on demand. In the latter case, server 120 may pre-process alternative layout information for the page based on the case in which the additional information would be displayed.
It will be appreciated that in all of these cases, the dynamic layout processing for the non-displayed areas may be performed by server 120 without affecting the interactivity or response speed of system 100. An example of this is a system in accordance with an embodiment of the present invention which supports full collaboration between users, so that concurrent editing is possible. Reference is now made to
Sites Sharing Single Design but Multiple Data.
An alternative embodiment to the present invention may employ the single design/multiple data (SDMD) model of application specification. In this model a single common design template is used by multiple applications having different content data. The template specifies the general structure of the fields, their interaction (e.g. pressing a button X will link to screen Y) and the content for some fields. Each of the multiple data instances of the application has its own set of field values and content. One example could be an electronic catalog application, in which the template would contain the layout and definition of the catalog, and the actual catalog item data (text, images etc.) would be part of each application using this catalog template.
It will be appreciated that each of the separate catalog applications based on the same catalog template may require dynamic layout processing due to different data content. Furthermore, such an application may be built on-line (by a designer who provides the component content through the on-line editor) or off-line (by automatically generating a new catalog application using the catalog template and data imported from external data sources).
It will also be appreciated that server assisted dynamic layout is especially helpful for applications which are built using imported data (i.e. off-line), otherwise known as external data applications. These applications require dynamic layout in order to handle the changes in the screen layout caused by the imported data. In systems which implement server assisted dynamic layout, processing the dynamic layout changes triggered by external data changes may be performed before pages are loaded by the client. In accordance with an embodiment of the present invention, server 120 may implement dynamic layout processing without requiring client-side processing. Reference is now made to
Dynamic Data Aggregation and Limiting.
Certain applications may contain components that reflect external data, and this data may change rapidly (e.g. stock rate information or news-wire item display). This in turn would cause rapid changes to the displayed application and require rapid reactivation of the dynamic layout mechanism.
As opposed to the prior art where each client has to connect to each individual data sources separately, in an alternative embodiment to the present invention, server 120 may provide an aggregation service, so that each client 110 may connect to a server module 180 which may receive updates from the data sources 190A, 190B and 190C as is illustrated in
Furthermore, server module 180 may provide update limiting. Clients 110A, 110B and 110C connected to server 120 may have different capabilities, processing power and communication bandwidth. In an alternative embodiment to the present invention, data server component 180 may filter the information updates going out to the clients 110A, 110B and 110C accordingly. For example, client 110A with low processing power or narrow communication bandwidth may receive only some of the changes and not all of them when the change in frequency is too high. This way the low processing power/narrow bandwidth clients 110 may keep up with the rest of the system.
It will be appreciated that in order to implement system 100 to aid dynamic layout, certain dynamic layout rules must be applied. Each dynamic layout rule may describe a situation in which a change to an element of the designed application may affect another element within the same designed application. Such an element may be a component, a container or the content of a given component. It will be further appreciated that the relationship between the affecting element A and the affected element B may be automatic or explicit, using automatic or explicit anchoring. The effect on the affected element B may be that of moving it or resizing it or (in some cases) both. For the sake of clarity, each triggering of a dynamic layout rule, in which changes to an element A may affect element B may be known as a dynamic layout event. It will also be appreciated that the dynamic layout concepts and rules as described in more detail herein below may also be implemented locally on a client 110 without server 120. It will be further appreciated that system 100 may employ a plurality of dynamic layout rules having a plurality of attributes and parameters (described in more detail herein below). It will be further appreciated that the dynamic layout rules may form part of the stored dynamic layout information and may be stored in data repository 80.
There may be multiple cases for dynamic layout events as discussed hereinabove such as user and system initiated layout display, use of multiple target platforms, differences in user screen size, dynamic data etc. It will be appreciated that some of these events may be local and focus on a single given component. Other events may be global and may generate multiple dynamic layout events which must be handled together in order to derive a new layout. For example, a change in display screen size such as opening the application on a smaller screen may require a dynamic layout change to all the components on the screen.
It will also be appreciated that dynamic layout events can be staggered so that the execution of one event may trigger another. Reference is now made to
It will be further appreciated that the rules and examples provided hereinabove and herein below for the sake of clarity, are detailed in terms of vertical movement of components in the downward direction. This direction is known as the primary direction of the dynamic layout process. It will further be appreciated that dynamic layout may be facilitated in all directions (up, down, left and right). Each container or page may specify the direction in which their components may move. For example, a header on a page may require a more rigid layout, permitting expansion in the downward direction only, whereas content areas below the header may require less rigidity in design and may allow dynamic layout in different directions. It will also be appreciated that a combination of directions may also be implemented. These attributes may be set by the designer or end user 5 for each component or container. Components may be marked to grow, shrink or move independently in any of the four directions. The lower edge may move downwards, for example, without affecting the other three edges.
It will be further appreciated that each of the four edges of a component (or a combination of them) may be locked. A locked edge is explicitly anchored to the closest edge of the container containing the pertinent component as is illustrated in
Each of the four corners of the component may also be locked. This is essentially a shortcut specifying that the two edges which meet at the given corner are edge locked.
It will be further appreciated that the center of a component may also be locked as is illustrated in
Components may also be marked with a “preserve aspect ratio” i.e. their existing aspect ratio, the proportion between their height and width cannot be changed. If no edge or center locking is specified, the lock is by default the top left hand corner of the component. In this scenario, as is illustrated in
As has been discussed hereinabove, dynamic layout events and rules may typically cause components to change their size and position compared to their original size and position as specified by the designer of the system. It will be appreciated that when the trigger that caused the dynamic layout event is reversed (fully or partially), the changes to the affected component may also be reversed. It will be appreciated that the extent to which the layout change may be reversed is limited in that the affected component cannot move beyond its original position or size. This original size notion is applicable to both expanding and shrinking components. It will also be appreciated, that if a component has been modified due to automatic layout, and the designer makes a further explicit change to that component that affects its size, the new size becomes the new “original size” also known as original size reset. However, if the designer makes changes to the component that do not affect component size (such as changes to display properties), the original size is preserved by the system. The original size concept also may be applied to position changes. If a designer moves a component manually, the preserved original position will be set to the new value. This is also known as an original position reset.
It will be further appreciated (as discussed briefly hereinabove) that dynamic layout rules may include a combination of anchors created explicitly, automatically or semi-automatically. An anchor may be created between one or more components and/or framework elements such as a screen boundary. The given edge of a component may be locked with an edge of a different component or a framework element. A set of interconnected edges may be known as an anchor set. A designer may add or remove edges to an anchor set at will. There may typically be multiple anchors active at any one time and thus multiple anchor sets.
Explicit anchoring may be performed by the designer using a pertinent user interface. The designer may create the specific anchoring between parallel edges and/or framework elements by selecting these edges and specifying that an anchor is to be created between them. It will be appreciated, that anchors are always created between components located inside the same container (or page). Reference is now made to
Anchors may be firm or flexible. In a firm anchor, the relative distance between linked edges are preserved whenever possible. In a flexible anchor, the distance may have a minimal and maximal relative distance. Reference is now made to
It will be further appreciated that explicit anchors are typically bidirectional so that a change in one anchored component edge can affect the other anchored edge and vice versa. It will be also appreciated that a designer may also specify that anchors are unidirectional as is illustrated in
It will also be appreciated that as well as being bidirectional, explicit anchors are typically two-way as illustrated in
As discussed hereinabove, anchors may be either explicit or automatic. Dynamic layout editor 70 may perform automatic anchoring when it detects a situation under which components are likely to be related, and that their spatial relationship should be preserved to a certain extent when one of them is moved (for example, to prevent one from occluding the other). In this way, dynamic layout editor 70 attempts to determine the intent of the designer, and save the work required to create explicit anchors or to move the components manually.
It will be appreciated that dynamic layout editor 70 may implement a number of automatic anchoring rules which may specify the situations under which automatic anchors are created or discarded, subject to certain dynamic layout base parameters and their effect. These rules are described in more detail herein below. It will be further appreciated that the description below details the creation of firm automatic anchors. However, layout editor 70 may also implement rules under which flexible automatic anchors may be created, complete with specific minimal and maximal distance specification for such anchors as described above. In such cases, the flexible anchor parameters may be pre-configured, or be based on the geometrical properties of the component it is connected to.
It will be further appreciated that the choice of a primary direction for any dynamic layout operation also defines a secondary axis, which is the axis (and the two directions) perpendicular to the primary direction. If the primary direction is up or down, the secondary axis is the horizontal one (X axis). If the primary direction is left or right, the secondary axis is the vertical one (Y axis)—as illustrated in
In order for dynamic layout editor 70 to determine if an automatic anchor exists between the parallel edges of two components, a series of conditions related to the proximity and/or intersection of the two components may be evaluated—both vertically and horizontally. These conditions are based on testing the inter-component distance or the intersection distance against user-defined minimum and maximum parameters, for a total of 8 different dynamic layout base parameters. The permutations are [primary or secondary]*[proximity or intersection]*[min or max].
For example, dynamic layout editor 70 may require any of the following conditions for an automatic anchor to be created. In all the examples discussed below, the primary direction is considered to be downwards. dynamic layout editor 70 may create an automatic anchor from the bottom edge of a component [a] (a1) and the top edge of a component [b] (b1) as illustrated in
Dynamic layout editor 70 may also create an automatic anchor if the distance between the bottom edge a1 of component [a] and the top edge b1 of component [b] if a1 is below b1 (i.e. the bottom of component [a] intersects with the top of component [b]) as is illustrated in
Dynamic layout editor 70 may also create an automatic anchor when the horizontal overlap or distance between potentially anchored components meets a further condition in addition to that of the vertical distance or intersection. An example of this is illustrated in
It will be appreciated that comparison against parameters which are not implemented or specified (as part of the dynamic layout base parameter set) is not performed. For example, if a minimal secondary axis intersection distance [x] is implemented, but no matching maximal intersection distance is implemented, then any amount of intersection greater than or equal to [x] would satisfy this dynamic layout basic parameter condition.
It will also be appreciated that dynamic layout base parameter sets may also include [0 to infinity] ranges. These are used, for example, to test whether a component [a] is higher than a component [b] and intersects it and whether size of the intersection region between components [a] and [b] is relevant to the systems' automatic anchoring decisions. In such a scenario, a range [0 to infinity] may be defined for the primary intersects [min, max] dynamic layout basic parameter pair.
It will also be appreciated, that the parameters may be combined using Boolean conditions or any other applicable conditions (such as a weighted combination) when dynamic layout editor 70 checks for an automatic anchor creation between component [a] and component [b].
For example, if components [a] and [b] are disjointed along the primary direction, a check is made to see whether their distance is in the relevant [min, max] range.
If components [a] and [b] intersect along the primary direction a check is made to see whether their intersection distance is in the relevant [min, max] range.
If components [a] and [b] are disjointed along the secondary axis (in either direction), check that their distance is in the relevant [min, max] range.
If [a] and [b] intersect along the secondary axis, a check is made to see whether their intersection distance is in the relevant [min, max] range.
Therefore, to create an anchor from component [a] to component [b], the two components have to be correctly positioned both vertically and horizontally. It will be appreciated that values for each of the dynamic layout base parameters may be determined using any combination of the following methods: using a general system parameter; using an override value for the specific web site or application being edited; using an override value for the specific component type of each of the two components being checked (e.g. leave a large space around a picture component as compared to a text component); using an override value for the specific screen being designed and using an override value for the specific container in which the links are being created;
It will be appreciated that the dynamic layout basic parameter values may be defined by the various automatic anchoring rules (described in more detail herein below). It will also be appreciated that the system may specify general dynamic layout basic parameter values to be used by all automatic anchoring rules, or as separate set of dynamic layout basic parameter values for each automatic anchoring rule.
It will be further appreciated that the automatic anchoring rules may also require a specific order between the components along the primary direction. For the sake of illustration, a particular rule may require that component [a] be above (either disjointed from or intersecting with) component [b]. Such an order condition will be tested in addition to the dynamic layout basic parameter conditions.
Furthermore, the actual dynamic layout basic parameter values may also be specified using any combination of the following methods:
Using Absolute Pixel Values.
Using a pixel value which is adjusted relative to the size of display device displaying the application, so if (for example), an application is scaled down 20% due to a display screen having a lower resolution, the threshold values are also scaled down by 20%.
Using a pixel value which is adjusted relative to the sizes of the two components being anchored—so if one of the components is enlarged, the required anchor distance would grow proportionally. The dynamic layout basic parameter value may be specified using the minimal, maximal or average size of the components involved.
It will also be appreciated that automatic anchoring gate conditions may be implemented as part of the dynamic layout basic parameter conditions. These are per-component/per-edge attributes for each of the implemented automatic anchoring rules which specify if a given rule would be applied to a given component edge or not. For example, as is illustrated in
Reference is now made to
Automatic anchors may also be broken when a third component is placed between the two anchored components. For example as is illustrated in
It will also be appreciated that dynamic layout editor 70 may also support semi-automatic anchoring. The pertinent visual design system may detect situations in which an anchor is likely to be needed between two or more component edges in an area where no automatic anchor has been designated. In such cases, the system may suggest the possible anchors to the designer, and the designer can select using an appropriate interface whether to confirm the suggestion (thereby creating an anchor) or not.
For example, system 100 may suggest that whenever parallel edges of two components lay on the same line, or are sufficiently close to the same line, that the designer confirms the creation of an explicit link between these two parallel edges as is illustrated in
It will also be appreciated that system 100 may implement a hierarchical component structure, in which some components are containers containing other components or sub-containers. It will be further appreciated that containers may be classed as single page containers or multi page containers. Reference is now made to
It will be appreciated that in such a layout, anchors (explicit, automatic or otherwise) can only be made between a component and its direct parent; between a container component and one of its descendants (in any of the contained areas in multi-page containers) or between two peer components which are both direct descendants of the same node—either the same application page/container or the same area in a multi-page container.
It will also be appreciated that when a dynamic layout event occurs, the anchored edge of the affected element (e.g. component, content, container etc.) has to move. Reference is now made to
It will be further appreciated that if the other horizontal edge of the same component is directly anchored to a framework element, the choice of direction is forced by that anchor. Otherwise, there are multiple options. For explicit anchors, dynamic layout editor 70 may provide a graphical user interface for the user to specify, for each explicit anchor, the direction for each anchor (since anchors may be bidirectional) and whether the anchor would move the affected component upon a dynamic layout event, or resize it instead.
For automatic anchors, this method is typically inappropriate as such anchors may be constantly created and removed. It will be appreciated that dynamic layout editor 70 may provide a default setting which allows the designer to specify which action should be taken (for both types of edges) in the case of automatic anchors. This may be specified at the application/web site level, with possible overrides at the application page, container and component level.
It will also be appreciated that for some types of automatic anchors, a single option may be available—typically a resize (rather than move). In particular, in all automatic anchor situations in which a component [a] affects the container component [b] which logically contains [a], the effect must always be a resize and not a move—since a contained component cannot move the container that contains it.
It will also be appreciated that some dynamic layout changes may require a component to shrink, e.g. when its bottom edge moves up due to an explicit anchor to another edge which was moved up. It may be possible to define a minimal size for each component or component type in order to prevent such components from shrinking below their minimal size. Reference is now made to
In scenario I, container [b] or the screen may be extended downwards. In scenario II, container [b] or the screen may be extended logically but not physically and therefore retaining the existing position and size of container [b]. The discrepancy between the physical and logical dimension of container [b] is resolved by making container [b] a scrollable object, with a vertical scroll bar which allows viewing of the non-displayed portions of container [b]. In scenario III, component [a] may continue moving or expanding down, but part of the component may become clipped (and thus hidden) by the bottom of container [b]. In scenario IV, component [a] may stop moving or expanding down—which may affect additional components as well. For example, if component [a] was moving downwards (e.g. due to a component [c] pushing it from above), component [a] may stop moving and thereby cause [c] to stop moving as well, or alternatively the distance between [c] and [a] may be shrunk (depending on the type of anchor D between them). It will also be appreciated that if component [a] expands downwards (e.g. due to editing text content inside component [a]), the content inside component [a] might be affected in a variety of ways, including (but not limited to): being displayed using different fonts and being displayed with scroll bars (which allow scrolling over the content). In scenario V, component [a] may start to shrink instead of just moving downwards.
It will be appreciated as discussed hereinabove, that the above mentioned examples may be classified into four main automatic anchoring rules.
The first rule is between content and a containing component. An automatic anchor may be defined between every container and its content. Under this rule, the size of a component which contains variable content may change as the content changes. This may occur due to content changes made by a designer or an end-user, changes in content initiated by the application itself while running and changes in content caused by dynamic content. System 100 may define a minimal distance threshold between the content and the component frame so that content changes only affect the lower edge of the component once the lower edge of the content is within a minimal distance from the lower edge of the container.
The second rule may be between a component and a peer component in a primary direction. An automatic anchor may be defined between parallel edges of adjacent components along the primary direction. If the primary direction is down, then an automatic anchor may be created between the bottom edge of a component [a] and the top edge of a component [b] when the dynamic layout basic parameter conditions are satisfied.
The third rule may be between the bottom of component [a] and the bottom of component [b]. Dynamic layout editor 70 may automatically create an anchor between bottom edges which are near to each other horizontally, or intersect each other in the horizontal direction as is illustrated in
If component [a] logically contains component [b], then moving edge b2 will only resize component [a] (by moving edge a2 up or down as appropriate). It would not move component [a]. This limitation does not apply if components [a] and [b] merely intersect and component [a] does not logically contain [b]. It will be further appreciated that if a bidirectional version of anchor A is implemented, when component [a] moves or expands down, component [b] would also move or expand down (as defined by anchor A) i.e. edge a2 pills edge b2 down. When edge a2 moves back up, it pushes edge b2 until edge a2 reaches its original position as is illustrated in
The fourth rule may be between the top of component [a] and the top of component [b]. Dynamic layout editor 70 may create an anchor between the top edges of both components which are near to each other horizontally or intersect each other in the horizontal direction as is illustrated in
It will be appreciated that dynamic layout editor 70 may apply automatic anchoring rules between more than two component edges if applicable, so that a more complex anchor may be created that connects three or more components.
It will also be appreciated that a flexible anchor may allow the distance between component [a] and container [b] to shrink further until a minimal distance is reached. In this scenario, the anchor may then become fixed so that no further anchor shrinking would be allowed. It will be further appreciated that system 100 may specify a default behavior (selected amongst the scenarios of
It will also be appreciated there may be multiple anchors which may dictate different behaviors for a given component when a dynamic layout event occurs as is illustrated in
It will be further appreciated that if the amount of text inside component [b] is reduced, component [b] would shrink, moving bottom edge b2 upwards. The top edge c1 of component [c] may also move up as much as is possible according to the limitations set by the two anchors XA and XB.
As discussed hereinabove, dynamic layout coordinator 170 may employ rules to evaluate and create automatic anchors, to determine when a dynamic layout trigger has been activated and to execute the dynamic layout changes based on the pertinent triggered dynamic layout events.
It will also be appreciated that these rules may run upon occurrence of any of the possible dynamic layout trigger events described herein above. It will be appreciated that these rules may also run even if triggering action is not completed. Reference is now made to
The rule in this situation may also be applied recursively for each container level inside the application (e.g. to each page separately, and to each container in each page). It may scan all possible anchor relationships—both existing anchors and potential semi-automatic and automatic anchors—and may perform the dynamic layout according to the dynamic layout rules described above, adding, removing and modifying the anchors and modifying component properties as required.
Therefore a server based system may be used to integrate dynamic layout rules across single and multiple clients sharing the same server enabling the efficient moving and resizing of components where necessary and thus improving the website creation and design process.
Unless specifically stated otherwise, as apparent from the preceding discussions, it is appreciated that, throughout the specification, discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” or the like, refer to the action and/or processes of a computer, computing system, or similar electronic computing device that manipulates and/or transforms data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.
Embodiments of the present invention may include apparatus for performing the operations herein. This apparatus may be specially constructed for the desired purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, magnetic-optical disks, read-only memories (ROMs), compact disc read-only memories (CD-ROMs), random access memories (RAMs), electrically programmable read-only memories (EPROMs), electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards, Flash memory, or any other type of media suitable for storing electronic instructions and capable of being coupled to a computer system bus.
The processes and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the desired method. The desired structure for a variety of these systems will appear from the description below. In addition, embodiments of the present invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.)
While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
This application claims priority from U.S. Provisional Patent Application No. 61/600,726 filed Feb. 20, 2012 which is hereby incorporated in its entirety by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5721848 | Joseph | Feb 1998 | A |
| 5796401 | Winer | Aug 1998 | A |
| 6144991 | England | Nov 2000 | A |
| 7222306 | Kaasila et al. | May 2007 | B2 |
| 7533142 | Ng et al. | May 2009 | B2 |
| 7554689 | Tonisson | Jun 2009 | B2 |
| 7568155 | Axe et al. | Jul 2009 | B1 |
| 7634725 | Nishikawa | Dec 2009 | B2 |
| 7812786 | Etelapera | Oct 2010 | B2 |
| 7856345 | Christensen et al. | Dec 2010 | B2 |
| 7992007 | Lazzaro | Aug 2011 | B2 |
| 8112502 | Emmelmann | Feb 2012 | B2 |
| 8312170 | Ng et al. | Nov 2012 | B2 |
| 8489984 | Violet | Jul 2013 | B1 |
| 8694900 | Bishop | Apr 2014 | B2 |
| 8862991 | Harrington et al. | Oct 2014 | B2 |
| 9043698 | Tucovic | May 2015 | B2 |
| 20040078776 | Moon et al. | Apr 2004 | A1 |
| 20050071755 | Harrington et al. | Mar 2005 | A1 |
| 20050198204 | Takahashi | Sep 2005 | A1 |
| 20060044604 | Mirmotahari | Mar 2006 | A1 |
| 20060103667 | Amit et al. | May 2006 | A1 |
| 20060143182 | Meadows | Jun 2006 | A1 |
| 20060190811 | Ohno | Aug 2006 | A1 |
| 20060198555 | Hosotsubo | Sep 2006 | A1 |
| 20060212805 | Allen et al. | Sep 2006 | A1 |
| 20060236231 | Allen et al. | Oct 2006 | A1 |
| 20060259860 | Kobashi | Nov 2006 | A1 |
| 20070028166 | Hundhausen et al. | Feb 2007 | A1 |
| 20070171716 | Wright et al. | Jul 2007 | A1 |
| 20080155387 | Yabe | Jun 2008 | A1 |
| 20080209533 | Abrams et al. | Aug 2008 | A1 |
| 20080215964 | Abrams et al. | Sep 2008 | A1 |
| 20080215965 | Abrams et al. | Sep 2008 | A1 |
| 20080215967 | Abrams et al. | Sep 2008 | A1 |
| 20080215985 | Batchelder et al. | Sep 2008 | A1 |
| 20080313533 | Hoyer et al. | Dec 2008 | A1 |
| 20090100129 | Vigil et al. | Apr 2009 | A1 |
| 20090309894 | Lam et al. | Dec 2009 | A1 |
| 20110213655 | Henkin et al. | Sep 2011 | A1 |
| 20120036423 | Haynes et al. | Feb 2012 | A1 |
| 20120226971 | Tocchini et al. | Sep 2012 | A1 |
| 20130212487 | Cote | Aug 2013 | A1 |
| 20130227617 | Carney et al. | Aug 2013 | A1 |
| 20130263280 | Cote | Oct 2013 | A1 |
| 20140250371 | Wabyick et al. | Sep 2014 | A1 |
| Entry |
|---|
| Masato Nakamura, A Dynamic Rearrangement Mechanism of Web Page Layouts Using Web Agents, 2009, Dept. of Computer Science and Engineering, Graduate School of Engineering, Nagoya Institute of Technology, Gokiso-cho, Showa-ku, Nagoya, Aichi, 466-8555 Japan, all pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20130219263 A1 | Aug 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61600726 | Feb 2012 | US |
