Kelut logo

Login
 
   
Forums >> JVMS
Port Questions for Chuck
Posted: 03/26/2003 18:46
By: Ben Litchfield
 
We talked about having a repository of interfaces(pg D-33)
so the user did not have to keep typing in repids.  Should
this be stored in the project where each project you would
start with an empty repository or should this be stored in
the system and be available to all projects?

When adding a port and setting the interface for that port,
should the list of available interfaces be just the ones
that have been set for that component or all of them that
are available?  We realize that it will need to end up in
the list of interfaces in the end.  We were thinking that a
designer could add a port pick one of the available
interfaces and if it was not already in the interface list
then the system would add it.  Either way is fine for us, we
just thought by adding it for them it might be a little
easier.  What are your thoughts?

-Ben
Linn re. question set 2
Posted: 03/28/2003 10:35
By: clinn
 
Q: We talked about having a repository of interfaces(pg
D-33)
so the user did not have to keep typing in repids. 
Should
this be stored in the project where each project you
would
start with an empty repository or should this be stored
in
the system and be available to all projects?

A: I would keep your life simple and have your largest
universe be the project.  "System" would be an unnecessary
complication, although it has merit.  If you really wanted
to, you could allow them to be imported / exported into a
file so they could be entered in multiple projects, but this
is a low priority requirement.


Q: When adding a port and setting the interface for that
port,
should the list of available interfaces be just the
ones
that have been set for that component or all of them
that
are available?  We realize that it will need to end up
in
the list of interfaces in the end.  We were thinking that
a
designer could add a port pick one of the
available
interfaces and if it was not already in the interface
list
then the system would add it.  Either way is fine for us,
we
just thought by adding it for them it might be a
little
easier.  What are your thoughts?

A: I agree - have to tool construct the interfaces section
at the end, based on what ports and supportsinterfaces were
actually used by the component.  In this way, when you add a
port to the component, you are given the global list of
interfaces (or if the one you want is not present, the
opportunity to add one).  The port type is then set, and
hence when XML is generated the interface type is added to
the interfaces section for that component.