Jeff I completely agree with your “wiki” application and that auto-sizing projects to be consistent with headings makes sense in that case. In some situations having a Pane “look smaller” because of where it happens to be in the Outline is ‘bad’ – but in others, it’s ‘good’. Which is a perfect reason to have both Headings and Projects, and to have them behave differently.
My ideal is that I never have to size my headings and don’t have to size my Projects – but might in the future choose to have big Projects for some special application. Right now I can do that, all I have to do is edit my Project styles so P1 is not larger than H4. I probably won’t bother setting P1=P2=P3=P4 since I always apply prefixes with a single hotkey stroke.
Jeff people who were using old-projects mainly as projects rather than headings,
If it’s not okay to ask users to update their outlines b/c an existing feature is changed then no feature can ever be revised and we’re stuck. We’ve certainly blown up filters plenty of times though so I can’t get behind this as an argument against change. It may be wise for Jay to pop a Toast that lets users “choose” whether their existing projects should be converted to Headings or Projects (probably with a link to a blog post explaining how they differ). I ended up with a mix of H and P due to my inconsistent methods of assigning P prefixes in the past, and am having to clean as I go…which is not very hard.
Jeff I don’t want to see an H1-sized project inside an H2 or H3 heading
Me neither. Since P and H default to the same sizes this will probably impact a lot of users. It’s easily solved with the style editor, or by using ^^^^ as you say – but I don’t consider either of those adequate for new users, non-techy users, or non-Pro users (no access to style editor). Jay mentioned having some general Display Settings that make batch-changes in the styles – this may be a perfect place to leverage that idea. For example, the setting could be:
Headings and Projects Weight:
[ ] Headings bigger than Projects
[ ] Projects bigger than Headings
[ ] Equal size Headings and Projects.
[ ] Custom (use Style Editor) <– grey if non-Pro
There might also be:
Project Styling:
[ ] Larger than plain <– must be checked for the above settings to be relevant
[ ] Same size as plain
[ ] Same size as plain, bold
[ ] Custom (use Style Editor) <– grey if non-Pro
Where the second two options would set P1, P2, P3, and P4 to = normal item text size. There would need to be some care taken in how these two settings interact with each other…I guess the second one should actually appear first, with the first set of options disabled unless valid.
I like the above vs. simply making Project auto-sizing optional, because without the additional controls, if a user chooses to auto-size Projects they would still match up with Headings and you could still get P1s under H3s looking bad.
