tag:support.nodebox.net,2012-11-01:/discussions/show-your-work/207-my-architecture-work-from-2008-2016NodeBox: Discussion 2017-07-07T21:46:08Ztag:support.nodebox.net,2012-11-01:Comment/428764462017-06-30T11:04:10Z2017-06-30T11:04:12ZMy Architecture Work from 2008-2016<div><p>This is the model I created for the graphic. Just a litte crazy big.</p></div>andy.treichlertag:support.nodebox.net,2012-11-01:Comment/428764462017-06-30T13:50:23Z2017-06-30T13:50:23ZMy Architecture Work from 2008-2016<div><p>Andy,</p>
<p>Wow. That is truly impressive. Your NodeBox network is impressive as well.</p>
<p>I find high-density charts like this interesting; it's something I do sometimes as well. You shared JPEGs, but when you view or share this diagram, do you use a PDF instead? The file size would be smaller and you could zoom in as deep as you want with no distortion (works great on tablets with pinch-zoom).</p>
<p>I'm sure you learned a lot about your own work making this chart. Now that it's finished, how to you use it? Are you the only consumer, or do other people in your company find this format useful?</p>
<p>I couldn't see individual nodes in your massive NodeBox network, but it looked like you used repeating blocks of similar structures. Did you use subnetworks?</p>
<p>Thanks for sharing this!</p>
<p>John</p></div>johntag:support.nodebox.net,2012-11-01:Comment/428764462017-07-06T21:04:38Z2017-07-07T00:55:49ZMy Architecture Work from 2008-2016<div><p>Dear John,<br>
thank you for your nice feedback. Sorry for the late response. Spend some days on holiday. I try to give you some answers on your question. Even if I think that you are the real Nodebox Guru in this game.</p>
<p>Question 1&2: Publishing Format. Depends on the target system and user group. I used it, in this case, Nodebox to document some of my working experience from the past in a nice style. I was always a great fan of the Circos graphs. But the system is too hard to handle and not flexible.<br>
In my working experience people like all the details and information on one page. Mostly they like to have an A0 poster in their offices with all the details to explain it to other users. They see on the physical graph poster all the real project names (Published Version: anonymized). So normal I use PNG and Graph format. It's better as JPEG from the quality. PDF if there has to be a secure format with change restrictions. I this case I published the hole Information on my LinkedIn Account. The problem on LinkedIn is, if you upload the file in your profile, the filed graph quality is horrible. So I loaded the file (4200*4200) up as feed detail and linked the information from my profile to one of my feeds. there the people are able to download the graphic with good quality if the want it. I published information in my follower circle only and not public. the response is good and some the key person would like to have the graph to publish it in-house.</p>
<p><a href="https://www.linkedin.com/in/andreas-treichler-651b3353/">https://www.linkedin.com/in/andreas-treichler-651b3353/</a></p>
<p>Question 3: I was a very hard way to find out about the functions and dependencies of all the nodes etc. The Documentation of Node box could be better. But thank's to guys like you I found my way trough the model details because of your examples. Thank you for that. I did not use sub-networks. Why It's easier to have an overview of the models and model groups. But I understand the concepts. The reason I have different sections in the model is more related to the color schemes. The colors in my scheme are strongly related to information and Business Divisions. If I used a calculated color asthma it always changed the colors of this divisions.</p>
<p>My conclusion in the moment on Nodebox 3 is, its a nice open source tool, with potential but I would like to some features & functions. Examples</p>
<ol>
<li>A 360 Degrees Text Turn functions on degree/angle or node position. It would be<br>
nice to be able the read the text always without making a handstand.<br></li>
<li>Ticks with text (Geometry). It's a little nerving to build the rings with an arc's and<br>
ellipse and set the text than as well.<br></li>
<li>Link should be able to set the position in the middle of a geometry and not outside<br>
of the geometry.</li>
<li>Open Ports extensions. In the moment restricted to 7 ports. I should be open to<br>
endless (user decision). Examples: Combine (One Node) with endless IN ports.</li>
<li>Point to Point connection (Line/Quad Curve) in the same circle. (System 1 to 10<br>
Systems). Why! The coordinated should be always the same of the systems,<br>
because of they relate to a higher group.</li>
</ol>
<p>So thank you for your indirect support with all your answers in other examples, they helped me to find my way trough Nodebox 3</p>
<p>Thanks and regards! Andy</p></div>andy.treichlertag:support.nodebox.net,2012-11-01:Comment/428764462017-07-07T21:46:06Z2017-07-07T21:46:06ZMy Architecture Work from 2008-2016<div><p>Dear Andy,</p>
<p>Thanks for the detailed reply and for your kind words. I keep putting up sample code but only rarely get feedback and usually have no idea whether anyone finds it helpful or even sees it. Occasional feedback like yours it what keeps me going.</p>
<p>I found your wish list quite interesting. One of the nice things about NodeBox is that you can often grant your own wishes by making custom nodes (if you can code in Python or Cloture) or simply by making a subnetwork entirety within NodeBox.</p>
<p>I decided to do the latter for your first wish. See the post I just made in the Show Your Work forum called Directional Text. I made two subnetworks, true_arc and true_spoke that I think solve the directional text problem we all encounter when placing text on the rim or spokes of a wheel. The two subnetworks automatically fix the text orientation so that it's easy to read regardless of where it happens to land.</p>
<p>I hope you will find this useful in your future projects. And I hope you will keep posting your work examples. We NodeBoxers have to stick together!</p>
<p>John</p></div>john