Richard Feynman

Requesting Linux support is reasonable, everyone is entitled to their own feature requests, thinking that EN is "being lazy" or somehow owes you Linux support because you pay for a premium account is not. Linux owns less than 1% of the desktop market. It probably makes about as much business sense for EN to develop for that market as it does to develop for the Commodore 64.

Thank you, I will look at previous posts. If you could, it would help me greatly if you could suggest either some specific threads or good keyword searches to find these posts.

I agree with you that anything over 10,000 in *tags* says that some reanalysis is necessary. However, my scenario assumed I was using tags, in a sense, as a substitute for creating pure hierarchy-based info organization. I would much rather use tags as they are meant to be used in all info management systems.

My project work has been going on for 25 years and truly does require tens of thousands of hierarchal levels because the information itself requires that kind of breakdown. Trust me, I am NOT partial to very complex hierarchies or to breaking down information to insignificant detail; my work actually is trying to pull these details up into less complex models. But I have to start with the details.

I understand where you are coming from. I am in the same boat as you of liking what it does, while being disappointed with what it does not do. My professional work is also very project oriented and personally I would never attempt to use EN for it, but maybe you'll be able to adapt it to your work. I don't know what is driving you to EN but IF you only need a desktop application you may want to take a look at InfoQube. InfoQube has no mobile client of any type though, it is strictly a desktop app. From a power users standpoint it makes EN look like a toy, but like everything it has its own shortcomings, and the GUI is not as beautiful as EN's. OneNote, EN and InfoQube are the three PIM's/info managers I like. IQ is the most powerful by far but also the most obtuse.

Currently EN only allows sharing at the notebook level. This greatly limits the functionality for those of us who use stacks, because it prevents us from sharing our hierarchical structure, and all context is lost. For instance, let's say I want to share:

Project 1 (stack)

- Tasks

- Notes

project 2 (stack)

- Tasks

- Notes

All the users us going to see is four notebooks, two named tasks and two named notes, they won't be able to see which project they are stacked under. All context is lost. And I have to share every single notebook. And before someone tells me how I can use a workaround , I know I could but I don't want to use a cumbersome workaround, I'd really like to see this added as a feature.

Thanks