PSICAT Development

I’ve been making steady progress on the 0.6 release.  The focus of this release is to really polish the UI and improve the user experience.  To that end, I’ve revamped the tooltips that are shown when you mouse over an object:

It shows you the depth/height where the mouse is at as well as some info about the object the mouse is over.  The description of the object will also show up if it is set.  The other new feature will be an option to import images into your diagrams.  This should allow people to start playing around with the better image handling support.

I’ve also been focusing a lot of performance improvements as well.  The new version of PSICAT feels pretty snappy for small projects but can get very sluggish to unusable with large projects like the 1285 meters of detailed description in the ANDRILL MIS hole.  I checked in a few changes today that speed things up dramatically.  Rendering in 0.6 should be at least as fast as the original version of PSICAT for large projects (and possibly faster).

I’m shooting for a release this week, so check back.  Thanks to all that have been providing feedback.  Keep it coming!

Sorry for the radio silence, I’ve been working hard on the 0.5 release.  It will be a fairly ambitious release with a big focus on closing the functionality gap between the development and stable versions of PSICAT.  Here are the main features in the roadmap:

• Grain Size Support
• Image Import
• Importing previous data/diagrams
• Documentation updates including a quickstart video showing how to get up and running with a customized lithology and symbol scheme

I’m working on the last few things and plan to make the release this weekend.  As always, comments, criticism, and questions appreciated.

This is a roadmap post for the 0.4 release of PSICAT.  My agenda includes the following issues:
- Issue 1: Export Dialog
- Issue 10: Description Column
- Issue 11: Grain Size Support
- Issue 12: Image Import
Add a comment or report an issue if there’s something you’d like to see or if you’ve found a bug.

Update: This page will show you the status of all issues for 0.4