Add Transform Helper methods

[Bayslak]

Objective

• The objective of this PR reflects the idea of adding some helper methods to Transform to avoid cumbersome way of providing direction and moving an object. The issue taken in consideration is the following: Helper methods on Transform

Solution

• I decided to add a basic translate method in the Transform class translate(&mut self, direction: Vec3, speed: f32, delta_time_seconds: f32). This function simply provides a faster way of adding a translation to the Transform by providing a direction, a speed and a delta_seconds (or delta in general referring to time). This doesn't take in account the rotation of the Transform.
• I also added a second function translate_with_local_rotation(&mut self, direction: Vec3, speed: f32, delta_time_seconds: f32). This function differs from the one above because it also utilizes the rotation of the Transform to provide a way of moving the object following a specific direction and taking in account also it's rotation.

Testing

• I didn't test the new function, but I changed the example translation.rs using the newly implemented function translate to see if the result was the same.
• I also tried the second method translate_with_local_rotation by modifing the example 3d_rotation and adding a new line just after the rotation. It moved as expected, but the addition of the line felt like out of scope of the example, so I removed it.

[github-actions]

Welcome, new contributor!

Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨

[IQuick143]

I think we should merge direction and speed into a single velocity: Vec3, else we're adding redundant ways to specify speed.

Alternatively if we really want to separate direction and speed (which in my opinion is not a necessary requirement since we multiply them back together anyway). It'd be best to use a Dir3 type for the direction, as it ensures the direction vector is normalised (length 1).

[Bayslak]

I do like your suggestion to be honest.
Didn't think about using the velocity as the result of the multiplication of direction and speed.

Going to implement that straight away!

[IQuick143]

Overall I think the code is good, I'm not sure on the naming though.
I feel like translate should take an offset vector, and translate the Transform by that value.
This is more related to velocities and kinematics (moving objects over time).

Not sure what would be a better name.

[Bayslak]

Overall I think the code is good, I'm not sure on the naming though.
I feel like translate should take an offset vector, and translate the Transform by that value.
This is more related to velocities and kinematics (moving objects over time).

Not sure what would be a better name.

I see what you mean.

Maybe to make it more coherent might be better to only have a Vec3 as the signature of the method, calling it translation and let the user create the translation vector by multiplying it by the speed AND the delta time?

[Bayslak]

Going to change it later to only receive a Vec3