RE: Re: [Vcb-framework] new config suggestions

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

we need name (instance name), class name and config name but in different
contexts. so in your example instead of:

<device name="controller" sourcename="controller.xml"  >

....
<part id="2" type="part" name="DefaultFilter" source="pageDefaultFilter.xml"
/>
<part id="3" type="part" name="ProductsFilter"
source="pageProductsFilter.xml" />

...

will be:

controller.vcb:

<device name="controller">

....
<part id="2" type="part" name="Filter 1"
source="vcb.org.filters.pageDefaultFilter" />
<part id="3" type="part" name="Filter 2"
source="vcb.org.filters.pageDefaultFilter" /> (note: I made both the same
part)

...

Part pageDefaultFilter.vcb file will be under vcb/org/filters to be found by
standard classloader

in the vcb file it will be something like:

<part name="DefaultFilter" class="vcb.org.filters.DefaultFilterImpl"> (note:
part name and class name are different)

...

THoughts?

H.

-----Original Message-----
From: Mehrabyan, Artavazd, Lycos Armenia 
Sent: Saturday, December 27, 2003 4:33 PM
To: 'vcb...@li...'
Cc: Avoyan, Hovhannes, Lycos Armenia
Subject: Re: [Vcb-framework] new config suggestions

We really don't need sourcename in root tag of device and part configuration
files

<device name="diagramEditor" sourcename="graphEditor.xml"  > 

as far as it is replication of information (actually instead of sourcename
"real filename" is used, which is = sourcename) 

Fully qualified names are good for structuring part's configuration file
with its binary back end and sometimes with the resources 

We can require to use the same class path and name for part configuration
and its binary back end

but we need both name and classname in the part configuration, because in
device configuration we can have several like instances of the same part:

for example

in controller device we may use several filters.

<device name="controller" sourcename="controller.xml"  >

....
<part id="2" type="part" name="DefaultFilter" source="pageDefaultFilter.xml"
/>
<part id="3" type="part" name="ProductsFilter"
source="pageProductsFilter.xml" />

...

<link ...

then in the configuation we should have unique names for filters (like names
of instances of the same class in the single java class) to be able to
differentiate them,

because we should set different filtering criteria, 

and we should consider that in current implementation of framework it  uses
embeding of parts in the device so even files should have unique names
describing the same filter part. (in future there will be option to link
part from part library and to embed one to developing configuration.

and we do not need name in device configuration for child parts and devices

for example for 

<device name="controller" sourcename="controller.xml"  >

<part id="2" type="part" name="DefaultFilter" source="pageDefaultFilter.xml"
/>
...

we can have 

<device name="controller" sourcename="controller.xml"  >

<part id="2" type="part" source="pageDefaultFilter.xml" />
...

without name because it is not used when reading configuration (or it can be
used as a name and name can be removed from the configuration root tag?)

Arto

The framework will look under classpath org/vcb/diagramEditor.vcb
> with standard extention .vcb
> 
> To read the file we will use ClassLoader.getResource

----- Original Message ----- 

From: < Hov...@ly...
<mailto:Hov...@ly...> >

To: < Vcb...@li...
<mailto:Vcb...@li...> >

Sent: Thursday, December 25, 2003 12:05 PM

Subject: [Vcb-framework] new config suggestions

> Here are my suggestions to simplify the config and make it more
> precise:
> 
> in part and device tags e.g.:
> 
> --------------
> <device name="diagramEditor" sourcename="graphEditor.xml"  >
> 
> <terminals>
> 
> </terminals>
> 
> <part id="1" type="part" name="pGraphEditorUI"
> source="pGraphEditorUI.xml"/>
> <part id="2" type="part" name="pToolBarUI" source="pToolBarUI.xml"/>
> <part id="3" type="part" name="VCBProxy" source="pNetBeansUI.xml"/>
> -----------------
> 
> 
> I am suggesting to remove sourcename, and as name use fully
> qualified name:
> 
> <device name="org.vcb.diagramEditor" >
> 
> <terminals>
> 
> </terminals>
> 
> <part id="1" type="part" name="org.vcb.pGraphEditorUI"/>
> <part id="2" type="part" name="org.vcb.pToolBarUI""/>
> ...
> 
> ----------------------
> 
> The framework will look under classpath org/vcb/diagramEditor.vcb
> with standard extention .vcb
> 
> To read the file we will use ClassLoader.getResource
> 
> On diagrams we will still use short names although with possibility
> to use full names. 
> 
> in part config files:
> 
> <part name="VCBProxy" type="SYSTEM_VIEW"
> classname="org.vcb.parts.view.VCBProxy" sourcename="pNetBeansUI.xml" >
> 
> we can have 
> 
> <part  name="org.vcb.parts.view.VCBProxy" type="SYSTEM_VIEW" >
> 
> when classname skipped then it use the same path to get both class
> and vcb files. Although if they are different then classname can be used:
> 
> <part name="org.vcb.VCBProxy" type="SYSTEM_VIEW"
> classname="org.vcb.parts.view.VCBProxy" >
> 
> Best
> Hovhannes
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278
<http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click>
&alloc_id=3371&op=click
> _______________________________________________
> Vcb-framework mailing list
> Vcb...@li...
<mailto:Vcb...@li...> 
> https://lists.sourceforge.net/lists/listinfo/vcb-framework
<https://lists.sourceforge.net/lists/listinfo/vcb-framework> 
>