Page: 0 ... 5 ... 10 ... 15 ... 20 ... 25 30 31 32 33 34 35 36 37 38 ... 40 ... 45 ... 50 ... 55 ... 60 ... 65 ... 70 ... 75
Lgi/Scribe/Linux News
Date: 21/12/2007
After months of tinkering with Lgi on linux, trying to get it to play nicely with Gnome I've worked out what was going on and made a work around for the issue.

If you initialize Gnome in UI mode, i.e.
gnome_program_init("Lgi", "2.0.0", LIBGNOMEUI_MODULE, Args, Arg, NULL, NULL);
Then it registers atexit handlers so the library image must remain in memory till the application exits, otherwise it'll try and call the atexit hooks back into Gnome (which has been unloaded) and it crashes. So I added a return parameter to the WmExit method that the parent Lgi app calls before unloading the window manager helper shared object and the WM helper can select to stay in memory.

There is still some question on how to read the right settings out using the Gnome API, but that is a minor issue compared to the ones I've already solved.

I know I could've shipped a build of Scribe without any WM support, but I've been a) too busy or b) too sick to do a lot of Linux work lately. I had a virus a few weeks ago where I spent the entire week in bed. Which is unusual for me, as I normally recover quickly from such minor things. Maybe I'm just slowing down a bit in my 30's :)

Speaking of intractable coding issues, I recently fixed (some) of the weird focus issues in Scribe. The recently releases were waiting on that fix. Basically I'm a dill and called SetFocus in the WM_CREATE handler if Focus(true) had been called before the view was attached. The problem with that is, if the view had the focus, you detach it, and then re-attach it later it takes the focus again. Which in my case was NOT what I wanted. But after some months of trying different things to work out the problem I hit on the issue and fixed it.

And of course... what of the Mac port? Ah... the Mac port. Yes yes. Well that has it's own thorny issue that has me mostly beat. I'm losing messages between the worker thread and the GUI thread and I don't know why. Unbelievably painful. *sigh*
(0) Comments | Add Comment

Wikipedia Notability
Date: 2/11/2007
So now any trace of i.Scribe and InScribe has disappeared from wikipedia entirely, apparently because it's not "notable" enough.

The comparison page has had all the not notable clients purged from it.

Wikipedia used to be awesome for looking stuff up. But I'm beginning to wonder it's imploding in on itself these days under the notability Nazis. I'm certainly no longer keen on putting any more of my time into editing wikipedia articles.
(5) Comments | Add Comment

Items For Sale
Date: 31/10/2007
Spring clean, some stuff on ebay:
(0) Comments | Add Comment

Scribe Stable Status
Date: 23/10/2007
I've been threatening to make a stable build of Scribe v1.89 for a while now and I'm basically happy with the codebase as it stands. For new users anyway, the situation for v1.88 users is a little grim. Apparently there are a lot of upgrade issues. And because there are a fair few users out there still on v1.88 I am going to focus on cleaning up the upgrade issues so that when v1.89 stable is released they get taken care of.
(0) Comments | Add Comment

Date: 17/10/2007
The Scribe page has dropped off Google.

It was listed on the 2nd page of results for "email client" but now it's not in the results at all. Not further down the results, completely not present. There is also a strong correlation between the change in Google ranking and a complete stop in InScribe sales.

Oh well. There goes that business plan.

The page hasn't changed in any significant way, and considering the inbound links to it, should still rank well. So I'm assuming Google is punishing me for some perceived slight, although I have no idea what.

Update: It seems that the wikipedia page on i.Scribe/InScribe has been deleted and I would hazard a guess that it doesn't help your Google ranking when that happens. Are there any wikipedians out there that could create a deletion safe page for i.Scribe/InScribe?

The text that was there for Scribe on wikipedia: 'Scribe' is a small and lightweight Email Program for Windows and Linux which first appeared as Freeware in 1999 and has been updated roughly once a month ever since. Previous versions ran on Beos as well. Scribe now comes in a freeware version: i.Scribe and a commercial version: InScribe. The commercial version adds multiple accounts and multiple user defined filters.

Scribe uses all the standard mail protocols, like POP, SMTP and IMAP and has various plugins that can add SSL, LDAP and spell checking support. It has a built in HTML viewer that is virus safe. Executable attachments are detected and optionally deleted. Scribe can be installed on removable media like USB keys so that you can carry around your mail between computers. Translators have added translations to many popular european and east asian languages. Scribe has very evolved Charset support and can display text correctly even if the Glyphs are not available in the current Font.

While Scribe itself is not open source, it is built on a LGPL porting layer (by the same company) that comprises about half of the final product.
(7) Comments | Add Comment

H.264 + AAC for Quicktime
Date: 16/10/2007
Today I was developing a mp4 encode path for my private stock VidEnc application which takes mpeg2 from Digital TV and re-encodes it. It has for a long time supported mpeg2 to xvid/avi via besweet and mencoder. But mencoder has a problem on longer videos where it drops the first 'n' frames, somewhere between 1 and 6 seconds of video. I could never figure this out so I just print out the "offset" to remux the A/V in VirtualDub. A right pain I can tell you.

So after using Handbrake a lot I decided that the pain of developing a new video pipeline would be offset by the better quality of H.264 and the smaller filesizes. So today I had some time and got into it. Things went fairly smoothly until I got my output mp4 file, and it wouldn't play in Quicktime.

This, as I'm finding out, is not unusual because Quicktime7 doesn't fully support H.264, just a subset of it. Anyway that wasn't what was causing this: "Error -50: An unknown error has occured" when I tried to open the file. My pipeline as it stands is:
  • Mpeg2 -> Pvastrumento -> separate a/v
  • Audio -> besweet to wav -> faac to aac
  • Video -> x264 to mp4
  • Mp4box to mux the A/V back together

I now know that I can do the Audio -> aac in one step using Besweet, but I havn't gotten around to fixing it yet. However there are a few gotchas in creating suitable mp4 files for QT7.
  • The AAC audio must be of the type MPEG4, rather than MPEG2. The faac option is "-w" to do that.
  • x264 should output to .mp4, not .264
  • Don't go higher then "--bframes 2" for x264.
  • Don't use "--b-pyramid" for x264 either.
This should give you a playable mp4.

(0) Comments | Add Comment