Hi Tim,
On Saturday 11 July 2009 09:28:21 Tim Moore wrote:
Vote against.
You will need two allocations for a new object that is used with the the
std::shared_ptr implementation - one for the object and one for the
reference count. I like to use that SGReferenced stuff for many small
Mathias Fröhlich wrote:
Hi Tim,
On Sunday 05 July 2009 22:51:32 Tim Moore wrote:
We can now rely on std::tr1:shared_ptr and its cousins, through Boost if
need be, so perhaps we could come up with some nice templates to paper over
the differences between OSG pointers an our own.
Vote
Hi Tim,
On Sunday 05 July 2009 22:51:32 Tim Moore wrote:
We can now rely on std::tr1:shared_ptr and its cousins, through Boost if
need be, so perhaps we could come up with some nice templates to paper over
the differences between OSG pointers an our own.
Vote against.
You will need two
Mathias Fröhlich wrote:
Hi Tim,
On Thursday 25 June 2009 23:58:42 Tim Moore wrote:
Mathias Fröhlich wrote:
Hi Tim,
Seriously, I didn't realize that reducing dependencies on OSG in simgear is
a design goal. That's fine, but I would really prefer to not think about
whether I need to pass
Hi Tim,
On Thursday 25 June 2009 23:58:42 Tim Moore wrote:
Mathias Fröhlich wrote:
Hi Tim,
On Thursday 25 June 2009 10:22:54 Tim Moore wrote:
OK, but in case you hadn't noticed, libsgmath depends on OSG.
Yes I have noticed that change in the quaternion/matrix.
If you mean the
Curtis Olson wrote:
2009/6/23 Mathias Fröhlich
Well, from my point of view. I would prefer to have these.
The reason is to have something self contained here.
Sure we already rely on osg at many places. But if I build an
aplication on
simgear, I hope to have simgear
Hi Tim,
On Thursday 25 June 2009 10:22:54 Tim Moore wrote:
OK, but in case you hadn't noticed, libsgmath depends on OSG.
Yes I have noticed that change in the quaternion/matrix.
I believe that we should get rid of that.
And yes, the vector storage is from osg. But it is a few line change to get
Mathias Fröhlich wrote:
Hi Tim,
On Thursday 25 June 2009 10:22:54 Tim Moore wrote:
OK, but in case you hadn't noticed, libsgmath depends on OSG.
Yes I have noticed that change in the quaternion/matrix.
If you mean the methods in SGGeod that return osg::Matrix, I wrote them
that way because
Hi Tim,
On Saturday 20 June 2009 19:46:50 Tim Moore wrote:
Actually, I am using osg::Vec3d and osg::Vec4d. I tend to view the SGVec
types as redundant, but that's a personal preference. I don't mind using
SGVec in the property system, but if I do that I would like to add an
operator to
2009/6/23 Mathias Fröhlich
Well, from my point of view. I would prefer to have these.
The reason is to have something self contained here.
Sure we already rely on osg at many places. But if I build an aplication on
simgear, I hope to have simgear classes there. SGProperties are simgear
Hi Curt, Tim,
On Friday 12 June 2009 20:10:17 Curtis Olson wrote:
I have one concern that I may not have voiced clearly before.
Well, I believe that I have to contribute here :)
I tend to think about these design choices in terms of what is often called
orthogonality. The idea stems from
Mathias Fröhlich wrote:
On Friday 12 June 2009 20:10:17 Curtis Olson wrote:
So as you speak of adding Vec3 and Vec4 types to the property system, I
immediately have orthogonality concerns. We seems to be adding a
specialized core type that is only good for one purpose along with the
Curtis Olson wrote:
Hi Tim,
I have one concern that I may not have voiced clearly before.
I tend to think about these design choices in terms of what is often
called orthogonality. The idea stems from the world of vectors.
...
So if you translate that concept over to computer
Tim Moore wrote:
I mostly agree with this, though I continue to maintain that the new types
are fully in the spirit of the property system, moreso than array types would
be. I'd also suggest that no one here knows the right answer to this question,
making the option of playing with the new
On 12 Jun 2009, at 17:39, Tim Moore wrote:
So, I propose to add an argument to readProperties that controls
whether or not the new
property types are recognized. By default they are not, so only code
that explicitly calls
for them will be able to use them.
Seems entirely reasonable to
On Friday 12 Jun 2009, Tim Moore wrote:
[snip...]
... I simply don't want to write files that use the more
verbose alternative...
[snip...]
I must commend your honesty.
LeeE
--
Crystal Reports - New Free Runtime and
Hi Tim,
I have one concern that I may not have voiced clearly before.
I tend to think about these design choices in terms of what is often called
orthogonality. The idea stems from the world of vectors.
The idea of orthogonality is if you want to represent any point in 3d space,
you can do it
17 matches
Mail list logo
