[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EDUML (Dr. Geo)



On Sat, May 01, 1999 at 09:42:28PM +0800, Hilaire Fernandes wrote: 

> > The first step, I think, is to propose (expose) a list of elements needed for
> > Dr. Geo data and incorporate/merge/harmonize that into/with EDUML
>
> To make life easier I've written down the Dr Geo API declaration to help
> convert XML Dr Geo figure to internal Dr Geo figure. This is a set of
> functions declarations like those ones :
 
> drgeo_point_free (gchar *name, gdouble x, gdouble y); 
> drgeo_line (gchar *name, gchar *point1, gchar *point2);
> drgeo_line_parallel (gchar *name, gchar *point, gchar *line);
> 
> 
> The first argument is always the name of the created object. The others
> arguments are gdouble or gchar (~double and char) 

Do you mean that we can create an assignment file like this:

drgeo_point_free ("A",34,45);
drgeo_point_free ("B",56,78);
drgeo_line ("AB","A","B");

which would create the desired line segment?

which means we can also have:
drgeo_point_free("A",rand(1,100),rand(1,100));

which would randomly select a point (making a unique assignment each time)

in which case, in current EDUML, a geometry <outcome> can call up
drgeo <functions> via <rpc>.

If I am on the right track, I'll write a sample assignment in EDUML for 
testing with DrGeo.

> May be a CVS will help other to jump in the development, Roger ?
You may need to contact Roger directly (not via the mailing list)


Bruno