On Tue, Jul 23, 2013 at 10:28 AM, Christopher Sean Morrison <[email protected]> wrote:
> NURBS are far too complicated to be fully comprehended within the limited > timeframe of GSoC. I wasn't sure at first, but I think that you simply don't > have sufficient background to tackle that right now. I admit it. Even students that take an advanced computer graphics course at the graduate level often to not get to that topic. :) > The suggestion of visualizing NURBS was to originally to use an API in order > to see them. Since an API does not yet exist in the web space, we need a > different target. Actual code progress is now of paramount importance, not > research. This seems to preclude NURBS altogether. > > Rai's suggestion to focus on showing the implicit entities in some other > manner is good. After reading Rai's mail, I started moving in that direction. I tried to read data from .g file. I successfully retrieve database title, version, name of file, and units (although they all are attributes of db_i struct, I accessed them easily using 'dbip', pointer to db_i struct.). Now looking how to get names and attributes of all objects out of g file. <snip> > I suggest focusing on (3) to simply display a polygonal conversion via the > browser so that the emphasis may be on the interface. You mentioned several > times in your development log that you've been working on a layout. It would > be good to see it. Please share what that layout currently looks like. > > If it's on pen and paper, scan it in. If you've implemented the layout as a > working web interface demo, even better. :) Here are wireframes of layout: [0] https://docs.google.com/file/d/0BwbGknrjPgERRmVsdXZxelBVUG8/edit?usp=sharing [1] https://docs.google.com/file/d/0BwbGknrjPgERSXdBOFhMSE5uODg/edit?usp=sharing Actually when I mentioned about layout in development logs, at that time I was focusing on it with different approach (one mentioned in the proposal). But after taking yours and Rai's suggestions, I redesigned them; sorry for not sharing a working demo but these front-end layouts are made just side by side while thinking about the following working and implementation of project: User will be able to see geometry in two steps: 1. Upload .g file. 2. Select entity to display. In (1), the uploaded g file scanned and names of all entities displayed in 'Geometry Browser' (see [0]). Then user selects an entity to display its geometry. As an entity is clicked in geometry browser, the corresponding OBJ file produced immediately in the back-end then passed to webGL and finally visualized on browser. I will use ThreeJs library for this project because of the following features: 1. Support for polygonal OBJ files. 2. CSG support. 3. NURBS support: Work in progress. 4. Vibrant user community and support. Implementation of all above will be done after mid term evaluations. In the mean time before evaluations, I will (1) display a standalone BRL-CAD model on browser and (2) retrieve names of all objects from g file. -- Harmanpreet Singh Blog: http://singhharman.wordpress.com/ ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
