Month: June 2005

  • Forum for malcolmhardie.com

    Following the suggestions in this article, I’ve been considering forum software recently to offer customers (and others) somewhere to discuss SQLEditor.

    Currently I’m considering PunBB, because it seems to be simple, fast and well received by reviewers and users.

    PhpBB seems a popular choice but is probably a bit more than I actually need for this project.

  • The length of my hair and the length of the grass

    Since I live in a small house as opposed to a flat I have a small amount of garden. Most of this is grass.

    I haven’t gone bald, so I also have some hair on my head.

    As I was looking at the grass the other day, un-mown for too long, I came to an odd realization. The length of the grass is proportional to the length of my hair. When my hair is long, the grass is long, when my hair is short then the grass is short.

    This is a curious realization.

    But it does have a logical explanation.

    I think that when I’m less busy then both grass and hair get cut at the proper intervals. When I become more busy the intervals get longer.

    And so there is a link.

    Which is kind of weird.

  • Not managing time very well

    Recently I haven’t been managing time very well, with the company business and the new release of SQLEditor things seem to have been building up and not getting done fast enough. The grass and my hair are growing too long as well 🙁

    I’m hoping to improve things, but if I’ve been running behind on things like email and communication in the last month or so, I ‘m sorry.

    I hope to resolve the back log shortly.

  • plutil

    STANDARDS
    The plutil command obeys no one’s rules but its own.

    from the plutil man page

  • No Osborne Effect?

    The Register has a new article up about the Osborne effect, a supposed problem that means that if you excessively pre-announce products then nobody buys the stuff that you’re selling right now. The article suggests that the whole idea is rubbish and that osborne was actually suffering from a totally different problem, Managment failure. Supposedly an executive found some old parts and spent a vast amount of money trying to put them into products, in the process wasting far more than the value of parts.

    Yet again Management failure causes a company to fail.

    [Article]

  • SQLEditor built for Mac On Intel

    SQLEditor has now been built for Mac OS X/Intel as well as Mac OS X/ppc. I was able to download the Xcode 2.1 release last night and worked on the port this morning. SQLEditor at the moment still has bits of Java as well as Objective C so I wasn’t entirely confident of success, but I converted the build target to the xcode native type and moved the java code into a separate target. Then I ran the build process and after a bit of fiddling I was able to produce what appears to be a working fat binary:

    file SQLEditor
    SQLEditor: Mach-O fat file with 2 architectures
    SQLEditor (for architecture ppc): Mach-O executable ppc
    SQLEditor (for architecture i386): Mach-O executable i386

    The new version of the application seems to run as well as the old on PPC, although it is currently set up to use the 10.4 sdk as opposed to the 10.2.8 sdk of release SQLEditor versions. (Although SQLEditor is not officially supported on less than 10.3)

    If I had a Mac On Intel machine to test it on I would be very curious to find out what happens. 🙂

    But as far as I can see, and with the assumption that the ported version will not have unexpected bugs, the process is simple.

    But will that assumption will hold? I have absolutely no idea.

  • Mac OS X Intel

    It has been officially announced that the Mac platform will be moving to Intel processors.

    I’m still thinking about what this means for MalcolmHardie Software and SQLEditor and I have been reading about the transition to find out more.

    Some useful points culled from publicly available documention:

    • Mac OS X on Intel doesn’t use Open Firmware (at least not currently). Does this mean that it uses a conventional BIOS or something entirely different?
    • Rosetta (the translation environment) does not run Applications built for Mac OS 8 or 9. Does this mean that the Classic environment will run them, or are these applications dead?
    • Rosetta doesn’t handle code written specifically for AltiVec
    • Rosetta must run the whole application, you apparently can’t mix some bits of native code and other bits of emulated code, even with plugins. (I suspect inter-application communication might work here though)
  • Apples & Intel?

    Maybe it’s going to be hardware based dynamic recompilation?

    Or some kind of microcode based emulator?

    Modern microprocessors are usually doing conversion of the assembly anyway, so why not from one instruction set to another.

    I guess we’ll all know in a few hours …