The blog-o-sphere is abuzz with postings referencing the official RAD Studio World Tour announcement starting to hit the wires, and it contains something of potential interest. I have also seen claims starting to appear that XE3 will not have any iOS support at all.
First, I have to mention again the apparent enthusiasm that Embarcadero have for shooting themselves in the foot when it comes to effective marketing.
Having already registered for my local event and having received email confirmation of that registration, it is not only annoying to get another email sent to that exact same email address inviting me all over again, but it makes one wonder just who is doing what in the Embarcadero marketing department ?
If you can’t get even the simple things right, what confidence does it inspire that you have any chance of getting the bigger things right ?
But, back to the interesting points in the World Tour announcement itself:
- HTML Builder
- iOS Support
- Windows 8 Looky-Likey, not “native”
So, taking each in turn.
1 – XE2 is dead, long live
XE2 Update 5 XE3
First up, “XE3″ appears for the first time. So this really is an XE3 release not just some event marking significant progress in the evolution of XE2.
So anyone hoping that the dry period since Update #4 was the result of the promised “frequent updates” of SmokedChimp simply getting backed up in a QA back-log can give up right about…. now.
2 – What is this … “HTML Builder” of Which You Speak ?
Also this is the first time I have seen any mention of this new “HTML Builder” beastie.
However, on Andreanno Lanusse’s blog post on the matter, this newness is typographically “air-quoted”.
I also couldn’t help noticing that “RadPHP” is notably absent from the list of RAD Studio family members referenced in the World Tour event details. It leads me to wonder whether this “new” “HTML Builder” is not in-fact just another rename of
Delphi for PHP RadPHP ?
3 – Alas Poor iOS Support… I Knew Him Only Briefly
With less certain provenance, I have also seen claims – in comments to both Andreanno’s and my own previous blog posts – that whatever new features may be present in XE3, one feature will actually have been removed.
That is, whatever progress may have been made in the area of iOS support since XE2, even the level of support that was available in that release will not be present in XE3. So if you are using XE2 for iOS then – if this is true – you will be stuck with XE2 for those projects, at least for the time being.
Mr “noiossupport” seems – or claims – to have inside information relating to an update for XE3 in Q1 of next year (2013) of a revised iOS framework, which might explain the removal of the existing hack-tastic support.
If this is true then I would hope at the very least that Embarcadero will be keeping XE3 customers informed as to their intentions, and progress, in this area on a regular and effective basis, without us having to
beg, cap in hand ask for the privilege of knowing how things are going with the software we have paid for.
If it Looks Like Windows 8 Then By Golly It’s Good Enough to Call It Windows 8
All of the language around the Windows 8 “support” is now very much couched in terms of “look and feel”. So it appears that my initial hunch that they have thrown together some Windows 8 looking tiley controls and containers in BurnedApe and dubbed it “Windows 8 Support” was sadly accurate.
At least they seem now to have got the memo that it isn’t “Metro” any more.
Roll on August 28th
As I mentioned at the outset, I already registered for my local Word Tour event – it will be 1 week after the first such event in Hamburg.
I guess we will only know once the actual information from the World Tour starts to get out, whether or not an XE3 “Windows 8″ application will be anything remotely Windows 8 in anything other than look and feel, and whether their is any iOS support at all and what “HTML Builder” really is.
Similarly w.r.t so much else about this release that we have all had to resort to speculation and gossip about, instead of being able to discuss actual developments and expectations.
Comments are now closed.