CapableObjects announced

-
There are exciting times ahead! The team that brought you ECO for Delphi are now a separate company named Capable Objects (http://www.capableobjects.com).

ECO will still be part of the next release of Delphi, but according to the official statement (http://dn.codegear.com/article/3673>) and comments in the newsgroups it is quite obvious there will also be a version of ECO for Visual Studio!

In the past the ECO guys released patches for ECO bugs, unfortunately it was not always possible to provide a patch. With the guys now being a separate company they are free to decide their own release schedules. Instead of having to wait for a Delphi update they can now release updates as often as they wish. Just like the good old BoldSoft days when we used to get an official update really quickly if ever a critical bug was found. Not only that, but it would also seem that they will be shipping source code too!

But that's not all John!

The guys at Capable Objects have asked me to write documentation. I've been adding XMLDoc to the source code so the API help will be more up to date. As soon as possible I will be writing a quick start document for Delphi (and any other IDE's) too.

Can't wait! :-)

Comments

Anonymous said…
Thanks for posting your take on this, Pete! How does this impact ECOModeler?
- JoeH
10 July 2007 at 16:04
Kyle A. Miller said…
Pete, I am happy you are excited, but the ECO guys were acting fairly independent anyway. They DID release patches outside the Delphi patch/hot fix release schedule. They maintained their own Wiki. So, I don't find that point in justifying the spin-off very valid.
10 July 2007 at 17:17
Peter Leslie Morris said…
Hi Kyle

The ECO guys tried to act as independently as they could, but they were still restricted in what they could do. Although patches were released independently to Delphi I do recall there were a few bugs that could not be patched in source. If the fault was due to a bug in the core of ECO a new binary would be required, and they couldn't release new binaries without a Delphi update I believe.

Now they have more freedom and their own separate installer they are not only free to release binaries whenever they like, but they are also free to release major versions to their own schedule rather than to the schedule of Delphi.

Hopefully now I have convinced you :-)
10 July 2007 at 17:48
Peter Leslie Morris said…
JoeH, it has had no impact on EcoModeler.
10 July 2007 at 17:48
Post a Comment

Popular posts from this blog

Connascence

-
I’ve just finished reading What every programmer should know about object oriented design . The first couple of sections are a bit useless really, but the 3rd section is very good. I particularly liked the section on the difference types of connascence in software. There’s some basic information about it here if you fancy a brief overview of what it is about. It’s a really good book, I recommend you read it! Should only take a day if you only read the 3rd section.
Read more

Convert absolute path to relative path

-
Today I needed to convert an absolute path to a relative path based on a specified base path. E.g. c:\a\b\c -> c:\a\b\c\d\file.txt = d\file.txt c:\a\b\c -> c:\a\file.txt = ..\..\file.txt c:\a\b\c -> c:\a\x\file.txt = ..\..\x\file.txt I am surprised there is nothing in the .NET framework so I had a hunt around and converted the code from the following URL ( http://www.vergentsoftware.com/blogs/ckinsman/default.aspx?date=2006-08-07 ) into C#.... private string RelativePath(string absolutePath, string relativeTo) { string[] absoluteDirectories = absolutePath.Split('\\'); string[] relativeDirectories = relativeTo.Split('\\'); //Get the shortest of the two paths int length = absoluteDirectories.Length //Use to determine where in the loop we exited int lastCommonRoot = -1; int index; //Find common root for (index = 0; index if (...
Read more

Printing bitmaps using CPCL

-
I've had no end of grief trying to print a PCX to a Zebra Printer using the CPCL printer language. Silly me, didn't notice the EG command (expanded graphics) so there was no need to convert my BMP to a PCX and then struggle with binary data. I still had a bit of grief working out how to print using the EG command because the documentation is quite frankly crap. The expected command format is EG {WidthInBytes} {HeightInPixels} {XPos} {YPos} {Data}\r\n The printer expects a 1 bit pixel matrix. So if pixel(0, 0) is set you will set "80" in the data. If pixel(0, 0) is set and pixel (7, 0) is also set you would sent "81". Basically what you need to do is to read each set of 8 horizontal pixels and then use bit operations to create a byte value 0..255, and then output this as hex 00..FF. Here's the routine :-) public void DrawBitmap(Bitmap bmp, int xPosition, int yPosition) { if (bmp == null) throw new ArgumentNullException("bmp"); ...
Read more