>> > [...]
>> >
>> >>>
>> >>> The Quaternionn class should be placed in the
>> >>> geometry.euclidian.threed package.
>> >>
>> >> I'd propose to put it in the "complex" package. It would thus
stand
>> >> out as a mathematical concept of its own, as you suggest above.
>> >
>> > I agree with Gilles
> > [...]
> >
> >>>
> >>> The Quaternionn class should be placed in the
> >>> geometry.euclidian.threed
> >>> package.
> >>
> >> I'd propose to put it in the "complex" package. It would thus
> >> stand out as a
> >> mathematical concept of its own, as you suggest above.
> >
> > I agree with Gilles
On 7/26/11 11:43 PM, Luc Maisonobe wrote:
> Hi Yannick and Gilles,
>
> Le 27/07/2011 00:37, Gilles Sadowski a écrit :
>> Hello.
>>
>>> In project SIRIUS (CNES), we would like to slightly modify the
>>> Rotation
>>> class so it can fit our needs, and to create an independant
>>> Quaternion
>>> class
Hi Yannick and Gilles,
Le 27/07/2011 00:37, Gilles Sadowski a écrit :
Hello.
In project SIRIUS (CNES), we would like to slightly modify the Rotation
class so it can fit our needs, and to create an independant Quaternion
class.
- Quaternion : We need to separate these two notions : the quatern
Hello.
> In project SIRIUS (CNES), we would like to slightly modify the Rotation
> class so it can fit our needs, and to create an independant Quaternion
> class.
>
> - Quaternion : We need to separate these two notions : the quaternion
> and the rotation representation, because we have to be abl
Hello,
In project SIRIUS (CNES), we would like to slightly modify the Rotation
class so it can fit our needs, and to create an independant Quaternion
class.
- Quaternion : We need to separate these two notions : the quaternion
and the rotation representation, because we have to be able to access
