|
Java
Blogroll Me!
Join Paul's mail list
|
|
Wednesday, February 09, 2005
|
|
|
|
Sunday, June 22, 2003
|
|
| |
:: Very neat utility for XUL interfaces on mobile devices ::
Thinlet is a GUI toolkit, a single Java class, that parses the hierarchy and properties of the GUI, handles user interaction, and calls business logic. It separates the graphic presentation (described in an XML file) and the application methods (written as Java code).
The GUI description is XML User-interface Language, XUL (apparently prounced "zool", rhyming with "cool"). XULPlanet has a tutorial on XUL.
The really great part is that the Thinlet toolkit supports MIDP, so there is a chance to play around with some interesting mobile interface ideas, not that I've tried any yet, just played around with XUL via the fabulous Thinlet authoring tool Theodore. Playing around with the Theodore tool is a great way to learn, or at least appreciate, the power and potential benefits of XUL. You can give it whirl by trying the evaluation copy online (but note that you need to have Java Web Start installed to do this).
You can try out the Thinlet class via some interesting web demos on the Thinlet website, including one that uses the Amazon Web Services API.
2:18:49 PM 
|
|
|
|
|
Wednesday, June 11, 2003
|
|
| |
:: Connecting MIDlets back to J2EE World - Made Easy by Sun ::
The Complexity of Developing Mobile Networked Data Services, J2ME Wireless Connection Wizard for Sun One Studio gives an overview of the J2ME Wireless Connection Wizard for Sun One Studio which facilitates the creation of networked wireless applications and services by automating significant parts of the development process.
Note that this is a proprietary network protocol, but that may not matter to you. If you want to go down the Web Services route, then you might want to look at JSR0172, which is a Web Services API for J2ME.
10:33:44 PM
|
|
|
|
|
Friday, April 04, 2003
|
|
| |
:: Operators "become handheld OS companies" ::
How timely that I should read this article today. I was just writing (in my new book) about the nascent shift in mindset that the operators are going through, some would say from telecoms mentality to IT mentality. The investment mentioned below by Vodafone and Orange would seem like a bid to get directly involved in the IT action to claw back some of the revenues that they would say they bring to handset OS licensors. On the one hand I'm glad they have gone to SaveJE (pronounced "savij"). I was an early adopter of SavaJE on my iPAQ, wiping Pocket PC clean from its memory only to find that this particular version of the SavaJE OS wasn't to be supported any longer by SavaJE - very savage indeed!
I just hope that this is not a bid by these operators to control the end-point of the network and tie-down all the value added services
Vodafone, Orange Invest in Wireless Java OS. Wireless carriers are increasingly getting into the software business as they look for more ways to differentiate their offerings and gain some leverage over Nokia, Microsoft and Symbian. As the market moves toward smartphones software becomes more important to carriers and handset makers. One way or the other we'll end up with a dominant OS that is used across carriers and handset makers. The question remains which one and when. Vodafone and Orange are doing their part by investing is Java start up SaveJe that is working on a full Java OS for handsets. A Java OS would allow Vodafone and Orange to commission completely custom handsets with their own unique interfaces (not necessarily a good thing) while still allowing the devices to run common java apps.
Source: [Techdirt Corporate Intelligence: Techdirt Wireless]
12:12:37 AM
|
|
|
|
|
Thursday, March 27, 2003
|
|
| |
:: Value-based Billing for Wireless Java Applications ::
The current model for charging for Java games is a one-off charge for downloading the game, with the billing mechanism often a premium-charge text message. However, such a model is limited. For an application that involves repeated value-added events, then event-based charging becomes a possibility, just like users pay each time they send a text message. JSR190 is a Java Community initiative to develop a suitable API for event-based charging.
A useful introduction to the topic and the JSR can be found in this article on the DevX website, written by Allen Lau, CTO, Tira Wireless.
11:04:37 AM
|
|
|
|
|
Thursday, March 13, 2003
|
|
| |
:: Wireless IM - Do it right now ::
If you're a Vodafone Live customer, then you can use Vodafone Messenger to chat with buddies. However, you will require their custom desktop client if you want to connect to the tethered world which is probably where most of your IM buddies hang out. However, the Vodafone offering is all set up out-of-the-box (with the appropriate phone) without requiring a PhD in wireless (except the strange twist that you have to register using the web and can't do it via WAP??).
Alternatively, you can download TipicME IM client (MIDP) and chat with anyone on the planet! Shame that the client is optimised for the P800 (as I don't have one).
Hooray for open standards and an open access world (note: remains to be seen if this service is allowable on mobile networks).
9:17:33 AM
|
|
|
|
|
Tuesday, March 04, 2003
|
|
| |
:: MIDlet portability ::
There are a number of issues concerning MIDlet portability from one device to another. Some of these issues are reminiscent of the compatibility problems faced by WAP designers. Testing remains a headache compounded by the problem of having to cope with a legacy of devices that cannot be updated in the field (at least not so easily that an average user would ever bother - or know about most likely).
I found some of the articles on Consultancy Penrillian's download site very informative on this issue. Managing Director Charles Weir has also written an intriguing book on patterns for low memory software design, though I have not read it myself, it seems to come highly recommended. I remember all too well the amount of research we did at Motorola into memory utilisation in GSM DSP devices. The irony was that much of the optimisation was done in the algorithms only to have clumsy control code hog all the memory. Perhaps this book would have been useful back then and is probably useful now to the MIDlet designers out there operating on low memory budgets.
6:00:18 PM
|
|
|
|
© Copyright
2005
Paul Golding.
Last update:
3/26/2005; 8:58:20 PM.
|
|
| March 2005 |
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
| |
|
1 |
2 |
3 |
4 |
5 |
| 6 |
7 |
8 |
9 |
10 |
11 |
12 |
| 13 |
14 |
15 |
16 |
17 |
18 |
19 |
| 20 |
21 |
22 |
23 |
24 |
25 |
26 |
| 27 |
28 |
29 |
30 |
31 |
|
|
| Feb Apr |
Sign up to my email list
- Send me email
Visit my personal website to find out more about me.
Consult my booklist
on Amazon
Blogroll:
|
