Review of Serenity

I just put up a review of Serenity. I might add more later, but it is late and I am tired.

Tags: [Movies] [Serenity] [FireFly]

Delphi Ares P2P is #5 project on SourceForge

I was reading through my September 2005 Sourceforge.net site update and noticed that Ares P2P, written in Delphi, is the #5 project on the site. Delphi is also the 10th most popular programming language on the site, with 1885 projects written in Delphi or Kylix (does not include the 349 written in Pascal or the 274 in Object Pascal).

The 20 most popular langauges on SourceForge.net by number of projects are:

1. 16,338 - C++
2. 16,163 - Java
3. 15,587 - C
4. 11,762 - PHP
5. 6,104 - Perl
6. 4,371 - Python
7. 2,745 - C#
8. 2,616 - JavaScript
9. 2,156 - Visual Basic
10. 1,885 - Delphi/Kylix
11. 1,802 - Unix Shell
12. 1589 - Assembly
13. 1124 - PL/SQL
14. 898 - Tcl
15. 723 - Objective C
16. 550 - ASP
17. 376 - Ruby
18. 349 - Pascal
19. 318 - Lisp
20. 274 - Object Pascal

There are a total of 90,417 projects on SourceForget.net, written in 72 different languages. Oberon is a langauge choice, but there are currently no projects for that langauge. There are however 4 for COBOL, 7 for MUMPS and 24 for D.

Update: Ares is now the #3 top downloaded project.

Tags: [Programming] [Software] [SourceForge.net] [Delphi] [Languages] [OpenSource] [P2P]

Migrating from .NET 1.1 to .NET 2.0

At PDC I recieved a copy of VS2005 RC1 along with .NET 2.0. We discussed devoping our next application at work in .NET 2.0 since it is due out any day now^TM. Our primary third party component vendor had a booth at PDC too, so I asked me if they were .NET 2.0 ready. They said they were really close, and commited to being 100% within 30 days of actual release, any day now^TM. I figured I would see if I could port our prototype over. The result was successful. This is what I had to do:

• Built in conversion wizard when you open a VS2003 solution / project converts to VS2005.
• Required checking the files out of source control so they could be modified.
• Not very tricky, pretty straight forward.
• Removed unused references to other 3rd party assemblies.
• Set all references to the same version of the 3rd party assemblies and .NET framework.
• Before this was done it resulted in some confusing runtime errors about not being able to cast something to the original type (this is because it was the same type from two different versions of the assembly.)
• Updated references to obsolte methods
• Each obsolte method was flagged with a warning which specified which method to use instead. The latter was a very useful feature.
• Some of the namespaces for the datasets needed to be adjusted to include the subdirectory the dataset was in.
• Pretty straight forward once I figured out what it was referring too. Not sure why it worked before in VS2003.

Overall it was a fairly simple process. I didn't get a chance to use VS2005 much yet, but the one HUGE anoying bug or missing / changed feature was that chaning which file you were editing didn't update the location in the solution explorer. This resulted in manually hunting for the files in the solution explorer, which waisted a lot of time and was very frustrating. VS2003 has that feature, so I am not sure why they removed it from VS2005. Hopefully they fix that bug in time for release.

Tags: [Programming] [Software] [.NET] [Visual Studio] [.NET 2.0] [Visual Studio 2005] [Migration]

More on the Delphi Roadmap

Robert Love has some updated information on the Delphi roadmap as a result of the BDN Radio broadcast. Hopefully an MP3 is forthcoming.

Going forward Delphi will support Win32, .NET, C++, C#, Delphi language, other .NET langauges (VB.NET, etc.) and there are now officially announced plans to support Win64 natively and .NET 2.0.

Update: You can listen to the MP3 recording of the Roadmap radio broadcast now. There is also a chat log with some other questions and answers in in. Good information!

Tags: [Programming] [Borland] [Delphi] [Future] [C] [.NET] [Win32] [Win64]

Fox News Opinion on OpenDocuments is Uninformed and Highly Biased

I am sure most people don't find that headline very surprising. It may be worth while to note the "article" is actually a guest editorial in the "views" section. The writer is not a Fox News columnist. The author is Jim Prendergast, the executive director of Americans for Technology Leadership. From the slant of that article I am guessing that organization is one that spouts praise for Microsoft and attacks Open Source all in the name of well paid research.

The OpenDocuments format is an OASIS approved document format that anyone is welcome to support. Choosing to standarize on OpenDocument supporting applications is like choosing to use applications that suppport XML or other standardized formats. It is not lockin to a specific vendor. While the article does raise what might appear to be good points it misses the whole objective. First of all it claims the decision circumvents the "merit-based procurement process", which is totally false. The state has decided to standardize on an open format that has free tools available for all to use while interacting with the state. As a government agency providing a free way for citizens to interact with them seems like a good policy.

They are still open to the merit-based procurement process and bids and proposals. Microsoft, or anyone else (including "mall state-based systems integrators") could choose to support the OpenDocument format and they may win the state contract.

I think government agencies that standardize on a closed and proprietary format that forces citizens to buy overpriced software just to interact with them is providing a public disservice. What if I am using Linux or some other platform that doesn't run Microsoft Word? Or what if I don't own a copy of Office? Should I be required to purchase a platform that runs office, and then purchase office just to interact with the government?

What if the state standardized on Bill and Ted's Excellent Office Suite because it was the absolutely fastest performer, uses the least memory, and they got a great deal. The only bad news is it uses a propritary file format that can only be read by this specific suite. Sure the state got an incredible deal because they purchased so many coppies, but if an individual wants to create or view one of these documents then it will cost them $5000 because it only runs on a specific operating system that only runs on specialized hardware. Is that doing the public a service?

OpenOffice and StarOffice are big supporters of the OpenDocument format and they alos provide excellent interoperability with Microsoft Office. In fact, they provide better interoperability then Microsoft Office, opening more formats of Office documents then even Microsoft Office does. A fact conveniently neglected in the opinion piece.

Interestingly the piece also says that:

In many cases, new technologies will have to be purchased even when current systems are fully functional. In other words, taxpayers will be paying duplicative costs.

But then later says "Microsoft keeps expanding into XML and metadata"

So the author is advocating the state upgrade to the latest Microsoft Office product, and pay all the additional duplicative (replacement) and training costs associated with that. But the author has a problem if the state wants to move in an open direction that could save money on licensing (up front and over the long run) and provide greater accessibility by standardizing on a tool that supports the OpenDocument format.

It sounds to me like the author owns MSFT stock and wants to see his portfolio improve more then he wants to encourage open accessibility to government technology.

He also falsely states that OpenOffice and StarOffice don't support assistive technologies. He obviously didn't research any since both StarOffice and OpenOffice have extensive accessibility features.

He does not the exception granted PDF, but I believe that is rightfully so. Adobe provides a free viewer for most all platforms, and they provide the useful feature that the document can be formatted on one machine and then printed identically on any other machine. I thought it was interesting that the author points out that "How confident can Adobe and others be that the government won't later change their minds and suddenly deny the exemption?" Isn't that the nature of government contracts? If a better, cheaper, more accessible alternative comes along, then the contract is awarded to a new vendor. It would appear the author doesn't believe in "free market competition" after all.

Tags: [Standards] [Microsoft] [OpenDocument] [Government] [Bias]

Free Barcode Font - TrueType Code 39

Tony just sent me this link for a free Code 3 of 9 barcode TrueType font. It is free for personal use.

Bar codes are pretty useful. I have one friend who prints out all his product keys in barcodes, and then scans them in when he reinstalls. Speeds up the reinstall time. Tony on the other had was using a barcode of (Carriage Return or ASC #13) to advance a powerpoint presentation. Get creative and fun!

Of course you will need a bar code scanner to read these back in. You can usually get one on eBay or maybe you can find an old CueCat lying around.

Tags: [BarCode] [Font] [Powerpoint]

The Unholy PDA Union

Since Palm OS split from Palm devices that opened them up to the an unholy union of Microsoft Windows Mobile 5.0 (FKA WinCE, WinXP mobile, Pocket PC, etc. . . .) on a Palm Treo device. Even with all the marketing Microsoft has put into encouraging adoption of their OS, including licensing the OS to a huge variety of hardware manufactures, Palm still dominates the market. Not sure what this will do to the mix, but I suspect it will really hurt the sales of all the other Microsoft OS devices and the Blackberry.

Interestingly, the Treo actually originated with Handspring, which was a company started by a couple engineers who left US Robotics shortly after they released the Palm Pilot. US Robotics was purchased by 3Com, and the name was changed to Palm because of a trademark conflict with Pilot pens. Later Palm was spun off from 3Com as PalmOne. Then it split into Palm and Palm Source, with the later making the OS and the former making the devices. At some point in there Palm purchased Handspring, keeping only their Treo product line, which is the most popular, and one of the first, PDA & Phone combos. Of course all of that is just by my best recollection, so feel free to correct me.

With Compact Framework the Microsoft devices are a whole lot more appealing since they are much easier to program on. Although Palm OS has Pocket Pascal.

Tags: [Palm] [Microsoft] [PDA] [Treo]

Real Delphi Roadmap

You may remember my projected Delphi Timeline. Well, David I. just unveiled an actual Delphi Roadmap, and it looks like it will make everyone happy. Marco Cantu has some great coverage.

No mention of Aspect Orientated Programming unfortunately. Also not on the time line is LINQ, but Danny Thorpe already talked about supporting LINQ in Delphi, but he didn't say which version (or I missed it). I would suspect LINQ support in Highlander / Delphi 2006, but it may be as late as 2007. Since DeXter is pretty much finished at this point I can't imagine it showing up there, unless it comes as an update.

The impression I got at PDC was that LINQ does not depend on a new features in the CLR, so it would not require .NET 3.0. It is a language feature that happens to be supported by both C# 3.0 and VB.NET.

Tags: [Programming] [Delphi] [.NET] [LINQ] [VB.NET] [C#]

Computer Programming Board Games

There has been a lot of fuss lately about c-jump, computer programming board game that teaches C syntax and logic to children. Very creative idea. When I think of computer programming board games I think of RoboRally, by Richard Garfield and Wizards of the Coast. This game was actually unavailable for years, but now you can buy it online!

I've played RoboRally, and it is a lot of fun. Now that it is available again maybe I will buy it.

Tags: [Programming] [Games] [Kids] [C-Jump] [RoboRally]

Orpheus 4.06 for Delphi 2005

This was a while ago, but I thought it was worth mentioning. Chee Wee Chua has updated Orpheus 4.06 to work with Delphi 2005. Orpheus was open sourced when TurboPower closed their doors. This library adds over 120 components to Delphi, covering a wide range of features. At one of my previous jobs we actually purchased a previous version of Orpheus, and now you can get the latest version free. Thanks Chewy!

I think it would be great if Borland started bundling these libraries with Delphi. If they actually put them in the IDE on installation then that would really jack up the number of components they shipped with. Do the TurboPower ones, and then the Jedi library.

That is the one thing about the Delphi community, the incredible selection of great quality open source components. Since Delphi was really doing component development while everyone else was just starting to figure it out they really got a great head start.

Tags: [Programming] [Delphi] [Open Source] [Components]