[openroad-developer] Empire XML Support - Two reviewmeetingtimesscheduled on May 20th 2008

[Teresa L. King]

Hi Bodo,
 
Will all of the comments fromt he review mtg be summarized somewhere on
the wiki as a Discussion Page.  Useful for those of us who did not
attend last nights meeting.
 
Teresa

________________________________

From: openroad-developer-bounces at lists.ingres.com
[mailto:openroad-developer-bounces at lists.ingres.com] On Behalf Of Bodo
Bergmann
Sent: Tuesday, May 20, 2008 6:18 AM
To: Sean Thrower
Cc: Roger L. Whitcomb; Joseph C. Kronk;
openroad-developer at lists.ingres.com
Subject: RE: [openroad-developer] Empire XML Support - Two
reviewmeetingtimesscheduled on May 20th 2008



See my comments below. 

_____________________________________________ 
From:   Sean Thrower  
Sent:   Tuesday, May 20, 2008 12:43 PM 
To:     Bodo Bergmann 
Cc:     Joseph C. Kronk; Roger L. Whitcomb;
openroad-developer at lists.ingres.com 
Subject:        RE: [openroad-developer] Empire XML Support - Two review
meetingtimesscheduled on May 20th 2008 

Bodo, 

Commands and Interfaces definition looks generally fine to me (I' ll
email separately on the export file structure).  I have a few comments
and questions below.

Regards, 
Sean. 


... I guess it is time that application compile stopped updating the
alter dates :-( thus removing all meaning from the value

... I don't yet get what -appsource is for, but no doubt the last page
will reveal all.  Whatever it is, I would have thought it needed the
metadata?

[Bodo]  The -appsource is the command line equivalent for the
"appsourceonly" parameter of the "ExportApp" method. 
It allows you to export only the "empty shell" of an application (as the
*.dsc files we are using internally in Piccolo) .

You will need this to recreate an empty application with all the
application properties (starting component, icon, db, flags, included
apps) set.

This is especially important if you use component based export files,
e.g. if you want to manage your changes using an SCM (Piccolo,
Subversion, ...).

Currently an export of an application contains the properties AND all
components. 
That is, to recreate an application from the component based export
files, you would have to import the application export which includes
all (hundreds) components,

then delete all components within the application (as they might be
actually old/deleted) and then import the components from their export
files.

Having an application export file that doesn't contain the components
makes this much easier - just import it (so you have an empty
application, but all properties set),

and then import the components from their export files. 

Otherwise a few suggested corrections, mostly minor but misleading. 

General typos: 

	*	It says -a not -appsource in lots of places, and "m"
instead of "meta" somewhere 

	[Bodo]  Yeah I missed a few - have to work on this. 

2.7.1: 

	*	Expected result should be new metadata (see 2.8.1) not
unchanged metadata 

[Bodo]   You are right. 
2.5.1 and elsewhere: 

	*	possibly => potentially 

[Bodo]  OK, will change 
2.6.2 

	*	implies that all the parameters are obligatory, although
they aren't in 2.6.1 - is this the case? 

[Bodo]  No they are not - these are just usage scenarios that should
work. 
3.2.1 

	*	Any value in having XF_DEF as the default value, where
XF_DEF = XF_EXP at present, but may change to XF_XML in future? 

[Bodo]   Good idea - probably with the ability to "define" from the
outside (config file, environment variable or command line switch) what
XF_DEF should be.










-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ingres.com/pipermail/openroad-developer/attachments/20080520/359e2bf1/attachment-0001.html