Re: [brlcad-devel] GSoC 2017

[Oleksandr Dubenko]

Hi,
Yes you are right, I should write more in my dev logs every weekday. That
shouldn't be a problem.

I really think communication is very important and I take it seriously.
W dniu pon., 12.06.2017 o 11:22 Inderpreet Singh 
napisał(a):

> On Mon, Jun 5, 2017 at 1:13 PM, Gauravjeet Singh
>  wrote:
> > If everything works well, I don't think there should be any problem of
> > doing it on BRL-CAD's official server.
>
> Hey Oleksandr
>
> How are you doing? Any updates, questions?
>
> Being a past GSOC student myself, I know updating daily logs daily
> might be tedious. However updating daily logs are  important for
> mentors to check your progress and it also helps in evaluation. As
> there hasn't been much communication otherwise, I advice you to make
> sure you update your daily-diary daily. Even if you haven't done much
> work or you were away, make sure you make an entry in daily diary and
> state so.
>
> Also when you do update your daily diary be as thorough as possible.
> Explain what you did, why you did, what problems you faced and so on.
> All this will help us in better evaluation and we might help/nudge you
> if we think you are going in wrong direction.
>
> Looking forward to more frequent and effective communication.
>
> --
> Ekoankar Sahai
> ishwerdas.com
> facebook.com/okayinder
> https://kippt.com/okayinder
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Re: [brlcad-devel] GSoC 2017

[Inderpreet Singh]

On Mon, Jun 5, 2017 at 1:13 PM, Gauravjeet Singh
 wrote:
> If everything works well, I don't think there should be any problem of
> doing it on BRL-CAD's official server.

Hey Oleksandr

How are you doing? Any updates, questions?

Being a past GSOC student myself, I know updating daily logs daily
might be tedious. However updating daily logs are  important for
mentors to check your progress and it also helps in evaluation. As
there hasn't been much communication otherwise, I advice you to make
sure you update your daily-diary daily. Even if you haven't done much
work or you were away, make sure you make an entry in daily diary and
state so.

Also when you do update your daily diary be as thorough as possible.
Explain what you did, why you did, what problems you faced and so on.
All this will help us in better evaluation and we might help/nudge you
if we think you are going in wrong direction.

Looking forward to more frequent and effective communication.

-- 
Ekoankar Sahai
ishwerdas.com
facebook.com/okayinder
https://kippt.com/okayinder

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Re: [brlcad-devel] Annotations: Implement support for 2D annotations, labels that can be added to geometry

[Daniel Roßberg]

Shubham,

> 1) In which file do you think, the placement flag values should be defined ?

include/rt/geom.h
Other primitives define their flags there too.

> 2) regarding the input. It was decided that the input will be through the
> "in" command:
>- in "parameters"
>- what all parameters are desired ?

The parameters which are needed to fill the rt_anno_internal(?)
structure.  The sketch should be a good template for how it should
look like for the annotation.

> 3) if we talk about line segment , then user can input the point to be
> annotated and the coords of the line segment.
>  but for beizer, nurb etc. we will need the editor. suggestions please.

Again: Similar as for the sketch.  It can be created with an "in" too.
The annotation has a parameter "anchor point in 3D space" plus a list
of 2D segments.  It should be possible to use a large portion of the
sketch code which interprets the TCL input for the annotation.

You should aim for getting a line on the screen.  When you are able to
see what you are doing it will make the live easier.


Regards,
Daniel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel