ES2948388T3 - Building Websites Using Data Lists - Google Patents

Abstract

A website building system (WBS) comprises: a set of content elements to be displayed on a website under construction; a set of views that can be used to display the elements, each view being a template for a section of a web page of said website; a dynamic match and adapt module to dynamically provide a suitable view for each content item to display the content item on the website. The dynamic matching and adaptation module performs at least one of: locating a matching view from the set of views; build a matching view on the fly; Locate a matching view from the view set and then modify the located view. (Automatic translation with Google Translate, without legal value)

Description

DESCRIPTION

Building Websites Using Data Lists

field of invention

The present invention relates to the field of website creation.

Background

Millions of users use the Internet every day to read or consume web content. For example, a user may use a personal computer, laptop, smartphone or tablet, typically running in a browser, to read online news, watch online videos, interact with other users through social networks, play games online games or similar.

Some websites can be built by writing code manually, particularly HTML and/or JavaScript code. However, as websites have become more sophisticated and offer a richer and more interactive user experience, various "website building" tools have been introduced to facilitate and/or automate the construction of particular web pages and even entire websites.

According to US 6 304 886 B1, a software tool is provided for use with a computer system to simplify the creation of websites. The tool comprises a plurality of pre-stored templates, comprising code in HTML format, text, fields and formulas. The templates preferably correspond to different types of web pages and other characteristic features commonly found on or available for websites. Each characteristic feature can have several options. To create a website, the tool asks the website creator (the person who uses the tool to create a website) through various views stored in the tool to select the desired characteristics and options for the website. Based on these selections, the tool prompts the website creator to provide data to enter data into the fields of the templates determined by the tool to correspond to the selected features and options. Based on the identified templates and supplied data, the tool generates the customized website without the website creator writing any HTML code or other programming code. Using multi-level role-based security, certain website users can have access to certain information and others cannot. WO 02/086704 A1 discloses an intelligent generator that allows the designer/developer/user to model Enterprise JavaBeans (EJB) components naturally without worrying about specific implementation details. The developer models the business objects using a UML drawing tool, and the intelligent generator creates a set of classes that implements these objects with reference to the Enterprise JavaBeans specification (see Figure 1). That is, the intelligent generator automatically creates reference contention handling and access procedures from the UML diagram.

Compendium

The present invention may comprise, for example, devices, systems and methods for creating websites using data lists. The invention is set forth in the set of attached claims.

The present invention provides a website building system (WBS) as defined in claim 1.

In some implementations, the system supports element types; and at least one view in the view set is associated with an item type and can be used to display items belonging to said item type.

In some implementations, the dynamic adaptation and composition module performs the composition of a view with a content element by searching for the composition of a suitable view with an element type of said content element.

In some implementations, for example, the WBS further comprises: a view manager for creating a view that has one or more conditional elements.

In some implementations, for example, said group of content items contains at least one collection of items updateable through at least one of: a collection update application programming interface (API), a web service collection update, an RSS feed and an interface for updating the collection based on an external data source.

In some implementations, for example, the WBS further comprises: a website/view converter to use a website page directly as a content element view.

In some implementations, for example, the WBS further comprises: a pre-association module for associating between a given view and a given element; in which the adaptation and dynamic composition module is to perform a dynamic composition based on a previous association between views and elements.

In some implementations, for example, preassociation comprises explicitly specifying the prior association between the given element and the given view.

In some implementations, for example, the preassociation is based on at least one of: a name attribute, a context attribute.

In some implementations, for example, the adaptation and composition module comprises: a view group finder to search, in a group of predefined views, one or more views that compose a given element. In some implementations, for example, the view group finder comprises a keyword-based finder for finding compositions between views and elements based on one or more keywords.

In some implementations, for example, the view group finder comprises an attribute-based finder for finding compositions between views and elements based on one or more attribute compositions. In some implementations, for example, the view group finder comprises a field composition finder for finding compositions between views and elements based on one or more composition fields. In some implementations, for example, the view group finder comprises an application-related parameter finder to find compositions between views and elements based on one or more application-related parameters.

In some implementations, for example, the dynamic composition and adaptation module excludes one or more view composition candidates taking into account a form factor of an electronic device that is used to display said website.

In some implementations, for example, the system supports view inheritance through a view inheritance module that can generate a derived view that inherits characteristics of an existing view.

In some implementations, for example, the WBS further comprises: a parent view finder to search up a suitable view in a view inheritance tree, if a given view is not suitable for a given content.

In some implementations, for example, the WBS further comprises: a view manager to automatically create a derived view based on an item type.

In some implementations, for example, the system supports element type inheritance through an element type inheritance module that can generate a derived element type that inherits characteristics of an existing element type.

In some implementations, for example, the WBS further comprises: a view manager to automatically create a derived item type based on a derived view.

In some implementations, for example, the WBS further comprises: an array finder to search up a type inheritance tree to locate a view composition for an array type of a given element type.

In some implementations, for example, the adaptation and composition module is for adapting a localized view, which composes a parent element type, based on modifications made from said parent element type to a derived element type.

In some implementations, for example, the WBS further comprises: a classification module for classifying possible view compositions for a given content element.

In some implementations, for example, the classification module applies a classification to at least one of: field composition, keyword composition, attribute composition.

In some implementations, for example, the WBS further comprises: a view priority manager for assigning a priority value to each view; wherein the dynamic composition module is for finding multiple candidate view compositions, and for selecting among said multiple candidate view compositions a single view for use based on said priority value.

In some implementations, for example, the WBS further comprises: a callback manager for defining a view classification callback for selecting a view for use among multiple compositions of candidate views located by the dynamic composition module.

In some implementations, for example, the dynamic composition module is for finding multiple candidate view compositions and for triggering an end-user selection interface generator to generate an end-user selection user interface that allows an end user to switch among these multiple candidate view compositions.

In some implementations, for example, the content item is viewable using a polymorphic display that uses two or more display formats that are switchable by an end user; where the end user's selection of a particular display format in polymorphic display affects the pairing of views with content elements.

In some implementations, for example, the WBS further comprises: a view choice persistence runner to execute persistence between views of sequential items that are displayed from a given set of items of the same item type.

In some implementations, for example, the adaptation and composition module comprises: a dynamic view constructor to dynamically modify a high-ranking candidate among multiple compositions of candidate views, for a given content element, if the adaptation and composition module does not finds no predefined view composition that composes that content element with a composition score that is greater than a threshold value.

In some implementations, for example, the adaptation and composition module comprises: a dynamic view constructor to dynamically construct a view, for a given content element, if the adaptation and composition module does not find any predefined view composition that composes said content element. content item with a composition score that is greater than a threshold value.

In some implementations, for example, the WBS further comprises: an integrated finder/builder module to search a set of predefined views, find a view composition, and modify said view on the fly to support one or more features of a content item. given.

In some implementations, for example, the WBS further comprises: a view region splitter for dividing a display into two or more regions that support two or more respective elements of said content element.

In some implementations, for example, the WBS further comprises: a landing zone location module for locating a new component in a view based on a landing zone defined relative to existing components of said view.

In some implementations, for example, the arrival zone location module is for selecting such a suitable arrival zone based on the properties of components to be located.

In some implementations, for example, the landing zone location module automatically generates the landing zone based on at least one of: end of container, end of minipage, end of container having a given type, end of container that has a given attribute, followed by a location of a recent field addition, at a location that has at least a given amount of empty screen space, on a newly created page or minipage.

In some implementations, for example, the WBS further comprises: a dynamic layout manager for applying one or more dynamic layout rules to said particular view.

In some implementations, for example, the dynamic layout manager takes into account such dynamic layout rules and dynamic layout anchors.

In some implementations, for example, the WBS further comprises: a full view creator for creating a full version of a view that has either (a) been composed or (b) been dynamically constructed on the fly or (c) has dynamically adapted on the fly.

In some implementations, for example, the full view creator comprises: a view-to-field composition module to project each data component in said view to a composition field on the element.

In some implementations, for example, the view-to-field composition module uses at least one of: (a) pre-association data; (b) common name used by a view component and element field;

(c) query on the composition of keywords assigned to view components and element fields.

In some implementations, for example, the full view creator comprises: a component resize module to resize a missing field to size zero.

In some implementations, for example, the full view creator comprises: a view display size adjuster for optimizing the dimensions of at least one component in said particular view to support an aspect ratio of a used display unit.

In some implementations, for example, the view display size adjuster comprises: a target width generator to generate a set of possible target widths of said component, and to perform a dynamic layout calculation to determine a corresponding height for each target width; a target width selector to select a single target width that best supports the aspect ratio of the display unit used.

In some implementations, for example, the given view comprises a repeater component contained within said view, wherein the repeater component displays a secondary list related to a primary list of content items displayed through said given view.

In some implementations, for example, the WBS further comprises: a repeater component display module for displaying said secondary list using attributes of the same name and context attributes that said primary list has according to said given view.

The WBS further comprises: a link component manager for defining a link component comprising a container that displays content obtained from said group of content elements.

In some implementations, for example, the link component manager displays a single minipage at a time, containing a single content item from that group of content items.

In some implementations, for example, the link component handler animates a transition between browsed content elements.

In some implementations, for example, the link component manager simultaneously displays a gallery of content items.

In some implementations, for example, the link component manager is for displaying one or more content elements linked by said link component in response to a direct URL that links directly to said link component.

In some implementations, for example, the link component manager is associated with a related list connection manager to interconnect two link components based on a related list of content items.

The link component manager is associated with an aggregator field connection manager to interface between two link components based on an aggregation function that calculates an aggregate value based on elements in one of said two link components.

In some implementations, for example, the link component manager is associated with a tag cloud connection manager to interconnect two link components based on the selection of tags from a tag cloud that is associated with one or both of them. link components. In some implementations, for example, the link component manager is associated with a hierarchy tree connection manager to interconnect two link components based on a hierarchy tree that has at least one parent/child pointer.

In some implementations, for example, the link component manager is associated with a form display connection manager to interface between two link components based on a request from a first link component to display an alternative presentation of an element. currently displayed of the first link component.

In some implementations, for example, the WBS further comprises: a dynamic layout manager for modifying a layout of a link component, containing said view, based on a presentation property of a content element in said view.

In some implementations, for example, the WBS further comprises: a specific element adaptation module for adapting a specific content element by performing at least one of: (a) adding one or more components to a content displayed in a context of application of a specific view; (b) remove one or more components of a content displayed in an application context of a specific view; (c) modify one or more components of a content displayed in an application context of a specific view.

In some implementations, for example, the element-specific adaptation module comprises: a local variant creator to create a local variant of a given view as a derived internal view and add a layer of modifications to said derived internal view.

In some implementations, for example, the derived internal view is stored together with an ID of the element to which the derived internal view applies.

In some implementations, for example, the derived internal view is stored in a current list application that comprises the item to which the derived internal view applies.

In some implementations, for example, the element-specific adaptation module comprises: a module customization to apply a view customization to all instances of a given view.

In some implementations, for example, the WBS further comprises: an application store manager module for managing an application store that allows a website designer to obtain one or more objects generated by the website creation system; wherein the obtaining comprises at least one of: (a) downloading; (b) obtaining from a storage item; (c) obtaining from a shipped storage item; (d) obtaining from a server computer that stores said objects; (e) obtaining from a cloud computing server.

The present invention also provides a computerized method for building a website as defined in claim 10.

In some implementations, for example, the procedure comprises: associating between a given view and a given element; in which the adaptation and dynamic composition comprises performing a dynamic composition based on a previous association between views and elements.

In some implementations, for example, the procedure comprises: supporting view inheritance by generating a derived view that inherits characteristics of an existing view.

In some implementations, for example, the method comprises: ranking possible view compositions for a given content element.

In some implementations, for example, the method comprises: dynamically modifying a high-ranking candidate among multiple candidate view compositions, for a given content element, if the composition and adaptation does not find any predefined view composition that composes said content element with a composition score that is greater than a threshold value.

In some implementations, for example, the procedure comprises: applying one or more dynamic layout rules to said particular view.

In some implementations, for example, the given view comprises a repeater component contained within said view, wherein the repeater component displays a secondary list related to a primary list of content items displayed through said given view.

The method comprises: defining a link component comprising a container that displays content obtained from said group of content elements.

In some implementations, for example, the method comprises: performing a specific element adaptation to adapt a specific content element by performing at least one of: (a) adding one or more components to a content displayed in an application context of a specific view; (b) remove one or more components of a content displayed in an application context of a specific view; (c) modify one or more components of a content displayed in an application context of a specific view.

In some implementations, for example, the method comprises: managing an application store that allows a website designer to obtain one or more objects generated by the website creation system; wherein the obtaining comprises at least one of: (a) downloading; (b) obtaining from a storage item; (c) obtaining from a shipped storage item; (d) obtaining from a server computer that stores said objects; (e) obtaining from a cloud computing server.

Some implementations may comprise, for example, a storage medium having instructions stored thereon that, when executed by a machine, cause the machine to execute a procedure according to the present invention.

In some implementations, for example, the one or more objects comprise one or more of: a view; a template; a type of element; a collection of elements; a list application; a link component.

The present invention may provide other and/or additional benefits or advantages.

Brief description of the drawings

For reasons of 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 greater clarity of presentation. Furthermore, reference numerals may be repeated between the figures to indicate corresponding or analogous elements. The figures are listed below.

Figure 1 is a schematic block diagram illustration of a website building system (WBS) that can be used to create a website, according to some demonstrative embodiments of the present invention;

Figure 2 is a schematic block diagram illustration of the WBS showing in particular components and its content, according to some demonstrative embodiments of the present invention;

Figure 3 is a schematic block diagram illustration of the WBS particularly demonstrating inheritance between objects, according to some demonstrative embodiments of the present invention;

Figure 4 is a schematic block diagram illustration of the WBS showing in particular templates, according to some demonstrative embodiments of the present invention;

Figure 5 is a schematic block diagram illustration of the WBS demonstrating particular types of elements, according to some demonstrative embodiments of the present invention;

Figure 6 is a schematic block diagram illustration of the WBS demonstrating in particular collections and elements, according to some demonstrative embodiments of the present invention;

Figure 7 is a block diagram schematic illustration of the WBS particularly demonstrating link components (LC), according to some demonstrative embodiments of the present invention;

Figures 8-9 are block diagram schematic illustrations of the WBS demonstrating in particular views and modules managing said views, according to some demonstrative embodiments of the present invention;

Figure 10 is a schematic block diagram illustration of the WBS demonstrating in particular modules of a three-step composition/construction and view completion process, according to some demonstrative embodiments of the present invention;

Figure 11 is a schematic block diagram illustration of the WBS showing in particular the location of the view (or view composition with element), according to some demonstrative embodiments of the present invention; Figure 12 is a block diagram schematic illustration of the WBS particularly demonstrating view preview association, according to some demonstrative embodiments of the present invention;

Figure 13 is a schematic block diagram illustration of the WBS particularly demonstrating view search, according to some demonstrative embodiments of the present invention;

Figure 14 is a schematic block diagram illustration of the WBS particularly demonstrating the dynamic view construction, according to some demonstrative embodiments of the present invention;

Figure 15 is a schematic block diagram illustration of the WBS particularly demonstrating view selection and polymorphic display, according to some demonstrative embodiments of the present invention;

Figure 16 is a schematic block diagram illustration of the WBS particularly demonstrating the creation of a complete view, according to some demonstrative embodiments of the present invention;

Figure 17 is a block diagram schematic illustration of the WBS showing the dynamic layout and settings for a full view, according to some demonstrative embodiments of the present invention;

Figure 18 is a schematic block diagram illustration of the WBS demonstrating the location and modification of the arrival zone, according to some demonstrative embodiments of the present invention;

Figure 19 is a schematic block diagram illustration of the WBS particularly demonstrating the modification of the view, according to some demonstrative embodiments of the present invention;

Figure 20 is a block diagram schematic illustration of the WBS particularly demonstrating LC connection management, according to some demonstrative embodiments of the present invention;

Figure 21 is a schematic block diagram illustration of the WBS particularly demonstrating the integration of the app store, according to some demonstrative embodiments of the present invention;

Figure 22 is a demonstrative user interface (UI) that supports explicit updating of collections for a restaurant listing application (LA), according to some demonstrative embodiments of the present invention; Figure 23A is a demonstrative restaurant LA that displays a hierarchy of elements from multiple collections within a single LC, according to some demonstrative embodiments of the present invention;

Figure 23B is an annotated version of the demonstrative restaurant LA, according to some demonstrative embodiments of the present invention;

Figure 24 is a sample LC displaying a single enlarged element, according to some demonstrative embodiments of the present invention;

Figure 25 is a sample LC displaying multiple views of elements in a gallery-style format. multiple columns, according to some demonstrative embodiments of the present invention;

Figure 26 is an example search box used to select elements to be included in a system-generated list, according to some demonstrative embodiments of the present invention; and

Figure 27 is a demonstrative effect of increasing the "element spacing" value on the spacing between view instances in the sample LA, according to some demonstrative embodiments of the present invention.

Detailed description of the present invention

In the following detailed description, numerous specific details are set forth to provide a comprehensive understanding of some embodiments. However, those skilled in the art will understand that some embodiments may be implemented without these specific details. In other cases, well-known procedures, components, units and/or circuits have not been described in detail so as not to complicate the analysis.

The present invention may comprise a website building system (WBS) that may implement list components and list applications as described herein. The WBS can be used by a designer or programmer or another person who wants to create a website. Some WBS implementations can be configured to be suitable for novice or lay users, or for website creators who do not necessarily have advanced skills (or any skills) in programming, and who are not necessarily proficient in programming languages. A direct user of the WBS, who can use the WBS to create a website, may be called a "designer"; while the website itself, once created and published, can be used by "end users".

According to the present invention, the WBS may comprise and/or enable the following characteristic features: elements and collections of elements; element types; views (including conditional, calculated and other elements); templates and inheritance (including derived views and derived types); link components (LC); dynamic composition between elements, types and views; support for automatic creation of element types from derived views and vice versa; support for customizations and automatically generated customization dialogs; support for adaptations of specific elements; support for creating connections between related LCs; App store integration support for all of the above features.

Some embodiments of the present invention may be used in conjunction with systems, procedures, modules and/or components described in U.S. Patent Application No. 13/771,119, entitled "Web Site Design System Integrating Dynamic Layout and Dynamic Content," filed on February 20, 2013, published under US Patent Application Publication Number 2013/0219263.

Pages, containers and components

Reference is made to Figure 1, which is a schematic block diagram illustration of a website building system (WBS) 100 that may be used to create a website 110, according to some demonstrative embodiments of the present invention. The WBS 100 may be used to build, produce, edit and/or generate a website 110, which may comprise pages 111 that may include components 120 (e.g., text, images, videos).

The components 120 may be, for example, atomic components 121 and/or container components 122. For example, container components 122 may be single-page containers 123 or multi-page containers 124 (including multiple minipages 125 spaced apart from each other). It is clarified that these are only demonstrative examples, not limiting ones. In particular, Figure 1 demonstrates a specific configuration of components and containers, but numerous such configurations are possible.

Multi-page containers 124 may display a single minipage 125 at a time (single page display), or may display some or all of the minipages 125 (e.g., implemented as a gallery or carousel or collection display, e.g. as demonstrated in figure 25). A multi-page container 124 may have a fixed display mode (e.g., gallery display only), or may allow the user to switch between multiple display modes.

When viewing a page containing a multi-page container 124, the user can move from one to another of the various mini-pages 125 contained in the multi-page container 124 using one or more suitable mechanisms, for example, navigation buttons (e.g. e.g., first, previous, next, last) and/or visual selection between multiple visible minipages 125 (or their thumbnails, reduced representations).

Reference is made to Figure 2, which is a schematic block diagram illustration of the WBS 100 showing in particular the components 120 (e.g., from page 111 of the website 110) and their contents 130, according to some embodiments. demonstrations of the present invention.

The components 120 may have content 130, for example, text content for a text component, an image for an image component, video content for a video player component, or the like. Components 120 may have (or may be associated with) attributes 131, for example, attributes 132 of display (e.g., color, frames) and layout 133 attributes (e.g., size and position). It is clarified that Figure 2 represents a demonstrative, non-limiting implementation; and that the various attributes 131, 132 and/or 133 may not necessarily "depend" on the content 130. For example, some of the components in the WBS 100 may have (or may be associated with) the attributes 131, 132 and/or 133, without necessarily having content 130. Similarly, in some types of components, attributes 131, 132 and/or 133 may be completely separate (and/or independent) from a particular content or from any content. In other component types, content may be associated with attributes; For example, one or more specific font types and/or colors may be associated with text elements displayed in a text component.

The WBS 100 may generate a page definition that may include dynamic layout rules (e.g., anchors connecting multiple component edges) that may be managed by a dynamic layout manager (DLM) 101. For example, the DLM 101 may be triggered each time a dynamic layout (DL) trigger is triggered, e.g., a change that affects the layout of the page (e.g., adding components, removing components, changing page content). a component in a way that affects the size of the component, moving components, resizing components), changing content for components that reflect external content, or the like. Other suitable activators or activation mechanisms may be used, for example, as detailed in the aforementioned US Patent Application No. 13/771,119.

Inheritance relationships

Reference is made to Figure 3, which is a schematic block diagram illustration of the WBS 100 that particularly demonstrates inheritance between objects, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise an inheritance support manager 102 that may support the inheritance relationship between entities of a given entity type, including in particular the following entity types: Templates (which may include pages), element types and views .

When an entity A inherits from an entity B, sub-elements of A are copied or imported from sub-entities of B. For example, entity B may be named "parent entity B" (denoted as 141); while entity A can be called "child entity A" or "inheritor entity

A" (denoted 142). It should be noted that entity A may include local modifications to the sub-items copied from B, including (without limitation): addition of new sub-items; deletion of copied sub-items; changes to the properties of the copied sub-items. Local modifications would only apply to the inheriting entity A and not the parent entity B.

The inheritance support manager 102 may comprise, or may use, or may be associated with, one or more inheritance enabling modules, for example, a copy inheritance module 103 and/or a full inheritance module 104 (which also can be referred to as a "continuous inheritance" module, since the inheritance link can continually affect the inheriting entity A when subsequent modifications are made to the parent entity B). It should be noted that in some implementations, WBS 100 may support copy inheritance only; while, in other implementations, the WBS 100 may support only full inheritance. Accordingly, in some implementations, WBS 100 may support full inheritance or copy inheritance, but not both.

The copy inheritance module 103 may allow copy inheritance, so that entity A is a separate entity created based on parent entity B by copying its structure and sub-elements. However, the copy is a separate entity and would not reflect changes made to the parent entity B after the creation of the inheriting entity A.

The full inheritance module 104 can enable full inheritance, so that the inherited entity A remains (even when modified) an instance of the parent entity B. For example, if the parent entity B is modified after it has been created inherit entity A, changes made to parent entity B would automatically be reflected in inherit entity A and would be combined with local modifications made to inherit entity A.

The inheritance support manager 102 and/or its modules may support (for each inheritance support entity type) any of the following inheritance types, or a combination thereof: (a) normal inheritance, such that A inherits from B; (b) multilevel inheritance, so that A inherits from B and B inherits from C; (c) multiple inheritance, so that A inherits from both B and C, combining sub-elements of both; (d) diamond inheritance, such that A inherits from both B and C, and both B and C inherit from another entity D.

Templates

Reference is made to Figure 4, which is a schematic block diagram illustration of the WBS 100 demonstrating in particular templates, according to some demonstrative embodiments.

of the present invention. The WBS 100 may comprise a template manager 105 that may manage page templates 128. For example, a 128 template may be a special type of page (or minipage) that is not part of the normal website being edited. Templates 128 can be embedded into regular pages and can be added to the content of said pages; Additionally or alternatively, the templates 128 can be used as a basis for the creation of new pages. In some embodiments, both functionalities of the templates 128 may be implemented by defining a page that inherits from a specific template. Optionally, a page can include multiple templates, which can be combined together with the content of the pages.

The WBS 100 may additionally support single component templates 129, which describe the properties of a single component, and may be used when building other templates and pages. It should be noted that page templates 128 can be viewed as multi-component templates with additional page-level properties (e.g., dynamic layout anchors).

In some implementations, the WBS 100 may enable or support the following types of templates: Page templates 128; 129 single-component templates; list application templates 127; and 126 view templates. It should be noted that the various types of templates described above for demonstration purposes are related to objects that may have very different scope and/or complexity and/or characteristics. For example, list application templates may describe an entire application environment or a substantial portion thereof, such as a turnkey restaurant site (e.g., as demonstrated in Figure 21), a website of turnkey news reports or similar. As such, a list application template can include a multiplicity of item types, elements, collections, views, and pages, all of which are used to create or generate the actual website.

Optionally, the WBS 100 may support or allow inheritance relationships between templates, so that modified templates can be derived from base templates. This characteristic feature of the present invention may be in addition to the inheritance relationship between pages and templates (e.g., a particular page inheriting from one or more templates).

Element Types

Reference is made to Figure 5, which is a schematic block diagram illustration of the WBS 100 demonstrating in particular types of elements, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise a type manager 106, which may manage element "types" or types 135, which may be data record definitions that describe elements (e.g., element schemas). For example, a display element type 135 may comprise a set of fields 136 (e.g., text, number, image). Optionally, a possible field type is a pointer 137 to an element (or set of elements), which can be used to create hierarchies of elements (via a pointer to the array), strings of elements (via a pointer to the next element) or other element relationships between two or more elements. Another possible type of field is a set of tags (selected from a list of tags for the given field), which are used to mark items for retrieval through a mechanism similar to a tag cloud.

An element type 135 may inherit from other element types 135, optionally with additions, deletions, and modifications applied to them. For example, an item type "shirt" can inherit from an item type "garment" and can have the additional field "sleeves (short/long)".

The element type group 135 can be defined at the collection level, application level, designer level, or WBS level. Optionally, the WBS 100 may support one or more sets 138 of element types, at one or more appropriate levels.

Collections and items

Reference is made to Figure 6, which is a schematic block diagram illustration of the WBS 100 demonstrating in particular collections and elements, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise, or may be associated with, a specialized database 143 that may include one or more collections 144 of elements 145. Each collection 144 may comprise one or more elements 145. Each element 145 may be associated with a type 136 specific element. A collection can be uniform (e.g., all elements in that collection have the same element type); or non-uniform (e.g., at least two of the elements in that collection have two different element types). It should be noted that Figure 6 represents, for demonstration purposes, that the database 143 comprises both the collections 144 and the elements 145. In some implementations, the collection and the elements may have hierarchical relationships, since a collection comprises elements.

Collection Update

Collections 144 of items 145 may be updated, for example, by adding items 145, deleting items 145, and/or modifying items 145. For example, the WBS 100 may optionally comprise a collection manager 146 that may provide automatically generated screens that can be used by the users (e.g., designers, developers, website creators) to update or edit a collection 144; for example, as demonstrated in Figure 22, which is an example UI that supports collection updating for a restaurant listing application (e.g., adding, deleting or editing menus/sections/dishes). Additionally or alternatively, a developer may create his or her own collection update form(s) 147 and provide them to the end user for runtime collection updates.

In some implementations, the WBS 100 may provide a programmatic interface (e.g., a collection update API 148) through which the created website can directly interact with the collection manager 146 and update the collection 144. Optionally, the WBS may provide an interface (e.g., a collection update web service 149) that allows an external application (e.g., web application, mobile application, desktop application, cloud-based application or similar) access collection 144 and update it directly, without needing to access collection 144 through the built website. In some implementations, the WBS 100 may provide an interface 150 for collection updating based on an external data source (e.g., RSS feed) to be attached to a given collection 144, and the WBS itself may be responsible to update collection 144 based on the incoming data source.

Optionally, a collection 144 may be constructed in a manner that represents (or points to) data present in an external system or data set, for example, as a "virtual collection" 151. In this case, changes to the system or data set underlying data would automatically be reflected in the virtual collection 144.

Link components

Reference is made to Figure 7, which is a block diagram schematic illustration of the WBS 100 particularly demonstrating link (LC) components 152, according to some embodiments of the present invention. The WBS 100 comprises, or allows the use of, link components (LC) 152, which can be managed or operated through an LC manager module 106. Each LC 152 is a special type of multi-page container that displays elements obtained from one or more collections through a view dynamically or statically associated with each element, and each minipage displays an element through the associated view. Implementations support various types of LC 152, including: (a) an LC 152 that displays a single minipage (and the related element and its associated view) at any time; (b) an LC 152 that displays multiple minipages simultaneously (e.g., carousel or gallery type container), or can display multiple elements through associated views (e.g., such that each view can be displayed in a minipage). LCs 152 are used directly (e.g., by including them in pages or minipages), or through templates that contain them (e.g., as other components that can be included in templates). A single page or minipage can contain multiple LC 152s.

Optionally, an LC can be associated with: a specific element directly; or a single collection of elements; or a set of collections (e.g., which can be displayed one after the other or hierarchically using a structure similar to a table of contents). For example, (as demonstrated in Figure 23), a restaurant listing application (LA) may use an LC menu that displays the hierarchical organization of the menu, such that it displays items from the "menus" collection (e.g. (e.g., the name of the current menu), "sections" (e.g., names of menu sections such as "salads", "sides and starters", etc.), and the collection of "dishes" (e.g. e.g., names and prices of specific dishes). Such LCs may be referred to herein as composite LCs.

In some implementations, a virtual minipage generator 107 may automatically generate a virtual minipage for each element in the one or more collections associated with an LC 152. It is clarified that a single LC 152 may be associated with multiple collections, some of which may be virtual and others not. When viewing an LC 152, designers and users can manually navigate between the multiple displayed mini-pages of that LC, for example, using a scroll bar or navigation buttons (e.g., first, previous, next, last). Designers and users can also perform additional operations, as detailed herein.

According to the present invention, the WBS 100 may comprise a direct LC access module 153 that may allow a direct link to an LC 152; for example, allowing a page containing LC to be accessed directly using a URL. These direct demonstration URLs can be, for example:

www.MySite.com/prefix/MyPage. html?Myitem

www.MvS¡te.com/prefix/MvPage.html?LC1=Mv¡tem1&LC2=MvItem2

www.MySite.com/pref¡x/MyPage.html?LC1=MyF¡lterQueryString

Use of such direct links may cause the WBS 100 to open the specific page (containing the LC(s) 152) with the LC(s) 152 already displaying the requested elements, or with a query determined that is used to filter elements, similar to the way queries and parameters are added to normal URLs (e.g., to be passed by PHP programs for processing).

When the WBS 100 opens a page containing an LC 152, with the LC 152 displaying the result of a query originating from the URL, the LC 152 will display the results of the query as a query results structure 108, which can be detailed or summarize. The list of results itself is not necessarily a page or minipage, but rather, may have an arbitrary or predefined structure as defined in WBS 100. A detailed list of results may optionally include multiple minipages (e.g., a minipage for each result found); This can be differentiated from the usual situation where an LC 152 displays one or more mini pages at any time.

Optionally, the WBS 100 may be configured to limit such forward link or deep link to specific LCs 152, or to specific LC types. For example, an LC link restrictions module 154 can be used to define restrictions or limitations on direct linking to specific LCs or LC types; and may further be responsible for enforcing such LC link restrictions.

In some implementations, the WBS 100 may comprise alternative interfaces (e.g., a web service-based interface or a message exchange-based interface) to access one or more of the functions described above.

The WBS 100 may optionally define and use specialized LC 152 for specific uses, for example: displaying only a filter search box (with the result displayed elsewhere); display a list of results; display a "tag cloud" or a group of tags that qualify the items in a given collection.

A demonstrative use of the LC 152 may include one or more of the following: (a) the LC 152 is directly associated with (and displays) a single, pre-specified top-level element (see Figure 24); (b) the LC 152 is directly associated with a single pre-specified top-level element and displays this element together with one or more related contained lists (displaying related elements from the same collection or from a different collection; see Figure 23A) ; (c) The LC 152 is associated with a filtered collection (with the filter selecting a given set of elements from the list), implementing a manual preselection of elements or an actual dynamic query.

In addition to list navigation (as described above), the WBS 100 may enable additional operations that may be activated when viewing a list on an LC 152, depending on the permissions and privileges of the designer/user. Such additional operations may include, for example: (a) going to the element add form (e.g., a view used in element add mode, as described herein); (b) go to an expanded item page; (c) go to related list; (d) go to element edit.

Views

Reference is made to Figures 8-9, which are schematic block diagram illustrations of the WBS 100 demonstrating in particular views and modules managing said views, according to some demonstrative embodiments of the present invention. Each view 155 may be a special type of template used to display collection items. Each view 155 displays a single element; while displaying multiple elements can be achieved using multiple views within an LC 152.

The WBS 100 may comprise a view manager 156, which may use different views 155 for different elements in the same collection. For example, if a user moves between blog posts that have multiple formats (e.g., text entries, image entries, video entries), the view 155 used to display may change from item to item, altering the format. on-the-fly viewing.

The view 155 may include fixed view elements 157, which always apply to (or are included in) the displayed view; and/or conditional view elements 158 that may be associated with the conditions 159 of the view. For example, conditional view elements 158 may depend on one or more of the following: (a) the existence of a given data field in the underlying element; (b) the value of a given data field in the underlying element; (c) a previously established formula involving data field values and relationships between them; (d) LC display parameters 152 (e.g., displaying a given field only when viewed in a list-type gallery); (e) user attributes, obtained from the user profile or other sources (e.g., displaying a particular field only to internal users within an organization, or only to users located in a certain region); (f) mode of use (e.g., whether view 155 is used for creation, editing or viewing).

In a demonstrative implementation, view 155 may comprise one or more of the following elements: (a) normal or fixed view elements 157 (e.g., page titles, background images); (b) data components 162 that are populated with data from the displayed item (e.g., the price of a house offered for sale, the image of said house, a descriptive text); (c) repeater components 163 used to display related lists within ^{the view (as detailed herein); (d) calculated components} 164 ^{that display information} calculated based on the content of the displayed item (e.g., the value added tax (VAT) value for a price extracted from a numeric price field); (e) conditional view elements 158 whose inclusion in the display (or whose attributes) depends on the conditions 159 of the view (e.g., a colored ribbon displayed for restaurant elements that have a predefined value in the "field" offer of the day"); (f) data validation rules 161, which may depend on the conditions 159 of the view; (g) conditional dynamic layout elements 165, which can be dynamic layout rules and anchors that can depend on the conditions 159 of the view.

The WBS 100 may comprise a view inheritance module 166 that allows a view 155 to inherit from one or more views 155, with additions, deletions, and changes applied. For example, a "shirt" view can inherit from a "garment" view and can have the additional component "sleeves (short/long)", thereby creating a derived view.

It should be noted that views and item types are different entities and reside in different groups, although both can comprise sub-entities similar to fields and can have inheritance relationships (elements can inherit from other elements in the element group, and views can inherit from other views in the view group). The item type defines which fields are included in the item, while the view defines how these fields are displayed. The WBS 100 may comprise a dynamic view builder 169 that allows for the dynamic construction of views based on the underlying template type information and the specific element being displayed.

One or more view groups 168 may be implemented at the application level, designer level, or WBS level. Optionally, views 155 may be predefined to be associated with element types, such that a particular view 155 must always 'belong' to a given element type (or element types inherited from it).

Using views to display elements

The WBS 100 may comprise an item display module 170, which may display an item using a predefined algorithm. First, a view composition for the display of the element is located (or created on the fly); For example, the item display module 170 may locate a view previously associated with the item, or a selected view by searching the group of available views; and if a suitable view is not located, then the element display module 170 may automatically construct a suitable view "on the fly" based on the element definition. Second, the element display module 170 can create a complete version of the selected view: (a) find the composition of each data component with a field in the element (if possible) and use the contents of the fields Of composition; (b) determine the value of all calculated components; (c) determine whether or not to include conditional view elements. Subsequently, the element display module 170 may perform dynamic layout on the entire view, thereby applying layout modifications resulting from changes in the content of fields, conditional view elements, or the like; and you can proceed to display the full view.

It should be noted that the process can be performed for multiple collection items; for example, when viewing an LC 152, which is a gallery-type multi-page container that displays multiple collection items simultaneously.

Repeater Components and Using Views Within Views

The view 155 may contain one or more repeater components 163. Each repeater component 163 may be generally similar to LC 152, but is contained within view 155. Each repeater component 163 displays a particular list and may typically display a list related to the parent item displayed in view 155. For example, For example, a person element can be related to other person elements (e.g., friends of that person) and to car elements (e.g., cars owned by that person). The person view can contain two 163 repeater components that display these lists (the "friends" list and the "cars" list). These two repeater components 163 would display the specific lists associated with the current person being displayed or highlighted in the LC 152 displaying the primary person. Note that repeater LCs should be differentiated from composite LCs as described above (and demonstrated in Figure 23A): repeater LCs display different related lists on different LCs, while composite LCs include multiple lists that are displayed within a LC only.

Unless overridden by specific configuration parameters, a repeater component display module 171 may ensure that a repeater component 163 displays a list using the same view attributes (e.g., name, context) as the view 155 used to display the main component. For example, a view named XYZ for type A can be used to display elements of type A; each of the elements of type A can be linked to a set of elements of type B; the list of type B items (related to the current type A) would be displayed in the repeater component 163 (by default, unless configured otherwise) using a view named XYZ for type B.

Using website pages for item display

In some embodiments of the present invention, instead of views being used to display elements within LCs, the system may use website pages directly as if they were views. In this case, the system can display data extracted from the associated elements directly within the data components included in the website page. For example, the designer can include data components within a regular website page and can specify which element their data should be extracted from. Optionally, a web page/view converter 172 may be comprised in the WBS 100 to implement conversion or settings to use a web page as a view.

The element to be used as a data source can be selected from one or more suitable shapes, for each data component; for example, of these candidate elements: (a) an element specifically associated with the website page (and therefore, if this element is changed, such as in another page inheriting from the current page, this would affect all data components); (b) a previously associated element for this specific component; (c) an element that answers a query specified at the page or component level. He data component can also specify the data field to be used directly, or can use a field query/detection mechanism.

Optionally, said page can be built and converted into a template, to be reused to display different elements within a manually constructed set of pages. The designer may only need to specify which component would change when an alternate element is associated with the page.

Three stage process

Reference is made to Figure 10, which is a schematic block diagram illustration of the WBS 100 demonstrating in particular modules of a three-step composition/construction and view completion process, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise, for example: (a) a view composition module 109A with element, which can search and locate a view composition for the element or elements to be displayed, and can dynamically construct a view on the fly if not a suitable predefined view is found; (b) a view completion module 109B, which can create a complete view based on the fields of the view and the fields of the elements; and (c) a DL applicator 109C that can apply a dynamic layout to the entire view.

Stage 1: Locate a view composition for the element (or element type)

Reference is made to Figure 11, which is a block diagram schematic illustration of the WBS 100 demonstrating in particular the location of the view (or composition of the view with the element), according to some demonstrative embodiments of the present invention. This may be the first stage of the three-stage process mentioned above.

The step of locating a view composition for the element(s) may be performed, for example: (i) using a view preassociation module 112A to preassociate views with elements and/or with element types; (ii) using a view search module 112B to search the group of available views; and/or (iii) using an on-the-fly dynamic view builder 112C to dynamically construct a suitable view "on the fly."

Previous association of views with elements and/or with element types

Reference is made to Figure 12, which is a block diagram schematic illustration of the WBS 100 particularly demonstrating a preview association, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise a view preview association module 173 (which may be similar to the view preview association module 112A mentioned above), to allow the preview association of a view (or multiple views) with particular elements and / or with particular types of elements. This can be done during the creation or editing of specific elements and/or element types, or during the creation or editing of inherited elements and element types.

Single view association can be done by the designer, who can explicitly associate a view with any given element type, and the association will be used for all elements that have the given element type. The association can additionally be used for all element types inherited from the given element type, unless they have their own view explicitly assigned. The designer can also explicitly associate a view with any specific element, thereby overriding the view associated with the element type of the given element.

Optionally, an attribute-based pre-association module 113A may allow a view to be pre-associated via attribute parameters 113D (including the use of context-based association, type-specific names, and inheritance-adapted association as described later). For example, attribute-based prebinding can be used when the system needs to bind views based on generic name, context, class, or other parameters. The attribute-based preassociation module 113A may support attribute-based preassociation as follows: (a) the system defines specific attributes for the views (e.g., name, context); (b) the view creator assigns values to these attributes; (c) the designer (using the list and the view) specifies the value for the given attribute; (d) the view would be selected based on the provided attribute values (e.g., name, context).

In a demonstrative example, the system may include a name attribute 113E for each view, unique for each element type. The designer can specify the name of the view to use when defining the LC (or web page). For each item type, the view that has the given name and is associated with the given item type would be used. It should be noted that there can be multiple views with the same name for different types of elements; and therefore specifying the view name can actually create multiple association relationships (e.g., as noted herein for repeater components).

In another demonstrative example, the system may assign a context attribute 113F, with the possible values of "thumbnail mode" and "zoom mode." The designer can specify for a given LC (or repeater component or web page) the context for view selection (e.g., thumbnail mode or zoom mode), and the selected view (for each type) would be the view that has the given context. Demonstrative examples are shown in Figures 23A and 25, which They show the same restaurant list app, which includes all three collections (menu, section, and dish) and composition item types. However, there are multiple views associated with each of the 3 types, and these are arranged as layouts, with each layout defining a specific view for each of the 3 types. As can be seen in these figures, the user can select a design in the design selection area (e.g., design [x] in Figure 23B and design [y] in Figure 25) and this affects the view used for each of the 3 types of elements. The design name/code serves as the context variable in this case.

Alternatively, multiple views can be explicitly associated with a given element or element type. In these cases, a conditional selector module 173B may define and/or impose one or more conditions under which one of the associated views is selected. These conditions may include, for example: (a) the type of LC used to display the item (e.g., a large area container may use a detailed view (which displays many fields), while a gallery-type container you can use a smaller view that includes a thumbnail and just some descriptive text); (b) the contents of a specific "selector" field in the displayed element; (c) the identity of the user accessing the collection, or specific properties in the user profile of the accessing user (e.g., an employee of the online store can see more information in additional fields, in relation to the content that is displayed to a visiting guest user).

Optionally, a view-by-function association module 173C may be used to associate different views for different functions and to execute such association. For example, the WBS 100 can assign different views for displaying elements, creating elements, and updating elements. The designer can define these views and can also specify that a given view will be used for multiple functions (e.g., it will be used for both creating and updating elements).

Searching the group of available views

Reference is made to Figure 13, which is a schematic block diagram illustration of the WBS 100 particularly demonstrating view search, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise a view group finder 174 (a finder module for searching view groups), which may execute a search query on the view group to locate a view composition. The applicable view group can be defined at any suitable level, for example, the system level, the application level, the item collection level, or the item type level. It can also be a combination of several groups (e.g., defined at different levels).

The view group search engine 174 may use one or more suitable query types, for example, keyword-based, field composition field, composition attribute, application-related parameters, or other suitable query types. The view group finder 174 may combine two or more of the query procedures, for example, to select among views that have composition fields while applying a particular condition to the attributes of the view.

In keyword-based view search, which may be implemented using a keyword-based view finder module or submodule 174A, both item types and views may have keywords attached or associated with them (e.g., a or more keywords, possibly selected from a predefined list). The composition algorithm attempts to locate the views that have the highest composition of keywords with the item type's keyword list.

In field view composition search, a field composition finder module or submodule 174B may search for the view that has the best component set composition with the field set in the element. Composition can be done based on field names, attributes, or special composition IDs. Rating, scoring, or ranking of compositions may be performed using a scoring/ranking module 175, for example, by comparing the number of composition fields, or using a per-field weighting to calculate a weighted score.

Optionally, a field data dictionary 176 can be defined and used (e.g., at the system level, application level, or other level) for the creation of item type fields and view components. Composition can be performed using field data dictionary 176, for example, using a dictionary finder 177 to locate view components and element fields that have one composition field per underlying data dictionary.

An attribute-based search engine 178 may perform an attribute-based search. For example, views can have additional attributes assigned to help find view compositions with elements. The element type (or element) may include a query (using an appropriate query language or expression) that is applied to the relevant or available views to select which views are the best composition for this element based on the one or more attributes of sight. The query can be fully specified (e.g., include all conditions) or can be parameterized to include one or more parameters, for example: (a) element-specific values (e.g., the query is specified in the element type level, but has specific parameters filled by the element); (b) element data field values (e.g., parameters based on data fields in the specific element); (c) LC type (e.g., parameters that depend on the specific LC on which the image is to be displayed). view), for example, so that the LC size and container type can determine which view size is optimal; and/or (d) general environment settings (e.g., user classification and privileges). Attribute-based search can be implemented as a generalized version of the view attribute pre-association (e.g., via name/context) described above.

Optionally, element and view type composition can be performed based on application-related parameters, using a search engine 179 for application-related parameters. The view search can therefore take into account parameters related to the application; For example, different views can be selected dynamically for the first and last item in the result of a filter query. This way the "next" and "previous" navigation buttons can be displayed dynamically as needed.

A multiple composition results handler 180 can handle multiple results, since some of the composition techniques described above can produce multiple candidate views for the display of a particular element. In such a case, compositional sorting (e.g., generally similar to search engine sorting) can be used to select the best view to use among the candidate results. Additionally, the multiple composition results handler 180 may choose to use the best composition found, but may retain the list of candidate views and may provide a GUI element that allows the user to toggle the display to use one of the other candidate views that are displayed. They have found.

A reservation handler 181 may guarantee reservation to the array element type. For example, item types can be created through an inheritance process based on other item types and a set of modifications. If no results (or no "good" results, high-quality composition, or high-scoring composition) have been found for the given element and element type, then the fallback handler 181 may order the process to be rerun. composition using the data values of the same element (if applicable) but uses the element type which is the array of the current element type. For example, an element type "shirt" can be derived from the parent element type "product"; If no composition view (or no high-scoring composition view) has been found for an element of type "shirt", then the composition process can be repeated automatically, this time using the parent element type "product" instead of the element type "shirt".

Dynamic view construction

Reference is made to Figure 14, which is a block diagram schematic illustration of the WBS 100 particularly demonstrating the dynamic view construction, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise a dynamic view builder 182, to dynamically generate "on the fly" one or more views as needed or preferred to display element fields, rather than searching through a group of existing views; or, in addition to searching an existing view group (e.g., if no compositions are found in the existing view group; or if only low-scoring compositions are found). Automatic view construction policies can be predefined or provided, along with field definitions.

In a demonstrative implementation, for example, the dynamic view constructor 182 can implement several generic and abstract view templates that only divide the display area into multiple regions, implemented using a region divider module or submodule 182A in the view. Each element type can specify which generic template to use. Each field can specify, for example, the region in which the field should be placed and an alignment code that indicates where the field should be added (e.g., top left, bottom center), as well as how the previous field or fields can be related to the same area of the region (e.g., join after the previous field; new line; below, but left aligned in the same way). A field can also specify dynamic layout type anchors or other layout rules (e.g., specifying that two particular fields should be aligned vertically). The dynamic view constructor 182 can thus create a suitable view for each element type automatically based on the provided directives and rules. This can be particularly useful for automatically creating data entry forms, update forms, and/or other forms.

Integrated View Search/Dynamic Construction

As described above, the WBS 100 may locate views (using preassociation or search) or may create views dynamically. Additionally, the WBS 100 may also integrate the two procedures, locating a base view and then expanding it (when necessary) or otherwise modifying it (via a localized view modifier module 182B) using the aforementioned dynamic view construction techniques. previously (e.g. arrival zones). This can be implemented using a finder/builder module 183, and can be particularly useful for elements that have a relatively fixed base format (and set of fields), which also have additional fields added dynamically (e.g. RSS feed with optional fields).

View selection and polymorphic display

Reference is made to Figure 15, which is a schematic block diagram illustration of the WBS 100 particularly demonstrating view selection and polymorphic display, according to some demonstrative embodiments of the present invention. In some cases, multiple views may be available (e.g., views 155A, 155B, and 155C) for the display of the same element. This may occur, for example, because the designer has previously associated multiple views with the same element (or element type), or because of a view selection query that has resulted in multiple view compositions. The set of possible view compositions may be known in advance (e.g., if they have been previously associated with the element), or may be determined dynamically (e.g., in the case of localized views using a composition query).

In these cases, the WBS 100 may provide one or more options to the designer, for example: (a) to use a view priority manager 184A to assign a priority value to the various views (assuming they are known in advance), so that the WBS 100 would select the view that had the highest priority value; (b) use a hook/callback manager 184B to define a hook or callback in the application, which would allow the application to select the correct view to use; (c) use an end-user selection UI generator 184C to expose multiple view options to the end user, allowing the end user to select the view to be used for the given element (e.g., using a default view and including a "switch view" dropdown menu or a combo box widget on the visualization).

In a first demonstrative example, a view choice persistence executor 184D may ensure that the view choice is persistent. For example, displaying items typically allows the end user to move from one item to another in the collection (e.g., navigate to the previous or next item). Displayed items can have different views used to display them. The view choice persistence applicator 184 may allow the designer to specify that the choice of a view to display a given element type is persistent. Consequently, if the end user hovers over the collection items and returns to the same item type, the same view would be used (among the multiple possible views); unless there is a specific reason not to reuse it (such as a different separate view association for the displayed element).

In a second demonstrative example, a polymorphic display generator 185 may enable polymorphic display. For example, the end user can affect view selection by changing the primary display type (e.g., multi-page container type) used by the LC to display the elements. The designer may allow the end user to determine whether a given list would be displayed in a "list mode" (displaying 1-2 lines of information per item) or in a "page mode" (displaying a full page of item information given). Similarly, a designer can allow the end user to switch an LC display between a grid-type gallery (displaying items arranged in a grid) to a slider-type gallery (displaying the item in a layout similar to a grid). slide presentation). The choice of LC display mode can also affect the view chosen for display. The polymorphic display generator 185 can be used to ensure that the user can switch between multiple views (or LC displays) that the designer has designed in advance for this purpose.

Stage 2: Create a complete view based on the view and element fields

Reference is made to Figure 16, which is a schematic block diagram illustration of the WBS 100 particularly demonstrating the creation of a complete view, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise a full view creator 186, to create a full version of the view composition or the dynamically constructed view. It is clarified that a complete view can be an instance of the view entity, constructed dynamically based on the data supplied by the element.

First, the full view creator 186 may use a view-to-field composition module 186A or submodule to project each data component in the view to a composition field in the element type (and the underlying element). This can be done, for example, using one or more of the following procedures: (a) explicit prior association by the designer; (b) common name used by a view component and element field; (c) Special association ID; (d) query on the composition of keywords assigned to view components and element fields; (e) a query defined for a data component that searches for prespecified attributes in the fields of the element composition. For non-data components (e.g., title text), such composition may not be necessary.

A missing field handler 187 can handle missing fields - view fields (which should be filled with content) for which no composition element field has been found. For example, if no composition field has been found, the missing field handler 187 may display the appropriate text or image in place of the view component (provided by the data component itself or by the WBS 100). This could occur during design time or at run time (e.g., when RSS feeds provide items and some required fields may be missing). Optionally, a discreet message or an informal warning message may be provided, displayed or recorded. The actual display message displayed may depend on the URL used for the user's call or login; so that, for example, the designer can receive a more exhaustive message.

If the component has anchors or other DL-related associations, the missing fields handler 187 may not delete the component, but rather may use a component resize module 187A to resize it to zero size. If the component has no anchors or other DL-related association, then the missing field handler 187 may remove the component along with any spacers. related to the attached layout, so that there is no additional space that would have been added if the field were present.

Second, the full view creator 186 may use a component value calculator 186B to determine the value of all calculated components; for example, calculated based on the values of the fields, including in particular the value entered in the data components. Third, the full view creator 186 can determine whether or not to include conditional components; For example, the view may contain conditional components whose inclusion depends on one or more conditions.

Stage 3: Apply the dynamic layout to the full view

Reference is made to Figure 17, which is a block diagram schematic illustration of the WBS 100 showing the dynamic layout and settings for a complete view, according to some demonstrative embodiments of the present invention. For example, DLM 101 may apply DL processing to the entire page (or minipage) containing the LC or LCs based on the full view. This DL processing can be done in conjunction with determining the best display size to use for the entire view.

DL processing may take into account DL-specific rules 101A and/or DL anchors 101B, for example, originating from the following: (a) the underlying element containing the LC; (b) fixed DL information contained in the view definition; (c) conditional DL information contained in the view definition applicable depending on the specified conditions of the view.

DL processing can affect the entire page containing the LC. For example, if the LC is used to view a new item in which a given text field is larger than the currently displayed item, the DLM 101 may cause the entire displayed minipage (containing the view) to grow or increases in size, thereby causing the LC to grow and move or relocate components on the containing page.

The DLM 101 can apply animation and transition effects, so that changes resulting from switching elements (and possibly views) in the LC are presented through smooth, animated changes, rather than abrupt changes.

Determining and adjusting the display size of a view

The display area required by a specific full view instance may vary and may be determined and/or adjusted (e.g., modified) by a view display size adjuster 188, since the data components in the view ( e.g., text, image) can include different amounts of data for different instances of the view. The view is typically displayed at the size defined for it in the WBS 100. However, in some cases, the size can be optimized for a specific screen, browser, or device configuration. In these cases, the view display size adjuster 188 may adjust the area assigned to the view, taking into account the specific full view data.

For example, changes to the width of the view can affect the height of the view. In particular, text display components that are required to fit a narrower area (horizontally) can grow vertically to display the same amount of text (e.g., splitting it into more lines).

The view display size adjuster 188 can optimize the displayed view to obtain the best aesthetically pleasing result. For example, the view display size adjuster 188 attempts to find the best size (and resulting layout) for the view, to achieve or optimize one or more of the following (possibly contradictory) objectives: (a) make the view displayed has an aspect ratio as close as possible to the browser display window for the application; (b) minimize the amount of scrolling required to view the full view (e.g., if zooming vertically down and requiring scrolling); (c) comply with all DL rules and anchors specified for the view.

In a demonstrative implementation, the view display size adjuster 188 may perform the following operations: (a) take the width of the original view instance; (b) use a target width generator 188A to create a set of possible target widths, starting with the original width and going down to a predefined value parameter (e.g., 100 pixels), thereby creating a set of possible "target widths" (e.g., calculated by limiting the size of the set by a minimum difference between the sizes); (c) perform the calculation of D ^l for the view instance for each of the target widths and obtain the resulting height for each of the target widths; (d) finding and selecting, using a target width selector module or submodule 188B, the resulting height-width set that is closest to the aspect ratio of the display window of the attached page, but does not exceed the height of the available screen; (e) if, for each of the target widths, the height exceeds the available screen height, then select the target width that has the smallest height.

View Modification and Derived Views

A view modification module 189 may allow the designer to modify a view by adding, removing and/or modifying the displayed components. The system can allow the designer to apply the modification "in place" (e.g., affecting the actual view and all elements that use it), or create a derived (inherited) view from the edited view ( modified).

A derived view can be thought of as an inheritance-based variant of a parent view. For example, a 'shirt' view is a derived child of the 'product' view, but may have an additional 'color' attribute/field. If the view is associated with a given item type (or types), Creating a derived view can also create a similarly modified element type (or types) that can be used to create elements in the associated collection or in other collections.

According to the present invention, the WBS 100 may use the given view if it is relevant to the element; and if this is not possible, then the WBS 100 can invoke a parent view finder 190 to go up the inheritance tree (or inheritance chain) and can use the top level view or views to display the given element. In some implementations, if a view composition is not found, the WBS 100 may move up the element type inheritance tree (e.g., using fallback handler 181); whereas, in other implementations, if no view composition is found, the WBS 100 may move up the view inheritance tree (e.g., using the parent view finder 190). Other implementations may use a combination of both procedures, with a mechanism to determine on the fly which composition procedure is preferred or which composition result is preferred and used.

The created (modified) view is also available for other elements. When a derived view is created or modified, it can be applied (or pre-associated) to existing elements or element types.

The WBS 100 may further provide the reverse option, allowing the designer to create derived types and have the WBS 100 automatically invoke a derived view generator 191 to also automatically create a derived view composition; for example, creating a derived view based on a derived type (and not the other way around).

The designer can create the new component based on a single component template. The view creator may further include such single component templates along with the created view, and such component templates may be suggested to designers who wish to modify the template.

Component arrival areas

Reference is made to Figure 18, which is a schematic block diagram illustration of the WBS 100 demonstrating the location and modification of the arrival zone, according to some demonstrative embodiments of the present invention. The WBS 100 may support arrival zones, such that new components added to a view can be automatically or semi-automatically located within the view using a landing zone location module 192. The view designer can define multiple landing zones in the view template. For example, components can be arranged in multiple columns and a landing zone is created at the bottom of each column; or alternatively, the components can be arranged in a particular hierarchy of containers and a landing zone can be defined at the bottom of some (but not all) of the containers. The designer of the original view can use an arrival zone editor 193 to designate explicitly specified arrival zones, assign names to the defined "arrival zones", and specify various arrival zone attributes. When a new component is added to the view, a list (e.g., drop-down list) of the landing zone names is displayed and the designer can select a target area for the new component.

Landing zones can include designer-specified attributes that define rules for finding component composition templates. For example, if the designer has specified that the new component will be added to a wide column, the system can recommend a wide format component template. This effect can operate in both directions, so the selection of the landing zone can affect the recommended component templates and vice versa.

Optionally, a landing zone generator 194 may automatically generate landing zones, including (for example): (a) at the end of each container or minipage; (b) at the end of containers that have a given type or attribute; (c) after places where recent field additions have been made; (d) in locations that have at least a given amount of empty screen space; (e) on a newly created page or minipage (e.g., adding a component to an additional page in a multi-page container). When a component is added to a view (using a landing zone or otherwise), the layout of the view is recalculated using dynamic layout.

Applying a derived view

Reference is made to Figure 19, which is a block diagram schematic illustration of the WBS 100 particularly demonstrating the modification of the view, according to some demonstrative embodiments of the present invention. When a view is modified, the WBS 100 may create a derived view that inherits from an existing view that is being modified. The existing view can be associated with multiple element types (possibly used by multiple elements in multiple collections) and can also be directly associated with multiple elements in multiple collections. In this case, the WBS 100 may invoke a "bulk search and association" module 195. prior" to perform a mass (or bulk or batch) prior association of types and/or elements.

For example, the "bulk search and preassociation" module 195 may scan all types and/or elements that are directly or indirectly associated with the existing view; and you can re-associate them with the derived view. Criteria for pre-association may include, for example: (a) conditions based on the content of element fields; (b) conditions based on the existence of element fields; (C) condition based on type/element attributes; (d) a combination of the above criteria. Optionally, manual confirmation can be requested from the designer, regarding which types/elements to re-associate (e.g., requested by type or by element).

In a demonstrative example, when creating a "shirt" item type derived from the "product" item type, the designer can specify that the product collection will be scanned and that all "product" items that have the word "shirt" will be scanned. in your title and that were created in the last two months will automatically be converted to the "t-shirt" type.

Customizations and Personalization Dialogs

The WBS 100 may comprise a customization module 201, which provides for the creation of customization dialogs that can be used by the designer (and possibly the end user) to customize various parameters and attributes in the displayed list application.

It will be appreciated that the personalization module 201 may include various characteristic features and/or technologies and/or submodules and/or processes, or may be associated with, or may utilize or implement, for example, as described in US 2014/ 0282130 A1, entitled "A System and Method for Dialog Customization", filed on the same day as this document (March 13, 2014)

Such customization can be applied to website elements, including views, elements, and view/element combinations (e.g., a given element is customized in some way, but only when displayed in a given view) . It may also apply to third-party applications included in the created website. The customization option may be available to the designer, or possibly to users of the application at a later stage who have specific design/modification privileges.

Customization can affect the attributes and elements of the specific elements or views involved, as well as other objects related to them (e.g., through containment or inheritance). It may include customizations such as (for example): (a) should the system display a given component (yes or no); (b) fixed content (e.g. title text); (c) the display attributes (e.g., font, size, color) of a specific component; (d) screen distances (e.g., distance between the name of the dish and its description); (e) counts (e.g., number of columns in a multi-column display); (f) generic parameters - which are passed to the component/element that handles the display; and/or other appropriate customizations.

The WBS 100 supports customization using generated dialog boxes that include attributes to customize. Such dialogs are generated using a customization dialog builder 201A, displayed to the user (and capable of interaction with the user) using a customization dialog viewer 201B, and then applied to the affected elements using a customization dialog result applicator 201C. personalization;

In many cases, a single customization value should affect multiple items. For example, the same color adaptation should be applied to multiple components in the display view that must remain harmonious; The distances between the right edge of the view and two separate components can be adjusted, but must remain the same for both components. Additionally, a customization can affect (for example) a specific view displayed, all views displayed (of a given type or all types), all instances of a given view, or views in a given scope (even if are not currently displayed), or to specific view instances explicitly selected by the designer.

The effect of the customization may not be identical on all affected objects. For example, components A and B may be required to maintain a particular layout, such as component B's distance from the top of the view being twice the distance of component A from the top of the view. . In this case, the customization can be applied individually as needed (using an object-specific formula).

An example of a customization dialog is shown in Figure 23A. In this example, a restaurant list application (LA) displays items from three collections (menu, section, and dish) hierarchically within a single LC. The system has generated the customization dialog shown, which includes the customizations "Section Image Height", "Show Section Image", "Show Section Separator", "Show Plate Description", "Show Price of the plate" and "Spacing between elements". Values entered through this dialog box affect all views displayed in the current LC.

Following this example, Figure 27 demonstrates how changing the "item spacing" (A) customization value from 15 pixels (as in Figure 23A) to 123 pixels would increase the spacing (B) between multiple instances of the "dish" view. ".

The generated dialog box can be pre-specified or automatically generated. It can also be a stand-alone UI element or integrated with the rest of the WBS 100 UI. It can also be displayed automatically or require explicit invocation by the designer.

Specific element adaptation

The WBS 100 may comprise an element-specific adaptation module 196 to create adaptations to a specific element, for example, by adding (e.g., by drag and drop) specific components to an element displayed at the element level and in context. of a specific view. This can be used, for example, to add "decoration" elements to specific elements, or to add additional information that is only available for certain specific elements, without having to create separate views and element types.

For example, the WBS 100 may use a local variant creator 196A to automatically create a local variant of the view, or an "internal" derived view. Adaptations can be stored as a "layer" of modifications to the existing view within this local derived view variant. The WBS 100 may store this derived view at the site level or at the page level or at the LC level, along with an ID of the element for which this adaptation applies. The adaptation can also be stored with the same list application whose instance is used in the site. The same LC or page can store multiple adaptations to multiple elements. The WBS 100 applies the adaptation each time the element is displayed with the specific view on the specific LC.

In some embodiments, optionally, the element-specific adaptation module 196 may offer the ability to apply the same adaptations to other elements in the same LC that use the same view, or to other views.

If adaptations are stored at the site level, then the adaptation will be applied to instances of the same element displayed in the same view in different LCs (or repeater components). It should be noted that adaptations are different from item customization; For example, adaptations involve adding additional elements and components to an existing element, while customizations involve changing the parameters and attributes of one or elements (or views) based on possible predefined customizations. It should be noted that customizations can include "show component X or not", which can make it seem similar to adding a new component.

Filters and search box

Optionally, a search box creator 197 may allow the designer to specify that a given LC display a subset of associated collection items, selected based on given search criteria (e.g., a given query applied to fields or other filters). ). The designer can further specify that the search box will be displayed to the end user when viewing the LC, allowing the end user to selectively filter or search the displayed content. An example of such a search box is shown in Figure 26.

LC connections

Reference is made to Figure 20, which is a block diagram schematic illustration of the WBS 100 particularly demonstrating LC connection management, according to some embodiments of the present invention. An LC connection manager 198 allows LCs residing on the same page or template to connect (or interconnect) in one or more appropriate ways. Connected LCs reside in different containers (or container levels) within the page. These connections can form a network, so that a particular LC can connect to multiple other LCs. The LC connection manager 198 supports an aggregator field connection and may support various other types of LC connections, for example, related list connection, tag cloud connection, element tree connection, and/or display connection. form.

In a related list connection, which may be managed or managed by a related list connection manager 198A, a first LC "A" displays a collection of "master items" (e.g., a list of hotels); while a second LC “B” displays a collection of “subordinate elements” (e.g., guest reviews for each hotel). A pre-specified field on the current element in LC "A" can be used to query the collection displayed in LC "B" and select subordinate elements. LC "B" would only display the selected elements that make up the current element in LC "A". The designer can define additional filtering and/or sorting criteria to query the collection of subordinate elements; for example, to select only the first K reviews, select only reviews that include a specific rating range, or similar. This can be implemented in any suitable way, including using a full query language (e.g. SQL). A single "master items" LC can be connected to multiple related list LCs; for example, allowing you to add a related list display of the ten best reviews and/or the ten worst reviews. This can be achieved by using repeater components contained in the view, rather than separate related LCs.

An aggregator field connection, which is managed or managed by an aggregator field connection manager 198B, is suitable when a related list connection has been defined. The designer can add a calculated field to the display in the master element LC "A" that displays the value of an aggregation function applied to a specific field in the subordinate list items. Said aggregation function is at least one of: count, total, average, median, minimum, maximum or other suitable function.

A tag cloud connection, which may be managed or handled by a tag cloud connection manager 198C, may connect a tag cloud LC to a regular LC, both LCs being associated with the same collection or collections. The tag cloud LC can be automatically populated with tags derived from existing items in the associated list (or a portion thereof, depending on the filtering criteria). The user can select multiple LC tags from the tag cloud. The selected tags are used to form a query, which serves as a filter and determines which items are displayed in the second LC "B". This may be a private case of "related query LC" (a related LC that is only used for queries).

In an element tree connection, which may be managed or managed by an element tree connection manager 198D, the LC may display a subhierarchy of elements (e.g., an element tree), such as an organization chart or a family tree. Hierarchy can be defined through the existence of pointer fields on elements, for example, a pointer to the parent element or a set of pointers linked to sibling elements. Aside from using a tree-like structure to display minipages (each containing a view used to view one item), the structure may be similar to other carousel-type LCs (which also display multiple items).

In a form display connection, which may be managed or managed by a form display connection manager 198E, an LC [a] may request that a given element [b] be opened in a given secondary LC [c], using an automatically selected view or a specific view [d]. This can be used, for example, to display an alternative version of an item currently displayed in the LC [a]; such as, to display a detailed version of the same item with a more detailed view, or to display an alternative presentation of the same information (e.g., displaying the location on a drop-down map instead of displaying a textual street address) . Similarly, this procedure can be used to display an "added item" to create a new item; or to display an "update item" or "delete item" form.

App store integration

Reference is made to Figure 21, which is a schematic block diagram illustration of the WBS 100 that particularly demonstrates the integration of the app store, according to some demonstrative embodiments of the present invention. The WBS 100 may comprise, or may be associated with, an application store ("app store") 199, which may be operated or managed through an app store manager module 199A. Although an external app store 199 is shown for demonstration purposes, it is clarified that the app store 199 may optionally comprise one or more application stores that may be operated by the WBS provider or third parties, and may be internal. or external to WBS 100. A developer at any level (e.g., a regular site developer or a separate third-party developer) may include one or more objects (e.g., depending on the developer's permissions) in a store 199 app, so that other users can buy and/or download them. Such objects may include, for example: List applications; views; templates (at all levels); element types; collections (e.g., selling access to the collection rather than the collection itself); components (e.g., particular LCs with their full associations).

The developer can define or attach icons, marketing materials, price, search keywords and various attributes to the objects offered in the app store 199. Offered objects may contain an encapsulated version of other objects required for them; For example, a view object may contain multiple item type objects that may be required for its operation. Offered objects may optionally refer to non-included objects; For example, a list application may rely on a particular view that is not included in it, and that view would be provided by the included website. The WBS 100 may use a missing reference handler 117 to resolve such missing reference by including it in one or more suitable ways, for example: (a) automatic resolution by name and type of missing reference; (b) ask the designer to provide an explicit resolution; (c) create a "draft version" of the missing reference object, based on the available information (type, name, attribute values) and mark it so that the designer has to complete it later, before publication. The missing reference handler 117 may also perform a search for possible candidates (e.g., based on similar name, similar properties, specific search attributes) and may provide the designer with a ranked list of possible compositions.

Discussions herein that use terms such as, for example, "processing", "computation", "calculation", "determination", "establishment", "analysis", "verification" or the like, may refer to operations and /or processes of a computer, a computing platform, a computing system or other electronic computing device, which manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the registers and/or memories of the computer or other information storage medium that can store instructions to perform operations and/or processes.

Some embodiments of the present invention may take the form of an all-hardware embodiment, an all-software embodiment, or an embodiment that includes both hardware elements. as software. Some embodiments of the present invention may be implemented in software, firmware, resident software, microcode, an application that a user can download and/or install, an application that can run in a browser, a client-side application, a client-side application. server, a client-server application, or similar. Some embodiments of the present invention may take the form of a computer program product accessible from a computer-usable or computer-readable medium that provides program code for use by, or in connection with, a computer or any execution system. Instructions. For example, a computer usable or computer readable medium may be or may include any device that can contain, store, communicate, propagate or transport the program for use by, or in connection with, the instruction execution system or device. . Some embodiments of the present invention may be implemented, for example, using a machine-readable medium or element that can store an instruction or set of instructions that, if executed by a machine, cause the machine (e.g., a computer or an electronic device) device) perform a procedure and/or operations described herein.

Some embodiments of the present invention may include or use, for example, a processor, a central processing unit (CPU), a digital signal processor (DSP), a controller, an integrated circuit (IC), a memory unit, a storage unit, input units, output units, wired and/or wireless communication units, an operating system and other suitable hardware components and/or software modules.

Some embodiments may be implemented as or through the use of an application or "app" for a smartphone or tablet or portable computing device, which may be downloaded and/or installed on said electronic device from an "app store" or a online marketplace for apps

The functions, operations, components and/or characteristic features described herein with reference to one or more embodiments of the present invention, may be combined or used in combination with one or more functions, operations, components and/or characteristic features described in the present document with reference to one or more embodiments of the present invention.

Claims (14)

1. A website building system, WBS, comprising: a group of content elements that will be displayed on a website being built; a set of views used to display said elements, each view being a template for a section of a web page of said website; a dynamic composition and adaptation module adapted to dynamically provide a suitable view for each content item for displaying said content item on said website, wherein the dynamic adaptation and composition module is configured to dynamically locate a view composition from said set of views and/or construct a view composition on the fly and/or modify the located view, the view creation system websites are characterized in that they also comprise: a link component manager (198) configured to define a link component; wherein each link component is a multi-page container that displays content elements obtained from said group of content elements through dynamically or statically associated view content elements, with each minipage of said content container multiple pages that display a content item through the associated view; and wherein the link component manager (198) is configured to connect two link components residing on the same web page or template based on an aggregator field connection; wherein an aggregation field connection manager (198B) is configured to apply an aggregation function to a field in a list of content items in one of said two link components; wherein said aggregation function is at least one of: count, total, average, median, minimum and maximum. 2. The website creation system of claim 1, wherein the system supports content item types, wherein at least one view in the view set is associated with a content item type and is can use to display items that belong to that content item type. 3. The website building system of claim 1, wherein the system supports view inheritance through a view inheritance module that can generate a derived view that inherits characteristics of an existing view. 4. The website building system of claim 3, further comprising a parent view finder for searching up a suitable view in a view inheritance tree, if a given view is not suitable for a given content item. . 5. The website creation system of claim 1, further comprising a dynamic layout manager for applying one or more dynamic layout rules to a particular view. 6. The website building system of claim 1, wherein a view comprises a repeater component contained within said view, wherein the repeater component displays a secondary list related to a primary list of content items displayed at through a view. 7. The website creation system of claim 1, wherein the link component manager is associated with a tag cloud connection manager to interface between two link components based on the selection of tags from one cloud tag that is associated with one or both of these link components. 8. The website creation system of claim 1, further comprising: a specific element adaptation module to adapt a specific content element by performing at least one of the following: (a) add one or more components to a content displayed in an application context of a specific view; (b) remove one or more components of a content displayed in an application context of a specific view; (c) modify one or more components of a content displayed in an application context of a specific view. 9. The website creation system of claim 8, wherein the element-specific adaptation module comprises a local variant creator for creating a local variant of a given view as a derived internal view and for adding a layer of modifications to said derived internal view. 10. A computerized procedure for building a website, comprising: store a group of content elements to be displayed on a website being built; storing a set of views that is used to display said elements, each view being a template for a section of a web page of said website; performing dynamic composition and adaptation to dynamically provide a suitable view for each content item for displaying said content item on said website, comprising dynamically locating a view composition from said set of views and/or constructing a view composition view on the fly and/or modify the localized view composition, the procedure is further characterized by: defining link components, wherein each link component is a multi-page container that displays elements of said group of content elements through a dynamically or statically associated view for content elements, each mini-page of said multi-page container displaying a content element through the associated view; and connect two link components that reside on the same page or template based on an aggregator field connection; applying an aggregation function to a field in a list of content items in one of said two link components; wherein said aggregation function is at least one of: count, total, average, median, minimum and maximum. 11. The computerized method of claim 10, further comprising supporting view inheritance by generating a derived view that inherits characteristics of an existing view. 12. The computerized method of claim 10, further comprising applying one or more dynamic layout rules to said particular view. 13. The computerized method of claim 10, wherein the given view comprises a repeater component contained within said view, wherein the repeater component displays a secondary list related to a primary list of content items displayed through said given view. 14. The computerized method of claim 10, further comprising: perform a specific item adaptation to adapt a specific content item by doing at least one of the following: (a) add one or more components to a content displayed in an application context of a specific view; (b) remove one or more components of a content displayed in an application context of a specific view; (c) modify one or more components of a content displayed in an application context of a specific view.