Bug 32239 - support registration of looks for (e.g. String) names
support registration of looks for (e.g. String) names
Status: RESOLVED WONTFIX
Product: contrib
Classification: Unclassified
Component: Looks
3.x
PC Windows 3.1/NT
: P4 (vote)
: 3.x
Assigned To: Petr Hrebejk
issues@contrib
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-24 15:09 UTC by Pavel Buzek
Modified: 2008-11-18 11:35 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Buzek 2003-03-24 15:09:50 UTC
This is motivated by use of looks in projects. I am not sure it all of it applies to looks in 
general.

Currently we can register looks for classes and for mime types. Some of the looks for 
visualization of project do not represent any real objects, they visualize "virtual" 
objects and do not need any data (they get the data from elsewhere in the project). 
Examples of these are Sources, Resources, Output in the projects infrastructure. Other 
examples need to be created in web module or j2ee modules (Document Base, Web 
Components, EJBs, etc.). It is now necessary to define empty marker classes to which 
the looks are then registered.
I propose to define a new look selector that would allow to define looks for instances of 
a given class (e.g. java.lang.String or some marker class defined by looks module).
Comment 1 Petr Nejedly 2003-03-24 16:43:55 UTC
It will be useful also for categorization nodes (Fields, Methods, ...)
Comment 2 Jesse Glick 2003-03-31 15:38:35 UTC
Can easily be done by some external code, e.g. Projects API module,
without help from looks.jar. Define some marker class with a name
field and a simple factory, and register a metalook for this class.
Anyway you need to specify the child objects so you will need some
additional machinery for that. IMHO should not be in base Looks API,
though if it used consistently from many modules (not just
projects-api-based) and code sharing is desired it could be added to
some util module in the future.
Comment 3 Pavel Buzek 2003-04-01 09:45:07 UTC
Jesse, that's clearly a possibility. I discussed this with Hrebejk and he thought that this may use 
useful more generally. He is the owner of looks api so I will let him decide.
As for the child objects you are right -- I using the fact that projects module puts the Project instance 
into a lookup of substitute.

Comment 4 Petr Hrebejk 2003-05-06 14:50:37 UTC
Marking as low priority enhancement. Some kind of support might be 
added later, when we see that it is really necessary. For now it 
sould be enough to create some class representing a group. Which
will hold name of the group and some data from parent. (Holding
data from parent is usaually necessary anyway to be able to produce
child objects etc.) And create a subclass of NamespaceSelector whit
namesFor() method overriden to return the name of the group.

The code which follows demostrates this feature on parsed HAT heap.
The groups will represent Classes and Roots on heap. It is possible
to registrate looks for the groups using XML layer (folder:
Looks/hat/Groups). 

The LookSelector would look like:

public class GroupSelector extends NamespaceSelector {
   
    public static final LookSelector INSTANCE = new GroupSelector();
    
    private static final String PREFIX = "Looks/hat/Group/";
    
    /** Creates a new instance of HeapSelector */
    public GroupSelector() {
        super( PREFIX );
    }
    
    
    public Enumeration namesFor( Object representedObject ) {
        return new SingletonEnumeration(
((Group)representedObject).getName() );
    }
        
    
}


The Group class:

public class Group {
    
    public static final String ROOTS = "ROOTS";
    public static final String CLASSES = "CLASSES";
        
    private Snapshot snapshot;
    private String name;
    
    /** Creates a new instance of Group */
    private Group( String name, Snapshot snapshot ) {
        this.name = name;
        this.snapshot = snapshot;
    }
    
    // Creation methods
    
    public static Group getClasses( Snapshot snapshot ) {
        return new Group( CLASSES, snapshot );
    }
    
    public static Group getRoots( Snapshot snapshot ) {
        return new Group( ROOTS, snapshot );
    }
    
    // Properties
    
    public String getName() {
        return name;
    }
    
    public Snapshot getSnapshot() {
        return snapshot;
    }
    
}
Comment 5 Petr Hrebejk 2004-07-20 14:58:30 UTC
Changing target milestone on all Looks issues to future
Comment 6 Petr Hrebejk 2007-01-09 15:06:02 UTC
x


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo