Frameworks and GRASS.app, yet again

I hope you’re not getting tired of the updates. ^_^

GRASS.app updated to latest CVS.

Many small framework updates. A big one is extra GDAL plugins can now be installed in /Library/Application Support/GDAL/PlugIns, or the same in your home folder. This keeps addon plugins safe from GDAL framework updates. Also, GD and PDFlib added as frameworks – getting ready to update PHP and MapServer.

Frameworks and GRASS.app, again

The frameworks seem to be stable enough for a 1.0 release. I reorganized the download – there is a single-download convenience package that contains the current versions of all the frameworks, then each framework has its own download, so you don’t have to download a monster file for a small update.

I also fixed a couple startup issues with GRASS.app. There are still some internal problems with running GRASS.app from a folder with spaces in its name, or in any of its parent folders (hard drive name doesn’t count). So, put it in /Applications and you’ll be fine.

enjoy!

Frameworks and GRASS.app and QGIS, Oh My!

Another quick beta – this time I pretty sure I have the Panther compatibility worked out. GDAL kept trying to use the system curl and sqlite, which are not compatible between Panther and Tiger.

That’s the whole shebang that’s been updated – frameworks, GRASS, and now QGIS. (Well, I haven’t tried QGIS in Panther, but it now uses the frameworks.)

GRASS.app and frameworks updated

GRASS and the frameworks should work on Panther now, but I haven’t had a chance to fully test them on Panther. A couple frameworks cleaned up to be easier to use from a normal configure. GRASS now autostarts X11.

Frameworks and GRASS.app

Here they are. Ready to be released into the wild. Frameworks for most of the libraries in the Graphics Libs and GIS Libs packages. See the Frameworks page for details.

Also, a new GRASS.app – double-click launch – uses the new frameworks.

GRASS updated, future plans

GRASS has been updated to the latest CVS. Also, due to continuing Aqua issues, NVIZ is now X11-based. The good news there is that it runs on both PPC and Intel Macs.

Other news:

I’ve been working on frameworks for almost everything in my library packages. When I first started these packages, I wanted to do frameworks, but I didn’t know much then and it was hard work (yet mostly successful), but I’ve figured out how to simplify their construction. And other Mac developers discouraged the idea, because ‘Apple tried it way back at the beginnings of OS X and gave up’. That was then, this is now, times change.

I’m trying to make them as easy to use in both environments as possibly – that is, as used in normal Cocoa/Carbon applications, and for ‘nix porting. So, in most cases they should be usable as is from a normal ‘nix configure-make-install without changes to the ‘nix source. As frameworks, they’re also brought out into the open more, not hidden away in /usr/local. Eventually, they should be easily movable to be packaged in a Mac OS X .app package, such as QGIS or GRASS.

If they work out well, I will switch my other packages (MapServer, PHP, GQIS, GRASS) to use them.

They’re almost ready, just some build and run testing needed, and the dreaded readmes.

Then there is Panther. While the current packages are Panther compatible, I was intending to continue creating Panther-only packages with help from another. I’ve been lazy contacting said help for progress status.

Right now the framework development is Tiger-only, but I may try to make them Panther compatible. The thing is, Leopard is in the radar. Knowing Apple’s record (or, unofficial policy) of back-supporting only the previous OS version, and with my policy (I think I mentioned it at one time) of supporting OS versions that Apple supports, I’m not sure it’s worthwhile to mash the frameworks into Panther compatibility. I’ll see how the frameworks work out in general first, then think about Panther…

Some PPC/Intel data file problems fixed

I fixed some endian issues in GRASS and GIS Libs. This includes:

  • GRASS stroked fonts (would cause Tcl scripts to have problems, as well as text display commands).
  • PROJ datum grid shift files (would cause failure of datum shifts for NAD datums).

These are now rebuilt at install-time from the source data so that they are correct for the install architecture (PPC or Intel).

NVIZ still has problems, on both PPC and Intel, it seems. NVIZ still crashes on Intel. But, while it runs on PPC, after the initial rasters and vectors added from the command, the file browsers get all twitchy and you can’t add other rasters or vectors to the display.

GRASS updated

I added X11 support for d.mon displays and all the d.* commands. NVIZ and gis.m still use Tcl/Tk Aqua for display. Best of both worlds!

I forgot to include FFTW in previous packages. It’s a framework, just drag it to /Library/Frameworks.