[WIP] pymenu, need beta-testers

[wth]

Advertising

where is the fun then?

C / C++ is way more fun than python for such a thing lol
and that way it's also lighter / powerful and easier to debug for smthg running on limited environments like user exploits

[Acid_Snake]

Advertising

when I said fun I meant the technical difficulties behind it, not the coding itself. C/C++ is very documented for the PSP, all the menus are written in it and it's easy for a dev to make another one, but making one in Python from scratch is challenging, that's what I meant.

[wth]

when I said fun I meant the technical difficulties behind it, not the coding itself. C/C++ is very documented for the PSP, all the menus are written in it and it's easy for a dev to make another one, but making one in Python from scratch is challenging, that's what I meant.

Indeed, but even just as a language, C / C++ are perfectly suited for such conditions
Languages like Python are meant to simply the developing process, but in this case it's clear that it doesn't help at all, rather complicates things for nothing (hence challenging indeed, but why bother, why not try making a python/lua hbl/cfw then ? [although I indeed know some people who'd actually love making a lua cfw xDD] lol)

[Acid_Snake]

when I said fun I meant the technical difficulties behind it, not the coding itself. C/C++ is very documented for the PSP, all the menus are written in it and it's easy for a dev to make another one, but making one in Python from scratch is challenging, that's what I meant.

Indeed, but even just as a language, C / C++ are perfectly suited for such conditions
Languages like Python are meant to simply the developing process, but in this case it's clear that it doesn't help at all, rather complicates things for nothing (hence challenging indeed, but why bother, why not try making a python/lua hbl/cfw then ? [although I indeed know some people who'd actually love making a lua cfw xDD] lol)

Actually its the loading process that its different (execution time is normal), and thats probably because of the gcc version used to compile the homebrew (or the OS), do the test: measure the time to start spider solitaire, psptools and this menu/custom interpreter.

[wth]

Actually its the loading process that its different (execution time is normal), and thats probably because of the gcc version used to compile the homebrew (or the OS), do the test: measure the time to start spider solitaire, psptools and this menu/custom interpreter.

yeah I noticed it was longer to start
but at exection time, you don't see it but it IS longer too, you get less power since the interpreter runs, that's only logical, it can't be as fast as compiled asm opcodes (unless you manage to code a psp python compilator xD)

[Acid_Snake]

Actually its the loading process that its different (execution time is normal), and thats probably because of the gcc version used to compile the homebrew (or the OS), do the test: measure the time to start spider solitaire, psptools and this menu/custom interpreter.

yeah I noticed it was longer to start
but at exection time, you don't see it but it IS longer too, you get less power since the interpreter runs, that's only logical, it can't be as fast as compiled asm opcodes (unless you manage to code a psp python compilator xD)

It wasn't slow at execution time, it has a delay, otherwise pressing a button would be recognised as pressing it continously (a bug in psp2d?), the problem comes when beta-testing, I usually test it on a PC before copying to the psp, so the delay time has to be increased on the PC

[wth]

It wasn't slow at execution time, it has a delay, otherwise pressing a button would be recognised as pressing it continously (a bug in psp2d?), the problem comes when beta-testing, I usually test it on a PC before copying to the psp, so the delay time has to be increased on the PC

well I code my C++ psp menu on pc too, and simply add a Sleep (1000/60); at each frame to simulate the psp's 60fps limit

[Acid_Snake]

It wasn't slow at execution time, it has a delay, otherwise pressing a button would be recognised as pressing it continously (a bug in psp2d?), the problem comes when beta-testing, I usually test it on a PC before copying to the psp, so the delay time has to be increased on the PC

well I code my C++ psp menu on pc too, and simply add a Sleep (1000/60); at each frame to simulate the psp's 60fps limit

it has nothing to do with framerate (but the concept is similar), remember a turbo controller, you turn the turbo on and by pressing a button once it interprets as more presses, thats what happens to psp2d.Controller and the only way to overcome it is using time.sleep, normally time.sleep(0.07) would suffice, but I use time.sleep(0.20) mainly because I beta-test on the PC itself (which is, obviously, faster).

[wth]

ok well maybe I'm not so fond of scripting languages like python/lua at all (I guess you noticed lol), just use python and others sometimes on pc for basic tools I need ^^
I prefer efficient ones like c++ lol

[Acid_Snake]

ok well maybe I'm not so fond of scripting languages like python/lua at all (I guess you noticed lol), just use python and others sometimes on pc for basic tools I need ^^
I prefer efficient ones like c++ lol

I know C/C++ is more efficient on low-end devices, but on pcs python can be as efficient as compiled languages, abd lua is used more as an extension language, also there are tools like py2exe or cxfreeze (I preffer this one better) that can compile python code into binary code, but again with a normal pc you dont really see the difference. Anyways, I finished the menu (same download links as before), I dont intend it to be used widely as it doesnt have that many features, it was mostly for learning purposes only, I even got into contact with some C code.