To the best of my knowlegde, the answer is NO. The properties of an object are listed in the Tag Definition dialog, where each tab displays the property of the selected object (individual, family, picture, occupation, source, ...).

For instance, if you wish to write the name and birth date of every individuals you could use the following code:

for (var i = 0; i < Individuals.Count; i++) {   var ind = Individuals(i);   if (!ind.IsDead) // Exclude any individual deceased   {      // The individual is alive, so fetch his/her birthday      var strBirthday = ind.Birthday.ToString("MMMM d");      if (strBirthday != "")      {         Report.Write3Br("<br/><b>", strBirthday, "</b>");         // Write the name of the individual in the page         Report.WriteBr(ind.Name);       }    } }

This example has been slightly modified from the build-in skin "Birthday Listing" in GenoPro

Jean-Claude Morin
Information Technology Director, GenoPro.
http://www.genopro.com

The following script will create a two dimensional array of records and fields, with each field createed an a javascript object having a name and value property. It then displays the data into the GenoPro Message Log. (but note that genopro skips duplicate messages in the log). The fields to be selected are preset in the array fieldnames.

<%[ var fieldnames = new Array('Name', 'Name.Display','Name.First', 'Name.Middle', 'Name.Last','MyCustomTag'); // create list of required fields (change as required) var i, records=new Array(Individuals.Count); for (var iCnt = 0; iCnt < Individuals.Count; iCnt++) {               // loop over Individuals collection  records[iCnt] = new Array();  i = Individuals(iCnt);  for (fCnt in fieldnames) {  records[iCnt][fCnt] = new Object();   try {                                                                           // trap error when Custom tag field does not exist for this record    records[iCnt][fCnt].name = fieldnames[fCnt];                    // store field name    records[iCnt][fCnt].value = i.TagValue(fieldnames[fCnt]);   // store field contents   } catch(e) {   // Report.LogError(e.description);   }  }  Report.LogWarning('Data for ' + i.Name);  for (var fCnt in records[iCnt]) {       // display selected field for each Individual   Report.LogWarning('  '+records[iCnt][fCnt].name + '=' + records[iCnt][fCnt].value);  } } Report.AbortReport(); ]%>

Collections can be considered as sets of records, with properties of each object/record in the collection corresponding to fields or 'tags'. Some of the 'fields' i.e. custom tags are optional and may not appear in all records.

As I said, I cannot properly 'visualize' how a collection is built/structured so there's no point in continuing further.

Thanks again,

JC

Various obs noticed during the script implementation:
1) The 'Unions' collection is not supported. In order to enumerate the Unions MLFs, I created a collection during the 'Families' process. Unless I miss something, this Fam Unions collection should exist, similar to an Ind Edu or Occu.
2) The 'ID' tag of the Emotional Relationships, Social Relationships, Labels, Shapes and Pedigree Links are not generated by Genopro.
3) Picture object: the 'Comment' and 'Description' Tags are the same. One tag, to my opinion, is therefore redundant. I only processed the 'Comment' tag in the attached file as it's the one shown in the Pict layout panel. Also for info, the tag recorded in the .xml file is 'Description'!
4) The Shape 'Position' tag doesn't seem to be supported. It's blank in the report. For the report, I used the 'Position.Points' tag.
5) Regarding the 'Custom Tags' (CTs), I noticed a 'Tag' tag within the Document root object but nothing appears in the report so I suspect this 'Tag' tag feature is not supported/implemented. In consequence, the attached file doesn't include any CTs MLFs.

For the Users using MLFs, extract the .zip file, copy/move the extracted Dir into your Skins Dir and run a report.
I tested the attached with my own tree, including many additional dummy MLFs, and the Report looks fine.
Thank you,
JC

Update: the attached file 12th May 2008

	Post Attachments
	Customized_Display_Multi-Lang_Fields.zip (0 views, 3.97 KB)

GenoPro 2007 does not have a tag ID for those objects.  The rationale is those IDs were unused by GenoPro, since no object would link them.  For instance, it is impossible to create a link to a label or a shape.  The lack of a unique identifier for every object prevents a third party to store the XML in a relational database.

We have fixed this issue for the next version.  The version we are currently using has a dedicated ID for every object - this is a requirement for the collaboration module since we need to compare and merge objects based on the XML content from