CONTEXT DEPENDENT PERSONALIZATION OF REUSE COMPONENTS FOR A USER INTERFACE
According to some embodiments, a business service provider may associate a user interface floor plan with a plurality of reuse components, each reuse component being adapted to be used with multiple user interface floor plans. For example, a second reuse component may be embedded within a first reuse component. In this case, an end user adaptation to the second reuse component may be received and the system may automatically store, within the first reuse component, a context dependent reference to the second reuse component associated with the end user adaptation.
1 . A computer implemented method, comprising:
associating a user interface floor plan with a plurality of reuse components, each reuse component being adapted to be used with a plurality of user interface floor plans, wherein a second reuse component is embedded within a first reuse component;
receiving an end user adaptation to the second reuse component; and
automatically storing, within the first reuse component, a context dependent reference to the second reuse component associated with the end user adaptation.
2 . The method of claim 1 , further comprising:
determining that the first reuse component is to be switched to a new reuse component; and
automatically copying the reference from the first reuse component to the new reuse component.
3 . The method of claim 1 , wherein the first reuse component is embedded within the user interface floor plan and further comprising:
determining that the first reuse component is to be deleted; and
automatically copying the reference from the first reuse component to use interface floor plan.
4 . The method of claim 1 , further comprising:
determining that a new reuse component is to be inserted between the first and second reuse components; and
automatically moving the reference from the first reuse component to the new reuse component.
5 . The method of claim 1 , wherein the reference comprises a component identifier and file path.
6 . The method of claim 5 , wherein the reference comprises a stable embedding anchor.
7 . The method of claim 6 , wherein the embedding anchor includes a reference to a software version number.
8 . The method of claim 6 , wherein the file path comprises a chain of file paths associated with a plurality of embedding anchors associated with embedded reuse components.
9 . The method of claim 1 , wherein the first and second reuse components are associated with a component repository maintained at a business service provider backend system.
10 . A non-transitory computer-readable medium storing program code executable by a computer to perform a method, the method comprising:
associating a user interface floor plan with a plurality of reuse components, each reuse component being adapted to be used with a plurality of user interface floor plans, wherein a second reuse component is embedded within a first reuse component;
receiving an end user adaptation to the second reuse component; and
automatically storing, within the first reuse component, a context dependent reference to the second reuse component associated with the end user adaptation.
11 . The medium of claim 10 , wherein the method further comprises:
determining that the first reuse component is to be switched to a new reuse component; and
automatically copying the reference from the first reuse component to the new reuse component.
12 . The medium of claim 10 , wherein the first reuse component is embedded within the user interface floor plan and further comprising:
determining that the first reuse component is to be deleted; and
copying the reference from the first reuse component to use interface floor plan.
13 . The medium of claim 10 , further comprising:
determining that a new reuse component is to be inserted between the first and second reuse components; and
moving the reference from the first reuse component to the new reuse component.
14 . The medium of claim 1 , wherein the reference comprises a component identifier and file path.
15 . The medium of claim 5 , wherein the reference comprises a stable embedding anchor including a reference to a software version number.
16 . A system, comprising:
a data store containing a plurality of reuse components adapted to be used with a plurality of user interface floor plan; and
an enterprise service infrastructure backend adapted to support a client device and to:
associate a user interface floor plan with a plurality of reuse components, wherein a second reuse component is embedded within a first reuse component;
receive an end user adaptation to the second reuse component; and
automatically store, within the first reuse component, a context dependent reference to the second reuse component associated with the end user adaptation.
17 . The system of claim 16 , wherein the enterprise service infrastructure backend is further to:
determine that the first reuse component is to be switched to a new reuse component; and
automatically copy the reference from the first reuse component to the new reuse component.
18 . The system of claim 16 , wherein the first reuse component is embedded within the user interface floor plan and the enterprise service infrastructure backend is further to:
determine that the first reuse component is to be deleted; and
automatically copy the reference from the first reuse component to use interface floor plan.
19 . The system of claim 16 , wherein the enterprise service infrastructure backend is further to:
determine that a new reuse component is to be inserted between the first and second reuse components; and
automatically move the reference from the first reuse component to the new reuse component.
20 . The system of claim 16 , wherein the reference comprises a stable embedding anchor including a reference to a software version number