XSLT - Resolve some speed issues!

[Hal Jenkins]

Hi all

Just a quick 'tip' for converting FP5/CDML solutions to FP7/XSLST. I am in the process of converting a reasonably complex (for me anyway) system. I was having alot of performance issues and spent alot of time messing around, almost giving up.

The solution consists of about 8 FMP files, that I haven't consolidated, I just did a straigt conversion and fixed any breakages. The problem that was causing the speed issues was bad file references. So, the first thing you should do when converting your 5 databases to 7 is FIX YOUR FILE REFS.

This changed the requests from being painfully slow, to acceptable... (still a touch slower than CDML, but hey, FMP7 is worth it!).

I hope this saves someone some time and hair.

Have a good day

Halski

Edited September 1, 2005 by Guest

[Martin Brändle]

This is not only true for CWP. Fixing file references during migration from pre-v7 to v7 speeds up the databases in general. There are tools like MetaDataMagic from New Millenium that help to clean up your solutions and to analyze them for possible conversion issues. They are really worth their price.

[Pjotr]

Mr Brändle,

I am surfing through this forum for the first time and I notice that your name shows up a lot.

In this particular case you answer to Hal jenkins.

Right now I am working on the conversion of an intranet. It's build in FM5 with CDML.

I found out about the file references and fixed everything until the manual fixing of the XSLT codes.

I used the CDML converter for the pages and I can enter the index.xsl page. What I can't get fixed is basically the dynamic valuelist.

Filemaker has the site assistant but the, working, valuelist-sourcecode doesn't work in the converted XSLT pages when I copy it into this page.

Do you know where I can get some kind of tutorial that explains to me step by step what to do with the XSLT code for FM.

[Martin Brändle]

Check p. 57 of the FMS7A Custom Web Publishing Guide, "Using a database’s layout information in a stylesheet", which shows an example of a dynamic value list, and Appendix C.

If there are still problems, you might post your XSLT file here in the forum.

[Pjotr]

plan2.xsl

Zoekpagina Papier

Let op : Alle gegevens zijn onder voorbehoud!! (Zie

memo Centrale Inkoop)

�

�

�

Index

Inkoop

�

�

�

�

�

�Leverancier

�

contacts::leveranciers_naam

Selecteer...

�

�Naam

Fabriek

�

fabriek::naam_fabriek

Selecteer...

�

�Soort

druk

�

Gravure

HSWO

CSWO

�

�Papiersoort

�

Boek

Courant

Directory

HVMC

HVO

LWC

MFC

SC Standaard

SC-B

SC-Cat

SC-K

SC-plus

Verb. Cour.

�

�gramsgewicht

�

�

�

�

�

�

�Papiernaam

�

�

�Machinebreedte

(bv 5, 53 of 538)

�

�

�Brightness

% ISO (bv 7 of 78)

�

�

�ISO

certificering

�

14001

9001

9003

�

�Productlabel

�

Blauer Engel

FSC-waardig

Nordic Swan

PEFC

�

�

�

[Martin Brändle]

QName means qualified name. If you can understand the W3C XML namespace definition in http://www.w3.org/TR/REC-xml-names/#ns-qualnames and http://www.w3.org/TR/REC-xml-names/#ns-decl, you will see that QNames are only allowed to start with a letter.

in cdml2xsl_includes, you use often

where "1Inkoop-..." is the QName.

You should replace "1Inkoop" with something like "oneInkoop", of course in all in cdml2xsl_includes, and in all

used in 1Inkoop/adm_pap_grsgew/pages/errorreplya.xsl and all files so on.

[Pjotr]

Martin,

Thanks for handing me the solutions so far. So far I am going smooth with the conversion with XSLT.

There are still a view things not clear but there is progression. Do you know if the usage of portals needs something special? In the converted files the 'portal codes' are working only the result of different fields that are next to eachother are published underneath eachother.

example:

result in fields is cities and area telephonecodes

Amsterdam 020

Rotterdam 010

Den haag 070

The published result is

Amsterdam

Rotterdam

Den haag

020

010

070

Top

Contactpersoon RSDB:

Functie:

Mobielnummer:

Opdrachtgever: 

 

edit.xsl?-db=kennisacts&-lay=web&kennisacts::currentrecid=&-find

Wijzig

& Delete

results1.xsl?-db=kennisacts&-lay=web&-script=maak&-sortfield.1=kennisbank::currentrecid nieuwe activiteit&-recid=&-Find

Nieuw

---

Before you start answering I would like to show my appreciation for helping me. Is it ok with you that I email you personally? I hope you are not offended by my offer you just helped me enormously allready!

Best regards

Ronald Post

[Martin Brändle]

Ronald,

just a comment: You should open a new thread and not reuse an existing thread if the subject is different.

No, do not write a private e-mail to me. Others are also interested in the result of the discussion happening here in the forum.

I did not see the fields cities and area phone code in your XSLT code.

You might also consider to rebuild the layout, see this thread: http://www.fmforums.com/forum/showtopic.php?tid/156998

[Pjotr]

Martin,

Thanks for the response. The private email is misunderstood. Ofcourse I understand that everybody can see and participate in the forum.

I am very pleased with fact that I can find help on the forum. And I hope that my questions and the solutions to that are helping others again.

The example with the cities is not existing. I just wanted to give a simple idea what I see in my browser.

Best regards

Ronald Post