Beta Mark II
Pinned
As we have alluded to previously, we have had a parallel version of the nvUltra beta under development for quite some time. This version served many different purposes, but to summarize -- it is designed to be faster, support additional features, and most importantly will be easier to maintain moving forward.
A few key, user-facing differences:
- Theme structure is slightly different. It is still in flux, so not ready for full documentation, but included in the beta are updated versions of the built-in themes. The theme file format is designed to be a bit more flexible in terms of theming window "chrome", but the syntax highlighting aspect is essentially unchanged (a few more features are planned for syntax highlighting.) The theme format is designed to be compatible with a new version of MultiMarkdown Composer, and potentially a few other applications in the future.
- More flexibility in the document/window model. For example, the same folder can be opened multiple times.
- The preview no longer requires a built-in web server (There are still a few tweaks still to work on with supporting the preview.) This should reduce system requirements somewhat.
- Build numbers use a timestamp system rather than a single number (this will provide a bit more information, but also make it immediately apparent which beta you are using.)
We *think* we have migrated over all the features and edge-case fixes from development to the new beta. It's possible we missed something, so the new beta will be tested in parallel for a bit, and then will become the only supported beta when it's been used by more people.
The latest version of the beta is always linked in the pinned Beta Release post.
As always, let us know if you find problems!!
-
Is it wise / unwise to install and run both release channels simultaneously?
0 -
Doesn't matter. But there hasn't been active development on the old branch in a few months -- all effort has been focused on the new branch. The old branch has just had some version bumps to keep it from expiring.
You only need the old branch if you find an issue that prevents the new version from meeting your needs.
0 -
Very cool. I'll give it a try.
The big missing functionalities for me has been Ultra's not being able to replicate nvAlt features that are essential to my workflow.
- being able to filter the left-hand file hit-list by either alpha or by file modification date
- being able to search for all dates regardless of year (eg, "0727" in nvAlt finds 20210727 and 20180727)
- using #hashtags at the beginning of a filename (eg, my daily notes are of the format #20210727.md, which nvAlt can render as a wiki-link [[#20210727]] but nvUltra cannot due to its stripping of ALL initial non-alphanumeric characters prior to indexing (rather than letting the user select a couple non-alpha prefix characters as indexable).
Those three things are what keeps me having an open nvAlt window when I need this functionality.
2 -
Theme changing doesn't seem to work. I have a folder open and I am trying to change the theme, but it is not adopting the next theme.
I am on 10.13.6.
macosxguru
0 -
1. How are you trying to change the theme?
2. Is this a built-in theme or a custom one?
3. If customized, did you ensure that it follows the examples set forth in the built-in themes for the new beta?
0 -
Good stuff. Multiple windows of the same folder is _boss_. Preview definitely much better. Still a little wonky if the preview needs to scroll to the top of the document—particularly if editing a headline; the preview will scroll just below the edit point.
0 -
Matthew Smith -- can you provide an example?
0 -
Fletcher,
I am trying to change the theme in the preferences window.
I deleted all my additions and the whole themes folder. I restarted nvUltra and it created a new themes v2 folder with themes in them. The theme it is using at this stage is the blank one I think. There is no syntax highlighting at all. When I pick one of them and restart. Nothing happens. It still stays blank.
I installed the beta on another computer where the previous version was not installed. It works fine there.
macosxguru
0 -
Fletcher Penney Sure, here's a screengrab of this in action. https://www.dropbox.com/s/lroky3dyywf1pru/nvultra-preview-scrolling.m4v?dl=0
You'll note toward the end I edited the h1 headline, but had to scroll up in the preview pane to see it.
0 -
macosxguru -- The preference window changes the default theme for new windows, not for existing/open windows. Are you closing and reopening windows after changing the preference? Were they already set to the previous default theme? If not, they will continue to use the previously selected theme for that specific window if a custom theme has already been chosen.
You might be better off using the View->Theme menu to change themes for a specific window until you're confident in what you're doing and see that everything is working for you.
You can also delete the preferences to remove any custom window->theme mapping that you have previously set. Then all windows will use the default selection.
If you're using the empty theme, then there is no syntax highlighting. That's what empty means. ;)
0 -
Okay. I took the new beta and completely uninstalled it through App Cleaner. Got rid of everything. Reinstalled the new beta and changed the theme to another one in the list. Restarted. The theme change took effect. No problems.
I took the Solarized theme and changed the cursor color and made a new theme. I didn't change the comment on the first line. It asked me whether I wanted to download a new solarized which is available. I said yes, and everything went back to blank. So I opened up the changed solarized theme and renamed the first line. I restarted nvUltra and chose the new revised theme. Restarted. It worked fine.
It is working fine now. The comment in the first line has to be changed.
Hope that helps.
macosxguru
0 -
Matthew Smith - Can you open a ticket and attach the actual file you are using? I can't replicate this and want to make sure it's not something specific to your file setup in some way.
Thanks!
0 -
Locking comments -- please open new topics or support tickets for issues.
Thanks!
0
Post is closed for comments.
Comments
13 comments