foa-devel — FOA Developers Mailing List

[Foa-devel] Hello

[John <jo...@jm...>]

Hello, I'm new to FOA.  I think it's very exciting to create PDF
documents from XML content, but how can somebody create that
XSLT coding without going crazy?!  FOA seems like a great tool
to solve that problem.

I posted to the FOA Developers forum, but I guess nobody uses
that forum.  Is this list where everybody hangs out???

I hope I can be some help to the team.

John

[Foa-devel] bank example - please help!

[<sun...@gm...>]

hi!

i'm trying to get foa to work with the simple bank example but command
GENERATE FO brings the following error:

error executing c:\...xt.bat;c:\foa...letter.xml......MyBank.fo

i've checked each path.. everything seams ok...

does anyone have an idea what i did wrong or is there a step by step
tutorial for dummies?

thanx a lot

jim

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

[Foa-devel] FW: region-name

[Giannetti, F. <Fab...@hp...>]

> -----Original Message-----
> From: Giannetti, Fabio 
> Sent: 22 March 2002 10:07
> To: 'Vaidya, Raghavendra (CORP, GEITC)'
> Subject: RE: region-name
> 
> 
> > I got the flow now.I have a question : How is FOA build done? 
> > Is there a ant
> > script or something like that?
> 
> Good new !!! For the script unfortunately I don't have any 
> script, I use JBuilder but if you think want to add a builder 
> like ant it will be great.
> 
> > Now that UI portion is done how do we commit the changes? and 
> > what are the
> > other things to be done?
> 
> OK, you must commit the changes using CVS inside the CVS tree 
> in Sourceforge, you can find the application and a book on 
> the net. If you need further help, let me know ... but I'm 
> not a CVS guru :-))
> The others thing to do are:
> modify the code in order to be able to parse the new version 
> and load the region-name
> modify the content sequence manager to show all the regions 
> for each page sequence. In the previous version for each page 
> sequence you have a representation of all the possible regions, e.g.
> 
> Sequence with first and repeated:
> First: header, body, start
> Repeated: header, body, footer
> => in the content sequence: header, start, body, footer
> 
> Now, because the headers could be different you can have the situation
> 
> Sequence with first and repeated:
> First: header(region-name="head1"), body, start
> Repeated: header(region-name="head2"), body, footer
> => in the content sequence: header(region-name="head1"), 
> header(region-name="head2"), start, body, footer
> 
> Fabio
> 
> PS: in the week-end I will add tables with header and footer 
> (complex tables) ... and I have to think how to generate 
> page-numbers ... I'd like to have a new set of Bricks that 
> generate static content (without a match) so new FOA will 
> have dynamic bricks and static bricks ...
> 
> > Regards
> > Vaidya
> > 
> > 
> > -----Original Message-----
> > From: Giannetti, Fabio [mailto:Fab...@hp...]
> > Sent: Tuesday, March 19, 2002 10:39 PM
> > To: foa...@so...
> > Cc: 'Vaidya, Raghavendra (CORP, GEITC)'
> > Subject: region-name
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Vaidya, Raghavendra (CORP, GEITC)
> > > [mailto:Rag...@ge...]
> > > Sent: 19 March 2002 05:31
> > > To: foa...@so...
> > > Subject: RE: [Foa-devel] RE: FOA development: getting serious ..
> > > 
> > > 
> > > Fabio,
> > > I did some initial analysis on this problem.Here is my 
> > > understanding.Correct
> > > me if I am wrong
> > > We need to be able to give the user the facility to name the 
> > > static elements
> > > like region-before etc.
> > 
> > That's exactly what we need ...
> > 
> > > right now the addRegion takes a string and a HashTable to add 
> > > the static
> > > element and this cascades to Element class thro' inheritence 
> > > hierarchy.So my
> > > understanding is that we need to add the name qualifier to 
> > > the hashtable as
> > > a first step.
> > 
> > No really ... from the method newRegion in the LayoutDirector 
> > you have this
> > code:
> > 
> > if (isAValidRegion) {
> >    if (currentRegion.equals("Body")) {
> >       regionDialog = new 
> > RegionDialog((Container)pageManager.getPageFrame(),
> > new Body(new Hashtable()), this);
> >    }
> >    else {
> >       regionDialog = new 
> > RegionDialog((Container)pageManager.getPageFrame(),
> > new Region(new Hashtable()), this);
> >    }
> > }
> > 
> > so from the regionDialog you will insert the params. If you 
> > look the the
> > group information (from the pachage properties/group you will 
> > discover that
> > each property group represent a tab pane. Each tab pane has a 
> > property set
> > that define which properties you want to change and inside 
> > each set you get
> > the type. So if you add inside the extent group a set with 
> > the region-name
> > (type StringOptionType) you will see the changes inside the 
> > user interface.
> > I made this in the attached new sources, so you could better 
> > understand how
> > does it works.
> > 
> > > I am not able to trace the code back to the UI part and am 
> > > not able to trace
> > 
> > see the previous explanation :-))
> > 
> > > the code which actually writes the XSLT file
> > > I need following information to complete the task.
> > > 1. Where does the Hashtable - attributes get generated?
> > > 2. HOw is the XSLT file written?
> > 
> > The XSL-T is written by the apps.XSLTWriter and it calls all 
> > the various
> > Directors responsible for their bit, so for the pagination the
> > LayoutDirector will be responsible. The layout director will 
> > call the pages
> > method to write the XSL and the pages (SimplePageMaster) 
> will call the
> > relative regions to write the XSL. SO if you add the 
> > region-name attribute
> > in the Region object (as made before) it will automatically 
> > added to the
> > sequence of available properties and will put in the open tag.
> > See the attached code and let me know if is clearer now ....
> > 
> > 							Fabio
> > 
> > > If you could get me started on this I will take it forward 
> > from there
> > > regards
> > > Vaidya
> > > 
> > > -----Original Message-----
> > > From: Giannetti, Fabio [mailto:Fab...@hp...]
> > > Sent: Monday, March 18, 2002 3:11 PM
> > > To: 'Vaidya, Raghavendra (CORP, GEITC)'
> > > Cc: 'foa...@so...'
> > > Subject: [Foa-devel] RE: FOA development: getting serious ..
> > > 
> > > 
> > > Hi Vaidya,
> > > 	I was thinking that could be a good starting point to work with
> > > pagination to add the possibility to have different 
> > > headers/footers on the
> > > sequence. In order to do this we need to change the 
> > > pagination creation
> > > adding the support for naming the static regions, such as 
> > > start, end, before
> > > and after and then change in the content sequence master give the
> > > possibility to add content to all the available regions 
> > > inside the sequence.
> > > I'm modifying WH2FO to support headers and footers, so I have 
> > > already an XSL
> > > representation of the new model, this could be a good 
> > > starting point to see
> > > how to implement it under FOA.
> > > This is an example :
> > > <fo:simple-page-master page-width="595pt" page-height="841pt"
> > > master-name="first">
> > >           <fo:region-before extent="67pt"
> > > region-name="fh1"></fo:region-before>
> > >           <fo:region-after extent="54pt"
> > > region-name="ff1"></fo:region-after>
> > >           <fo:region-body margin-top="67pt" margin-bottom="54pt"
> > > ></fo:region-body>
> > >         </fo:simple-page-master>
> > >         <fo:simple-page-master page-width="595pt" 
> > page-height="841pt"
> > > master-name="even">
> > >           <fo:region-before extent="67pt"
> > > region-name="eh1"></fo:region-before>
> > >           <fo:region-after extent="54pt"
> > > region-name="ef1"></fo:region-after>
> > >           <fo:region-body margin-top="67pt" margin-bottom="54pt"
> > > ></fo:region-body>
> > >         </fo:simple-page-master>
> > >         <fo:simple-page-master page-width="595pt" 
> > page-height="841pt"
> > > master-name="odd">
> > >           <fo:region-before extent="67pt"
> > > region-name="h1"></fo:region-before>
> > >           <fo:region-after extent="54pt" 
> > > region-name="f1"></fo:region-after>
> > >           <fo:region-body margin-top="67pt" margin-bottom="54pt"
> > > ></fo:region-body>
> > >         </fo:simple-page-master>
> > >         <fo:page-sequence-master master-name="page-seq">
> > >           <fo:repeatable-page-master-alternatives>
> > >             <fo:conditional-page-master-reference 
> > master-name="first"
> > > page-position="first"></fo:conditional-page-master-reference>
> > >             <fo:conditional-page-master-reference 
> master-name="even"
> > > odd-or-even="even"></fo:conditional-page-master-reference>
> > >             <fo:conditional-page-master-reference 
> master-name="odd"
> > > odd-or-even="odd"></fo:conditional-page-master-reference>
> > >           </fo:repeatable-page-master-alternatives>
> > >         </fo:page-sequence-master>
> > >       </fo:layout-master-set>
> > > 
> > > So, now the big difference is that the region-before and 
> > > region-after for
> > > each page will produce in the page sequence (called Content 
> > > Sequence in
> > > FOA):
> > > 
> > > <fo:page-sequence master-name="page-seq">
> > >         <fo:static-content flow-name="eh1">
> > >         </fo:static-content>
> > >         <fo:static-content flow-name="h1">
> > >         </fo:static-content>
> > >         <fo:static-content flow-name="ef1">
> > >         </fo:static-content>
> > >         <fo:static-content flow-name="f1">
> > >         </fo:static-content>
> > >         <fo:static-content flow-name="fh1">
> > >         </fo:static-content>
> > >         <fo:static-content flow-name="ff1">
> > >         </fo:static-content>
> > >         <fo:static-content
> > > flow-name="xsl-region-before"></fo:static-content>
> > >         <fo:static-content 
> > > flow-name="xsl-region-after"></fo:static-content>
> > >         <fo:flow flow-name="xsl-region-body">
> > >         </fo:flow>
> > >       </fo:page-sequence>
> > > 
> > > all these extra static content element with the appropriate 
> > > flow-name, as
> > > well as the standard ones if the region name has not been 
> > > specified ....
> > > Because the Page Sequence Manager and the Content Sequence 
> > Manager are
> > > strictly related I suggest you to start to implement name 
> > > supporting for
> > > static areas inside the Page Manager and then we can start to 
> > > think about
> > > the Page Sequence and Content Sequence, because I'm already 
> > > working with the
> > > second to correct some bugs. I also like to insert some 
> > > support for the page
> > > number, we can come out with a new Brick that use a match, 
> > just at the
> > > beginning (already present in WH2FO 0.3.0) and then introduce the
> > > possibility to add content without the matching (a sort of 
> > > static FO inside
> > > the XSL-T ...), but this will complicate the stuff a lot and 
> > > I think we can
> > > put it into the 0.4.0 release :-))
> > > Ok, good work and don't hesitate to ask me all the problems 
> > > or clarification
> > > that you could need.
> > > 
> > > 				Fabio
> > > 
> > > PS: if you are not subsribed to the dev mailing list, please 
> > > do that so our
> > > mails could be read also by Kenneth and all the developers 
> > > could know about
> > > the development and the current situation.
> > > 
> > > > -----Original Message-----
> > > > From: Vaidya, Raghavendra (CORP, GEITC)
> > > > [mailto:Rag...@ge...]
> > > > Sent: 17 March 2002 06:39
> > > > To: Giannetti, Fabio
> > > > Subject: RE: FOA development: getting serious ..
> > > > 
> > > > 
> > > > Fabio,
> > > > I understand your concern.
> > > > Please assign some features / bugs to me so that I can start 
> > > > off.I can spare
> > > > some time for this activity
> > > > Regards
> > > > Vaidya
> > > > 
> > > > -----Original Message-----
> > > > From: Giannetti, Fabio [mailto:Fab...@hp...]
> > > > Sent: Friday, March 15, 2002 10:46 PM
> > > > To: 'foa...@so...'
> > > > Cc: 'Ken...@sp...';
> > > > 'Rag...@ge...'
> > > > Subject: FOA development: getting serious ..
> > > > 
> > > > 
> > > > Hi guys,
> > > > 	I think we have got (and have) plenty to do with our 
> > > > jobs, but I'm
> > > > seeing, from bugs and feature requests, that people is asking 
> > > > for a new
> > > > release with some new features. I'd like to now your personal 
> > > > status in
> > > > order to seriously plan the development for the next month 
> > > > (if you are too
> > > > busy just let me know and I will put you into a temporary 
> > > > inactive status
> > > > ...) otherwise if you have seen my proposal and you like it 
> > > > we can proceed
> > > > setting down a timescale.
> > > > I'm, in parallel, developing WH2FO (0.3.0) and I have 
> > > > introduced parsing of
> > > > multiple headers/footers with page numbers (created from a 
> > > > special XML tag)
> > > > and I wish to update both WH2FO and FOA from the CR 
> support to the
> > > > Recommendation support, that basically means to change 
> > > > master-name into
> > > > master-reference, but also involve to change the current 
> > > > customized FOP
> > > > version or re-customize the latest version .....
> > > > 
> > > > 							Fabio
> > > > 
> > > > 
> > > > "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> > > > ONLY FOR THE
> > > > ADDRESSEE and may contain confidential and privileged 
> information.
> > > > If the reader of this message is not the intended recipient,
> > > > you are notified that any dissemination, distribution or 
> > > copy of this 
> > > > communication is strictly Prohibited. 
> > > > If you have received this message by error, please notify us 
> > > > immediately, return the original mail to the sender and 
> > delete the 
> > > > message from your system."
> > > > 
> > > 
> > > 
> > > 
> > > "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> > > ONLY FOR THE
> > > ADDRESSEE and may contain confidential and privileged information.
> > > If the reader of this message is not the intended recipient,
> > > you are notified that any dissemination, distribution or 
> > copy of this 
> > > communication is strictly Prohibited. 
> > > If you have received this message by error, please notify us 
> > > immediately, return the original mail to the sender and 
> delete the 
> > > message from your system."
> > > 
> > > 
> > > _______________________________________________
> > > Foa-devel mailing list
> > > Foa...@li...
> > > https://lists.sourceforge.net/lists/listinfo/foa-devel
> > > 
> > 
> > 
> > 
> > "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> > ONLY FOR THE
> > ADDRESSEE and may contain confidential and privileged information.
> > If the reader of this message is not the intended recipient,
> > you are notified that any dissemination, distribution or 
> copy of this 
> > communication is strictly Prohibited. 
> > If you have received this message by error, please notify us 
> > immediately, return the original mail to the sender and delete the 
> > message from your system."
> > 
> 

[Foa-devel] region-name

[Giannetti, F. <Fab...@hp...>]

> -----Original Message-----
> From: Vaidya, Raghavendra (CORP, GEITC)
> [mailto:Rag...@ge...]
> Sent: 19 March 2002 05:31
> To: foa...@so...
> Subject: RE: [Foa-devel] RE: FOA development: getting serious ..
> 
> 
> Fabio,
> I did some initial analysis on this problem.Here is my 
> understanding.Correct
> me if I am wrong
> We need to be able to give the user the facility to name the 
> static elements
> like region-before etc.

That's exactly what we need ...

> right now the addRegion takes a string and a HashTable to add 
> the static
> element and this cascades to Element class thro' inheritence 
> hierarchy.So my
> understanding is that we need to add the name qualifier to 
> the hashtable as
> a first step.

No really ... from the method newRegion in the LayoutDirector you have this
code:

if (isAValidRegion) {
   if (currentRegion.equals("Body")) {
      regionDialog = new RegionDialog((Container)pageManager.getPageFrame(),
new Body(new Hashtable()), this);
   }
   else {
      regionDialog = new RegionDialog((Container)pageManager.getPageFrame(),
new Region(new Hashtable()), this);
   }
}

so from the regionDialog you will insert the params. If you look the the
group information (from the pachage properties/group you will discover that
each property group represent a tab pane. Each tab pane has a property set
that define which properties you want to change and inside each set you get
the type. So if you add inside the extent group a set with the region-name
(type StringOptionType) you will see the changes inside the user interface.
I made this in the attached new sources, so you could better understand how
does it works.

> I am not able to trace the code back to the UI part and am 
> not able to trace

see the previous explanation :-))

> the code which actually writes the XSLT file
> I need following information to complete the task.
> 1. Where does the Hashtable - attributes get generated?
> 2. HOw is the XSLT file written?

The XSL-T is written by the apps.XSLTWriter and it calls all the various
Directors responsible for their bit, so for the pagination the
LayoutDirector will be responsible. The layout director will call the pages
method to write the XSL and the pages (SimplePageMaster) will call the
relative regions to write the XSL. SO if you add the region-name attribute
in the Region object (as made before) it will automatically added to the
sequence of available properties and will put in the open tag.
See the attached code and let me know if is clearer now ....

							Fabio

> If you could get me started on this I will take it forward from there
> regards
> Vaidya
> 
> -----Original Message-----
> From: Giannetti, Fabio [mailto:Fab...@hp...]
> Sent: Monday, March 18, 2002 3:11 PM
> To: 'Vaidya, Raghavendra (CORP, GEITC)'
> Cc: 'foa...@so...'
> Subject: [Foa-devel] RE: FOA development: getting serious ..
> 
> 
> Hi Vaidya,
> 	I was thinking that could be a good starting point to work with
> pagination to add the possibility to have different 
> headers/footers on the
> sequence. In order to do this we need to change the 
> pagination creation
> adding the support for naming the static regions, such as 
> start, end, before
> and after and then change in the content sequence master give the
> possibility to add content to all the available regions 
> inside the sequence.
> I'm modifying WH2FO to support headers and footers, so I have 
> already an XSL
> representation of the new model, this could be a good 
> starting point to see
> how to implement it under FOA.
> This is an example :
> <fo:simple-page-master page-width="595pt" page-height="841pt"
> master-name="first">
>           <fo:region-before extent="67pt"
> region-name="fh1"></fo:region-before>
>           <fo:region-after extent="54pt"
> region-name="ff1"></fo:region-after>
>           <fo:region-body margin-top="67pt" margin-bottom="54pt"
> ></fo:region-body>
>         </fo:simple-page-master>
>         <fo:simple-page-master page-width="595pt" page-height="841pt"
> master-name="even">
>           <fo:region-before extent="67pt"
> region-name="eh1"></fo:region-before>
>           <fo:region-after extent="54pt"
> region-name="ef1"></fo:region-after>
>           <fo:region-body margin-top="67pt" margin-bottom="54pt"
> ></fo:region-body>
>         </fo:simple-page-master>
>         <fo:simple-page-master page-width="595pt" page-height="841pt"
> master-name="odd">
>           <fo:region-before extent="67pt"
> region-name="h1"></fo:region-before>
>           <fo:region-after extent="54pt" 
> region-name="f1"></fo:region-after>
>           <fo:region-body margin-top="67pt" margin-bottom="54pt"
> ></fo:region-body>
>         </fo:simple-page-master>
>         <fo:page-sequence-master master-name="page-seq">
>           <fo:repeatable-page-master-alternatives>
>             <fo:conditional-page-master-reference master-name="first"
> page-position="first"></fo:conditional-page-master-reference>
>             <fo:conditional-page-master-reference master-name="even"
> odd-or-even="even"></fo:conditional-page-master-reference>
>             <fo:conditional-page-master-reference master-name="odd"
> odd-or-even="odd"></fo:conditional-page-master-reference>
>           </fo:repeatable-page-master-alternatives>
>         </fo:page-sequence-master>
>       </fo:layout-master-set>
> 
> So, now the big difference is that the region-before and 
> region-after for
> each page will produce in the page sequence (called Content 
> Sequence in
> FOA):
> 
> <fo:page-sequence master-name="page-seq">
>         <fo:static-content flow-name="eh1">
>         </fo:static-content>
>         <fo:static-content flow-name="h1">
>         </fo:static-content>
>         <fo:static-content flow-name="ef1">
>         </fo:static-content>
>         <fo:static-content flow-name="f1">
>         </fo:static-content>
>         <fo:static-content flow-name="fh1">
>         </fo:static-content>
>         <fo:static-content flow-name="ff1">
>         </fo:static-content>
>         <fo:static-content
> flow-name="xsl-region-before"></fo:static-content>
>         <fo:static-content 
> flow-name="xsl-region-after"></fo:static-content>
>         <fo:flow flow-name="xsl-region-body">
>         </fo:flow>
>       </fo:page-sequence>
> 
> all these extra static content element with the appropriate 
> flow-name, as
> well as the standard ones if the region name has not been 
> specified ....
> Because the Page Sequence Manager and the Content Sequence Manager are
> strictly related I suggest you to start to implement name 
> supporting for
> static areas inside the Page Manager and then we can start to 
> think about
> the Page Sequence and Content Sequence, because I'm already 
> working with the
> second to correct some bugs. I also like to insert some 
> support for the page
> number, we can come out with a new Brick that use a match, just at the
> beginning (already present in WH2FO 0.3.0) and then introduce the
> possibility to add content without the matching (a sort of 
> static FO inside
> the XSL-T ...), but this will complicate the stuff a lot and 
> I think we can
> put it into the 0.4.0 release :-))
> Ok, good work and don't hesitate to ask me all the problems 
> or clarification
> that you could need.
> 
> 				Fabio
> 
> PS: if you are not subsribed to the dev mailing list, please 
> do that so our
> mails could be read also by Kenneth and all the developers 
> could know about
> the development and the current situation.
> 
> > -----Original Message-----
> > From: Vaidya, Raghavendra (CORP, GEITC)
> > [mailto:Rag...@ge...]
> > Sent: 17 March 2002 06:39
> > To: Giannetti, Fabio
> > Subject: RE: FOA development: getting serious ..
> > 
> > 
> > Fabio,
> > I understand your concern.
> > Please assign some features / bugs to me so that I can start 
> > off.I can spare
> > some time for this activity
> > Regards
> > Vaidya
> > 
> > -----Original Message-----
> > From: Giannetti, Fabio [mailto:Fab...@hp...]
> > Sent: Friday, March 15, 2002 10:46 PM
> > To: 'foa...@so...'
> > Cc: 'Ken...@sp...';
> > 'Rag...@ge...'
> > Subject: FOA development: getting serious ..
> > 
> > 
> > Hi guys,
> > 	I think we have got (and have) plenty to do with our 
> > jobs, but I'm
> > seeing, from bugs and feature requests, that people is asking 
> > for a new
> > release with some new features. I'd like to now your personal 
> > status in
> > order to seriously plan the development for the next month 
> > (if you are too
> > busy just let me know and I will put you into a temporary 
> > inactive status
> > ...) otherwise if you have seen my proposal and you like it 
> > we can proceed
> > setting down a timescale.
> > I'm, in parallel, developing WH2FO (0.3.0) and I have 
> > introduced parsing of
> > multiple headers/footers with page numbers (created from a 
> > special XML tag)
> > and I wish to update both WH2FO and FOA from the CR support to the
> > Recommendation support, that basically means to change 
> > master-name into
> > master-reference, but also involve to change the current 
> > customized FOP
> > version or re-customize the latest version .....
> > 
> > 							Fabio
> > 
> > 
> > "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> > ONLY FOR THE
> > ADDRESSEE and may contain confidential and privileged information.
> > If the reader of this message is not the intended recipient,
> > you are notified that any dissemination, distribution or 
> copy of this 
> > communication is strictly Prohibited. 
> > If you have received this message by error, please notify us 
> > immediately, return the original mail to the sender and delete the 
> > message from your system."
> > 
> 
> 
> 
> "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> ONLY FOR THE
> ADDRESSEE and may contain confidential and privileged information.
> If the reader of this message is not the intended recipient,
> you are notified that any dissemination, distribution or copy of this 
> communication is strictly Prohibited. 
> If you have received this message by error, please notify us 
> immediately, return the original mail to the sender and delete the 
> message from your system."
> 
> 
> _______________________________________________
> Foa-devel mailing list
> Foa...@li...
> https://lists.sourceforge.net/lists/listinfo/foa-devel
> 

RE: [Foa-devel] RE: FOA development: getting serious ..

[Vaidya, R. (C. GEITC) <Rag...@ge...>]

Fabio,
I did some initial analysis on this problem.Here is my understanding.Correct
me if I am wrong
We need to be able to give the user the facility to name the static elements
like region-before etc.
right now the addRegion takes a string and a HashTable to add the static
element and this cascades to Element class thro' inheritence hierarchy.So my
understanding is that we need to add the name qualifier to the hashtable as
a first step.
I am not able to trace the code back to the UI part and am not able to trace
the code which actually writes the XSLT file
I need following information to complete the task.
1. Where does the Hashtable - attributes get generated?
2. HOw is the XSLT file written?
If you could get me started on this I will take it forward from there
regards
Vaidya

-----Original Message-----
From: Giannetti, Fabio [mailto:Fab...@hp...]
Sent: Monday, March 18, 2002 3:11 PM
To: 'Vaidya, Raghavendra (CORP, GEITC)'
Cc: 'foa...@so...'
Subject: [Foa-devel] RE: FOA development: getting serious ..


Hi Vaidya,
	I was thinking that could be a good starting point to work with
pagination to add the possibility to have different headers/footers on the
sequence. In order to do this we need to change the pagination creation
adding the support for naming the static regions, such as start, end, before
and after and then change in the content sequence master give the
possibility to add content to all the available regions inside the sequence.
I'm modifying WH2FO to support headers and footers, so I have already an XSL
representation of the new model, this could be a good starting point to see
how to implement it under FOA.
This is an example :
<fo:simple-page-master page-width="595pt" page-height="841pt"
master-name="first">
          <fo:region-before extent="67pt"
region-name="fh1"></fo:region-before>
          <fo:region-after extent="54pt"
region-name="ff1"></fo:region-after>
          <fo:region-body margin-top="67pt" margin-bottom="54pt"
></fo:region-body>
        </fo:simple-page-master>
        <fo:simple-page-master page-width="595pt" page-height="841pt"
master-name="even">
          <fo:region-before extent="67pt"
region-name="eh1"></fo:region-before>
          <fo:region-after extent="54pt"
region-name="ef1"></fo:region-after>
          <fo:region-body margin-top="67pt" margin-bottom="54pt"
></fo:region-body>
        </fo:simple-page-master>
        <fo:simple-page-master page-width="595pt" page-height="841pt"
master-name="odd">
          <fo:region-before extent="67pt"
region-name="h1"></fo:region-before>
          <fo:region-after extent="54pt" region-name="f1"></fo:region-after>
          <fo:region-body margin-top="67pt" margin-bottom="54pt"
></fo:region-body>
        </fo:simple-page-master>
        <fo:page-sequence-master master-name="page-seq">
          <fo:repeatable-page-master-alternatives>
            <fo:conditional-page-master-reference master-name="first"
page-position="first"></fo:conditional-page-master-reference>
            <fo:conditional-page-master-reference master-name="even"
odd-or-even="even"></fo:conditional-page-master-reference>
            <fo:conditional-page-master-reference master-name="odd"
odd-or-even="odd"></fo:conditional-page-master-reference>
          </fo:repeatable-page-master-alternatives>
        </fo:page-sequence-master>
      </fo:layout-master-set>

So, now the big difference is that the region-before and region-after for
each page will produce in the page sequence (called Content Sequence in
FOA):

<fo:page-sequence master-name="page-seq">
        <fo:static-content flow-name="eh1">
        </fo:static-content>
        <fo:static-content flow-name="h1">
        </fo:static-content>
        <fo:static-content flow-name="ef1">
        </fo:static-content>
        <fo:static-content flow-name="f1">
        </fo:static-content>
        <fo:static-content flow-name="fh1">
        </fo:static-content>
        <fo:static-content flow-name="ff1">
        </fo:static-content>
        <fo:static-content
flow-name="xsl-region-before"></fo:static-content>
        <fo:static-content flow-name="xsl-region-after"></fo:static-content>
        <fo:flow flow-name="xsl-region-body">
        </fo:flow>
      </fo:page-sequence>

all these extra static content element with the appropriate flow-name, as
well as the standard ones if the region name has not been specified ....
Because the Page Sequence Manager and the Content Sequence Manager are
strictly related I suggest you to start to implement name supporting for
static areas inside the Page Manager and then we can start to think about
the Page Sequence and Content Sequence, because I'm already working with the
second to correct some bugs. I also like to insert some support for the page
number, we can come out with a new Brick that use a match, just at the
beginning (already present in WH2FO 0.3.0) and then introduce the
possibility to add content without the matching (a sort of static FO inside
the XSL-T ...), but this will complicate the stuff a lot and I think we can
put it into the 0.4.0 release :-))
Ok, good work and don't hesitate to ask me all the problems or clarification
that you could need.

				Fabio

PS: if you are not subsribed to the dev mailing list, please do that so our
mails could be read also by Kenneth and all the developers could know about
the development and the current situation.

> -----Original Message-----
> From: Vaidya, Raghavendra (CORP, GEITC)
> [mailto:Rag...@ge...]
> Sent: 17 March 2002 06:39
> To: Giannetti, Fabio
> Subject: RE: FOA development: getting serious ..
> 
> 
> Fabio,
> I understand your concern.
> Please assign some features / bugs to me so that I can start 
> off.I can spare
> some time for this activity
> Regards
> Vaidya
> 
> -----Original Message-----
> From: Giannetti, Fabio [mailto:Fab...@hp...]
> Sent: Friday, March 15, 2002 10:46 PM
> To: 'foa...@so...'
> Cc: 'Ken...@sp...';
> 'Rag...@ge...'
> Subject: FOA development: getting serious ..
> 
> 
> Hi guys,
> 	I think we have got (and have) plenty to do with our 
> jobs, but I'm
> seeing, from bugs and feature requests, that people is asking 
> for a new
> release with some new features. I'd like to now your personal 
> status in
> order to seriously plan the development for the next month 
> (if you are too
> busy just let me know and I will put you into a temporary 
> inactive status
> ...) otherwise if you have seen my proposal and you like it 
> we can proceed
> setting down a timescale.
> I'm, in parallel, developing WH2FO (0.3.0) and I have 
> introduced parsing of
> multiple headers/footers with page numbers (created from a 
> special XML tag)
> and I wish to update both WH2FO and FOA from the CR support to the
> Recommendation support, that basically means to change 
> master-name into
> master-reference, but also involve to change the current 
> customized FOP
> version or re-customize the latest version .....
> 
> 							Fabio
> 
> 
> "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> ONLY FOR THE
> ADDRESSEE and may contain confidential and privileged information.
> If the reader of this message is not the intended recipient,
> you are notified that any dissemination, distribution or copy of this 
> communication is strictly Prohibited. 
> If you have received this message by error, please notify us 
> immediately, return the original mail to the sender and delete the 
> message from your system."
> 



"THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED ONLY FOR THE
ADDRESSEE and may contain confidential and privileged information.
If the reader of this message is not the intended recipient,
you are notified that any dissemination, distribution or copy of this 
communication is strictly Prohibited. 
If you have received this message by error, please notify us 
immediately, return the original mail to the sender and delete the 
message from your system."

[Foa-devel] RE: FOA development: getting serious ..

[Giannetti, F. <Fab...@hp...>]

Hi Vaidya,
	I was thinking that could be a good starting point to work with
pagination to add the possibility to have different headers/footers on the
sequence. In order to do this we need to change the pagination creation
adding the support for naming the static regions, such as start, end, before
and after and then change in the content sequence master give the
possibility to add content to all the available regions inside the sequence.
I'm modifying WH2FO to support headers and footers, so I have already an XSL
representation of the new model, this could be a good starting point to see
how to implement it under FOA.
This is an example :
<fo:simple-page-master page-width="595pt" page-height="841pt"
master-name="first">
          <fo:region-before extent="67pt"
region-name="fh1"></fo:region-before>
          <fo:region-after extent="54pt"
region-name="ff1"></fo:region-after>
          <fo:region-body margin-top="67pt" margin-bottom="54pt"
></fo:region-body>
        </fo:simple-page-master>
        <fo:simple-page-master page-width="595pt" page-height="841pt"
master-name="even">
          <fo:region-before extent="67pt"
region-name="eh1"></fo:region-before>
          <fo:region-after extent="54pt"
region-name="ef1"></fo:region-after>
          <fo:region-body margin-top="67pt" margin-bottom="54pt"
></fo:region-body>
        </fo:simple-page-master>
        <fo:simple-page-master page-width="595pt" page-height="841pt"
master-name="odd">
          <fo:region-before extent="67pt"
region-name="h1"></fo:region-before>
          <fo:region-after extent="54pt" region-name="f1"></fo:region-after>
          <fo:region-body margin-top="67pt" margin-bottom="54pt"
></fo:region-body>
        </fo:simple-page-master>
        <fo:page-sequence-master master-name="page-seq">
          <fo:repeatable-page-master-alternatives>
            <fo:conditional-page-master-reference master-name="first"
page-position="first"></fo:conditional-page-master-reference>
            <fo:conditional-page-master-reference master-name="even"
odd-or-even="even"></fo:conditional-page-master-reference>
            <fo:conditional-page-master-reference master-name="odd"
odd-or-even="odd"></fo:conditional-page-master-reference>
          </fo:repeatable-page-master-alternatives>
        </fo:page-sequence-master>
      </fo:layout-master-set>

So, now the big difference is that the region-before and region-after for
each page will produce in the page sequence (called Content Sequence in
FOA):

<fo:page-sequence master-name="page-seq">
        <fo:static-content flow-name="eh1">
        </fo:static-content>
        <fo:static-content flow-name="h1">
        </fo:static-content>
        <fo:static-content flow-name="ef1">
        </fo:static-content>
        <fo:static-content flow-name="f1">
        </fo:static-content>
        <fo:static-content flow-name="fh1">
        </fo:static-content>
        <fo:static-content flow-name="ff1">
        </fo:static-content>
        <fo:static-content
flow-name="xsl-region-before"></fo:static-content>
        <fo:static-content flow-name="xsl-region-after"></fo:static-content>
        <fo:flow flow-name="xsl-region-body">
        </fo:flow>
      </fo:page-sequence>

all these extra static content element with the appropriate flow-name, as
well as the standard ones if the region name has not been specified ....
Because the Page Sequence Manager and the Content Sequence Manager are
strictly related I suggest you to start to implement name supporting for
static areas inside the Page Manager and then we can start to think about
the Page Sequence and Content Sequence, because I'm already working with the
second to correct some bugs. I also like to insert some support for the page
number, we can come out with a new Brick that use a match, just at the
beginning (already present in WH2FO 0.3.0) and then introduce the
possibility to add content without the matching (a sort of static FO inside
the XSL-T ...), but this will complicate the stuff a lot and I think we can
put it into the 0.4.0 release :-))
Ok, good work and don't hesitate to ask me all the problems or clarification
that you could need.

				Fabio

PS: if you are not subsribed to the dev mailing list, please do that so our
mails could be read also by Kenneth and all the developers could know about
the development and the current situation.

> -----Original Message-----
> From: Vaidya, Raghavendra (CORP, GEITC)
> [mailto:Rag...@ge...]
> Sent: 17 March 2002 06:39
> To: Giannetti, Fabio
> Subject: RE: FOA development: getting serious ..
> 
> 
> Fabio,
> I understand your concern.
> Please assign some features / bugs to me so that I can start 
> off.I can spare
> some time for this activity
> Regards
> Vaidya
> 
> -----Original Message-----
> From: Giannetti, Fabio [mailto:Fab...@hp...]
> Sent: Friday, March 15, 2002 10:46 PM
> To: 'foa...@so...'
> Cc: 'Ken...@sp...';
> 'Rag...@ge...'
> Subject: FOA development: getting serious ..
> 
> 
> Hi guys,
> 	I think we have got (and have) plenty to do with our 
> jobs, but I'm
> seeing, from bugs and feature requests, that people is asking 
> for a new
> release with some new features. I'd like to now your personal 
> status in
> order to seriously plan the development for the next month 
> (if you are too
> busy just let me know and I will put you into a temporary 
> inactive status
> ...) otherwise if you have seen my proposal and you like it 
> we can proceed
> setting down a timescale.
> I'm, in parallel, developing WH2FO (0.3.0) and I have 
> introduced parsing of
> multiple headers/footers with page numbers (created from a 
> special XML tag)
> and I wish to update both WH2FO and FOA from the CR support to the
> Recommendation support, that basically means to change 
> master-name into
> master-reference, but also involve to change the current 
> customized FOP
> version or re-customize the latest version .....
> 
> 							Fabio
> 
> 
> "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> ONLY FOR THE
> ADDRESSEE and may contain confidential and privileged information.
> If the reader of this message is not the intended recipient,
> you are notified that any dissemination, distribution or copy of this 
> communication is strictly Prohibited. 
> If you have received this message by error, please notify us 
> immediately, return the original mail to the sender and delete the 
> message from your system."
> 

[Foa-devel] FOA development: getting serious ..

[Giannetti, F. <Fab...@hp...>]

Hi guys,
	I think we have got (and have) plenty to do with our jobs, but I'm
seeing, from bugs and feature requests, that people is asking for a new
release with some new features. I'd like to now your personal status in
order to seriously plan the development for the next month (if you are too
busy just let me know and I will put you into a temporary inactive status
...) otherwise if you have seen my proposal and you like it we can proceed
setting down a timescale.
I'm, in parallel, developing WH2FO (0.3.0) and I have introduced parsing of
multiple headers/footers with page numbers (created from a special XML tag)
and I wish to update both WH2FO and FOA from the CR support to the
Recommendation support, that basically means to change master-name into
master-reference, but also involve to change the current customized FOP
version or re-customize the latest version .....

							Fabio

[Foa-devel] RE: FOA Bugs

[Giannetti, F. <Fab...@hp...>]

Hi Paul,
	having the application in a single window will bring less complexity
on the swapping windows operation, but will bring more complexity on menus
and so on. My idea was to create separate "managers" that could be easily
mantained and live on their own ...
BTW, I'm always open to new ideas and comments, but at the moment I don't
see it as a crucial implementation issue.
There isn't a todo list on the web site, is true, but "we" have got a little
bit of discussion of what next. So I copy my proposal here (this was a
previous mail into the dev-mailing list ...)
Features:
- tables with header and footers (let's call them complex tables :-)).
- page numbers
- multiple headers/footers for each page sequence

I think this is enough .....

Now I will try to better explain the features and then you will choose the
one that you will feel more "confortable" :-))

Complex Tables
To implement this feature it will be necessary to create a new brick that is
based on the current simple-table but will add the header and footer pieces.
Basically the complex table is a table that share the columns concept of the
simple-table but is formed by 3 different sub tables: body, header and
footer. So I think it will be necessary to add a new brick type with a new
GUI, it will require also the generation of the necessary XSL-T piece.

Page Numbers
There are 2 different lind of page numbers, the simple one is like page 1, 2
and so on ... the complex one is related to give the page 1/n, 2/n and so on
and this is more difficult because you must add a marker to find out which
is the last page. I think we can go for the simple one !!
The problem here is to understand if it will be necessary to have a new
brick that match some content inside the xml (like <page-num/>) fairly
simple or (I guess better) generate a new serie of Brick that are withou the
matching and will be inserted directly inside the content-sequence like
static content (or invariant content :-)) In order to do this there is quite
a lot of job to do and to radically change the content-sequence-manager.

Multiple Headers/Footers for page
To do this it will necessary to change the page manager to allow the insert
of multiple regions with a different region name and update the
content-sequence-manager to deal with multiple static-region per sequence. 

Example:
<fo:layout-master-set>
<!-- layout for the first page -->
<fo:simple-page-master master-name="first"
    page-height="29.7cm"
    page-width="21cm"
    margin-top="1cm"
    margin-bottom="2cm"
    margin-left="2.5cm"
    margin-right="2.5cm">
    <fo:region-body margin-top="3cm"/>
    <fo:region-before region-name="header-first"
        extent="3cm"/>
    <fo:region-after extent="1.5cm"/>
</fo:simple-page-master>

    <!-- layout for the other pages -->
<fo:simple-page-master master-name="rest"
    page-height="29.7cm"
    page-width="21cm"
    margin-top="1cm"
    margin-bottom="2cm"
    margin-left="2.5cm"
    margin-right="2.5cm">
    <fo:region-body margin-top="3cm"/>
    <fo:region-before region-name="header-rest"
        extent="3cm"/>
    <fo:region-after extent="1.5cm"/>
</fo:simple-page-master>

<fo:page-sequence-master master-name="firstAndRest" >
 <fo:repeatable-page-master-alternatives>
  <fo:conditional-page-master-reference master-name="first"
   page-position="first" />
  <fo:conditional-page-master-reference master-name="rest"
   page-position="rest" />
 </fo:repeatable-page-master-alternatives>
</fo:page-sequence-master>

  </fo:layout-master-set>
  <!-- end: defines page layout -->

  <!-- actual layout -->
  <fo:page-sequence master-name="firstAndRest">

<fo:static-content flow-name="header-first">
<fo:block>
Blah blah blah
</fo:block>
</fo:static-content>

<fo:static-content flow-name="header-rest">
<fo:block>
Blah blah blah
</fo:block>
</fo:static-content>

So, if you are interested to do some job, please send me an e-mail with your
login name and I will add you to the team.

Thanks, Fabio 

> -----Original Message-----
> From: pfu...@ma... [mailto:pfu...@ma...]
> Sent: 07 March 2002 18:50
> To: Fabio Giannetti
> Subject: Re: FOA Bugs
> 
> 
> Fabio,
> 
> > first of all thank you for submitting some bugs.
> > I'm currently working on them and I have already
> > fixed a couple of them :-)
> 
> You are welcome and thanks for the fixes.  I'm
> sorry it has taken me so long to respond to your
> message.  I have gotten behind in things since the
> switch over from bankrupt Excite@Home to Comcast's
> own networks causes a nearly day-long interruption
> in my work (maybe it was longer, but however long
> it was, it sure was frustrating trying to get my internal
> network and connection to the Internet.)
> 
> > I'd like to know if you are interested to join
> > the forming FOA team like a developer and/or
> > tester. I think you are a skilled person and we
> > need all the available help.
> 
> I am interested in doing something, but I'm not
> sure what and how much time I have to devote
> to the project.
> 
> The project's Web site did not have a To Do list
> the last time I checked, so I don't know what kinds
> of things you still need to work on.  I do have one
> thing in my mind which I'll describe next.
> 
> Before I start, I have to commend you for a great
> effort which resulted in a highly usable program.
> There is only one problem with the design from
> from my standpoint -- there are too many windows.
> I'd like to see a program which is contained in a
> single window.  (If you knew my background in
> computing -- very much based in the Macintosh
> world where the idea of multiple windows took
> hold -- you might be surprised to read this.  I do
> most of my Java development on Windows machines;
> however, I do much of my non-programming work
> on Macs.)  It used to be the paradigm for stand-alone
> applications to spawn lots of windows, one for each
> document, and so on.  But that paradigm becomes
> really inefficient in cases where you are frequently
> switching between views or documents, as one does
> in something like a programmer's IDE.  FOA invites you
> to switch views a lot, and therefore, would benefit
> from being reorganized into an application which
> uses only a single window.
> 
> So, one thing I was thinking of doing was trying to
> doing a prototype of a reorganized FOA which
> presents the application in a single window.  This was
> something that I would do -- if I have the time -- on
> my own and then demonstrate to you and the other
> developers after it was working.
> 
> What do you think?  I'll be a bit busy in the coming
> weeks, so I don't know how much time I would have
> to devote to this side-line activity.
> 
> 
> Paul
> 

RE: [Foa-devel] Why the main window (project) does not come up?

[Giannetti, F. <Fab...@hp...>]

Hi Mathy,
	your problem is related to the fact that you haven't download and
installed the Jaxp package.
See: http://java.sun.com/xml/downloads/javaxmlpack.html
Download it and put into the CLASSPATH (if you unzip the package in C:\):

C:\java_xml_pack-winter-01-dev\jaxp-1.2-ea1\xerces.jar;C:\java_xml_pack-wint
er-01-dev\jaxp-1.2-ea1\xalan.jar

(To update the CLASSPATH use the right button in My
Computer->Properties->Advanced->Environment Variables)
If CLASSPATH is not present add it and put the two .jars

NOTE: DON'T PUT ANY SPACE BETWEEN THE JARS OTHERWISE IT DOESN'T WORK !!!!!

Hope this helps, Fabio

> -----Original Message-----
> From: Mathy V Arumugam [mailto:Mat...@jp...]
> Sent: 05 March 2002 18:35
> To: foa...@li...
> Subject: [Foa-devel] Why the main window (project) does not come up?
> 
> 
> Hi,
> I am having difficult time in bringing up the FOA main window (all the
> other windows come up fine).  I have tried both the versions available
> on FOA site and no luck.
> 
> The following is what I have put in 'foa.bat' file.  I am running
> WINDOWS 2000.
>     javaw -cp
> C:\FOA_0_2_2\lib\xalan-2.0.0.jar;C:\FOA_0_2_2\lib\xerces-1.2.3
> .jar;C:\FOA_0_2_2\lib\batik.jar;C:\FOA_0_2_0\bins\foa.jar;
> 
> foa.apps.Foa
> 
> Pls someone help me.  Anxiously waiting for a solution from you!
> 
> Thanks
> Mathy
> 
> 
> _______________________________________________
> Foa-devel mailing list
> Foa...@li...
> https://lists.sourceforge.net/lists/listinfo/foa-devel
> 

[Foa-devel] Why the main window (project) does not come up?

[Mathy V A. <Mat...@jp...>]

Hi,
I am having difficult time in bringing up the FOA main window (all the
other windows come up fine).  I have tried both the versions available
on FOA site and no luck.

The following is what I have put in 'foa.bat' file.  I am running
WINDOWS 2000.
    javaw -cp
C:\FOA_0_2_2\lib\xalan-2.0.0.jar;C:\FOA_0_2_2\lib\xerces-1.2.3.jar;C:\FOA_0_2_2\lib\batik.jar;C:\FOA_0_2_0\bins\foa.jar;

foa.apps.Foa

Pls someone help me.  Anxiously waiting for a solution from you!

Thanks
Mathy

[Foa-devel] New Release: FOA 0.2.2

[Giannetti, F. <Fab...@hp...>]

Hello guys,
	I just update the CVS and created a new Release 0.2.2 that resolve
many bugs (thanks to Paul Furbacher and Narendra).
I decide to put a new release and not only a patch because I discover some
vicious errors like the error stream filling problem. Basically when FOA
invokes FOP and get some messages on the ErrorStream it goes into a loop,
now is fixed !
I also changed some icons (close instead of remove) and added a the Save As
feature for the Attribute Sets.
I think having this maintenance release was important expecially for the
ErrorStream problem, otherwise was very difficult to get the Preview !! 

							Fabio

RE: [Foa-devel] Let's start with a list of implementable features and bugs

[Giannetti, F. <Fab...@hp...>]

Hi guys,
	I think it's time to put something inside the kitty ....
I know that everybody has shortage of spare time, but it will be better to
start to do something, at least to get an idea of how to do stuff, learn
more on FOA and so on ....
So if everybody agree I will assign the job in this way:
Kenneth: tables with header and footers (let's call them complex tables)
Raghavendra: multiple headers/footers for each page sequence
Fabio: page numbers & bugs

As I said before I'd like to work very close together, this will bring some
overhead in mailing and so on but I think will made a smoothly integration
of the pieces and will give a consistent design strategy.
I really appreciate your collaboration, and I will do the necessary to help
you in accomplish these tasks :-))

							Fabio

> -----Original Message-----
> From: Giannetti, Fabio [mailto:Fab...@hp...]
> Sent: 11 February 2002 09:33
> To: 'Foa...@li...'
> Cc: 'Rag...@ge...'
> Subject: [Foa-devel] Let's start with a list of implementable features
> and bugs
> 
> 
> Hi,
> 	I think I can start to propose some features to 
> implement and bug to
> fix:
> 
> Known bugs:
> 1. when you start to generate a new project from scratch, if 
> you create a
> new Attribute file and you don't save it before creating any 
> brick the XSLT
> file will be inconsistent and generate an error, priority: HIGH
> 
> Features:
> - tables with header and footers (let's call them complex tables :-)).
> - page numbers
> - multiple headers/footers for each page sequence
> 
> I think this is enough .....
> 
> Now I will try to better explain the features and then you 
> will choose the
> one that you will feel more "confortable" :-))
> 
> Complex Tables
> To implement this feature it will be necessary to create a 
> new brick that is
> based on the current simple-table but will add the header and 
> footer pieces.
> Basically the complex table is a table that share the columns 
> concept of the
> simple-table but is formed by 3 different sub tables: body, header and
> footer. So I think it will be necessary to add a new brick 
> type with a new
> GUI, it will require also the generation of the necessary XSL-T piece.
> 
> Page Numbers
> There are 2 different lind of page numbers, the simple one is 
> like page 1, 2
> and so on ... the complex one is related to give the page 
> 1/n, 2/n and so on
> and this is more difficult because you must add a marker to 
> find out which
> is the last page. I think we can go for the simple one !!
> The problem here is to understand if it will be necessary to 
> have a new
> brick that match some content inside the xml (like <page-num/>) fairly
> simple or (I guess better) generate a new serie of Brick that 
> are withou the
> matching and will be inserted directly inside the 
> content-sequence like
> static content (or invariant content :-)) In order to do this 
> there is quite
> a lot of job to do and to radically change the 
> content-sequence-manager.
> 
> Multiple Headers/Footers for page
> To do this it will necessary to change the page manager to 
> allow the insert
> of multiple regions with a different region name and update the
> content-sequence-manager to deal with multiple static-region 
> per sequence. 
> 
> Example:
> <fo:layout-master-set>
> <!-- layout for the first page -->
> <fo:simple-page-master master-name="first"
>     page-height="29.7cm"
>     page-width="21cm"
>     margin-top="1cm"
>     margin-bottom="2cm"
>     margin-left="2.5cm"
>     margin-right="2.5cm">
>     <fo:region-body margin-top="3cm"/>
>     <fo:region-before region-name="header-first"
>         extent="3cm"/>
>     <fo:region-after extent="1.5cm"/>
> </fo:simple-page-master>
> 
>     <!-- layout for the other pages -->
> <fo:simple-page-master master-name="rest"
>     page-height="29.7cm"
>     page-width="21cm"
>     margin-top="1cm"
>     margin-bottom="2cm"
>     margin-left="2.5cm"
>     margin-right="2.5cm">
>     <fo:region-body margin-top="3cm"/>
>     <fo:region-before region-name="header-rest"
>         extent="3cm"/>
>     <fo:region-after extent="1.5cm"/>
> </fo:simple-page-master>
> 
> <fo:page-sequence-master master-name="firstAndRest" >
>  <fo:repeatable-page-master-alternatives>
>   <fo:conditional-page-master-reference master-name="first"
>    page-position="first" />
>   <fo:conditional-page-master-reference master-name="rest"
>    page-position="rest" />
>  </fo:repeatable-page-master-alternatives>
> </fo:page-sequence-master>
> 
>   </fo:layout-master-set>
>   <!-- end: defines page layout -->
> 
>   <!-- actual layout -->
>   <fo:page-sequence master-name="firstAndRest">
> 
> <fo:static-content flow-name="header-first">
> <fo:block>
> Blah blah blah
> </fo:block>
> </fo:static-content>
> 
> <fo:static-content flow-name="header-rest">
> <fo:block>
> Blah blah blah
> </fo:block>
> </fo:static-content>
> 
> OK, let me know what do you think and what will be your 
> favourite piece to
> develop. I think I will choose the second, sounds to me a 
> little bit messy
> :-))
> By the way, choosing a piece doesn't force you to die trying 
> to implement it
> ... I think it will be better and more interesting to have a 
> frequent and
> useful interaction to easily bypass problems and choose the 
> better way to do
> the suff and of course share our knowledge ....
> 
> 								
> Hope to hear
> you soon, Fabio
> 
> _______________________________________________
> Foa-devel mailing list
> Foa...@li...
> https://lists.sourceforge.net/lists/listinfo/foa-devel
> 

[Foa-devel] RE: Urgent problem!

[Giannetti, F. <Fab...@hp...>]

Hi Narendra,

 
> Well now I have started playing with multiple pages.
> I have created three new pages. P1, P2 and P3.
> I have created a page sequence (alternative) where p1 is 
> first p2 odd and p3
> even.
> I designed an attribute file.
> 
> I created 4 bricks.
> brick1-commmon header
> brick2-name
> brick3-address
> brick4-email
> 
> Till here every thing is OK.
> Now my objective for doing this all mess is to -
> 1) Give my all three pages (p1,p2,p3) a common heading which 
> I have designed
> in my brick1.
> 2) Put brick2-name content in page P1,
>           brick3-address in page P2
>           and brick4-email in page P3.
> 
> So I put brick1-common header in the body-before section of 
> the content
> Sequence Manager and all other three bricks in the body 
> section because
> there was no other choice, I could found the content sequence Manager.
> I generated .fo and than rendered it. I got PDF with single 
> page having all
> header, name, address and email in single page, where header 
> and name were
> overlapped, address in new line, mail in new line.
> 
> Where as the purpose was, I should be able to get 3 pages in 
> the PDF having
> same heading and different content first name, second address 
> third email.
> I was unable to do so. How can I do it?

There are 2 ways to obtain it it depends on what you prefer and which are
your requirements:
1) You have to express for the current content bricks the property
break-after="page" so the render engine will be forced to skip to the next
page and so you will get the first page with the name, the second with the
address and the third with the e-mail.
2)You can have 3 different single page sequences and the put for all of them
the common header in the before section and point to the 3 different sub
elements in the xml content file for the three pieces (name, address and so
on). It worth to have a look to the Multipage example in WH2FO
(http://wh2fo.sourceforge.net) that could be opened with FOA.

> 
> MY Understanding with FOA TOOL:
> ============================
> In Page Manager: I create and manage page region margin etc.

right

> In Page Sequence Manager: I link my all pages. May be more 
> but not aware of it's full features.

The page sequence manager gives you the possibility to express in which way
do you want to use the created pages. The pre-defined solution available in
FOA are the most common used, single page, repeated (with first/last)
alternating (with first/last). In FO you can freely generate all the page
sequences that you like using the conditional statement. This introduce a
big degree of uncertainless because you can generate inconsistent page
sequences that will end up with nothing rendered. I just avoid this keeping
the stuff simple but useful because my first goal was to give users a fast
way to create XSL-T that are correct.

> In Attribute Set Manager: I define the basic style for 
> contents like font, colour, padding etc.

right. These are subdivided int categories or classes again to avoid
mistakes like give to a block a property that belongs only to a table or an
inline element.

> In Brick Manager: I build up bricks to combine my XML data 
> and style as basic block.

you're right again :-))

> In XMl Manager : I map XML data to a brick.

The XML manager gives you a way to refer to the content that you want to
style or select for the sequence.

> 
> Till here all cool and good.
> 
> But but but........
> In content sequence manager: I just show few sections like body,
> before-body, after-body.

I know that this is the most difficult stuff to undestand, but is also the
only way to get the content to put on the page. The content sequence manager
shows, for each page sequence created, the list of possible areas that you
want to fill with your XML content. I try to make an example.
If in your first page you define the header and the body and in your
repeated pages you define the footer and the body and made a repeated
sequence with the first page, the content sequence manager will show 3
regions: header, footer and body. This because these are all the available
regions in your sequence, it's then responsibility of the render engine to
render the footer content only in the second page. The content sequence
manager is a sort of abstraction of all the possible regions that you can
fill in your sequence. When you select a piece of XML that means that the
content starting from that tag to the end will be inserted in that region
and styled with the defined bricks, that doesn't belong to the region itself
but are independent, so you can generate a brick that transforms the tag
<par> into an fo:block and re-use it for the content inside the header as
well the body. I hope this is quite clear :-))

> 
> This not specific to pages which I have created. I mean I 
> have built all
> separate entities (page, page sequence, attribute, bricks) in 
> very fine
> modular approach "divide and conquer" Nice implementation. 

I'm a good italian, I always learn from our past ... and Caesar was a good
teacher :-)))

> But here I stuck
> don't know where I am putting these bricks.
> 
> Body section means: means page body but which page???? I have 
> created so
> many pages.

As I have explained before the body area is an abstraction of all the bodies
definded for the page sequence, so basically you can select which content
send into the flow that will be automatically redistribuited across the
pages. You can express control using the page breaks, the keeps and so on.

							Fabio

> 
> Suggestion:
> =======
> Cannot this section be re-developed for a clear mapping of 
> bricks with the
> pages. Like common header, common footer, then is displays 
> each section for
> all pages I have created in page manager?
> 
> Please help developer to understand this problem.
> Thanks in advance.
> Narendra.
> 
> PS: Happy to hear the announcement for recognition of new 
> features most
> wanted in next release.
> 
> 

[Foa-devel] Urgent problem!

[Narendra <na...@it...>]

Hi Fabio,

Well now I have started playing with multiple pages.
I have created three new pages. P1, P2 and P3.
I have created a page sequence (alternative) where p1 is first p2 odd and p3
even.
I designed an attribute file.

I created 4 bricks.
brick1-commmon header
brick2-name
brick3-address
brick4-email

Till here every thing is OK.
Now my objective for doing this all mess is to -
1) Give my all three pages (p1,p2,p3) a common heading which I have designed
in my brick1.
2) Put brick2-name content in page P1,
          brick3-address in page P2
          and brick4-email in page P3.

So I put brick1-common header in the body-before section of the content
Sequence Manager and all other three bricks in the body section because
there was no other choice, I could found the content sequence Manager.
I generated .fo and than rendered it. I got PDF with single page having all
header, name, address and email in single page, where header and name were
overlapped, address in new line, mail in new line.

Where as the purpose was, I should be able to get 3 pages in the PDF having
same heading and different content first name, second address third email.
I was unable to do so. How can I do it?

MY Understanding with FOA TOOL:
============================
In Page Manager: I create and manage page region margin etc.
In Page Sequence Manager: I link my all pages. May be more but not aware of
it's full features.
In Attribute Set Manager: I define the basic style for contents like font,
colour, padding etc.
In Brick Manager: I build up bricks to combine my XML data and style as
basic block.
In XMl Manager : I map XML data to a brick.

Till here all cool and good.

But but but........
In content sequence manager: I just show few sections like body,
before-body, after-body.

This not specific to pages which I have created. I mean I have built all
separate entities (page, page sequence, attribute, bricks) in very fine
modular approach "divide and conquer" Nice implementation. But here I stuck
don't know where I am putting these bricks.

Body section means: means page body but which page???? I have created so
many pages.

Suggestion:
=======
Cannot this section be re-developed for a clear mapping of bricks with the
pages. Like common header, common footer, then is displays each section for
all pages I have created in page manager?

Please help developer to understand this problem.
Thanks in advance.
Narendra.

PS: Happy to hear the announcement for recognition of new features most
wanted in next release.

[Foa-devel] Let's start with a list of implementable features and bugs

[Giannetti, F. <Fab...@hp...>]

Hi,
	I think I can start to propose some features to implement and bug to
fix:

Known bugs:
1. when you start to generate a new project from scratch, if you create a
new Attribute file and you don't save it before creating any brick the XSLT
file will be inconsistent and generate an error, priority: HIGH

Features:
- tables with header and footers (let's call them complex tables :-)).
- page numbers
- multiple headers/footers for each page sequence

I think this is enough .....

Now I will try to better explain the features and then you will choose the
one that you will feel more "confortable" :-))

Complex Tables
To implement this feature it will be necessary to create a new brick that is
based on the current simple-table but will add the header and footer pieces.
Basically the complex table is a table that share the columns concept of the
simple-table but is formed by 3 different sub tables: body, header and
footer. So I think it will be necessary to add a new brick type with a new
GUI, it will require also the generation of the necessary XSL-T piece.

Page Numbers
There are 2 different lind of page numbers, the simple one is like page 1, 2
and so on ... the complex one is related to give the page 1/n, 2/n and so on
and this is more difficult because you must add a marker to find out which
is the last page. I think we can go for the simple one !!
The problem here is to understand if it will be necessary to have a new
brick that match some content inside the xml (like <page-num/>) fairly
simple or (I guess better) generate a new serie of Brick that are withou the
matching and will be inserted directly inside the content-sequence like
static content (or invariant content :-)) In order to do this there is quite
a lot of job to do and to radically change the content-sequence-manager.

Multiple Headers/Footers for page
To do this it will necessary to change the page manager to allow the insert
of multiple regions with a different region name and update the
content-sequence-manager to deal with multiple static-region per sequence. 

Example:
<fo:layout-master-set>
<!-- layout for the first page -->
<fo:simple-page-master master-name="first"
    page-height="29.7cm"
    page-width="21cm"
    margin-top="1cm"
    margin-bottom="2cm"
    margin-left="2.5cm"
    margin-right="2.5cm">
    <fo:region-body margin-top="3cm"/>
    <fo:region-before region-name="header-first"
        extent="3cm"/>
    <fo:region-after extent="1.5cm"/>
</fo:simple-page-master>

    <!-- layout for the other pages -->
<fo:simple-page-master master-name="rest"
    page-height="29.7cm"
    page-width="21cm"
    margin-top="1cm"
    margin-bottom="2cm"
    margin-left="2.5cm"
    margin-right="2.5cm">
    <fo:region-body margin-top="3cm"/>
    <fo:region-before region-name="header-rest"
        extent="3cm"/>
    <fo:region-after extent="1.5cm"/>
</fo:simple-page-master>

<fo:page-sequence-master master-name="firstAndRest" >
 <fo:repeatable-page-master-alternatives>
  <fo:conditional-page-master-reference master-name="first"
   page-position="first" />
  <fo:conditional-page-master-reference master-name="rest"
   page-position="rest" />
 </fo:repeatable-page-master-alternatives>
</fo:page-sequence-master>

  </fo:layout-master-set>
  <!-- end: defines page layout -->

  <!-- actual layout -->
  <fo:page-sequence master-name="firstAndRest">

<fo:static-content flow-name="header-first">
<fo:block>
Blah blah blah
</fo:block>
</fo:static-content>

<fo:static-content flow-name="header-rest">
<fo:block>
Blah blah blah
</fo:block>
</fo:static-content>

OK, let me know what do you think and what will be your favourite piece to
develop. I think I will choose the second, sounds to me a little bit messy
:-))
By the way, choosing a piece doesn't force you to die trying to implement it
... I think it will be better and more interesting to have a frequent and
useful interaction to easily bypass problems and choose the better way to do
the suff and of course share our knowledge ....

								Hope to hear
you soon, Fabio

RE: [Foa-devel] Situation ...

[Birney, K. <Ken...@sp...>]

sure thing Fabio, im ready to go.

-----Original Message-----
From: Giannetti, Fabio [mailto:Fab...@hp...]
Sent: 08 February 2002 10:40
To: foa...@li...
Subject: [Foa-devel] Situation ...


Hi Folks,
	how it is going ? Have you got time to undestand FOA ? Are you ready
to start to do some development ?
There are any questions ?
I think that when you two guys have enough confidence with the code we can
start to put down a development plan to get the 0.3.0 release.
Narendra has highlight some of the missing feartures, so we can start do
implement some of those .....
Let me now your opininions.

						Fabio

_______________________________________________
Foa-devel mailing list
Foa...@li...
https://lists.sourceforge.net/lists/listinfo/foa-devel

[Foa-devel] Situation ...

[Giannetti, F. <Fab...@hp...>]

Hi Folks,
	how it is going ? Have you got time to undestand FOA ? Are you ready
to start to do some development ?
There are any questions ?
I think that when you two guys have enough confidence with the code we can
start to put down a development plan to get the 0.3.0 release.
Narendra has highlight some of the missing feartures, so we can start do
implement some of those .....
Let me now your opininions.

						Fabio

[Foa-devel] Re: Foa-devel digest, Vol 1 #2 - 1 msg

[Narendra <na...@it...>]

Thanks it really helped.
:)

/narendra
----- Original Message -----
From: <foa...@li...>
To: <foa...@li...>
Sent: Thursday, February 07, 2002 1:41 PM
Subject: Foa-devel digest, Vol 1 #2 - 1 msg


> Send Foa-devel mailing list submissions to
> foa...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/foa-devel
> or, via email, send a message with subject or body 'help' to
> foa...@li...
>
> You can reach the person managing the list at
> foa...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Foa-devel digest..."
>
>
> Today's Topics:
>
>    1. RE: Few queries (Giannetti, Fabio)
>
> --__--__--
>
> Message: 1
> From: "Giannetti, Fabio" <Fab...@hp...>
> To: foa...@li...
> Cc: "'foa...@li...'" <foa...@li...>
> Date: Thu, 7 Feb 2002 15:43:15 -0000
> Subject: [Foa-devel] RE: Few queries
>
> Hi Narendra,
> unfortunately from SourceForge is impossible to open the Word
> attachment, so I copy your questions, so everybody could take advantage
...
> So let's go in order:
>
> > 1) I have to view contents in following format
> >     Street  : 28, Mountain Road
> > City     : Washington
> > State   : NY
> >     So what type of XML file shall I have? Currently I have the
following
> type:
> >     <address>
> > <street>28, Mountain Road</street>
> > <city>Washington</city>
> > <state>NY</state>
> > </address>
> >     Question: How can I get the tag name as the label for my data in to
> the report?
> >     i.e. <street>28, Mountain road</street>
> >     Label: Yellow high-lighted
> >     Data: Blue high-lighted.
> >
> >     Or I need to redesign my XML in this format:
> >     <address>
> >  <street>
> >                <label> street</label>
> >                <data>28, Mountain Road</data>
> >           </street>
> > <city>
> >                <label>City</label>
> >                <data>Washington</data>
> >           </city>
> > <state>
> >                <label>City</label>
> >                <data>NY</data>
> >           </state>
> > </address>
>
> I think there is a little bit of confusion here ... the two proposed model
> have difference in the content, so the first model could be transformed
into
> a list using the standard bulled or numbered lists, the second one could
be
> generated using a label&body list in which you can select the appeareance
of
> the label and body separately.
> At the moment, is not possible to change the style for the label for a
> bullet or numbered list, but could be a feature to be added.
>
> > 2) My Report stretches to multiple rows of the table some time it
> covers more than one page. Depends on data, how can I fix the same heading
> to > >     all tables with goes to multiple pages.
>
> This feature is not implemented yet, in fact at the moment you can obtain
> headers using special elements inside the table ... this works only if you
> don't replicate the headers and footers across the pages. To do this there
> is a header and footer definition in XSL-FO but this will made the tables
> more complicated, so next feature it's to have complex tables ....
>
> > 3) How can I put headings of the table in different
> font/colour/background etc?
>
> If you have inside your XML a way to distinguish between the table data
and
> the table header you can use 2 different bricks, your xml file:
> <clients>
> <header>
> <item>Name</item>
> <item>Address</item>
> </header>
> <client>
> <item>Fabio</item>
> <item>Bristol</item>
> </client>
> ...
> </clients>
>
> So you can generate a brick that creates a cell for clients/header/item
> different from the one that generate a cell for clients/client/item
> This solution is of course not so good, just because FOA doesn't support
yet
> real headers and footers.
>
> > 4) I need to give common header and footer to every page, don't know
> how to do it?
>
> This is quite simple actually, when you define a new page you could set a
> content sequence for the region after and before. After that you can
> generate a brick that will style that content. See the MyBank example.
>
> > 5) Can I take the sum of a particular column? Like I view prices of
> different items in a column and take grand total in last row.
>
> This is an XSL-T issue, I think FOA doesn't have to embedd operations on
> data inside the styling stuffs. So you can generate an XSL-T stylesheet
that
> perform that operation and then think how to create the FO document using
> FOA.
>
> > 6) Can I see page number at the bottom of the page like 1 of 5.
>
> This is a not implemented feature, FOA doesn't have yet also the page
> numbering.
>
> Hope this helps and make the current FOA state of development clearer.
> We can also start to think which features implement next, I hope that you
> and all the users/developers will give inputs to drive the development.
>
>
> Fabio
>
>
>
> --__--__--
>
> _______________________________________________
> Foa-devel mailing list
> Foa...@li...
> https://lists.sourceforge.net/lists/listinfo/foa-devel
>
>
> End of Foa-devel Digest
>

[Foa-devel] RE: Few queries

[Giannetti, F. <Fab...@hp...>]

Hi Narendra,
	unfortunately from SourceForge is impossible to open the Word
attachment, so I copy your questions, so everybody could take advantage ...
So let's go in order:

> 1)	I have to view contents in following format
>     Street  : 28, Mountain Road
>	City     : Washington
>	State   : NY
>     So what type of XML file shall I have? Currently I have the following
type:
>     <address>
>		<street>28, Mountain Road</street>
>		<city>Washington</city>
>		<state>NY</state>
>	</address>
>     Question: How can I get the tag name as the label for my data in to
the report?
>     i.e. <street>28, Mountain road</street>
>     Label: Yellow high-lighted
>     Data: Blue high-lighted.
>
>     Or I need to redesign my XML in this format:
>     <address>
>  		<street>
>                <label> street</label>
>                <data>28, Mountain Road</data>
>           </street>
>		<city>
>                <label>City</label>
>                <data>Washington</data>
>           </city>
>		<state>
>                <label>City</label>
>                <data>NY</data>
>           </state>
>	</address>

I think there is a little bit of confusion here ... the two proposed model
have difference in the content, so the first model could be transformed into
a list using the standard bulled or numbered lists, the second one could be
generated using a label&body list in which you can select the appeareance of
the label and body separately.
At the moment, is not possible to change the style for the label for a
bullet or numbered list, but could be a feature to be added.

> 2)	My Report stretches to multiple rows of the table some time it
covers more than one page. Depends on data, how can I fix the same heading
to > >     all tables with goes to multiple pages. 

This feature is not implemented yet, in fact at the moment you can obtain
headers using special elements inside the table ... this works only if you
don't replicate the headers and footers across the pages. To do this there
is a header and footer definition in XSL-FO but this will made the tables
more complicated, so next feature it's to have complex tables ....

> 3)	How can I put headings of the table in different
font/colour/background etc?

If you have inside your XML a way to distinguish between the table data and
the table header you can use 2 different bricks, your xml file:
<clients>
	<header>
		<item>Name</item>
		<item>Address</item>
	</header>
	<client>
		<item>Fabio</item>
		<item>Bristol</item>
	</client>
	...
</clients>

So you can generate a brick that creates a cell for clients/header/item
different from the one that generate a cell for clients/client/item
This solution is of course not so good, just because FOA doesn't support yet
real headers and footers.

> 4)	I need to give common header and footer to every page, don't know
how to do it?

This is quite simple actually, when you define a new page you could set a
content sequence for the region after and before. After that you can
generate a brick that will style that content. See the MyBank example.

> 5)	Can I take the sum of a particular column? Like I view prices of
different items in a column and take grand total in last row.

This is an XSL-T issue, I think FOA doesn't have to embedd operations on
data inside the styling stuffs. So you can generate an XSL-T stylesheet that
perform that operation and then think how to create the FO document using
FOA.

> 6) Can I see page number at the bottom of the page like 1 of 5.

This is a not implemented feature, FOA doesn't have yet also the page
numbering.

Hope this helps and make the current FOA state of development clearer.
We can also start to think which features implement next, I hope that you
and all the users/developers will give inputs to drive the development.

	
Fabio

[Foa-devel] Few queries

[Narendra <na...@it...>]

Hi,

Please find attached a document where I have raised few points.
These are just queries or suggestions may be some of them could be out of
the scope of the FOA current version.
 I just need to know can we do so?

Thanks and Regards,
Narendra.

[Foa-devel] Access to the sources

[Giannetti, F. <Fab...@hp...>]

If you download the distribution, inside the directory src there are the
sources.
You can also, separately download the UML diagrams and the javadocs from the
download page in the web site.
To browse the documentation from your machine, please create inside the
distribution dir a dir called docs and extract inside the javadocs and the
uml
FOA_0_2_0
	    |
	    |- docs
			|
			|- javadocs
			|- uml


					Fabio

> -----Original Message-----
> From: Vaidya, Raghavendra (CORP, GEITC)
> [mailto:Rag...@ge...]
> Sent: 04 February 2002 09:13
> To: Giannetti, Fabio
> Subject: RE: New Devel
> 
> 
> Hi Fabio,
> Thanks.
> Can you tell me how do I download all the code(in one shot)so 
> that I can go
> thro' the UML diagrams and the code at the same time in my 
> local machine. I
> am not very familiar with CVS
> Regards
> Vaidya
> 
> -----Original Message-----
> From: Giannetti, Fabio [mailto:Fab...@hp...]
> Sent: Monday, February 04, 2002 2:16 PM
> To: 'Vaidya, Raghavendra (CORP, GEITC)'
> Subject: RE: New Devel
> 
> 
> Hi Vaidya,
> 	I do all the necessary, so now you have the grants to 
> write on the
> CVS tree and you appear in the team page !
> So, as I told to Kenneth, the other member, first of all try 
> to familiarize
> with the code and post questions on the dev mailing list so 
> all the answers
> will be public.
> 
> 						Fabio
> 
> > -----Original Message-----
> > From: Vaidya, Raghavendra (CORP, GEITC)
> > [mailto:Rag...@ge...]
> > Sent: 02 February 2002 08:31
> > To: Giannetti, Fabio
> > Subject: RE: New Devel
> > 
> > 
> > Hi Fabio,
> > I have subscribed at SourceForge
> > my User Name is rpvaidya
> > please do the needful
> > Regards
> > Vaidya
> > 
> > 
> 
> 
> "THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED 
> ONLY FOR THE
> ADDRESSEE and may contain confidential and privileged information.
> If the reader of this message is not the intended recipient,
> you are notified that any dissemination, distribution or copy of this 
> communication is strictly Prohibited. 
> If you have received this message by error, please notify us 
> immediately, return the original mail to the sender and delete the 
> message from your system."
>