dadie / dfm-toolkit Goto Github PK

libdfm should be able to be compiled on Windows and for Windows.

I haven't yet tried to compile the library on or for Windows but it's likely that at least because of the used function ::iconv() some changes are required to support building for/on Windows.

Currently only the plain text dfm format is supported as I'm lacking examples of the older binary dfm format used on older version of Borland Delphi.

Add support for the BMP DIB of Type BITMAPV4HEADER.

Currently the weeder for the parse tree while having a configuration it's not available for users of the library. Each possible configuration should be tested to make sure a valid ast can be generated from the more or less weeded parse tree.

It could be as simple as adding another argument to dfm::pt::weed().

Example files for TImage objects are needed.

For each example file the following information should be provided:

1. expected output image(s)
2. RAD Studio Version which which they were created (e.g. RAD Studio XE)

Using this information a test should be defined.

This might also include <=> operators for each dib type, pixel type, pixel array type and dfm::utils::image::basic_bmp

Currently aside from padding no configuration is available for the formatted dfm output of the ast.

The following options should be available:

• Column limit (n, default:120)
• Use tabs (yes, no, default: no)
• Tab width (n, default: 8)
• Indent width (n, default: 2)
• Empty inline objects in one line (yes, no, default: no)
• Binary string column limit (n, default: 64)
• Escape non ASCII characters (yes, no, default: yes)
• Space before trailing comment (yes, no, default: yes)
• Reflow comments (yes, no, default: no)
• Break before braces (yes, no, default: no)
• Break before comma (yes, no, default: no)
• Break after braces (yes, no, default: yes)
• Break after comma (yes, no, default: no)
• Align assigns (left, right, none, default: none)
• Newline (cr, lf, crlf, preserve, default: preserve)

Currently the weeder for the tokens while having a configuration it's not available for users of the library. Each possible likely configuration should be tested to make sure a valid parse tree can be generated from the more or less weeded tokens.

It could be as simple as adding another argument to dfm::lexer::weed().

Argument was added to the function dfm::lexer::weed() but tests are still missing.

Add check if the given token in the cfg parser of rule VALUE_STRING_ELEMENT_STRING is valid. For more information/context see

To make template types more readable the declaration and definition of member functions should be separated.

Before

template<typename A>
struct B {
    RetTypeC MemberFnD(ParamE e){ /* Do Stuff */ return {}; }
    RetTypeC MemberFnF(ParamE e){ /* Do Stuff */ return {}; }
    RetTypeC MemberFnG(ParamE e){ /* Do Stuff */ return {}; }
    RetTypeC MemberFnH(ParamE e){ /* Do Stuff */ return {}; }
};

After

template<typename A>
struct B {
    RetTypeC MemberFnD(ParamE e);
    RetTypeC MemberFnF(ParamE e);
    RetTypeC MemberFnG(ParamE e);
    RetTypeC MemberFnH(ParamE e);
};

template<typename A>
RetTypeC B<A>::MemberFnD(ParamE e){ /* Do Stuff */ return {}; }

template<typename A>
RetTypeC B<A>::MemberFnF(ParamE e){ /* Do Stuff */ return {}; }

template<typename A>
RetTypeC B<A>::MemberFnG(ParamE e){ /* Do Stuff */ return {}; }

template<typename A>
RetTypeC B<A>::MemberFnH(ParamE e){ /* Do Stuff */ return {}; }

Currently expressions are mostly ignored and simply stored as a list of tokens in the abstract syntax tree. Instead the expression (e.g. 1+2+3+4 or 'abc'#50'def') should be parsed so they could be (partially) evaluated if requested.

Add support for the BMP DIB of Type BITMAPCOREHEADER.

Add support for the BMP DIB of Type BITMAPV5HEADER.

Example files for TImageList objects are needed.

For each example file the following information should be provided:

1. expected output image(s)
2. RAD Studio Version which which they were created (e.g. RAD Studio XE)

Using this information a test should be defined.