From: Vasiliev M. <mic...@ma...> - 2003-04-01 21:48:54
|
Well, I decided to make a short list of first TODO's we need to perform: 1. Organize command-line driven interface.(e.g. user may enter something like: symphysmodel file.geom ) 2. Make "loger" object and realise it's work with other objects in system.(e.g. in .geom file can be entered something like: mat_dot A x =3D 10 vx =3D 0.1 end mat_dot loger file.log step 100 interface text header "coord, velocity\n" format "%f %f\n" vars A.x,A.vx tailer "data is over..." end loger And in the result user will get file named file.log: coord, velocity 10 0.1 20 0.1 30 0.1 <skipped> data is over... )=20 3. Create the folowing physical objects: Surfaces of different types (planes and triangle systems for begining) Lines of different types (strait line and spline-interpolated curve) External fields (constant,periodical,exponential... and network-based) General massive body (with mass and tensor of inertion) Frequent-used simple objects (levers[=F0=FB=F7=E0=E3=E8], pulleys[=E1=EB=EE=EA=E8],ropes[=E2=E5=F0=E5=E2=EA=E8]). External force sources. Create GUI - with graphical and text-based editors of initial state and real-time drawing of the experiment. Also we need to be able to create video clip about system's life. 4. Organize array support in .geom files, like this: array AAA[6,3,8] type mat_dot x[i,j,k] =3D i y[i,j,k] =3D j*5 z[i,j,k] =3D x[i,j,k] + y[i,j,k] end array may be use yacc/lex for analising of source files? For open discussion:=20 What should be added to this list, or ,may be, what should be removed? Should we organize support for partial differential equestions - driven fields? What do you think about this kind of GUI?(see attachment) |