Imo, it's time to focus on getting a1 out the door. This involves: 1. Fixing all bugs that could have a major impact on Leo's stability:
For example, issue #35 re duplicate gnx's is now closed. It had to be fixed for a1. I'll review all outstanding bugs for their effects on stability. I am dithering about issue #28 re large nodes. This must become completely solid before a1. Failing that, it will be declared a failure. 2. Making the install process as easy as possible: The to-do list contains several good ideas, such as supporting homebrew install and making Leo a portable app. I'll do as many as possible. 3. Making Leo as easy as possible for newbies: For example, Fidel made several good suggestions: https://groups.google.com/d/msg/leo-editor/KOXSm8crU1I/qCLYzZCJuc4J For example, Fidel suggests quickstart guide should open by default instead of the user's workbook. 4. Refine the "fit and finish" items as much as possible: Seemingly small issues such as focus issues are surprisingly important and difficult to test. 5. Resolving *all* outstanding documentation issues, including summarizing many previous conversations: This could take several days. That's everything on my list for a1. Your comments, please. 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
