On Mar 19, 2014, at 3:24 AM, K RAJ KOUSHIK REDDY wrote:
> I have made changes to my proposal with an updated time line. This now has
> time distribution based upon the complexity of the primitive to be
> implemented.
>
> http://brlcad.org/wiki/User:Krajkreddy/GSOC14/proposal#Development_Schedule
>
> Also I have updated my proposal on the Google - melange page.
This is looking pretty great Raj, especially after the updates. Your plan
looks pretty solid now, but a few minor details:
1) Some of the primitives you propose are deprecated/obsolete and scheduled for
removal, so you probably shouldn't focus on them at all, or only later as time
permits. More on these below.
2) My goodness, we don't use CVS! :) That is a specific system which we
haven't used in 10 years. I believe the general term your looking for is a
Source Code Management (SCM) system.
3) I'd like to see some mention for how you plan to go about testing your
implementation. What happens if you run into a primitive that cannot be
wrapped, for whatever reason? Are you going to fix the C code, then return to
the Python wrapping? Are you going to skip it and try to come back to it
later, if so what later task is getting dropped?
4) I see no mention of documentation besides the grandiose summary at the end.
The focus is and should be on the code, but you should plan to spend a small
percentage of your time writing examples (e.g., wiki page) or test harnesses or
some manual page that you expand, etc.
5) It might be helpful to specifically itemize your deliverables -- what actual
tangible items you are planning to produce. You hint at most of them
throughout (like your test script, the wrapped interfaces, a project summary, a
blog entry, etc).
6) Weeks 10-12 are "high risk". That's a lot of time and no detail to account
for it. Note that "brep" and "nurb" are synonymous. Maybe try to find a way
to break that work up into smaller subtasks.
As for primitives, these should probably be skipped: grip, pg (poly), hf, and
bspline (which you don't list, good). These are of lesser priority and
shouldn't have much time invested in them due to their status: cline,
constraints, annotation. I'd rather see a nice wiki page example showing an
example (with images) of how to use the python interface than to focus on any
of those old primitives. However, I defer to your guru mentors on that
decision.
Cheers!
Sean
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
