Difference between revisions of "JEE Status Meetings/2009-06-18"

From Eclipsepedia

Jump to: navigation, search
(Agenda)
(Agenda)
Line 5: Line 5:
 
== Agenda ==
 
== Agenda ==
  
*Proposed scenarios for Module Assembly preference page:
+
Content of the Module Dependency Page
**Select projects (add/remove)
+
--------------------------
**Select jars (or other resources) inside the workspace (add/remove)
+
*Cosmetic
**Select jars (or other resources) outside of the workspace (add/remove)
+
**Two column vs three column
**Editing the deployment path (unless it is in a fixed location, such as the EAR lib dir)
+
***2 column would be [icon] Identifier, Deploy Path
*Review of last weeks discussion (& Rob's initial work ?)
+
***3 column would be [icon] Identifier, Deploy Path, More Info (full path)
**Konstantin wants to reduce the UI down to 2 columns - system path and deploy path
+
**Getting acceptable strings for column 0 https://bugs.eclipse.org/bugs/show_bug.cgi?id=276825
**Original discussion was icon plus 3 columns
+
***This could require functionally similar results from the API for all virtual components?
***Icon allows for type (project, workspace resource, external resource, VAR) plus decorations for additional information (such as "in lib dir")
+
**Same requirements for column 2 (right-side)
***Short name gives something more "developer friendly"
+
***The goal here would be so that the UI doesn't have to check a million conditions to see if it's an archive, if it's binary, etc, before getting a String to display
 +
**Icons on the left, but how many types of component are there?
 +
***How many different types of virtual component are there? Not how many classes, as anyone can make their own component type, but how many TYPES? From what I can see there's only lib, var, classpath, and project type. Are there any more?
 +
****Must identify the API's that tell us what these types are
 +
**Do we even show unmovable jars?
 +
***If this page is meant to be a component xml file editor of sorts, physically added files do not belong (since they are not referenced in the xml file)
 +
**Ironing out the buttons
 +
***Option A: just 2
 +
****Add Entry...  :  Remove Entry
 +
*****Add Entry... opens a multi-page wizard (extendable via points)
 +
*****Remove Entry offers to remove the entry
 +
***Option B: Three
 +
****Add Project..., Advanced..., Remove Entry
 +
***Option C: More than 3
 +
****Add Project... Add Jar... Add External Jar... Advanced... Remove Entry, Kitchen Sink...
 +
*Content
 +
**Currently (my) page only holds IVirtualComponent objects inside the viewer. I assume anything returned from Advanced... or a button must be an IVirtualComponent. The references are created at the end during performOK.
 +
*Functionality
 +
**Can the advanced button multi-page wizard also perform operations relevent to the module and return null to signify no addition is needed? For example, changing library directory? ;)
 +
**Should the table (first column) be able modify the archiveName attribute in the component.xml? See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=280411
 +
***If yes, this makes the issue of having the first column not just show some identifier but rather some actual jar / ear / war name (see 276825)
 
*Classpath entries
 
*Classpath entries
 
**Leveraging the JDT UI (is it possible yet?)
 
**Leveraging the JDT UI (is it possible yet?)

Revision as of 08:39, 17 June 2009

Attendees

Agenda

Content of the Module Dependency Page


  • Cosmetic
    • Two column vs three column
      • 2 column would be [icon] Identifier, Deploy Path
      • 3 column would be [icon] Identifier, Deploy Path, More Info (full path)
    • Getting acceptable strings for column 0 https://bugs.eclipse.org/bugs/show_bug.cgi?id=276825
      • This could require functionally similar results from the API for all virtual components?
    • Same requirements for column 2 (right-side)
      • The goal here would be so that the UI doesn't have to check a million conditions to see if it's an archive, if it's binary, etc, before getting a String to display
    • Icons on the left, but how many types of component are there?
      • How many different types of virtual component are there? Not how many classes, as anyone can make their own component type, but how many TYPES? From what I can see there's only lib, var, classpath, and project type. Are there any more?
        • Must identify the API's that tell us what these types are
    • Do we even show unmovable jars?
      • If this page is meant to be a component xml file editor of sorts, physically added files do not belong (since they are not referenced in the xml file)
    • Ironing out the buttons
      • Option A: just 2
        • Add Entry...  : Remove Entry
          • Add Entry... opens a multi-page wizard (extendable via points)
          • Remove Entry offers to remove the entry
      • Option B: Three
        • Add Project..., Advanced..., Remove Entry
      • Option C: More than 3
        • Add Project... Add Jar... Add External Jar... Advanced... Remove Entry, Kitchen Sink...
  • Content
    • Currently (my) page only holds IVirtualComponent objects inside the viewer. I assume anything returned from Advanced... or a button must be an IVirtualComponent. The references are created at the end during performOK.
  • Functionality
    • Can the advanced button multi-page wizard also perform operations relevent to the module and return null to signify no addition is needed? For example, changing library directory? ;)
    • Should the table (first column) be able modify the archiveName attribute in the component.xml? See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=280411
      • If yes, this makes the issue of having the first column not just show some identifier but rather some actual jar / ear / war name (see 276825)
  • Classpath entries
    • Leveraging the JDT UI (is it possible yet?)

Minutes