Mar 232010
 

I am in two minds about the need for multitasking on the iPhone. I can see that it would be useful for applications such as music streamers such as the one for LastFM or Spotify (personally I prefer LastFM), but having multiple GUI programs running on a machine as small (in terms of hardware resources) as the iPhone could be problematic.

It could also make the iPhone less stable.

But there is a demand for running lightweight background tasks in a way with a only a small risk of interfering with the currently running GUI application.

It would be easy to allow too – just allow the iPhone application to fork a helper daemon with some means of controlling it. After all under that pretty skin, the iPhone is just an computer running OSX as anyone who has jailbroken it has probably found out.

Mar 162010
 

Probably of not much use to most, but useful to me …

On occasions, I have been known to start an application and switch virtual desktops as the application window appears which can sometimes lead to Enlightenment (but the DR16 version) “displaying” the window in a non-visible location. Fortunately there is a convenient and fairly trivial fix for this :-

  1. Open a terminal window
  2. Display a list of windows with the command eesh window_list (or eesh wl for short).
  3. This displays a list of two columns – a window ID and the title of each window. Pick the window ID of the window that is not visible.
  4. Next iconify the window with the command eesh wop iconify ${window_id}.
  5. At this point the icon for the application window should appear in your iconbox and you can uniconify it with the mouse and it should appear on the currently displayed desktop.
Feb 272010
 

One of the great things about OpenSolaris is that the archaic packaging tools have been replaced with something that looks like it may be a little better; one of the disadvantages is that trying to install packages from something like OpenCSW is a little awkward when the first command fails.

Given that I’ve just to hunt around for the details a second time, it is worth working up the basics into something that can be added here. Firstly we need to install the commands necessary to support the old packages :-

pkg install SUNWpkgcmds
pkg install SUNWwget

Now that has been done, it should be possible to install the OpenCSW package command using pkgadd :-

pkgadd -d http://www.opencsw.org/pkg_get.pkg
Feb 042010
 

Macports is a convenient way of adding conventional Unix software to an OSX machine; this guide is not intended as a replacement for the main documentation but as a simple convenient cheat sheet. Mainly for myself, but as it is here, anyone is welcome to use it (and send in corrections!).

After you have installed the main Macports package you need to periodically update the main macports binary and the index files with :-

% sudo port selfupdate -d

This conveniently tells you to update the outdated ports with :-

% sudo port upgrade outdated

But neglects to suggest that removing inactive ports would be wise :-

% sudo port uninstall inactive

As an upgrade does not by itself remove older packages; merely makes them “inactive”. A considerable amount of space can be used by these “inactive” ports!

Variants

Once you have found a port you are interested in installing :-

% port search emacs

It is worth checking what variants are available :-

% port info emacs | grep Variants
Variants:             gtk, motif, universal, x11

This allows you to specify what features you want :-

% port install emacs +gtk

Further details may be added …

Jan 302010
 

According to an article on The Register, our friends at Adobe are  somewhat irritated by Apple’s insistence on not allowing Flash to run on the iPhone and now the iPad. Because Apple’s platform for both products is closed, Adobe has to live with Apple’s decision on whether to allow it or not. Complaining about it amuses me, because Adobe is effectively guilty of the same kind of actions.

Almost all desktop web browsers have had the Flash plugin installed so “enhance the web browsing experience”. The fact is that we do not have much choice in the matter – many web developers insist on putting Flash elements onto web pages; sometimes the lack of Flash is merely irritating, but in many cases the whole purpose of the web service is list without Flash. For instance a Flash-less YouTube would be somewhat short on video (there is an experimental HTML5 video interface for YouTube which looks interesting but I am overlooking that for now).

Mind you that Flash plugin is also responsible for most the occasions when your web browser crashes, and it also has a tendency to “spin the wheel” and consume huge quantities of cpu time to no purpose. Admittedly it may be that the Flash experience on more conservative platforms (such as Windows) may be less unpleasant, but from what I have heard, Flash doesn’t much like Windows either.

Perhaps Apple does not want their products to get the reputation of being unreliable and unresponsive ? Of course the reason that Apple gives is that the Flash plugin is an interpreter and that they do not allow such software onto the iPhone/iPad platform for security reasons. Now on a phone, the lack of Flash can be overcome by producing specialist applications such as the YouTube app, or by accepting a phone just is not as effective at browsing the web. Of course on something like the iPad, it is going to be a little harder to accept when web sites appear broken.

Which is of course Adobe’s point. And to some extent they are right. But you do suspect that Adobe are actually more worried about their own business than the interests of consumers.

If the iPad takes off, those web sites that use Flash extensively are going to have a big incentive to produce alternate versions of their sites. Some may well opt to “wrap” their site into a iPhone/iPad app; others may simply opt to switch to HTML5 and it’s support for video (which is not quite ready for prime time just yet). The modern standard of HTML provides for much more options in generating dynamic content.

Of course this hypothetical shift away from Flash content would be bad for Adobe, because people will be less interested in paying for Adobe’s content production software. Perhaps Adobe should admit defeat and modify their software to generate standards-based web pages rather than closed binary “blobs”. It will certainly be easier to do that than to persuade Apple to unlock their platform!