Hi everybody, I just tested The Gendoc tool (so I use the 2.3rpc for win).
A few questions/remarks : A) I've tested it on a small example that is dlable on the website to test the states machine : CDPlayer.uml and on a small example, I've made. I cannot choose the class diagram as a root container. Is this normal ? B) there are image quality differences on my example than the one in TPC_2.3_GenDoc_Tutorial... The generated images are not resized correctly. I tried to modify this, but I did not see any changes. This is annoying since the document is not readable at the end. C) What would be nice is to add automatically (if possible) the description of the contains of the model (If you add a description for the model, and/or a reference document, add it automatically for example). D) Do you plan to add the class architecture, or more "textual" information than the generated images ?(classes, packages, different kind of links ... ) Regards, Pierre Pierre Moro, ASTRIUM ST Tel: +33 (0)1 39 06 72 64 Fax: +33 (0)1 39 06 27 97 Site: LES MUREAUX BD: 19 Floor: 1 Room: 141 > -----Message d'origine----- > De : [email protected] > [mailto:[email protected]] De > la part de Thibault LANDRE > Envoyé : lundi 12 janvier 2009 15:59 > À : [email protected] > Objet : Re: [Topcased-users] two questions on the new > document generation > > Hi Francesco, > > Francesco Lanteri a écrit : > > Hi everybody, > > > > I have some questions about the new document generation > mechanism in > > Topcased 2.3.0. > > First of all, I downloaded and followed with success the document > > generation tutorial. Now, I have some questions: > > > > 1. I succeeded in generating a .docx (word) but not an odt > (actually, > > I got the file but it's empty). In both cases I used a > .docx template > > done with MS Word and the macros, as in the tutorial example. > > Question: is the .odt generation already implemented? > Yes. > If you want to create an odt, you need a template in odt format. > With Gendoc, we just insert fragments (coming from the > generation) in an existing document. > We don't transform the whole document. > > We assume that the user interface needs some improvments. > Gendoc is still experimental and a lot of work is still required :) > > > 2. I noticed that, after the importation of the template, the file > > having the extension ..docx.gendoc may be modified in the Topcased > > editor, not only by completing the missing fields as > described in the > > tutorial, but also adding new entries that weren't in the original > > template (e.g a new chapter, a new Model Data Source etc, in other > > words, at a first glance, more or less the same work macros do when > > working in Word on a template). This could be interesting > as it would > > be quicker than modifiyng within Word and the re-importing. > > If I try to do that, however, the generated document does not > > incorporate the changes, i.e. its layout and its entries are still > > those in the original .docx template. > > Here, the question is: what is exactly the role of the > .docx template > > and what is the role of the ..docx.gendoc? What changes to the > > .docx.gendoc are allowed once the template has been imported? > > The .docx template is the skeleton of the final document. > It contains all the tags needed for Gendoc to insert the > fragments, obtained through generation, into the document. > You can add a fragment in your .docx.gendoc but you will have > to add the corresponding tag into the template document. > Otherwise the fragment won't be inserted. > > This mechanism will probably evolve. The .docx.gendoc would > maybe disappear and be replaced by a wizard. > > > Regards, > > Thibault > > Thanks a lot, > > Francesco > > > > > > > -------------------------------------------------------------- > ----------------------------------------- > > > > Questa comunicazione contiene informazioni confidenziali ed > e` riservata > > esclusivamente ai destinatari. Se ritenete di averla > ricevuta per errore > > o di non essere il corretto destinatario siete pregati di > eliminare il > > messaggio senza stamparlo, copiarlo, distribuirlo o usare questa > > informazione in alcun modo, e di notificare l'errore al mittente. > > > > This communication contains confidential information and is > intended for > > the named recipient(s) only. If you believe that you have > received it in > > error or that you are not the intended recipient, do not > print, copy, > > disseminate or use this information in any way, and notify > this error to > > the sender. > > > -------------------------------------------------------------- > ------------------------------------------ > > > > > > > > > -------------------------------------------------------------- > ---------- > > > > _______________________________________________ > > Topcased-users mailing list > > [email protected] > > http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users > _______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
