swhalemwo / obvz Goto Github PK

continued from #2 (comment)

Main use case would be, having org-mode files with only a single image file for example, which you want to comment via its relationsship links, parent,child,friend. Having the image in the center, arrows going out, then enabling text, you could nicely comment any image. Directly using org-mode, org-brain, obvz.

If there are more than one image in the org-file, the other images should be ignored, not to clutter the visualization, so the idea is, one image (= first image) per node.

When node text is enabled, some texts and nodes appear outside of the window, thus not visible, but those could be contained at least in the svg export, if possible. Thanks in advance.

Oh, was my program only, when opening in inkscape I can see all is there. Can be closed. Perfect.

Hey, thanks for sharing this cool project. I found it simply by github's suggestion list on the right side, somehow it seems to know what I am interested in :)

In the last weeks or month there are some new interesting graphing projects around org-brain, org-graph-view, now discovering this, cool, best would be if we could just use them all in parallel, and indeed nothing is against that. This reminded me of the old touchgraph* visualization of TheBrain, many years ago. There was one more interesting graphing project at that time, but I do not remember its name now. Your style goes in this direction. If your graph could be exported also as .svg that could be very useful, if you want to explain something around those words, in a lecture context for example. Instead of starting from zero, you would start from this network, and add here and there comments, color it, painting more, and ready would be the nice overview! No need for any extra mind mapping tool, just your tool, exported as .svg, then converted to pdf, then opened in xournal, then drawing on it! Thanks again for all your efforts!

• https://www.touchgraph.com/navigator

Not sure if this is a "bug" or not. Anyway, here the experiment:
Add an entry to org-brain. Then add two parents to this entry. Now visualize entry, none of them is shown in obvz. But if you add two children to this entry, both are visualized as well.

It seems obvz only collects entries in child direction but not in parent direction. Is this correct? My guess would be yes, so far.

If the network gets a bit bigger it could be useful if there would be an option to auto-shift the current entry to the center, automatically, some nice gliding, if possible. Imagine something like google earth, and it flies to the direction of the selected entry, until it stay in the center of the gui. Slow movement in that direction.

Now all text have same color, can we get custom colors for the first 12 headers at least? The 13th header and further would use the current default text color, separate from the first 12.
Then I would always see automatically by color, which text/header is in which position, and those positions could mean something, e.g. importance, or generally, separating by color can be nice visually. All their child nodes could use this same parent nodes color, if possible.

If you can add this, I can send 12 very beautiful colors.

https://github.com/jrfonseca/xdot.py

in case you did not know it.

I'm a rank beginner/dabbler with elisp code, but I take it you're "reading in" an org brain directory -- all the file and heading entries -- and creating a big cache or hash or something in live memory, right? Could you point this code out and/or explain what's happening and your general data management idea here? Lisp is the world of data as code and lists -- which is mind blowing sometimes.

Better than no visualization at all for friends, and requiring friend edge annotation first is an unnecessary block, one could change those annotations later, if anyone wants to do so.

I would prefer this, if possible. Or a setting for any color of choice for the background.

continued from #2 (comment)

I wanna give a shout-out to you, @swhalemwo! I am glad you find EAF to be useful. I added obr-viz to the README so more people will see this package! This is a very cool package, I can see people using org-brain will use it, you might want to let org-brain's people know too @Kungsgeten 😃

I am not a python (or even dev) user but I would like to test obvz.

Since it's not a package yet I have a doubt about the installation (spacemacs in my case). I'm used to install with the following command (example with org-brain-export) but I think it won't work... I wouldn't want to break everything ;-)

(org-brain-export :location (recipe :fetcher github :repo "Kungsgeten/org-brain-export"))

Could you give me an example of a functional configuration ?

Example: You have in your harddisk

• concept.org
• concept.png
  both in same directory. When selecting "concept", as background concept.png should be displayed, if available.

This would be then almost a nice presentation, if you design/prepare your background images nicely. Maybe all child concepts could use same parent concepts background image, if they do not have their own background. That could be very useful and cool, I guess.

For installing obvz I set four parameters:

(setq obvz-dir "~/org-brain")
(setq obvz-python-version "/home/mj/miniconda3/bin/python")

(add-to-list 'load-path "~/packages/obvz")
(load-library "obvz")

Then when running:
M-x obvz-start

I am getting following error:
/home/mj/miniconda3/bin/python: can't open file 'obvz.py': [Errno 2] No such file or directory

What I could try? Thanks in advance. My python3 is there. At least this python is used when updating pip3, for example.

python --version gives:
Python 3.7.4

Toggling node text is great, but if entire text is used it can destroy the usability again, maybe something inbetween as a second variant could be useful.

For example, using only first paragraph of the node text, and not everything. Then one could finetune this first paragraph with all essential information which should appear in the visualization later, thus in svg export, for example. Would be much more useful.

There is a parent but not visualized, strange.