Dingoo A320 forum

I'm releasing dmenu 0.1 as a test release. Please give your feedback. It's compiled and tested on ezelkow1's rootfs. Source is also attached here. You can compile your own if you want.

To automatically start it when Lingux boots up, simply add these 2 lines to the end of /etc/init.d/rcS, (assuming you are using ezelkow1's rootfs, and you have unpacked dmenu to /root)

Code: Select all

export SDL_NOMOUSE=1
cd /root; ./dmenu&

In the main menu screen, use arrow keys to navigate menu items, 'A' key to run.

If the menu item is configured to have file selector (I have configured snes9x as a sample to show this function), a file list will be shown after you pressed 'A' key. You can navigate and chose the file to be passed as an argument to the program. In this case, you can chose the rom file name to be passed to snes9x.

File explorer can be used to run any program on your dingoo. Currently it does not check whether the file is executable. If you select any non-executable file and press 'A', dmenu will attampt to run it, prints an error message and returns immediately.

If you want to add more programs to dmenu, take a look at dmenu.cfg. It should be pretty easy to figure out. Ask here if you have any question.

I'm using the stock dingoo wallpaper and icons as place holder for the moment. If anyone is interested to contribute a set of wallpaper and icons to be used as dmenu default, please let me know. I'd prefer the default to be consistent and minimalist in style, similar to the stock dingoo icons.

Thanks for your work

Do you have any pictures of this?

Very cool stuff, much nicer to use... especially with the file manager!

definitely niiiiceeer than the command line and hence much more productive, Great Work!
it seems i can't get my scripts shells to work:
i have res, dmenu and dmenu.cfg in home directory and then let's say duke nukem:
home/duke3d/duke(my script shell with executable permission)

my dmenu.cfg is:
Icon = "res/game1.png"

Name = "Duke Nukem 3D"

Executable = "duke"

WorkDir = "./home/duke3d"

it says duke does not exist
Why?? i have not too clear how should i type the path or the executable
Thanks

Just tried it, it looks very nice!

maxif875 wrote:definitely niiiiceeer than the command line and hence much more productive, Great Work!
it seems i can't get my scripts shells to work:
i have res, dmenu and dmenu.cfg in home directory and then let's say duke nukem:
home/duke3d/duke(my script shell with executable permission)

my dmenu.cfg is:
Icon = "res/game1.png"

Name = "Duke Nukem 3D"

Executable = "duke"

WorkDir = "./home/duke3d"

it says duke does not exist
Why?? i have not too clear how should i type the path or the executable
Thanks

Be careful of the . in WorkDir. That means "current directory". So you're probably actually pointing it to /home/home/duke3d, which is probably incorrect.
Try this:
Executable="/home/duke3d/duke"
WorkDir="/home/duke3d"

If that doesn't work then try:
Executable="cd /home/duke3d; ./duke"

it's a strange thing
now find the duke file but cannot run it, same thing with snes9x the only i could run was scummvm but when it starts it has no games loaded
mmmm...
don't know what it could be wrong...
the same shell scripts run well with vifm
maybe i'm doing something wrong

Great job rookie1 - thanks for your work on this! Excellent first menu system for Dingux - much nicer than scrolling through commands in history.

This is straight up great. PRECISELY what the dingoo scene needed at this moment in time.

I think developers need to make it a rule to provide the lines that should be added to the dmenu.cfg file, though it's fairly self explanatory.

Couple requests:

First, could you make it so that a loading screen appears instead of the command line after an application is selected?

It would be cool if there was a feature where it could scan certain directories for applications. Each application would have included dmenu based cfg files that would be imported by dmenu, and all the applications would then appear in dmenu. This would then remove the hurdle of having to edit config files.