Hi Gernot.
I just got this auto-rejection from HP -
Quote
Your App Has Been Rejected
We received the following submission on 2011-07-06 19:11:24:
Ken2X - MathDoku
com.iprice.ken2x
One or more serious issues were found and your app was rejected. These issues were identified using an automated app scanner that is a new part of the app review process. If you feel any of these issues were found in error, please contact us at pdc@palm.com.
Please review the list below, update your application and/or its metadata and submit the revision when you are ready.
The App Review Team
App Type Mismatch
Your application may have configuration errors that must be corrected. The application type specified in your appinfo.json file does not match with the application content in the package.
The following issues were found:
appinfo.json: App is a PDK app
Non-public Library Linkage
Your application uses non-public libraries or restricted symbols. You can review the library policy at http://developer.palm.com/help/index.php?topic=1817.
The following issues were found:
glbasic-webos-exe: app links to libdl.so.2
Non-public API Usage
Your application may be using non-public APIs. Please remember that your application should only be using API's that are documented on the HP webOS Developer Center. You can review our application criteria here: http://developer.palm.com/help/index.php?topic=1817.
The following issues were found:
glbasic-webos-exe: app calls dlopen
glbasic-webos-exe: app calls dlsym
The app was created with v10.XX. I never had this problem with V9.XX
:(
Might be worth emailing PDC to see if it can be manually forced through - people have to do that if they use Bluetooth for example...
QuotePlease remember that your application should only be using API's that are documented on the HP webOS Developer Center.
QuoteMight be worth emailing PDC to see if it can be manually forced through - people have to do that if they use Bluetooth for example...
I know it states "should" and not "must" so I will contact PDC tomorrow (hopefully Gernot will comment on this). New public APIs are released daily, so it's a bit unfair on devs to stick to a proven few. I can understand the reasons for this though.
[EDIT] Sod it. The email states contact PDC, so I did. Fingers crossed that the rejection will be overturned and the app properly reviewed (and probably rejected then).
No-one has mentioned it on the Palm forums, so you might be okay :)
I sent them links to PDC to show that the extra libs etc are public and open-source. Hopefully that'll do the trick.
I'll keep you posted.
That'll be great!
[UPDATE]
Chuq responded already and has passed it along to the Review Team. My app is still marked as Rejected in App Status though. Hopefully this will be sorted soon :)
Hopefully they wont be too long...
I'll remove the DECLARE functions for WebOS - noone's gonna load a .so file anyway.
So sorry. I'll try to kick an update within the next hours.
Cheers Gernot.
Update for v10 rC is live.
I just did a test for an update and got it. That was fast! Cheers Gernot =D
Rather than using the old "Wait and see" method, I re-submitted the app. It went through (the submission process) without problems this time.
Phew!! Palm is my favorite platform. I really would weep if we were locked out of it.
I suppose allowing dyload and all those functions could become a security risk. Would have been interesting to see if they would have allowed it though.
QuotePalm is my favorite platform. I really would weep if we were locked out of it.
So Gernot, have you ordered a TouchPad yet? Is GLB likely to work on TouchPad as it is now? Does anyone know anyone that can test GLB apps on a TouchPad?
All this and more will be revealed (maybe) in the next exciting installment! :P
BTW The app status is now "Ready for review", so it's been accepted past the "Submitted" stage. I suspect that it'll take a while to see it available, with HP wanting to get TP apps out there.
GLBasic should work on a Touchpad as it would scale graphics if not set for its default resolution.
Unfortunately, reviews of the device haven't been overwhelmingly positive - at the moment it suffers from speed issues, especially when rotating the device and all applications having to be rotated. However, it should be possible to solve this with an update.
By the way, if you use keyboard entry or use DDGui, you may get an email from Peter Helm saying it's not compatible with the Touchpad. For DDgui, I just sent him back a screenshot of the on-screen keyboard that DDgui uses when clicking on an text entry widget, and he promised to re-evalutate the application :
QuoteI wanted to contact you about some issues we came across in testing Spots for compatibility with the HP TouchPad.
As you may already know, PDK apps originally developed for smartphones can run on the TouchPad in "PDK portability mode," which emulates their native environment and automatically scales the graphics to run full-screen on the TouchPad. However, PDK portability mode has some limitations and doesn't work optimally for every app. Unfortunately, Spots has been marked as Not TouchPad Compatible as it requires a physical keyboard to create a profile.
Adding TouchPad support to your PDK app
Because apps running in PDK portability mode have inherent limitations, including lower apparent resolution and sometimes slower performance, we encourage you to develop a version of your app that is made specifically for the TouchPad using the webOS 3.0 SDK, now available in our Early Access program. This positions you to take advantage of TouchPad's big summer launch.
We have also posted an article on preparing your PDK app for TouchPad in our Early Access forums for your reference. If you do not have Early Access, I have included the information at the end of this email for your private use only – please do not share or post this information through any public channels, as this is under our private Early Access program at this time.
Addressing issues with your app in PDK portability mode
While we generally advise you to prepare an update for your app that runs on TouchPad without relying on PDK portability mode, there may be some cases in which it makes sense for you to attempt to identify and fix the issues that are causing your application not to function properly in PDK portability mode. For instance, if all that's required to make your app fully functional is to add Back buttons to various screens, the shortest path to a TouchPad-ready app may be for you to simply add those buttons.
After you have made the necessary corrections, you can send the IPK to me so we can test it on TouchPad hardware.
OH!!!!! The WebOS-Version of DDgui won't open a OSD, because the Pre/Veer/Pixi _have_ a real keyboard. We have to find a way to determine it's a Pad and enable the keyboard then. You can set this variable:
GLOBAL DDGUI_AUTO_INPUT_DLG // auto-open DDgui_input, when you click/tap a text?
I've read the reviews and tbh, most have appeared less than professional - highlighting negatives and not/rarely mentioning positive aspects/differences) between the TP and all-conquering iPad. However, it's early days and they are judging a brand new platform against other competing platforms that have had upgrades and many more apps since they were first launched.
Sure, there appear to be plenty of mistakes and indeed missing features in the TP (and that price isn't a seller either), but from what I can see, HP have only had the bat for a year and hit the ground running. HP won't win the race, but it looks as though it's going to put in a good performance. And for us that's great - we've got a pretty open field to play on (don't you just hate sports metaphors?), with fewer competitors playing on it than iPad etc.
If sales of my apps allow, I'll probably get one (I haven't got any form of Pad) at some point.
As for the on-screen keyboard issue - I'd rather roll my own than rely on the standard internal software one - nothing worse than a message or keyboard that is at very much at odds with the app it's being used in.
QuoteGLOBAL DDGUI_AUTO_INPUT_DLG // auto-open DDgui_input, when you click/tap a text?
If I remember correct, I set this to TRUE in Spots, so it does open the OSD - I anticipated what would happen when I was testing the game :) It would be nice if DDgui used the tables OSD as well...
QuoteIf sales of my apps allow, I'll probably get one (I haven't got any form of Pad) at some point.
Considering it's HP's first tablet they did well. I think a fair few reviews are based on pre-production machines as well.
I signed up for Touchpad device loaner program:
https://developer.palm.com/content/community/device_loaner_program.html (https://developer.palm.com/content/community/device_loaner_program.html)
I received an email and should know if a qualify within 12 days.
I'll keep you updated if I get accepted.
for the keyboard issue, I think we need a PLATFORMINFO$("haskeyboard") as well PLATFORMINFO$("haskeypad") or such info, so we can checkout if its have a keyboard, keypad and such? That could been cool to been detected for some Androids phones as well desktop OS too.
or its is something I missing (etc misunderstanding)?
Someone else has just come across this problem : https://developer.palm.com/distribution/viewtopic.php?f=70&t=16165
Apparently it could be a scanner problem :)
There was another one, the same day as mine (IIRC) after I posted my report here too. I never did read the outcome of that one though, forgot all about it due to being busy at work.
Its a good job Gernot changed it, as a definite statement from HP has stated that libdl isn't allowed...
QuoteIts a good job Gernot changed it, as a definite statement from HP has stated that libdl isn't allowed...
Indeed.
Sorry to kick the thread. I'm busy porting my three GLBasic games to Palm Pre and I've ported "Break The Code" which runs just fine on the device. So I've uploaded it and got an e-mail which doesn't mention any "Non-public Library Linkage", so that is good :). But it does still say that it is a PDK (Plug-in Development Kit) app and there is a "App Type Mismatch" (btw I'm using GLBasic IDE v10.106).
Quote
Your App Is Being Reviewed
We received the following submission on 2011-09-09..
...
App Type Mismatch
Your application may have configuration errors that must be corrected. The application type specified in your appinfo.json file does not match with the application content in the package.
The following issues were found:
appinfo.json: App is a PDK app
Please review and save this message. If your app is rejected, you will be asked to address the issues and re-submit your app.
According to this other forum message (https://developer.palm.com/distribution/viewtopic.php?f=90&t=16607) it is actually a bug on HP-Palm's side, and the app-receive script always spits out this e-mail for PDK apps. So I assume you always get this message when submitting Palm apps developed with GLBasic.
I guess I can just ignore this message?
I did and it was all ok. Note that Palm/HP are rubbish at keeping you upto date. My 3 games had been on the store for about 4 days before I realised it. Search the app store every day to see if it is there.
Cheers
Yep, every .PDK app gives that error - just ignore it. Your app will be reviewed as normal and as Crivens states you won't receive any further notification about your apps from HP, unless they reject it. Keep checking "Your Apps" on the Dev portal fro info about your app.
I am glad that it is resolved.
Palm is one of my favorite platforms!
QuotePalm is one of my favorite platforms!
By Palm, I'm presuming you mean webOS. If so, then count me in as a webOS lover too.
Ian Price and Kitty Hello,
I have tested 2 GLBasic games on my HP Touchpad, Crocogame and S-zero.
Crocogame loads and works ok, there is some overlaping of the screen on the right side due to the screen size.
I have to change the mouse inputs, it does not respond well to mouse commands, there is no button 2!
S-zero works fine.
Speed is not a problem they are satisfactory.
On both the problem is the screen size and position, I compiled with screen size 320 x 480.
They also get the screen chopped off on the top.
let me know if you want some screen shots!
I hope that helps.
If you need more testing I am available.
We know about those problems. Gernot (Kitty Hello) hasn't got his TouchPad yet, so has not been able to address the problem. Rest assured that this will be sorted. :)
I'd love to see screenshots of what you are working on - not just to see the problems ;)
Ian Price and Kitty Hello,
Here are the Touchpad screen shots of S-zero and Crocogame.
On The Pre 2 I took a picture os the S-zero, for some reason pressing the keys, Shift+Sym+P causes the screen to change and does not allow me to take the screen shot.
Alos on the Pre2 the Crocogame takes awhile to load, and it crashed after a while.
It may need more memory. ("requiredMemory": 10)
To know if the Palm/HPdevice has a keypad the PLD API has the following options:
int PDL_GetHardwareID(void);
Returns
HARDWARE_UNKNOWN -1
HARDWARE_PRE 101
HARDWARE_PRE_PLUS 102
HARDWARE_PIXI 201
HARDWARE_VEER 301
HARDWARE_PRE_2 401
HARDWARE_PRE_3 501
HARDWARE_TOUCHPAD 601
or
PDL_Err PDL_GetScreenMetrics(PDL_ScreenMetrics *outMetrics);
Device(s) horizontalPixels verticalPixels horizontalDPI verticalDPI aspectRatio
Pre, Pre2, Pre+ 320 480 213 183 1.164
Pixi, Veer 320 400 190 190 1.0
Pre3 480 800 260 260 1.0
TouchPad 1024 768 132 132 1.0
TouchPad GO 1024 768 182 182 1.0
[attachment deleted by admin]
I thought you were talking about your own game (hence why I asked to see screenies). It's always nice to see what others are working on =D
I really wouldn't worry too much about any TouchPad issues at the moment - let Kitty get his paws on a machine and the problems will be sorted pretty quickly.
The screen shots are a good comparison and as you can see they are not the same on Pre2 and TP comparing to Windows.
I am here to help.
Ass soon as I have my first GLBasic game ready i will send you the screen shots!
the pre2 screen looks really great, can the device cope with the 3d at a reasonable speed?
if so, it must be a good piece of hardware
It does, if you look at the FPS at the bottom of the screen it was averaging 65 FPS, some times I saw it at 57 FPS!
The Pre 2 has a nice performace running 3D games from PDK and native code such as the ones generated by GLBasic.
For instance Asphalt 5 on Pre 2 performs the same comparing it to an iPod 3G running the same game!
Enyo runs 2D games well, but you have to use an audio plug in, because repetitive sounds, like shooting and other short clips don't work well on Enyo and neither on Mojo.
Is update for v10 rC available?
Where can I get it?
Available from the front page, downloads section - http://www.glbasic.com/files/glbasic_sdk.exe
Download, then do an internet update.