[gecode-users] Examples

[Christian Schulte]

...and after that we will continue writing documentation for programming
with Gecode: how to program propagators, branchings, search engines, and
variables. Again with step by step examples.

Christian

--
Christian Schulte, www.it.kth.se/~cschulte/

-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Guido Tack
Sent: Monday, February 16, 2009 11:29 AM
To: gecode list
Subject: Re: [gecode-users] Examples

Dear Malcolm,

you're right, the examples are not very helpful as a starting point.   
However, the tutorial documentation we're currently writing (and which  
is going to be available soon) will provide exactly the kind of  
information you're asking for.  The new tutorial examples will be self- 
contained and explained step by step, and the document will cover  
everything that is essential for modeling with Gecode (creating  
variables, posting constraints, search, and compiling/linking).

Cheers,
	Guido

Malcolm Ryan wrote:

> If I may offer a well-intentioned criticism of the Gecode
> distribution, I'd like to suggest that the examples that come with the
> distribution do not serve their purpose well. They do a good job of
> demonstrating the the strengths of the library, but are less useful as
> examples of how to use it. They are simply too complicated, with too
> many options spread over too many files. Trying to single out a
> particular concept, such as 'how to use Gist' or 'how to write a
> custom branching' is tricky. The answer is there, but it is woven in
> among several other advanced concepts, with an option system for
> turning different parts on and off.
>
> It would be nicer to have simple self-contained examples that
> illustrate just one concept at a time and highlight the particular
> code elements that are necessary to make that feature work, keeping
> the number of options down to a minimum.
>
> If you do this, it would make like easier for all of us. Users such as
> myself would find your library much easier to learn, and you wouldn't
> have to spend as much of your time answering our stupid questions on
> the mailing list. While I am very grateful for all your help, I am
> sure we would all like to get on with our work.
>
> Malcolm


_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users