Data analysis/visualisation: good practice?

[toshiro]

As an intern, I am writing a tool that reads data from a log file, evaluates the data and uses an existing GUI toolset to visualise that data. Essentially, methods search for specific strings in the log file and use them to write that data in GUI toolset code to new files.

My question now is this: Is it good practice and 'okay' to make my code write the framework for these files, too (specific, non-repetitive code for things like Level of Detail etc.), or should I pre-define 'header' files and just 'include' them (actual implementation works slightly different, but I don't think I should post how it works here...) with the application?

Or does it make no difference which approach I choose?

Edit: I realize this is perhaps not entirely the correct forum, but I wouldn't know where else to put it. Lounge?

[Zaita]

Ideally, you shouldn't write a framework unless it's going to be re-used. This is a common mis-conception among a lot of programmers. They believe that writing framework offers them better flexibility and functionality. In reality, it just takes longer.

If this code has no viable (and be realistic about this) re-use in other projects. I wouldn't worry about a framework and code the solution as simple as possible while offering the functionality you need.

[toshiro]

Thanks, that helps a lot :)