Topic Review (Newest First)
|
| 24-06-2009 10:59 PM |
| Jonnycat26 |
Quote:
Originally Posted by Unregistered
I think that's a loose assumption. NGage has nothing much to do with S60.
QT FOR S60 as it is called:
|
Actually, the Symbian foundation roadmap (as reported on this site) has reported that QT is *replacing* the S60 UI. S60 service components are being retained, but the UI is history.
Suck it up, it's true.
|
| 24-06-2009 07:27 PM |
| Unregistered |
Quote:
Originally Posted by Jonnycat26
Isn't the Nokia calculator from beta labs written in Java?
Nokia is definitely pushing widgets and Java to help developers survive the S60 UI - QT UI migration. They've been pushing it with NGage for a number of reasons, and they obviously believe in it to the point where they've felt it's OK to drop 3D chipsets from handsets (I suppose they feel it's not necessary with the J2ME 3D APIs).
|
I think that's a loose assumption. NGage has nothing much to do with S60.
QT FOR S60 as it is called:
http://wiki.forum.nokia.com/index.php/Qt_for_S60
FOR S60, not instead of.
The 3D chipsets conjecture is a joke too. This whole java thing is utterly lame and I am bored with it. Bank on J2ME if you like, you'll be down with the second raters and bargain basement.
|
| 24-06-2009 04:33 PM |
| Jonnycat26 |
Quote:
Originally Posted by Unregistered
As a developer I see no push for java. I see widgets, but no java. If the popular Nokia supplied apps like sprot tracker, maps, photo browser beta, Ovi were java then I would agree. But they are not.
|
Isn't the Nokia calculator from beta labs written in Java?
Nokia is definitely pushing widgets and Java to help developers survive the S60 UI - QT UI migration. They've been pushing it with NGage for a number of reasons, and they obviously believe in it to the point where they've felt it's OK to drop 3D chipsets from handsets (I suppose they feel it's not necessary with the J2ME 3D APIs).
|
| 24-06-2009 07:53 AM |
| Unregistered |
timber maquet
Quote:
Originally Posted by Jonnycat26
That's true. It's also true that the roadmap also clearly says that QT will replace the S60 UI in Symbian^3.
|
That will be "QT for S60" as Nokia call it. QT programming is done in C++. Java is there for convenience, PYS60 would make a better higher level partner for Nokias.
|
| 24-06-2009 07:41 AM |
| Unregistered |
Quote:
Originally Posted by Jonnycat26
That's true. It's also true that the roadmap also clearly says that QT will replace the S60 UI in Symbian^3.
Java is being pushed by Nokia, and for good reason.
|
As a developer I see no push for java. I see widgets, but no java. If the popular Nokia supplied apps like sprot tracker, maps, photo browser beta, Ovi were java then I would agree. But they are not.
|
| 23-06-2009 11:41 PM |
| Jonnycat26 |
Quote:
Originally Posted by Unregistered
That's just a lie. The forums are getting silly. The roadmap clearly says Symbian^2 will stay compatible with S60 apps.
|
That's true. It's also true that the roadmap also clearly says that QT will replace the S60 UI in Symbian^3.
Java is being pushed by Nokia, and for good reason.
|
| 23-06-2009 09:13 PM |
| Unregistered |
Quote:
Originally Posted by Jonnycat26
Part of the problem for the java haters is, Nokia is actively pushing developers towards J2ME and WRT. The other part is, J2ME just makes sense if you're going to do any Symbian development. S60 is scheduled to be phased out (per the Symbian foundation roadmap) next year, and any development investment would be shot once that happens.
|
That's just a lie. The forums are getting silly. The roadmap clearly says Symbian^2 will stay compatible with S60 apps.
And further, the apps that have really gone down well (because they have silly UI effects in them) have been Symbian native apps. Like Gravity. No java app ever caused a splash like Gravity. Same with Profimail, which doesn't even use S60.
Java = bargain basement.
|
| 23-06-2009 04:56 PM |
| Jonnycat26 |
Part of the problem for the java haters is, Nokia is actively pushing developers towards J2ME and WRT. The other part is, J2ME just makes sense if you're going to do any Symbian development. S60 is scheduled to be phased out (per the Symbian foundation roadmap) next year, and any development investment would be shot once that happens.
I see native Symbian apps becoming rarer and rarer, and relagated to the "system" level, with J2ME becoming more and more common. A quick look at what's being offered via Ovi seems to confirm that.
|
| 23-06-2009 10:12 AM |
| Unregistered |
Quote:
Originally Posted by malbry
Well, I guess that's what I mean by 'well-written'. J2ME has supported pointer events from the start. So a competent programmer would write code which catered for both touch and non-touch devices and for varying screen sizes. I mean we know there are devices with different form factors out there. Anyone writing code just for QVGA non-touch devices would realise that he/she is limiting the portability of their software. I still maintain that well-written Java code is reasonably portable. Not 100% perfect, but on the whole less work to move between devices than (for example) C++.
Best regards,
Malcolm
|
Even with all the best intentions and cleanest programming, only the simple, basic apps work out reasonably portable.
|
| 23-06-2009 08:27 AM |
| malbry |
Quote:
Originally Posted by Unregistered
But java isn't portable, write once run anywhere is pure marketing BS hype. Program your app for Nokia device #1, then re-program for device #2 with its new touch interface and different screen dimensions.
|
Well, I guess that's what I mean by 'well-written'. J2ME has supported pointer events from the start. So a competent programmer would write code which catered for both touch and non-touch devices and for varying screen sizes. I mean we know there are devices with different form factors out there. Anyone writing code just for QVGA non-touch devices would realise that he/she is limiting the portability of their software. I still maintain that well-written Java code is reasonably portable. Not 100% perfect, but on the whole less work to move between devices than (for example) C++.
Best regards,
Malcolm
|
| 23-06-2009 07:40 AM |
| Unregistered |
Quote:
Originally Posted by Unregistered
But java isn't portable, write once run anywhere is pure marketing BS hype. Program your app for Nokia device #1, then re-program for device #2 with its new touch interface and different screen dimensions.
It is just as easy to use C++.
|
Correct. "Minimal customisation" LOL! Someone must have a minimal app.
|
| 23-06-2009 07:38 AM |
| Unregistered |
But java isn't portable, write once run anywhere is pure marketing BS hype. Program your app for Nokia device #1, then re-program for device #2 with its new touch interface and different screen dimensions.
It is just as easy to use C++.
|
| 23-06-2009 07:03 AM |
| malbry |
Well J2ME certainly has some weaknesses, as the previous posters have highlighted. But when I decided to write a mobile personal finance application in 2004, I figured that I was going to spend many hundreds of hours coding and refining the program. I wanted to create an application that was as 'future-proof' as possible. Knowing that I change phones every 12 to 18 months, I didn't want to find that my latest must-have device wasn't compatible with the software I'd written. Back in 2004 (pre Android, pre iPhone), the only language that ran on almost every phone was Java.
Five years later, it is still the case that Java is the most widely-used language on mobile devices - whether normal 'dumb' phones by most manufacturers, S40, S60, UIQ3, WinMob, Blackberry. Yes, there are some quirks in the Java implementations. But generally well-written J2ME code will run on all these devices with minimal customisation.
Not so for Android and iPhone which, in my opinion, is a shame.
Best regards,
Malcolm
www.freepoc.org
|
| 23-06-2009 03:41 AM |
| Unregistered |
J2me
"Any language that has to include its own src in the executable to work (regardless of the reasons) is just insane on a limited memory device such as mobiles, even today"
Are you sure about that? I think you may be thinking of JavaScript. afaik, Java uses IL, in the same way .net does, which is NOT source, but rather a platform independent binary. Yes, slightly bigger than a normal binary, but with an efficient runtime engine, almost as performant, and the choice of dev environment, and portability make it a no brainer for cross platform apps, which is where the money is, and where developers will generally go.
on another topic, are these captcha's getting more and more abstract, or do I need glasses?? :P Had to refresh 3 times before I could get the words..
|
| 23-06-2009 12:45 AM |
| Unregistered |
java thoughts
this continues from the last posting, when comparing say the N97 against the iphone, aside from the proof of concept features, and bells and whistles "how many applications serve a purpose" on both platforms and how many are simply bloatware. fun applications are nice, however not when there are about 7-8 doing the same thing imo.
|
Posting Rules
|
You may not post new threads
You may post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
All times are GMT. The time now is 04:58 AM.
|
|
