This area is where you daring souls will be able to try Mori as I continue to develop it. This is pre-release, pre-beta and pre-alpha. In short, you'll be able to play with features before they're finalized.
Some warnings:
- This code is under construction. Wear a hard hat.
- Do not use Mori documents you consider important.
- There is no guarantee that features you see will be in the v1.7 release.
- There is no guarantee that you will see every build for testing, nor all the components or features.
- As in any construction or remodeling project, layouts and fixtures tend to move quite unexpectedly.
- It's all an illusion. Don't treat anything as real.
Here's a recap of the v1.7 development philosophy, strategy and purpose:
The focus for Mori is to be an indispensable storage and organization tool for your information. To do that, it will just let you do your thing, and then collect and organize it when you want to and how you want.
Mori will not become more complex. It does simple things simply and allows you to extend them as you want. The current release provides simple interfaces to set up and work with your notebooks. Future releases will make it even simpler.
As an information storage utility it should allow you to begin entering data without having to go into a mode or click on a special box. Any entry should work just from the keyboard. Depending on the current selection, you might need to press cmd-m, or navigate through the notes with arrow keys first in order to get to a place where you can enter, but it should be possible to do quickly (2 or 3 keystrokes) and easily.
For organizing your info, it includes outlining, tags, flags, smart folders, etc. These tools will continue to be strengthened and made seamless to the workings of Mori's note management.
Most popular and oldest requests have priority for inclusion in a feature release. The degree to which the request falls into the philosophy, and can be done simply and easily determines how likely it will be included in Mori. The degree to which I'm familiar with the portion of code which would have to be changed carries less weight in the decision.
There is already a planned v2.0, which requires a change in the file format and the way the Blocks components interact. However, I'm not scheduling it for release until the end of the year. So requests which require elements that are part of the format change will either be postponed until then or will force an earlier release of v2.0.
The key enhancements are:
- Keyboard navigation
- Outlining improvements
- Better outlining support will make for a better organization tool.
- Enumeration of source and entry items
- Continuous Text
- LinkBack
- Self-downloading updates
- Font customization for Source & Entries
- Renaming of Labels
Releases
| Development snapshots | Date | Size | Links |
|---|---|---|---|
| 1.7dev | 2007-Oct-12 | 1.63 MB | Download | Release notes |
Does this mean we can expect
Does this mean we can expect to see a 1.7 beta soon?