Settings and activity
3 results found
-
9 votes
An error occurred while saving the comment -
5 votes
An error occurred while saving the comment 
AdminThijs Muller
(Admin, NAPA)
commented
Hi Kristoffer,
Thank you for your Idea.
This touches very much our thinking at the moment about what should take precedence. Our thinking right now is that we would rather bring and visualize the existing managers / workflows to the node network than the other way around. The idea of the node network is to visualize and break down the tasks for the naval architect to a understandable size rather than be confronted by the total workflow when you start, much like how the manager applications are doing it currently. The main difference however is that the node network is much more flexible and can more easily be adapted to individual user needs.
-
10 votes
An error occurred while saving the comment AdminThijs Muller
(Admin, NAPA)
commented
Hi Thijs,
Thank you for this idea.
Due to the development stage of NAPA Engineer we are nowhere near ready, to take this idea on, with a serious effort. However, we are developing the syntax highlighting of which you will find the first version in the alpha releases of Napa engineer, this should already help with trouble shooting and speeding up the macro writing.
We will keep this idea in the backlog for now.
Hi Kristoffer,
Thank you for your idea.
We will add document output to the node network but we are currently still considering what form it needs to take. One idea is to have this contextual ribbon where the commands are located together with a text editor window for the doc code and a output window for the resulting pdf side by side, like overleaf is providing for latex (Overleaf, Online LaTeX Editor). The question remains however, how we should include all the lists and figures from the node network that are normally included in a document, while keeping an overview in the node network. And how to provide a more complete implementation of a document output formatter like docbook or wpr.