![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
hirez(That's the sound of me hitting a wall)
Bugger.
As mentioned previous, like, some part of the S-40 http connector bolts a ':80' into the URL. While not illegal, it's spurious and confuses Gradwell's cgi-wrapping script. Neither problem appears fixable by me in any useful timeframe.
It would also seem that direct access to the camera is part of the Mobile Media API, which is (drum roll) S-60 only. Ok, not a problem. There's a Good Enough picture-taking application that saves out JPEGs - I can just grab those and...
... Bollocks. I don't hold out much hope of the saved pictures in the phone being available as part of the Palm-like 'record store'. (Can't think of anywhere else they might be, mind.)
[Sigh]
Does anyone want a nice biorhythm calculator?
Bugger.
As mentioned previous, like, some part of the S-40 http connector bolts a ':80' into the URL. While not illegal, it's spurious and confuses Gradwell's cgi-wrapping script. Neither problem appears fixable by me in any useful timeframe.
It would also seem that direct access to the camera is part of the Mobile Media API, which is (drum roll) S-60 only. Ok, not a problem. There's a Good Enough picture-taking application that saves out JPEGs - I can just grab those and...
... Bollocks. I don't hold out much hope of the saved pictures in the phone being available as part of the Palm-like 'record store'. (Can't think of anywhere else they might be, mind.)
[Sigh]
Does anyone want a nice biorhythm calculator?
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2003-10-21 03:54 am (UTC)You couldn't simply wrap the wrapping script? (A comment offered in total ignorance of what the wrapping script actually does or where it sits in the chain of things - but removing all occurrances of :80 is quite an easy problem).
no subject
Date: 2003-10-21 03:57 am (UTC)It appears to me that you're trying to create an all-singing-all-dancing all-in-one application for a series of tasks that should essentially be client-server.
The phone is your client.
The web server is your bitch.
Let the web server do all the hard work. You have a perfectly capable colour WAP browser on your phone, you have a perfectly functioning "send phonecam picture as email attachment" feature, why on earth do you want to process the pictures on the phone? This is so not the place.
How I'd Do It:
This is a task for PHP & Perl, not J2ME. J2ME, as you pointed out, is for biorhythms and tetris-clones. (I do have a rather excellent J2ME-MIDP Solitaire, if you want it).
no subject
Date: 2003-10-21 04:33 am (UTC)It's actually three lines of mod_rewrite that looks like a terrible accident in a regular expression factory. And there's some other malarkey to get it running as unprived punter in a BSD jail.
If I point the thing at my BSD box (that runs a webswerver on port 82 so BY's security scanner doesn't have a fit) then it works cheerfully enough.
no subject
Date: 2003-10-21 04:39 am (UTC)no subject
Date: 2003-10-21 04:55 am (UTC)You've not read anything I've posted previously, have you?
[Oh, and the next person who uses the phrase '($thing) is your/my bitch' in my hearing is going to be Spoken To.]
It is client-server. There's a documented spec. for talking to (most) weblog code what is known to work. If I want to Just Do Text, then I could install Azure or Kablog on the phone and have done with it.
I don't want to 'process' the picture on the phone. There's a JPEG in a 'directory' on the device. I want to open that, translate it to base64 (a kXML library function, so I don't have to do any work there either) and squirt it up the line as a 'metaweblog.mediaUpload' RPC call. The MMS library isn't going to be doing anything different.
The functionality for remote clients is already in the weblog code. I'm trying not to reinvent boring wheels and have a small amount of fun fiddling with Shiny Toys.
But if the phone is crippled such that you have to use MMS to get pictures off the thing and thus make $$$ for the airtime provider... I shan't be in the least bit surprised.
no subject
Date: 2003-10-21 04:58 am (UTC)no subject
Date: 2003-10-21 05:40 am (UTC)I do get exactly what you're aiming at here; yes, you are already doing client-server so I should have purported my 2p as "browser-server" instead of "client-server".
> There's a JPEG in a 'directory' on the device. I want to open that, translate it to base64 (a kXML library function, so I don't have to do any work there either) and squirt it up the line as a 'metaweblog.mediaUpload' RPC call.
I don't think you're going to be able to do that, and even if you could, I very much doubt you'd still have a useful program wot would work on anything other than your specific phone running your specific firmware revision. AFAIK (and if I've got this wrong, I am missing the point) there is no standard for addressing phonecam pics from J2ME because there is no standard for where the pics are stored on all phones (and that's without even addressing the sandbox issue- do we really want our Java applets to be allowed to crawl around the innards of our phones? That's a recipe for virii and privacy breaches).
Which is why we've all been complaining about the nonstandardness of J2ME and why I suggested bypassing J2ME altogether and doing the whole thing via the already proven and very much standardised MMS/WAP route.
I also don't see what advantages editing the entry (be it pics, HTML, plaintext, whatever) on a client application on the phone, as opposed to doing it via a WAP browser with a WML form, provides.
>The MMS library isn't going to be doing anything different. [...] But if the phone is crippled such that you have to use MMS to get pictures off the thing and thus make $$$ for the airtime provider... I shan't be in the least bit surprised.
I think Sir very much has the measure of the situation. My solution was knock up a dirty sendmail perl script and then swear a little, buy a bolt-on bundle of MMSes for 3 quid extra a month, and be done with it, rather than pay 50p+ per pic and swear a lot.
no subject
Date: 2003-10-21 05:43 am (UTC)On the :80 front, questions:
Is this just a Gradwell problem ? If so, got anywhere else where it could be hosted ?
Is there a possible hack to get you going on Gradwell involving a tiny url-rewriting proxy ?
If you use the phone's HTTP layer to post stuff directly, does it do the :80 thing ? If not, you have a variety of hackety-hack options available (get xml-rps to make you the text, the post it yourself, or make the text by printf, or whatever)
no subject
Date: 2003-10-21 05:49 am (UTC)no subject
Date: 2003-10-21 06:06 am (UTC)And if Java won't do it, there's always C++/Symbian development. That would be fun.
no subject
Date: 2003-10-21 06:16 am (UTC)Although XML-RPC is cheerfully bidirectional.
I'll have a look at mod_rewrite. I may be some time...
no subject
Date: 2003-10-21 06:17 am (UTC)no subject
Date: 2003-10-21 06:21 am (UTC)no subject
Date: 2003-10-21 06:36 am (UTC)Gradwell? Yes. Hosting elsewhere? Not worth the hassle-value.
Possibly.
I think so. There's next-to-nothing in that library. (in that it's a sensibly written layer on top of the XML library) I've not really tried to prod it with a stick.
Brain hurts. Will fiddle with MX settings and LDAP instead, given it's daytime.
(You were just taunting me with those latches, right? What are they for?)
no subject
Date: 2003-10-21 06:54 am (UTC)~HS~
Luci xxx (the human touch to your posts)
no subject
Date: 2003-10-21 06:57 am (UTC)Oh, you mean what are they *for* ? God knows. They're each the size of your foot. They're explosion-venting latches, with a calibrated (and adjustable) push-open force so when your chemical plant goes up all the doors fly open in a Laurel-and-Hardy manner. These are 180-lb open-force models. But I think I'll be likely to use as Gratuitously Big Latches on some as-yet-uninvented item of furniture.
More details here:
http://www.brixon.com/latch3.htm
and here :
http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=2563136269&ssPageName=ADME:B:EOAB:UK:6
no subject
Date: 2003-10-21 07:43 am (UTC)no subject
Date: 2003-10-21 09:06 am (UTC)*waits*......
~HS~
Luci xxx
no subject
Date: 2003-10-21 12:23 pm (UTC)Though I don't know how much deeper I can get into forum.nokia w/o running amok...
no subject
Date: 2003-10-21 01:43 pm (UTC)For a java enabled phone with source and install instructions? Yes. Spent half an hour trying to write "hellophone" failed. (Phone says "file format not recognised" to my .jar but recognises other people's fine - I suspect I am missing lots of the technicalities so an example would help lots).
no subject
Date: 2003-10-21 02:24 pm (UTC)The Currant-bun Wireless Toolkit works well enough, though it defaults to MIDP-2.0 projects. The 7210/50/i is a MIDP-1.0 device, so if you've got one of them it'll fail dismally. Edit the field in the .jad file (project properties button), rebuild, repackage, reinstall, repair to the pub.
Mind you, if you've a !Nokia, then I'm less sure. As if I knew anything anyway.
(The 'calculator' thing probably makes more sense if read in the same tone as 'Would anyone like a nice game of chess?')
no subject
Date: 2003-10-21 02:37 pm (UTC)Hmm.. just my luck. Still, that Deathboy post is useful indeed - thanks kindly for pointing it out.
no subject
Date: 2003-10-21 03:47 pm (UTC)no subject
Date: 2003-10-21 03:55 pm (UTC)*bounce*. Now, what chance I could get a z-machine emulator running on it.
Actually, I really should do some proper real work - but this stuff is fun.
Re: Does anyone want a nice biorhythm calculator?
Date: 2003-10-25 07:10 pm (UTC)No...don't say a word! ... I much preferred my old Sony CMD J5 ... And before yoy say anything about that, unless you've used one ... and then gone back to a 'normal' Nokia-style system and discovered just how UNfuckingIntuitive it is ... you have absolutely NO idea of what the words 'intuitive', 'user-friendly' or 'transparent' actually mean
Re: Does anyone want a nice biorhythm calculator?
Date: 2003-10-26 02:46 am (UTC)I suspect not.
This Java business appears to be flash-bastard smartphones only (aka 'kit that's licensed Symbian'). And handbag-specials like the 72xx series. (aka 'bare minimum j2me you bastards')
I think phone UIs have gone downhill ever since they did away with the rotary dial and the bakelite handset attached with plaited fabric-covered wire.