Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "TigerstripeF2F 20080421"
(→Proposed Discussion Topics) |
|||
| Line 17: | Line 17: | ||
b. Default settings for new Artifacts/components. Possible save a "template" object with the default types, values, stereotypes etc. Any new "thing" would use this template. | b. Default settings for new Artifacts/components. Possible save a "template" object with the default types, values, stereotypes etc. Any new "thing" would use this template. | ||
| + | |||
| + | 3. Headless Environment | ||
| + | * Initialization | ||
| + | * Plug-in configuration via Headless plug-in (Maven, ANT). | ||
Revision as of 10:26, 2 April 2008
Contents
< To: Tigerstripe Face2Face Meetings
Where/When
- April 21-23, 2008
- Seattle, WA, hosted by Cisco Systems, Inc.
Proposed Discussion Topics
1. Testing a. API b. GUI c. Diagrams
2. "Customisability" a. Custom naming rules for new ModelComponents (incl artifacts). This is an idea to allow users (eg Chameleon) to override the naming rules for new things - as opposed to fixing naming rules in teh application - eg having "Has" in the middle of association names.
b. Default settings for new Artifacts/components. Possible save a "template" object with the default types, values, stereotypes etc. Any new "thing" would use this template.
3. Headless Environment
- Initialization
- Plug-in configuration via Headless plug-in (Maven, ANT).