Re: [Uml-devel] Methods/attributes hiding...

You are right. That's a quick way useful in many situations.

It is important to tie such a feature to the class representation, 
and not to the class itself!

Anyway specifying the single methods/attributes would be better. 

Infact in some diagrams the interface is the intersting part, 
in others the focus has to be on the kernel of the class.

Pietro Mele


--- Jonathan Riddell <[email protected]> wrote:
> On Tue, Mar 30, 2004 at 03:46:42AM -0800, Pietro Mele wrote:
> > A suggestion about methods and attributes:
> > a class can have many of them, and they don't have all the same
> > importance. It should be possible to make just some of them
> visible.
> > 
> > It is useful for the following reasons:
> > 
> > - You can import a cass from the source code, but you may want to 
> >   view just part of it (e.g. the most important part).
> > 
> > - You can use the same class in different diagrams, and in 
> >   each diagram you may want to show different details.
> > 
> > - Other programs already do it.
> > 
> > It should not be a hard task: just add a flag to each
> attribute/method
> > for each diagram.
> 
> One feature I'd like is 
> 
> http://bugs.kde.org/show_bug.cgi?id=76209
> 
> Ability to show only public elements
> 
> I think that takes care of 90% of cases where you want to show only
> some methods/attributes.
> 
> Sorry for the delayed reply.
> 
> Jonathan Riddell



	
		
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click