On Tue, Dec 26, 2023 at 11:40 AM Thomas Passin <[email protected]> wrote:
> It's a nice way to display and balance out key information. The > organization is basically parents and children. I didn't see any examples > where a node had more than one parent. That means the diagram could be > stored in a standard Leo tree. As usual, the hard part is creating a > layout of the diagram. > > The metadata - phase, ticket number, assignees, etc, could be stored in a > node's UAs, or the way I've adopted, with tagged lines in the node's body. > But probably all that data will usually come from a database. > Thanks for these ideas. My first thought was to look in vs-code. Searching plugins using "tree" gives lots of results, but none seem directly applicable. Looking around the demo page <https://app.mural.co/t/industriallogic9109/m/industriallogic9109/1652365224808/45156490f5e94897dae8ec507461d19e5797a071?sender=u43adf1f95af7b58911e42493> with F11 was another idea :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS21%2B%2BYgX%3Di89zCxZ7qwcaWY8NdHWuxBrFUu5pVr_qHCHg%40mail.gmail.com.
