EA 5.0 Document Generation

[michael_rainwater]

The new document generation looks good (as I have just started viewing it).  I am excited about the possibility to actually create my own cool templates for generating documents.  I am also excited about the prospect of actually generating a complete document (including title page, table of contents, etc) all from within EA.  This is very nice.

I was surprised (at least a little) in the inconsistency in which this seems to be implemented.  I am hoping this is because I am using a beta and it is not complete yet.

But I will not find this new feature to be useful unless I can use it with "virtual documents".  I use the virtual document feature extensively to allow me to select a number of packages in a given order for a particular document.

Perhaps I can get around this by using the new features (which I have yet to figure out) for transforming my model.  If I can literally copy the packages into another package in the order I want, and transform them... then maybe this should replace the entire need for virtual documents.  I could have my source information, and then transform into other packages with different organization for each document I want to create.

Anyone -- Am I on the right track with this at all???

If not, is it intended to have the new RTF Generator available for virtual documents in the 5.0 release??

I am willing to accept alternative ideas.  :-)

Thanks

[potterm]

I agree - the ability to be able to define RTF templates in the new style (on a per package basis) and then drag each of those packages into a Virtual Document and have the new templates applied would be very powerful.

I'm kind of surprised that Sparx didn't add support for this in the new version - the mix of new style RTF templates and old (RTF template) style virtual documents seems abit of a cludge.

Presumably the plan is not to support the legacy report generation forever, in which case does this mean that Sparx will add this feature, or will we lose Virtual Document support completely?

Thanks,
Martin.

[thomaskilian]

Add my vote. Either you do it the one or the other way. This legacy switch is purely nonsense. Sparx has to maintain both styles and they have to pay for that. I'm also missing support for the virtual documents. PLEASE Sparx: Dare to cut. Step to the new RTF styles in all respects and throw away the old functions.

[KP]

Add my vote. Either you do it the one or the other way. This legacy switch is purely nonsense. Sparx has to maintain both styles and they have to pay for that. I'm also missing support for the virtual documents. PLEASE Sparx: Dare to cut. Step to the new RTF styles in all respects and throw away the old functions.

We've kept the legacy RTF generator because we have many thousands of users who have invested many thousands hours in setting up their documentation to look exactly how they want it and if we made them all change report styles in mid-project they would all beat us with sticks (and rightly so). We hope people will use the new RTF generator for all new documentation so we can remove the legacy generator at a future date.

Regarding virtual documents, they're on the way...  

[michael_rainwater]

Regarding virtual documents, they're on the way...  

Thank You!  I look forward to this.

I also want to compliment you on the way you allow switching between the two.  But here is an idea you might want to consider to help people make the switch.

In the options screen, create a new option like this:
[ X ] Use Legacy Report Generator.  If this option is checked, you can show the legacy screen (in all places).  But for those who have moved on... they can uncheck and always get the new screen.  This way, you have the consistency we all beg for.  Either do it one way or the other.  If the user gets to choose, then that is fine.  But it is still consistent.

At some point, you could begin displaying a warning that the legacy method is being removed.  Then, be brave and actually remove it.  I know it's hard.

I once heard a user say (about a different product) that it was "like my garage... they never throw anything out."  That could be true of many products.  Let's not let it be true of EA.

There are always good ways to form a sunset strategy (even for a feature).  But I think consistent use of the same report generator everywhere would be a real big plus.  And your new one is better... so let's keep it. :-)

Now -- Do you have anything more specific on when I might be able to use this on virtual documents?  You are such a tease.  

[Paolo F Cantoni]

Thank You!  I look forward to this.

[SNIP]

Thanks Michael, couldn't have said it better myself...  So I won't!

Paolo

[potterm]

Regarding virtual documents, they're on the way...  

Many thanks KP - that was the news I was hoping to hear.  Good work on the new 5.0 version BTW - glad to see that EA is keeping the momentum up with new features.

regards,
Martin

[dave_Mathews]

The 5.0 rtf generation is an improvement, but it doesn't appear that styles can be applied at a very low level.

For example, I can apply a single style to the {Pkg.Notes} element in the template, but it applies to all content in the Notes field for the package.  What if I want to apply multiple styles to the content on the Notes field? A simple example would be applying a normal style  to the first paragraph and a bullet style to the list items below it.

Related to this, applying a style to an element property applies to all instances of the property in the output. For example, can I format some Notes for some packages as a bullet list, but Notes for other packages as a numbered list in the same document?

I couldn't find an answer for this in the help or searching this forum, so would appreciate any feedback.

   

[michael_rainwater]

Related to this, applying a style to an element property applies to all instances of the property in the output. For example, can I format some Notes for some packages as a bullet list, but Notes for other packages as a numbered list in the same document?

I believe what you are looking for are RTF notes.  This is something that has been requested by several people on this forum.  I am not sure of the status of being able to create notes with rich text.  I have many times I would like to do this (just to bold a word, etc).

I thought I read somewhere that Sparx was working on that.  Then, you could place your RTF formatting within the given note and you wouldn't need to apply the style to the RTF template.

[kgish]

I would like to push for better documentation in general for all the RTF-document stuff as there are still many things which are unclear to me. Thanks alot in advance.