You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/02/19 03:46:35 UTC
[jira] Created: (SHINDIG-80) Clean up GadgetSpec / GadgetView /
Gadget / ParsedGadget
Clean up GadgetSpec / GadgetView / Gadget / ParsedGadget
--------------------------------------------------------
Key: SHINDIG-80
URL: https://issues.apache.org/jira/browse/SHINDIG-80
Project: Shindig
Issue Type: Improvement
Components: Gadgets Server - Java
Reporter: Kevin Brown
Assignee: Kevin Brown
Priority: Minor
The GadgetSpec / GadgetView / Gadget heirarchy are a bit overwrought and difficult to follow at present. I propose simplifying this into a model with two classes:
- GadgetSpec: Roll up current GadgetSpec + GadgetView, represent an immutable, parsed representation of the gadget state.
- Gadget: Mostly the same as current "Gadget", sans functionality that belongs in GadgetSpec. This still represents a fully-processed gadget, including user pref values, hangman substitution, etc., but no longer deals with static details.
After making these changes, we can clean up the dependent code to always deal with appropriate data structures and will no longer have inconsistent structures being passed around.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SHINDIG-80) Clean up GadgetSpec / GadgetView /
Gadget / ParsedGadget
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Brown closed SHINDIG-80.
------------------------------
Resolution: Fixed
Applied.
> Clean up GadgetSpec / GadgetView / Gadget / ParsedGadget
> --------------------------------------------------------
>
> Key: SHINDIG-80
> URL: https://issues.apache.org/jira/browse/SHINDIG-80
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java
> Reporter: Kevin Brown
> Assignee: Kevin Brown
> Priority: Minor
>
> The GadgetSpec / GadgetView / Gadget heirarchy are a bit overwrought and difficult to follow at present. I propose simplifying this into a model with two classes:
> - GadgetSpec: Roll up current GadgetSpec + GadgetView, represent an immutable, parsed representation of the gadget state.
> - Gadget: Mostly the same as current "Gadget", sans functionality that belongs in GadgetSpec. This still represents a fully-processed gadget, including user pref values, hangman substitution, etc., but no longer deals with static details.
> After making these changes, we can clean up the dependent code to always deal with appropriate data structures and will no longer have inconsistent structures being passed around.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.