I'm not sure I understand the data/code mixing argument as it applies to XSL:FO. Are you arguing that the fact that there's margins, colors, and fonts specified in the transformations are the problem?
I guess I see the XSLT that outputs fo as essentially being just a stylesheet. That's it's job. If I've got (via some other XML transform) xml that looks like: <Chapter number="1" title="First"> This is my first chapter. </Chapter> <Chapter number="2" title="Second"> This is my first chapter. </Chapter> It's already formatted for display. The transform to fo doesn't know what any of the data means.. only how it is structured on the page (the same is true for CSS isn't it?) I'm likely missing something here.. ~Phill -----Original Message----- From: Richard Birkby [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 8:53 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Using XML/XSLT to generate WinForm reports Microsoft see xHTML + CSS + SVG as the universal display formatting technology, not XML + XSL:FO. They like XSLT as a _data_ manipulation language, not as a presentation language. The problem with XSL:FO is that it encourages the mixing of data (styles) and code (Transformation templates) which we've all been trying to get away from for the past 7 years. Richard > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of > Phill Tornroth > Sent: 12 April 2002 16:36 > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Using XML/XSLT to generate WinForm reports > > > Ok, not with a ten foot pole.. Seriously? Apache's FOP is amazing, we've > been working with it for documentation and reporting for a over a > year now. > I'm very much planning on using it in our .NET project too. > > On a side note, I specifically asked Mr. Box (and maybe he can comment > further if he's reading) about the lack of XSLT:FO.. I can't > quote him, but > he essentially told me that XSLT wasn't something Microsoft finds all that > valuable. > > I'd LOVE to see more FO implementations. It's a really powerfull tool. If > someone starts a managed FO project.. let me know. > > ~Phill > > -----Original Message----- > From: Erick Thompson [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 11, 2002 5:38 PM > To: [EMAIL PROTECTED] > Subject: [DOTNET] Using XML/XSLT to generate WinForm reports > > > I would really like to use XML and XSLT to generate reports for > viewing in a > WinForm application. However, I can't find a good solution to show the > resulting report. It seems like XML-FO with a PDF or RTF output > format would > be best, but all the projects out there are Java, which I don't want to > touch with a 10 foot pole. I could embed a WebBrowser Ax control and show > the report as HTML, but that doesn't have a lot of appeal for me, > mainly due > to the interop. Can anyone think of a better solution? > > On a related note, it seems like someone with some Java knowledge > could port > these over to C# fairly quickly (J# -> IL -> C#). Is anyone moving Java > projects to C# like this? I would do that for jfor if I know my way around > Java better. > > Erick > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
