Re: [pygccxml-development] improving user experience

[Roman Y. <rom...@gm...>]

On 7/24/06, Matthias Baas <ba...@ir...> wrote:
> The _logging_ sub-module now contains a new class multi_line_formatter_t
> that splits long messages into several lines. The class is used just
> like the logging.Formatter class. The constructor takes one additional
> argument 'width' (default: 70) that controls the maximum width of the
> generated text blocks. What the new formatter actually does is that it
> modifies the 'message' attribute of a log record (i.e. it inserts
> newlines based on 'width' using the textwrap module).

1. I changed the name of the file to multi_line_formatter.py. I think this
way it more readable
2. I changed a little bit internal logic + how it devides a messages:
    If message is not formatted as we expect, that I just apply wrap
algorithm and return it.
    Otherwise, I leave declaration as is. I don't wrap it. All other lines
starts with '>' sign.

    My editor ( scite ), is able to give a different color to the message. I
assume other editors
    are able to do the same thing too.

    WARNING: unnamed_enums::color [variable]
    > pyplusplus can not expose unnamed variables

> I left the code structure in creator_t._prepare_decls() as it is and
> just converted the messages into single-line messages.

All messages in py++ are now single line messages. From now this is a rule(
law ).

One more thing, I write documentation for "readme" feature. Can you post a
code, that
change multi_line_formatter_t to default one?

Thank you.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/