Metadata driven user interface system and method

• US 9,268,538 B2
• Filed: 04/04/2008
• Issued: 02/23/2016
• Est. Priority Date: 05/02/2007
• Status: Active Grant

• Current Assignee: Sugarcrm Incorporated
• Original Assignee: Sugarcrm Incorporated
• Inventors: Taylor, Jacob, Itani, Majed, Smith, Roger
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): KABIR, MOHAMMAD H
• Application Number:
  US12/062,511
• Publication Number:
  US 20080276218A1
• Time in Patent Office: 2,881 Days
• Field of Search: 717/106
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A metadata driven user interface system and method are provided. In an exemplary embodiment, a software-based customer relationship management system and method may include the metadata driven user interface system.

Claims

1. A software application system, comprising:

a computing device with a processing unit;

an application having a plurality of lines of computer code wherein the plurality of lines of computer code are executed by the processing unit of the computing device to generate a user interface of the application;

a data store having one or more controllers and one or more views;

the one or more controllers that each control the generation of the application;

a controller factory that selects a particular controller for a particular instantiation of the application using a discovery process of the one or more controllers;

a module controller that selects an action associated with the instantiation of the application based on the selected particular controller; and

a view factory that selects a particular view based on the selected action using a discovery process of the one or more views.

2. The system of claim 1, wherein the controller factory selects from a custom controller.

3. The system of claim 1, wherein the controller factory performs the discovery process to select a custom controller for the particular instantiation of the application, select a my module controller and select a default controller if no custom controller and my module controller exists.

4. The system of claim 1, wherein the module controller using a execution process to handle the action.

5. The system of claim 1, wherein the view factory performs the discovery process to select a custom view for the particular instantiation of the application, select a my view and select an MVC view.

6. A method for generating a user interface of a software application system that has a computing device with a processing unit, an application having a plurality of lines of computer code wherein the plurality of lines of computer code are executed by the processing unit of the computing device to generate a user interface of the application, a data store having one or more controllers and one or more views and the one or more controllers that each control the generation of the application, the method comprising:

executing, on a processing unit of the computing device, an application having a plurality of lines of computer code;

discovering, using a controller factory of the software application system being executed on the processing unit, a particular controller for a particular instantiation of the application using a discovery process of the one or more controllers;

selecting, using a module controller of the software application system being executed on the processing unit, an action associated with the instantiation of the application based on the selected particular controller; and

discovering, using a view factory of the software application system being executed on the processing unit, a particular view based on the selected action using a discovery process of the one or more views.

7. The method of claim 6, wherein discovering the particular controller further comprises selecting a custom controller.

8. The method of claim 6, wherein discovering the particular controller further comprises selecting a custom controller for the particular instantiation of the application, selecting a my module controller and selecting a default controller if no custom controller and my module controller exists.

9. The method of claim 6 further comprising using, by the module controller, a execution process to handle the action.

10. The method of claim 6, wherein discovering the view further comprises selecting a custom view for the particular instantiation of the application, selecting a my view and selecting an MVC view.