Developer.com winners for 2006
By lukas on Jan 10, 2006
but... Personally I'm little bit disappointed that NetBeans or Mobility Pack are not listed there.
How could Wireless ToolKit (WTK) beat Mobility Pack?
I understand that they are longer time in the market and therefor well-known in wireless development area. I understand that users use it as emulator platform and run application on it. I understand that users like confusing, old fashion look of enviroment of KToolbar. Developers like to switch between lot of programs (KToolBar, Notepad, etc.) and like debug with System.out messages. No, I'm kidding I really don't understand it. Why should I vote for a tool that doesn't help me in development in category Wireless/Mobile Development Tool or Add-in of the Year? Are all the mobility developers eclipsoized? - that means that they like their Eclipse so much that they even didn't try NetBeans' Mobility Pack 5.0 (or 4.1, 4.0)? Maybe there is different reason that I'm scared the most - THEY DON'T KNOW US. If they'd know Mobility Pack with they couldn't vote for WTK. I like WTK but I use it only as emulator platform for developing in Mobility Pack. I wanted to use it once for a development but it doesn't provide any editor. WTK enables you only to compile and run. It could be really helpful 5 years ago but I'd expect more from development tool of year 2006. I'm sorry WTK team...
I'll quickly summarize what user can expect from NetBeans' Mobility Pack 5.0:
- real Integrated Development Enviroment (NetBeans) - edit, compile, debug, run, deploy
- integrated emulator platform - WTK 2.2 You can run your MIDlets in emulator immediatelly after installation of Mobility Pack
- device fragmentation solution - code for different devices in the same file - preprocessor, configurations, abilities
- RAD for midlets - drag and drop to create application - Visual Mobile Designer
- support for access to server-side data from MIDlets via servlet - Mobile Client to Web Application (known as Wireless Connection Wizard in 4.1)
- generator of mobile clients for webservices (JSR172) - J2ME Web Services Client
- custom components - WaitSreen, SplashScreen, TableItem
- I definitelly forgot about lot of features that you can find useful and new but they seem normal and old to me
Isn't it much more than compile and run...
NOTE: this is Lukas' opinion. Not his employer