Oh yeah! (OpenTK C#)
[IMG]http://i.imgur.com/CyE6g.jpg[/IMG]
Pretty much hello world with OpenGL, but this time with VBOs
[QUOTE=Matt-;35795497]Oops I'm late but:
[img]http://dl.dropbox.com/u/3659637/fpwaywo/apr.png[/img]
Rating winners of the last thread.[/QUOTE]
Hooray!
[url]http://filesmelt.com/dl/Phyzicle1.apk[/url]
New test build of Phyzicle for Android
This time it should work better on the Galaxy S and the Android 2.2 devices, so if you guys could test it, that'd be awesome :)
Once again, I'd like:
1) Device
2) OS
3) Result of running the app
There are many other fixes (softkey support, better UI sizing, and so on) but I'm mainly concerned about the device compatibility. If you have a device that worked in the previous test, feel free to try it again, just to make sure I didn't fuck something up!
[QUOTE=icantread49;35798438][url]http://filesmelt.com/dl/Phyzicle1.apk[/url]
New test build of Phyzicle for Android
This time it should work better on the Galaxy S and the Android 2.2 devices, so if you guys could test it, that'd be awesome :)
Once again, I'd like:
1) Device
2) OS
3) Result of running the app
There are many other fixes (softkey support, better UI sizing, and so on) but I'm mainly concerned about the device compatibility. If you have a device that worked in the previous test, feel free to try it again, just to make sure I didn't fuck something up![/QUOTE]
Will this work on 4.0+?
[QUOTE=icantread49;35798438][url]http://filesmelt.com/dl/Phyzicle1.apk[/url]
New test build of Phyzicle for Android
This time it should work better on the Galaxy S and the Android 2.2 devices, so if you guys could test it, that'd be awesome :)
Once again, I'd like:
1) Device
2) OS
3) Result of running the app
There are many other fixes (softkey support, better UI sizing, and so on) but I'm mainly concerned about the device compatibility. If you have a device that worked in the previous test, feel free to try it again, just to make sure I didn't fuck something up![/QUOTE]
I tried it on Android x86, but it said that there was a problem parsing the package :(
A couple of things about your app:
A) Please have your app hide the bottom bar on devices with no hardware keys.
B) Your polygon tool is fucked.
C) The UI is a bit confusing, I'm not really sure where to start with the app.
D) Something feels 'off' about scrolling and zooming etc.
[editline]2nd May 2012[/editline]
Android 4.0.1 - Kindle Fire Rooted & Flashed with Linux 3.0 kernel
That space stuff has kind of given me an idea for a game. After sitting down and letting my dead heart spew its creativeness, or lack of, on to a page, I think I have a decent and simple idea. Just want to say that I'm not stealing the planet orbiting idea, as that won't be a major mechanic.
[QUOTE=Jawalt;35798658]Will this work on 4.0+?[/QUOTE]
Yes
[editline]2nd May 2012[/editline]
[QUOTE=supersnail11;35798729]I tried it on Android x86, but it said that there was a problem parsing the package :([/QUOTE]
It's an ARM package
[editline]2nd May 2012[/editline]
[QUOTE=Jawalt;35798792]A couple of things about your app:
A) Please have your app hide the bottom bar on devices with no hardware keys.
[/quote]
Why? How would you exit it?
[quote]
B) Your polygon tool is fucked.
[/quote]
What's fucked about it?
[quote]
C) The UI is a bit confusing, I'm not really sure where to start with the app.
[/quote]
I'm not sure how much simpler the UI can get than "tap the square button, draw squares"
[quote]
D) Something feels 'off' about scrolling and zooming etc.
[/quote]
Hard to figure out what you mean.
This is progressing quite nicely:
[img]http://puu.sh/sBN8[/img]
I hope this doesn't get covered in app reports for null :(
[QUOTE=icantread49;35798945]Yes
[editline]2nd May 2012[/editline]
It's an ARM package
[editline]2nd May 2012[/editline]
Why? How would you exit it?
What's fucked about it?
I'm not sure how much simpler the UI can get than "tap the square button, draw squares"
Hard to figure out what you mean.[/QUOTE]
Well the bar thing handles itself, when you tap the very bottom of the screen it comes back up. It gives a whole solid cm of extra viewing space which is a big deal on 7" tabs.
Draw circles with your n sided polygon tool, watch as it produces crazyness. You should probably find some way to prevent that, or something.
I for instance couldn't figure out how to freeze things, and starting the simulator was non-obvious. You'd expect the start button to be big and in an obvious place.
The fourth might not be your fault, but take a middle-end android device on any version prior to Android 4.0, that's how your scrolling feels.
[QUOTE=Jookia;35798894]That space stuff has kind of given me an idea for a game. After sitting down and letting my dead heart spew its creativeness, or lack of, on to a page, I think I have a decent and simple idea. Just want to say that I'm not stealing the planet orbiting idea, as that won't be a major mechanic.[/QUOTE]
I don't think there's much of an idea left to steal from planet orbiting anyway. N-body sims have been done to death and there's more than a handful of games based around this concept.
Good luck tho!
[QUOTE=Jawalt;35799026]Well the bar thing handles itself, when you tap the very bottom of the screen it comes back up. It gives a whole solid cm of extra viewing space which is a big deal on 7" tabs.[/quote]
Holy fuck is it really 1cm on a 4.0 ROM? I'm running 2.3.3 and the bar is about 5 mm, which feels perfect on the Kindle Fire.
[quote]
Draw circles with your n sided polygon tool, watch as it produces crazyness. You should probably find some way to prevent that, or something.
[/quote]
The triangulation will fail if you draw self-intersecting shapes. It's not worth the effort to prevent it, but I am investigating how to properly triangulate self-intersecting shapes.
[quote]
I for instance couldn't figure out how to freeze things, and starting the simulator was non-obvious. You'd expect the start button to be big and in an obvious place.
[/quote]
Jeez, that's the first item in the FAQ :v: Did you even bother open the side menu and tapping the big question mark? As for the start button, it feels pretty obvious to me, no one else has brought that up. But thanks for the feedback, I'll take it into consideration.
[quote]
The fourth might not be your fault, but take a middle-end android device on any version prior to Android 4.0, that's how your scrolling feels.[/QUOTE]
The Kindle Fire is known to have extremely laggy touch input, if that's what you mean. It does feel slightly less responsive than other tablets.
I spent this entire afternoon and evening trying to get a Java CAS (Computer Algebra System) to compile correctly. It would only compile after I gave Eclipse 3 GB of heap memory and it wanted to recompile itself every time I changed a single line in my own application.
Now you would expect me to say something about a stupidly simple fix, e.g. some compile checkbox in the Eclipse settings. Unfortunately I found out something rather depressing: it's a known bug with the Android SDK.
Now, the Java compiler does actually know about which files change and which don't and it only rebuilds new .class files for those files that change. Unfortunately there's another step in the pipeline that translates Java bytecode to bytecode suitable for Android, the dex tool. This application performs that process on every single file (library or otherwise) every time I want to run my app to test something new.
This process takes up to a minute, so now I pretty much have to resort to using a dummy library that imitates the CAS just so I can stay sane while developing this app :v:.
Oh well, at least I learned something new.
[QUOTE=icantread49;35799174]Holy fuck is it really 1cm on a 4.0 ROM? I'm running 2.3.3 and the bar is about 5 mm, which feels perfect on the Kindle Fire.
The triangulation will fail if you draw self-intersecting shapes. It's not worth the effort to prevent it, but I am investigating how to properly triangulate self-intersecting shapes.
Jeez, that's the first item in the FAQ :v: Did you even bother open the side menu and tapping the big question mark? As for the start button, it feels pretty obvious to me, no one else has brought that up. But thanks for the feedback, I'll take it into consideration.
The Kindle Fire is known to have extremely laggy touch input, if that's what you mean. It does feel slightly less responsive than other tablets.[/QUOTE]
Well the touch input is actually TOO sensitive with a 4.0 rom, and it's pretty accurate your app and netflix are the only touch issues I get.
[QUOTE=Jawalt;35799218]Well the touch input is actually TOO sensitive with a 4.0 rom, and it's pretty accurate your app and netflix are the only touch issues I get.[/QUOTE]
Can you please describe the issue a bit better? What doesn't work exactly? When you tap a button, it doesn't really get pressed? Or something else? The Kindle Fire's screen is horribly sensitive (even compared to the PlayBook, which already had a horribly sensitive screen compared to an iPhone or iPod), so there's a "touch radius" which can be configured. Tap 5 times, type in "touchpx 20", and tell me if that helps.
[QUOTE=icantread49;35799300]Can you please describe the issue a bit better? What doesn't work exactly? When you tap a button, it doesn't really get pressed? Or something else? The Kindle Fire's screen is horribly sensitive (even compared to the PlayBook, which already had a horribly sensitive screen compared to an iPhone or iPod), so there's a "touch radius" which can be configured. Tap 5 times, type in "touchpx 20", and tell me if that helps.[/QUOTE]
I don't think it's so much physical as maybe like the 'tactile feel' of it. it's a bit floaty, and there's no reference frame since the background is static.
That command didn't really fix it, but I think the I nailed where it comes from down. Place your finger on the screen, scroll, stop moving your finger and stay as still as possible, then lift. It "snaps" a bit.
[QUOTE=SEKCobra;35796163]Well then use OpenOffice, geez.[/QUOTE]
Uh. Oracle has rights to the OpenOffice name, so new versions of OO are called LibreOffice.
OpenOffice LibreOffice = new OpenOffice();
Edit: Whelp, looks like I'm horribly late..
[editline]3rd May 2012[/editline]
[QUOTE=voodooattack;35796438]I'm scrotum deep in this shit...
[IMG]http://dl.dropbox.com/u/27714141/hnnnng.png[/IMG]
..and I'm adding text shadows/outlines in aero glass mode to mintty as a side-project.[/QUOTE]
It looks like you're trying to compile mono under cygwin. I thought it compiled fine under Windows natively?
[QUOTE=Overv;35799199]I spent this entire afternoon and evening trying to get a Java CAS (Computer Algebra System) to compile correctly. It would only compile after I gave Eclipse 3 GB of heap memory and it wanted to recompile itself every time I changed a single line in my own application.
Now you would expect me to say something about a stupidly simple fix, e.g. some compile checkbox in the Eclipse settings. Unfortunately I found out something rather depressing: it's a known bug with the Android SDK.
Now, the Java compiler does actually know about which files change and which don't and it only rebuilds new .class files for those files that change. Unfortunately there's another step in the pipeline that translates Java bytecode to bytecode suitable for Android, the dex tool. This application performs that process on every single file (library or otherwise) every time I want to run my app to test something new.
This process takes up to a minute, so now I pretty much have to resort to using a dummy library that imitates the CAS just so I can stay sane while developing this app :v:.
Oh well, at least I learned something new.[/QUOTE]
one of the many reasons why android is a ghetto
[QUOTE=icantread49;35798438]xxx[/QUOTE]
Oh man, that filesmelt background made me think my phone's screen was fucked at the bottom :v:
ICS on a nexus s.
Works exactly the same as before.
A few things I noticed this time around:
- The box tool is selected by default. I think this should be the move tool instead. The first thing I did was try to pan, which made me draw a box and get rather confused.
- Menu items can be "selected" while you're trying to scroll, which is confusing. You should only show the tick on release, or you think you've made a mistake. Maybe highlight the background, box or text instead if you want to keep some kind of feedback.
- The app takes a while to restore when the phone is unlocked. Not much you can do about that I guess, but for example anomaly warzone earth doesn't take any time at all.
- It wants a permission entitled "phone calls". This is ominous, but I guess you need something from there or you would have removed it.
I also felt that the background could have a texture that scrolls with the view, to give it a better feel than just stuff floating around.
[QUOTE=icantread49;35798438][url]http://filesmelt.com/dl/Phyzicle1.apk[/url]
New test build of Phyzicle for Android
This time it should work better on the Galaxy S and the Android 2.2 devices, so if you guys could test it, that'd be awesome :)
Once again, I'd like:
1) Device
2) OS
3) Result of running the app
There are many other fixes (softkey support, better UI sizing, and so on) but I'm mainly concerned about the device compatibility. If you have a device that worked in the previous test, feel free to try it again, just to make sure I didn't fuck something up![/QUOTE]
I get a parse error on my ZTE Blade with Android 2.2 as soon as I try to open the apk file.
[QUOTE=Dlaor-guy;35800036]I get a parse error on my ZTE Blade with Android 2.2 as soon as I try to open the apk file.[/QUOTE]
Download it again?
[QUOTE=Catdaemon;35799782]
- The box tool is selected by default. I think this should be the move tool instead. The first thing I did was try to pan, which made me draw a box and get rather confused.
[/quote]
I think you might have accidentally pressed it because it's in the corner. I just tried it and it wasn't selected at startup (and there's no reason for it to be selected at startup :v:)
[quote]
- Menu items can be "selected" while you're trying to scroll, which is confusing. You should only show the tick on release, or you think you've made a mistake. Maybe highlight the background, box or text instead if you want to keep some kind of feedback.
[/quote]
Good point.
[quote]
- The app takes a while to restore when the phone is unlocked. Not much you can do about that I guess, but for example anomaly warzone earth doesn't take any time at all.
[/quote]
Really? That's odd. I never noticed that.
[quote]
- It wants a permission entitled "phone calls". This is ominous, but I guess you need something from there or you would have removed it.
[/quote]
[code]
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>
<uses-permission android:name="android.permission.SET_ORIENTATION"/>
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="com.android.vending.BILLING" />
[/code]
Those are all of the permissions it asks for. It comes as a template with Marmalade so I haven't messed much with it (I did remove a lot of unused ones). Maybe it's READ_PHONE_STATE? I have to check out what that's for.
[quote]
I also felt that the background could have a texture that scrolls with the view, to give it a better feel than just stuff floating around.[/QUOTE]
A lot of people have mentioned this and I should probably try it, thanks for the tip.
[QUOTE=icantread49;35800080]I think you might have accidentally pressed it because it's in the corner. I just tried it and it wasn't selected at startup (and there's no reason for it to be selected at startup :v:)
[/QUOTE]
Yeah I just tried it again and you're right, my bad.
The phone state thing I think has to do with the device ID or something.
[QUOTE=Catdaemon;35800064]Download it again?[/QUOTE]
It turns out I downloaded the Filesmelt download page. Derp.
[editline]3rd May 2012[/editline]
Alright, installed it but the colors are all wonky and it instantly freezes as soon as I try to do anything. Can't expect much from a Blade, though.
[url]www.livestream.com/mrstaneh[/url]
If anyone wants to see my bad coding, I'm gonna try and code these orbiting planets too, for a change.
warning: loud
[video=youtube;bgq5K8s0c0A]http://www.youtube.com/watch?v=bgq5K8s0c0A[/video]
In my defense, this wasn't my idea.
[QUOTE=icantread49;35798438]New test build of Phyzicle for Android[/QUOTE]
Samsung Galaxy S
Android 2.3.3
- Doesn't attempt to load, hides my status bars but goes straight to a black screen. I've left it running for a while and still nothing, doesn't use any CPU and hovers around 23MB of RAM usage.
- Somehow makes the task manager crash, might not be this app, but it's never crashed before.
- Can send touch events to the app, and knows its running, but nothing happens.
- No errors outputted to the debug monitor, and the app appears to be running normally, but it sits on the black screen.
[IMG]http://www.adamncasey.co.uk/upload/image/4037/d/o/[/IMG]
Out of interest, is there any debug messages in the application? Mine's not showing any. I'll keep trying different ways of getting it working, as before it was just a bad download that caused the previous error.
[editline]lol[/editline]
Might have found something interesting. Upon installing it appears not to get given permission to set the orientation of the screen, causing it to error out.
[IMG]http://www.adamncasey.co.uk/upload/image/4038/d/o/[/IMG]
[editline]lol2[/editline]
It's been mentioned before, but it doesn't appear to actually ask for the correct permissions when installing (although the terms are a bit sketchy, it could be asking for the correct information, but not showing the trivial things like screen rotation in here). All it asks for are permissions to phone calls and network communication.
[IMG]http://www.adamncasey.co.uk/upload/image/4039/d/o/[/IMG]
[QUOTE=icantread49;35798438]
New test build of Phyzicle for Android
Once again, I'd like:
1) Device
2) OS
3) Result of running the app
[/QUOTE]
1) HTC Glacier (myTouch 4g)
2) Cyanogenmod 7.0.3 (2.3.3)
3) Black screen then crash
[img]http://img196.imageshack.us/img196/9707/screenshot2012050219552.png[/img]
Time to start developing on Linux (yeah I'm using a VM that's what it say's I'm on Windows)
Sorry, you need to Log In to post a reply to this thread.