So what does this mean? A commercially very successful company bought a very inventive (yet not commercially successful) company.  Just look at the list of acquired companies. So Oracle bought a company with 3 key products: Sun hardware & OS, Java and MySQL. The hardware business was suffering from the biggest losses. Premium hardware with excellent software and support, but expensive and outran by cheap X86 hardware + Linux. Still, if you need one machine to serve your big and battered database, a Sun Solaris box running Oracle (!) is your best bet. MySQL caused the biggest concern for the EC to deeply investigate the merger. Their fear was that Oracle would be come a too big player on the database market. I don’t know how, but somehow the EC now thinks this is not a major concern so that their approved of the merger. I am still concerned, especially after the original creator of the open source database wrote that the world should object. However, MySQL is still open source and has been for some while, so buying the company that bought the company that offers support (and yes does a lot of development) should not hinder the further development from MySQL too much.

So what about Java? Ha, this is a matter that is important to me. As everybody else, I think that Java was the one reason for Oracle to buy Sun. Why? Because apart from its database all other products are running Java, and Java is used a lot by its existing clients. And controlling Java, well… Fortunately a lot of Java parts are already open source, mainly through the Java Community Process. But, yes, I agree with Douglas Allen’s post on TheServerSide , Oracle has always been about big businesses and this will become true for Java. Arrived, big businesses, as banks, telco’s, 10 billion + companies that have a lot of politics and can shell out hundreds of thousands or euros to pay licenses and consultants.

So what about the smaller more agile new web 2.0 startups that do not need ESB, 2PC, JTA, or EJB?  Yes, Java (J2ee or JEE to be more precise) is used in internet companies like Linkedin.com, Facebook’s Cassandra, Amazon, Google’s Ajax framework GWT that is used for Gmail,  Ebuddy but a lot of new companies are using script languages like PHP , Python or Ruby on Rails. I think this is partly because of perception, partly because of the promise of productivity. Yes, Java has a lot of things you need to learn (strong typing, packages, runtimes) but for bigger projects this helps you to organize things. So yes, I hope the open source part of Java will become stronger, and products like Spring, Tomcat, Jetty, ActiveMQ, Eclipse will form a separate open source ecosystem besides Oracle’s business oriented Java family.

1. extend a UITableViewController instead of implementing UITableviewDataSource and UITableViewDelegate yourself
2. disable reuse of cells by using a unique cell identifier:

NSString *CellIdentifier = [NSString stringWithFormat: @"Cell%i", indexPath.row];

UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];

if (cell == nil) {

cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:CellIdentifier];

..

}

The UITableViewController handles scrolling into view when the keyboard is shown quite nicely. Using the unique identifier will prevent a cell and it’s content to be reused. And I had to agree to some of the feedback: using a UIScrollView to nest a tableView is kind of a hack.

There is a down side to this: UITableViewControllers don’t like to be combined with other view controllers, so you have to use a NavigationController or TabBarController to offer further interaction possibilities. I tried to, but never managed nicely to have for instance a UIToolBar over the UITableView.

Try it out and let me know what you think!

Download XCode project TestTableViewWithKeyboard2 with demo using UITableView to create a form.

So a decent number of iPhone apps will not only show things like data, but also offer you the possibility to edit data. Many controls like UISlider, UISwitch and UITextfield are provided by Apple to create some type of edit screen, almost like a web form on a HTML page. Creating a simple form that only covers the top half of your screen is simple: you create your elements like UITextField at the top, and when you touch inside the field the onscreen keyboard will show up. You hit a Done Button or a non-UITextField control and the keyboard disappears again.

Now, when you have more data to add/edit than will fit in half a screen, things get more daunting:

1. the keyboard should only be visible when editing a UITextField
2. when touching a UITextField so that the keyboard becomes visible, it should not cover the field you are editing
3. with the keyboard visible you should still be able to scroll to all elements of your editing form, and not have parts be covered indefinitely by the keyboard

Well, the most natural kind of view to use to display all controls is a UITableView. Apple uses it herself, look at the editing screen for your Mail.app settings. But when you just throw in a UITableView, you run into problems:

1. when scrolling off screen, table cells are reused and therefore also its subviews like UITextFields, which causes your newly entered data to be destroyed
2. when having a UITextField being firstResponder (cursor in it),  you scroll it off screen and the touch inside another UITextField that then becomes firstResponder, your app will crash. This is problably because the first UITextField is destroyed before it can resignFirstResponder

So how do we do this then? Apple does use a UITableView in some way, but the above problems are show stoppers. Well the answer is: use a UITableView, but don’t let it scroll.

The trick is to nest a UITableView inside a UIScrollView. And then to give the table and the contentSize of exactly the same size that the whole form is. So if you have 10 cells each 44 pixels high, you create a UITableView with a height of 440, and put that inside a UIScrollView with a contentSize that is also 440 pixels high. This way the table is exactly the size of all the cells combined. This way no scrolling for the UITableView and therefore no reuse of cell’s with all it’s problems.

Here’s the code to set the size correctly:

// actually more object in reality

self.countries = [[NSMutableArray alloc]initWithObjects: @”Belgium”, @”Brittain”,nil];

[self.scrollView setContentSize:CGSizeMake(320, (CELL_HEIGHT * [self.countries count]))];

[self.tableView setFrame:CGRectMake(0, 0, 320, (CELL_HEIGHT * [self.countries count]))];

Well, that’s the main trick. Added to that, you want to resize the frame when the onscreen keyboard is shown and scroll the UITextField you touched in to scroll into view. Have a look at the source code to see how that’s done.

Download TextfieldsWithKeyboard XCode iPhone project

Hottest newest features of 3Gs:

1. better camera
2. faster CPU and more memory
3. better battery life (both by improved hardware and software)
4. video recording and editing
5. voice control

The coolets thing about iPhone OS3.0:

1. Cut-copy-paste
2. MMS (but who uses this anymore?)
3. Push notification (no background processes though, but workable other solution)
4. Spotlight search on your Iphone
5. Thethering (using your phone as a modem for your computer)

So what about disappointments with the new iPhone 3Gs:

1. Evolution not revolution: faster? better camera? video? No brainers I’d say. BTW camera is only 3 MP, in contrast the 2 year old N95 already had a 5 MP camera.
2. In majority of countries the iPhone 3Gs  is only sold together with a rate plan from the local telco (AT&T in USA, T-mobile in the Netherlands). So you have to agree to a 2 year contract to get your hands on an 3Gs, even if you already have an iPhone. Guess I will be going down to Belgium, where by law this practice is forbidden and phones have to be available also for sale without a contract. Expect to pay 600-700 Euro for a phone. Yes, a lot of money.
3. Tethering works on the phone, but the telco may not allow it. Why? Because they are not ready yet, network wise. And of course they sell separate 3G receivers for computers with a big fat contract.
4. Standard apps are the same. Yes landschape keyboard message typing, but no major upgrades
5. No development phones . So 1. you have to get a contract to get a phone, and 2. no special phones with you can play around with, like restoring an OS image any moment you want to. In contrast, for Android there is a special Dev phone, no lock and completely customizable. You can restore specific OS images, or even toy with the OS and it’s system’s libraries if you want to. Fear of misuse of development phones has been cited to be the reason for Apple not to put out developer phones. I’d say make them as ugly as the Android dev g1, and you don’t have a problem. And sell only a limited number to registered developers (only 50.000 world wide in March)
6. Still missing: Flash!

Overall verdict: better than the previous model, but no big surprises. Let’s see what cool Android devices will show up, so that real competition arises.

More reading:

• Gizmodo’s iPhone 3GS Complete Feature Guide
• Crunchgear.com’s review of Iphone 3Gs
• Say hello to the iPhone 3Gs (techcrunch.com)
  

Google has been very secretive of their server and data center design. They own dozens of data centers around the world, trying to get as close as possible to the end user while reducing reliance on a limited set of data center and network backbones. Last week more details were released about their home grown server design. Keywords: completely Google custom, standard cheap components, all power is 12 Volt, on board battery instead of shared UPS usage. Also they showed their design of data centers, which is very interesting. Keywords: shipping containers as standard unit filled with servers within the data center, highly optimised air conditioning and efficient water usage.

Further reading: 

• http://www.datacenterknowledge.com/archives/2009/04/09/googles-data-center-water-treatment-plant/
• http://www.techcrunchit.com/2009/04/09/googles-data-storage-goes-green/

Yesterday Apple held meeting to announce the new upcoming version of their Iphone OS, version 3 (we’re now at 2.2.1), to be released somewhere this summer. Already days ahead was a buzz going on, with lot’s of people making lists of new features they thought/wished were added to the already popular platform.

Major awaited features were cut/copy-paste, Flash, background processes, MMS, tethering (using your phone as a modem to your laptop), wireless keyboards, better app organisation

Majority of new features are indeed implemented. Cut/copy-past is there in a nice fashion as is MMS and tethering. Flash is still at large, Adobe and Apple are trying their best to solve the technical issues. Background processes are not there, but instead Apple opted for Push notifications. This will allow a service to push a short message (alert, text, audio) to an application without the application being running. Wireless keyboards and better app organisation is still missing.

What is also interesting is the new payment models. Now, you could only charge per download. Added to this will be 3 new models: subscription to apps, purchase of additional content (great for media companies) and purchase of additional levels (great for gaming apps). This means you can also purchase new things from within the apps.

What is most interesting to me?  The push notification! I am working together with partners to create a messaging solution with a big focus on mobile. As third party apps, as opposed to the standard Mail.app on the Iphone, cannot run in the background with 2.0 it’s quite difficult to go head to head with Mail.app. Push notification will change that. As this services goes through Apple services, I am quite curious what they will charge though.

Other new features that were not so much anticipated are Search (through Spotlight), landscape keyboard, Google Maps libraries for third party apps.

I downloaded the beta SDK already, but unfortunately Apple doesn’t allow any disclosure of information or screenshots:( I honoustly hope they don’t make the mistake that they made with 2.0 again, to lift this NDA so late that no publisher dares to invest in publishing an Iphone 3.0 development book. Go over to Crunchgear to see some screenshots (while it lasts).

OS 3.0 will be available this summer, and downloadable for current Iphone and Ipod touch users (Ipod users have to pay 10 USD). So you don’t have to get a new phone to be able to run 3.0, which is great. Big question: at what speed will users upgrade their OS, and will any (major) problems arise. 

You can watch the full presentation here at the Apple site.

More reading about Iphone OS 3.0:

• http://www.tuaw.com/2009/03/17/iphone-3-0-feature-roundup/
• http://i.gizmodo.com/5171796/iphone-30-os-guide-everything-you-need-to-know
• http://www.engadget.com/2009/03/17/iphone-os-3-0-hands-on/
• Techmeme coverage of Iphone OS 3.0

After Apple launched the Iphone 3G last summer, T-mobile will begin rolling out the Android platform in The Netherlands. Within weeks the HTC G1 will be available (the phone has been out in the USA since October and in the UK since November). And now, to the surprise of the whole industry Palm made a strong comeback with the Palm Pre, running their brand new OS called webOs. It has been announced at CES just last week, but yet has to get reviews and into the market.

So, it seems that we have at least 2 strong players with an outsider (Palm) ready to bring mobile computing to the next level, and really change that thing in our pockets and hands into a computer with a small screen instead of just an apparatus to call and text with. It’s not about that anymore, it’s about all the applications that you can run on.

What will determine the success of these platforms?

• user experience: usability, seamless integration, slick looks: Apple with having one device, one manufacturer has controls hardware, OS, store has created a complete package with eco-system around it. And of course it’s experience with good user interfaces and design for Mac and Ipod has given it a head start. Android is not a complete deal but a platform, that hardware manufactures have to run on their phones that will come in many shapes and forms.
• good apps that can easily be purchased:
  • developer support: good language and good tooling. Apple offers Objective-C with a number of UI libraries, together with their IDE Xcode. Android is for 95 % Java, that is supported by Eclipse plugins. This means that all those Java developers out that can start creating Android apps in no time, while much less Objective-C developers are out there. Learning Objective-C and XCode will take some time for developers from other platforms.
  • easy app stores to browse, look, buy and download applications. Apple’s app store has already proved to be a success. Android’s app store has yet to kick in. Maybe multiple app stores will become available, that certainly will be more open but also more fragmented than Apple’s.
  • the creation of an ecosystem that makes it profitable for developers to create apps for a platform is crucial for turning phones into a mobile computing platform. Until now the Apple app store has been a success, offering free and paid apps. Selling an app is just submitting the app to the store, although Apple has rejected apps for unclear reasons. This means that you do not know if your investment will make any money untill you submit the app, which is definitely a bad thing. Also installation of apps should not be limited by telco settings or anything.
• good availability of devices. For now Apple has chosen to sell the Iphone in most countries only together with a subscription plan with a mobile operator. For instance, if you are with Vodafone.nl but want an Iphone, you’re stuck. Of course the device is expensive (you can get it simlock free in Belgium for 650-700 EUR), but why not let users buy it simlock free? Android devices when on the market will soon be available in all kind of forms, and with or without subscription packages.
• pricing: Apple is and will always be a brand that focuses on quality and less on competing on price. Android is open source and free, so let’s see if any manufacturer will create a cheap but powerful Android phone.

And oh yeah, where are the mobile manufacturers? Nokia, Motorola, Ericsson? Motorola apparently is getting ready to move over to Android.  Nokia still hangs on to Symbian, but that OS never got the leverage Iphone OS and Android seem to get. It will take a while though before Nokia admits that Symbian is dead, and that is has to switch over. So apparently it took computer companies to move over to the mobile industry to really make phones a success as a computing platform. Let’s hope they do not turn Android into a fragmented market that brings no value to end users and developers.

More reading:

• Phonedog.com review of HTC G1
• Robert Scoble’s post about the Palm Pre
• Is Android’s language Java?

So why? Well, not to replace my Dell XPS machine, which has been my faithful companion for the last 8  months I have worked as a freelancer. With 4 GB memory it runs Vista just fine. No, for 2 reasons I wanted to get a Mac: first, to be able to test my web sites on a Mac, as more and more users have Macs. Second, to be able to develop Iphone apps. As mobility is important to me, a laptop was a natural choice. A 15 inch Macbook pro would have been a more productive option, but equally more expensive. So I settled for a Macbook 13 inch.

So what is my first impression? I never owed a Mac, but worked quite a lot with Macs like Apple Classic at the universities I studied. So I have some experience with them, but not too much recently. So getting to know the specifics of Mac OS X will get some time. For instance I am used to type blindly, so doing Apple-C instead of Ctrl-C etc. will take some time. Also Ctrl-Home doesn’t really seem to have a Mac equivalent. Of course operating the new trackpad will take to get used to, but is already fun. Increasing the font size by just swiping two fingers is a breeze, haven’t tried apps that allow rotating images yet. Resize/minimize/maximize buttons are located at the left top hand corner, not right as on Windows. And maximizing works differently.

Of course under the hood is a real Unix (FreeBSD) operating system, so within 15 minutes I was having a go at the terminal. Quite a relief to type in a command like  locate java | grep -c class. There is a lot preinstalled, like Java, and even Maven (although not the version I need). A root account you need to activate first, but after that you can change what you want, su-ing to root first.

What does it look like? Well perfect of course, it’s Apple. The aluminum case is perfect, and so is the LED screen. Quite sharp, but a bit shiny/reflective.

How does it perform? Pretty good, Eclipse runs just fine with 2 Gb of memory. Hard drive is not too fast, but still pretty fast. But what is really remarkable to me is battery life: 4-5 hours. My XPS does 1-1.5 hours, what a difference. I don’t know if it is because the laptop is so efficient or the battery is so good, but it is impressive. Also it is pretty cool, perfect to have this machine on your lap.

Overall, I am quite happy with my machine. I downloaded the Iphone SDK and am anxiously awaiting my Iphone. Will be a lot of fun!

More reviews:

http://gizmodo.com/5063492/macbook-and-macbook-pro-dual-review

http://online.wsj.com/video/mossberg-reviews-new-macbook/5143CE13-603E-438B-8E39-5FDE666726E3.html

http://www.obsessable.com/news/2008/10/16/warhammer-online-on-a-macbook-2008-running-xp/

First my requirements for a netbook:

1. dispensable: so cheap and not containing any vital information (which rules out bringing my main laptop)
2. light: easy to carry around
3. proper keyboard: typing long messages on a N95 phone becomes difficult after some time..
4. Standard browser installed that can show web sites in a normal way.
5. Good Wifi
6. Good battery life

So how does the EEE hold up in practice?:

1. Dispensable: at 300 euro’s yes I say it is dispensable, and as it is not my main laptop I do not store important data on it. That’s a yes
2. Light: less than a kilo, so yes. Of course it can’t fit in a pocket, but that should speak for itself
3. Proper keyboard: party. Yes it has to fit a 9 inch netbook, so of course it is smaller than a normal keyboard. I am used to typing blind with 10 fingers, well I can’t on this machine. Although I have pretty small fingers that is not possible, so I have to type with 4 fingers, and look a lot at the keyboard. That’s a yes/no
4. Standard browser: yes. It has Firefox 3 installed with Flash.
5. Good wifi: well, I can’t connect it to Airport networks. And although everybody was suffering from less-than-perfect wifi at the Excel convention center, my machine seems to be outperformed by others. That’s a yes/no
6. Good battery life: at 3 hours it’s not bad, but also not excellent. The adapter is not heavy and the cord is long enough though.

Overall rating: a 7 out of 10. It’s dirt cheap, light and runs Firefox in a pretty normal resolution. Typing you have to get used to though, and the wifi could be better. Performance is ok, although Youtube videos are not as smooth on a real machine. Normal browsing performance is perfect. It has more than enough input/output like USB and VGA, for me the webcam wasn’t necessary.

Hyves will support version 0.7, the version with Javascript but without REST support. So why am I attending? Well, I helped Hyves out integrating Shindig, the java implementation of OpenSocial at Hyves. So I am there to see if all works as intended:)

For more info, check out the Hyves API hyve.