Think over how the demo codes should look like

[Alpar Juttner]

Some basic principles:

• The demos should be simple and easy to understand.
• They should read the graphs from a file instead of creating them by hand. (Except the one which demonstrates how to build and modify a graph.)
• We should provide a limited number of general input files instead of a lot of demo specific ones.
• The command line syntax should be uniform, we should use ArgParser everywhere.

[Peter Kovacs]

#81 have been postponed. Shouldn't we postpone or close this ticket, too?

[Alpar Juttner]

Replying to kpeter:

#81 have been postponed. Shouldn't we postpone or close this ticket, too?

Yes, we should.

[Peter Kovacs]

These guidelines will be relevant for the demo files that will be involved in the tutorial, and even more for the more complex ones that will be put in the repo.

Should we close this ticket then? Or should we keep it until we port some complex examples to the repo?

[Alpar Juttner]

Now, it is quite clear that the majority of the demos will go to the tutorial instead. Some kind of hello_lemon.cc would still be nice in the main repo, but it isn't urgent at all.