0.16 Features We'd Like To See

[wmayer]

Imagine you have a model with a few dozens of objects what a big mess this will become. Maybe such a chart could be additionally used to the tree view but I really doubt that it can replace the tree view.

[rockn]

Perhaps a small feature could be the ability to refresh the Grah Dependency. AFAIK we have to relaunch it and so open a new grah dependency window.

[quick61]

Perhaps a small feature could be the ability to refresh the Grah Dependency. AFAIK we have to relaunch it and so open a new grah dependency window.

+1 Having a refresh/recompute function for the current dependency graph would be a very nice feature.

Mark

[bejant]

1 Having a refresh/recompute function for the current dependency graph would be a very nice feature.

I'll suggest also allow the user to zoom in / out of the the Dependency Graph window.

Add Cross Section and symbol (diameter, GD&T, etc.) support.

When I saw the welding symbols in Hamish's Drawing plug-in, I thought GD&T would be handy there too.

[saso]

The tree and graph view have also been two things on my mind, but my ideas around them have been to improve them, but keep them separated as they are now.

The thing that bothered me with the dependency graph was that it is IMO such an important and useful tool but it depends on graphviz, so is generally not directly available on windows by default and one has to download an ~35 mb install just to see one simple image and there is not much one can do with this image in the end. So I was looking for something that could work out of the box on all FC supported platforms, would be more simple / smaller from the package / code side and more powerful for the user. My idea and research was in to html / javascript. Googling a bit around I found there are a few projects around this, some also still based on graphviz, and I am sure it could be further extended for things like zoom, pan, group ???, cluster ???, ... (did not yet research what would be the best way to go forward).

https://github.com/mdaines/viz.js/
https://github.com/cpettitt/dagre
https://github.com/cpettitt/dagre-d3
https://github.com/cpettitt/graphlib-dot
https://github.com/gyuque/livizjs
https://github.com/bpartridge/graphviz.js
https://www.nodebox.net/code/index.php/Graph
https://code.google.com/p/canviz/ (requires graphviz? must find something that does not!)
http://visjs.org/ https://github.com/almende/vis
http://arborjs.org/ https://github.com/samizdatco/arbor

http://www.ryandesign.com/canviz/ DEMO
http://arborjs.org/halfviz/#/journey-under-the-sea DEMO
http://arborjs.org/halfviz/#/python-grammar DEMO
http://arborjs.org/atlas/ DEMO
http://theantworks.herokuapp.com/industry-report/tesla/ DEMO with also zoom and pan
http://visjs.org/examples/network/graph ... llery.html DEMO with also zoom and pan
http://www.lexmath.com/grafos/sigma/eje ... sters.html DEMO with also zoom and pan

http://stackoverflow.com/questions/7034 ... javascript
http://socialcompare.com/en/comparison/ ... -libraries

---

And about the tree view... My idea / wish (not directly connected to the dependency graph as discussed by others) was to simple add an option to make the tree view work in two different modes. the first would be to keep it as it is now, the second / new mode however would be to split the tree view in two views. In the first we would have only model related objects (basically things that are in the dependency graph) and in the second we would have all the other stuff (lets call them documents for now).

[tom]

I would like to see a working topological naming. FreeCAD wants to be a parametric modeler. But in all my previous models that were more complicated than a simple cube a change of a parameter in an early stage of the history messed up the whole model, because many of the references edges and face got a new identity. I understand that this problem is difficult to solve, but I fear that the more new features are added to FreeCAD the more difficult will be the introduction of a working topological naming.

[drei]

An alternative Tree Representation to show the dependency graph instead of the current hierarchy.

And with what kind of widgets would this be possible? As a simple example use a diamond structure where you have an object A, then B and C which depend on A and then object D which depends on B and C. If a tree is used you can solve this only by showing multiple items of certain objects -- i.e. show A as a child of B and C in this example.

How do commercial cad applications handle this?

I'm not sure how other CAD appications handle such dependencies, but it seems that LabVIEW has some ideas that could be used.

labview_dependency_example.png (265.95 KiB) Viewed 914 times

I can post other examples if someone is interested.

[rockn]

Perhaps a small feature could be the ability to refresh the Grah Dependency. AFAIK we have to relaunch it and so open a new grah dependency window.

+1 Having a refresh/recompute function for the current dependency graph would be a very nice feature.

Mark

http://www.freecadweb.org/tracker/view.php?id=2058

[dubstar-04]

I would like to see a working topological naming. FreeCAD wants to be a parametric modeler..

This is possibly a top feature / bug fix for everyone as its plagues the history of FreeCAD but as you mention its difficult to fix.

Let's hope someone can step up and spare the time to have a look at this.

[tanderson69]

At the risk of a further thread hi-jack: I have had the idea of a more advanced tree view for a long time. I wrote a trial program using openscenegraph. The idea would be to make it a transparent overlay of the model scene. Kind of like what ickby was demoing a while back. I got some basic icon loading and expanding and collapsing animation done, but haven't done much in a while. Here is a picture of the demo and I have also attached a inkscape svg of some thoughts. Have I already shared this once sorry If I have.

view.png (39.58 KiB) Viewed 899 times