Is it possible and I'm just glossing over that functionality somehow?
If not, any products you guys would recommend with the rough functionality of Bloom + this feature.
This is one of the only things holding me back from using or recommending the product for widespread use at our company.
Often times, properly setting up a data model or complex perspective is a time consuming process and the positioning setup of that model/perspective is important when viewing/demoing the perspective.
I agree with OP (@tj_a) - that would be a powerful feature and something I really need as well.
@aottens: even if the data changes... it wouldn't matter from what the OP is asking. It's merely saving a snapshot of the results at the time of query and it retains the layout that was edited as nodes were moved around to the desired viewing. Rerunning a saved query (even with static data) always returns the results in a default layout and losing the work done with the layout changes.
I agree. Even if the underlying has changed, the old positioning information could be used as a starting point for the layout of the graph (instead of some random starting point.)
There's a lot of work in adding features/fixing bugs. This isn't so critical, so I don't think it will be worked on anytime time soon... that's my guess.
Hello all!
This conversation will certainly help us shape Blooms future.
Is there additional information that you think would help us in creating this feature?
I totally agree, how can you say this is not an important feature.
I can't not imagine, that everyone wants to recreate a layout every time they look at the data. This is one feature that would resolve many of the issues I have when sharing the data with other people.
As for the stupid comment what happens when data gets updated? Hello! it is still a directed graph, and would insert its self where appropriate to other more static placements. once viewed it could then be moved around.
I don't know why people think this is so tough. It is recording the X/Y maybe even z axis and if exists put it back in that same spot.
its these simple features that make the product great, and is preventing me in rolling it out to my entire team, C'level and company wide for use.
This product won't work for us either unless this is fixed. It should be simple. Arrows already does it.
Bloom is great for "exploration", but it's useless for visualization of a relatively simple schema because the visualization reorganizes itself bizarrely every time you display or remove something. We need both.