Difference between revisions of "Google Summer of Code/Project Ideas"

From BRL-CAD
(recategorize the gui projects)
(make the task descriptions sub-context information)
Line 9: Line 9:
 
== Graphical User Interface (GUI) Projects ==
 
== Graphical User Interface (GUI) Projects ==
  
BRL-CAD uses the concept of a '''''display manager''''' to visualize 3D geometry, wireframes, text and more within a graphical windowOne of our project goals is to implement a ''new'' display manager using a cross platform toolkit that hides implementation detail so we can use one display manager across multiple platforms.
+
The primary environment in which users interact with BRL-CAD geometry is the MGED geometry editor.  The "next generation" interface for MGED, dubbed ''Archer'', has been under development for some time as the follow-on interface but there is a lot more migration of functionality still requiredMost of the tasks below relate directly to either MGED, Archer, or both.
  
* [[Cross Platform Display Manager]] (C/C++)
+
* [[New Cross-Platform 3D Display Manager]]
 +
**BRL-CAD uses the concept of a '''''display manager''''' to visualize 3D geometry, wireframes, text and more within a graphical window.  One of our project goals is to implement a ''new'' display manager using a cross platform toolkit such as Qt or OGRE so we can use one display manager for most platforms.
 +
**Language: C/C++
 +
**Difficulty: medium
  
In addition to the 3D display manager, BRL-CAD also implements 2D '''''framebuffers''''' to display images.  For now, you can think of it as a simple 2D graphics context in a window.  Having a single cross-platform framebuffer interface built upon a common framework is very desirable.
+
* [[New Cross-Platform 2D Framebuffer]]
 +
**In addition to the 3D display manager, BRL-CAD also implements 2D '''''framebuffers''''' to display images.  For now, you can think of it as a simple 2D graphics context in a window.  Having a single cross-platform framebuffer interface built upon a common framework is very desirable.
 +
**Language: C/C++
 +
**Difficulty: medium
  
* [[Cross Platform Framebuffer]]  (C/C++)
+
* [[MGED to Archer Command Migration]]
 +
**Command functionality is being moved out of MGED into LIBGED and then shared between MGED and Archer. MGED has more than 700 commands.  Archer presently has around 100 with 100-200 more to go before it will be ready for production use.
 +
**Language: C and Tcl
 +
**Difficulty: medium
  
The primary environment in which users interact with BRL-CAD geometry is the MGED geometry editor.  The "next generation" interface for MGED, dubbed Archer, has been in development for some time as the new follow-on interface.
+
* [[MGED Sketch Editor Migration and Enhancement]]
 +
** MGED has a terribly cumbersome 2D sketch editor written in pure Tcl/TkArcher, however, has nothing.  This task involves working on either or both, but should concentrate on at least providing a usable interface within Archer.
 +
** Language: Tcl (presently) and/or C
 +
** Difficulty: hard
  
* [[MGED to Archer Command Migration]]  (C/Tcl)
 
* [[MGED Sketch Editor Migration and Enhancement]]  (Tcl)
 
 
* [[Ayam Editor Feature Integration]]  (C/Tcl)
 
* [[Ayam Editor Feature Integration]]  (C/Tcl)
 
* [[Analytical Raytracing Visualization]] (C)
 
* [[Analytical Raytracing Visualization]] (C)

Revision as of 00:12, 24 March 2011

The list of possible projects below should serve as a good starting point for new developers that would like to get involved in working on BRL-CAD. The ideas below range from the very hard and math intense to the very easy, see the link to each for more details. You are also welcome to scale the scope of the project up or down as needed as the ideas suggested below are merely starting points.

A detailed articulate (i.e. excellent) proposal that has been discussed with us beforehand will generally trump any listed priority. Please do contact us (IRC or brlcad-devel mailing list) if you have any questions, corrections, comments, or ideas of your own that you'd like to suggest.

Be sure to read up on our application process for getting started with your proposal submission if you have not done so already including our checklist.

Project Categories

Graphical User Interface (GUI) Projects

The primary environment in which users interact with BRL-CAD geometry is the MGED geometry editor. The "next generation" interface for MGED, dubbed Archer, has been under development for some time as the follow-on interface but there is a lot more migration of functionality still required. Most of the tasks below relate directly to either MGED, Archer, or both.

  • New Cross-Platform 3D Display Manager
    • BRL-CAD uses the concept of a display manager to visualize 3D geometry, wireframes, text and more within a graphical window. One of our project goals is to implement a new display manager using a cross platform toolkit such as Qt or OGRE so we can use one display manager for most platforms.
    • Language: C/C++
    • Difficulty: medium
  • New Cross-Platform 2D Framebuffer
    • In addition to the 3D display manager, BRL-CAD also implements 2D framebuffers to display images. For now, you can think of it as a simple 2D graphics context in a window. Having a single cross-platform framebuffer interface built upon a common framework is very desirable.
    • Language: C/C++
    • Difficulty: medium
  • MGED to Archer Command Migration
    • Command functionality is being moved out of MGED into LIBGED and then shared between MGED and Archer. MGED has more than 700 commands. Archer presently has around 100 with 100-200 more to go before it will be ready for production use.
    • Language: C and Tcl
    • Difficulty: medium
  • MGED Sketch Editor Migration and Enhancement
    • MGED has a terribly cumbersome 2D sketch editor written in pure Tcl/Tk. Archer, however, has nothing. This task involves working on either or both, but should concentrate on at least providing a usable interface within Archer.
    • Language: Tcl (presently) and/or C
    • Difficulty: hard

Core Geometry Processing Projects

Core Analysis & Rendering Projects

NURBS (Non-Uniform Rational B-Splines) Projects

BRL-CAD has recently implemented raytracing support for NURBS-based boundary representation geometry. There are several remaining tasks to be done with NURBS, most of them are very high impact and very high visibility. They are also pretty hard so be careful to have lots of milestones. Strong math background and/or familiarity with computer graphics representation types is highly recommended.

Other Tool Projects

Some of these project ideas aren't as detailed or elaborate as the ones above, but would be interesting and useful nonetheless. Please discuss with us before proposing one of these ideas.

<AN IDEA OF YOUR OWN>

Do you have an idea of your own? Let us know and maybe we'll like it too. We're very open to new ideas, areas of academic research, industry applications, and any other ways that may help get you hooked on BRL-CAD development. Just remember that BRL-CAD is a solid modeling CAD suite so keep that in mind when scoping your project. The idea needs to fit in with our project goals, it needs to be specific, and it needs to be detailed.

Requirements:

  • Passion for the task being suggested
  • Buy-in from one of the existing developers

Difficulty: variable