Bouml

by **valade** » Thu 15 Nov 2012 07:16

Embedded html written inside any page of use wizard does not seem to work.
In despite of the -tag after all ghtml in all pages of tools settings.

by **Bruno Pagès** » Thu 15 Nov 2012 18:22

The use case wizard saves the information you enter through properties of the use case.
The option -tag only concern the production of the description of the element, not their properties, if you want to extend it I encourage you to modify the HTML code generator

Again, you can modify by yourself the HTML generator and other the other plug-outs like the use case wizard, to follow your own needs, modify them. Also create the additional plug-outs you need, the plug-outs are made for that

by **valade** » Fri 16 Nov 2012 15:30

if I modify the HTML generator, will an update of bouml overwrite my customized generator ? if so, I do not want to customize the plug-in !
Please, might you take this as a new feature ?

by **Bruno Pagès** » Fri 16 Nov 2012 15:57

to not see you changes overwritten by an update just clone the html generator plug-out in a new one (load html generator project, save-as before to modify it), and modify the name of the generated executable.

I insist, by only waiting for changes from me, and worst to not write your own plug-outs to automatize some operations, is a shame because you lose a lot.

Remember the HTML generator as a dual implementation, one in C++ and one in Java, so you can do your changes in C++ or Java depending on the language you prefer

by **Bruno Pagès** » Sat 17 Nov 2012 11:59

valade wrote:Embedded html written inside any page of use wizard does not seem to work.
In despite of the -tag after all ghtml in all pages of tools settings.

Let's note the initial request concerned only the description of the elements, today you ask for the properties set by cap wizard, tomorrow may be additional/all properties, then state's behaviour etc, this is what happens when the specification is not clear enough

To extend to scope of the tag option to all the fields may be a source of problem, and I don't think you always need to produce (unchanged) HTML, so the best seems to indicate explicitly when a (portion of) text must not be protected, for instance to not protect the text between the marks <html> and </html>, and of course to not generate these marks. Of course to be compatible with the previous version the effect of the option tag must be unchanged. So, out of a description, or inside a description but supposing the option tag is not set, the text "a always</html> true" will produces "a always true".

The protected characters are :

'<' : if protected produces <
'>' : if protected produces >
'&' : if protected produces &
'@' : if protected produces @
'\n' : if protected produces
'\r' : bypassed if protected

Are you ok with that ?

by **valade** » Tue 20 Nov 2012 12:27

Perfect !
Might be possible to apply -tag option globally ?

by **Bruno Pagès** » Tue 20 Nov 2012 12:46

I am always looking backward compatibility, to extend the scope of the -tag is incompatible with that, so to unprotected all it is needed to have an other option, let's say -tag_all

by **valade** » Fri 23 Nov 2012 17:17

should be fine !
what about program argument : bouml -tag_all

by **Bruno Pagès** » Sun 2 Dec 2012 22:57

The release 6.4 is available adding -tag_all and <html>..</html> management

Bouml

Doc generation - embedded HTML - use case wizard does not

Doc generation - embedded HTML - use case wizard does not

Re: Doc generation - embedded HTML - use case wizard does no

Re: Doc generation - embedded HTML - use case wizard does no

Re: Doc generation - embedded HTML - use case wizard does no

Re: Doc generation - embedded HTML - use case wizard does no

Re: Doc generation - embedded HTML - use case wizard does no

Re: Doc generation - embedded HTML - use case wizard does no

Re: Doc generation - embedded HTML - use case wizard does no

Re: Doc generation - embedded HTML - use case wizard does no

Who is online