akossh has quit [Quit: Leaving.]
uvos__ has quit [Ping timeout: 240 seconds]
Pali has quit [Ping timeout: 252 seconds]
sch has quit [Remote host closed the connection]
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
LjL is now known as Freud
Freud is now known as LjL
hexagonwin has quit [Quit: Bye! Shutting down..]
mdz has quit [Ping timeout: 260 seconds]
xmn has joined #maemo-leste
elastic_dog has quit [Ping timeout: 255 seconds]
elastic_dog has joined #maemo-leste
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
Danct12 has quit [Quit: ZNC 1.8.2 - https://znc.in]
asriel has quit [Quit: Don't drink the water. They put something in it to make you forget.]
Danct12 has joined #maemo-leste
mdz has joined #maemo-leste
xmn has quit [Ping timeout: 264 seconds]
<Wizzup> ok, I think I figured out my gobject question
elastic_dog has quit [Ping timeout: 268 seconds]
Pali has joined #maemo-leste
elastic_dog has joined #maemo-leste
diejuse has joined #maemo-leste
n900 has quit [Ping timeout: 255 seconds]
<diejuse> Wizzup Lately I've been playing around with editing the menu to create various submenus, editing ~/.config/menus/hildon.menu.
<diejuse> I have also manually changed the order of the debian submenu.
<diejuse> As you say, hildon launcher editor because it breaks everything.
akossh has joined #maemo-leste
<Wizzup> sicelo: I pushed code to also edit the debian submenu
<Wizzup> so all issue should be fixed with that PR
<Wizzup> diejuse: ^
<Wizzup> diejuse: how do you create the submenus
<Wizzup> diejuse: this would be good to know, because currently the editor doesn't support more than the debian submenu, because I don't know how to make it work
<Wizzup> there is both /etc/xdg/menus which I presume you edited, but then there is /home/user/.config/menus/
<diejuse> I only edit /home/user/.config/menus/menu.hildon
<diejuse> First I created a folder that I called "main" /usr/share/applications/main
<diejuse> In menu.hildon the main structure is this: <menu><AppDir>/usr/share/applications/main</AppDir><DirectoryDir>/usr/share/applications/main</DirectoryDir>   </menu>
<diejuse> After <DirectoryDir>/usr/share/applications/main</DirectoryDir> you add your submenus
<Wizzup> yes, but this means you can't see the default hildon ones in the main view
<diejuse> I have converted the default Hildon menu to another submenu.
<Wizzup> yes, but this probably won't "fly" with us, but let's discuss
<Wizzup> so the way hd-launcher-editor used to work: it always writes to /home/user/.config/menus/hildon.menu
<Wizzup> I made some changes to that it can write that file, but also /home/user/.config/menus/hildon/<SUBMENUNAME>.menu
<Wizzup> however, for this to work and not 'take over' the menu as your example does, you have to double nest
<Wizzup> let me explain
<Wizzup> this is my /home/user/.config/menus/hildon.menu now: https://bpa.st/XIFQ
<Wizzup> and this is my /home/user/.config/menus/hildon/debian.menu now: https://bpa.st/XSGQ
<Wizzup> nevermind the Layout and Filename entries, those are just for sorting/ordering
<Wizzup> note that in hildon.menu there is an explicit <Menu> and <Name>Debian</Name> around the merge dirs
<Wizzup> if you don't do this, the merge dirs will override everything standard maemo and you'll get what you have: no standard maemo icons
<Wizzup> I'm assuming we do want to keep this, and maybe just add sub menus for debian, android, webapps, etc
<Wizzup> this would be somewhat easy to add in my current PR, *but* this nesting I mentioned above is hardcoded
n900 has joined #maemo-leste
<Wizzup> I could add code to detect the different categories from the /etc/xdg/menus/ ... and somehow write those to hildon.menu
<Wizzup> I might also be "doing it wrong" but I don't see a better way to do this
moparisthebest has quit [Ping timeout: 260 seconds]
<Wizzup> but yes, you *cannot* manually override /home/user/.config/menus/menu.hildon and expect it to work
<Wizzup> brb
<diejuse> The truth is that I realized that everything is made too complicated.
<diejuse> I removed the part from <MergeFile type="parent">/etc/xdg/menus/hildon.menu</MergeFile>
<diejuse> to make my structure independent.
<diejuse> For me the ideal operation is that a user could create a folder structure from ~/config/menus/hildon with .desktop files and that each folder was a submenu. For example ~/config/menus/hildon/debian and ~/config/menus/hildon/webapps.
<diejuse> And then Maemo will simply show a menu how you have created your folders.
mdz has quit [Ping timeout: 260 seconds]
<Wizzup> diejuse: well I am working on the code now so let's think it through
<Wizzup> we could easily create more menus like the debian one(s), but I am not sure how those should be managed
<Wizzup> what are these android things you mention, do they run inside of maemo, or
<diejuse> Do you mean the Android submenu I created?
<Wizzup> yes, what is in there
<Wizzup> do those open android apps inside maemo X? or?
<diejuse> Since I am emulating Maemo via proot I cannot open the camera or make calls natively, but I can directly open the Android camera or call the Android calling app from Maemo
<diejuse> If I click on the camera icon, the Android camera application opens. I take the photo, hit the Android button "back" and it returns to Maemo.
<diejuse> Yes, open android apps inside maemo
<Wizzup> ok, so it leaves the maemo X
<diejuse> yes
<Wizzup> what do these .desktop files look like
<diejuse> Those .desktop files exec scripts I have in the /diejuse_scripts folder. Do you want to see the script that opens the camera?
<Wizzup> just curious how it works, but not super important
diejuse has quit [Quit: Client closed]
diejuse has joined #maemo-leste
<diejuse> for example: /diejuse_scripts/android_camera.sh has:
<diejuse> am start -a android.media.action.STILL_IMAGE_CAMERA --user 0
<diejuse> it is a adb shell command to open the default android camera
<diejuse> with proot in my PATH variable I add a path with adb shell commands
<diejuse> That way I can execute Android commands from within Maemo
<diejuse> I am already creating an image prootMaemoLeste_arm64.tar.gz so that it can be unzipped on any Android and use maemo.
<diejuse> I'm trying to minimize its space because it takes up between 2 and 3 gigabytes.
<diejuse> I want a user-friendly installation
<diejuse> I'll put the installation steps here: https://github.com/diejuse/proot_MaemoLeste_on_Android
asriel has joined #maemo-leste
k1r1t0 has joined #maemo-leste
<k1r1t0> Hello, I updated the kernel, but it won't load. It can be fixed? Or reinstall the system.
<k1r1t0> A week or two ago. The devel repository has been enabled
<gnarface> almost certainly it's repairable
<gnarface> though i can't really give you specifics
n900 has quit [Ping timeout: 256 seconds]
n900 has joined #maemo-leste
<Wizzup> k1r1t0: what device are you on
<Wizzup> diejuse: thanks for elaborating
noidea_ has quit [Ping timeout: 272 seconds]
diejuse has quit [Quit: Client closed]
noidea_ has joined #maemo-leste
<k1r1t0> Nokia N900
<Wizzup> surprising to hear a kernel upgrade would break it, what behaviour do you observe
diejuse has joined #maemo-leste
arno11 has joined #maemo-leste
crab has quit [Quit: WeeChat 3.8]
<arno11> k1r1t0: when you say 'updated the kernel', you mean using 'apt dist-upgrade' ?
crab has joined #maemo-leste
diejuse has quit [Quit: Client closed]
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup> sicelo: fwiw I'll merge your changes once we have a new kernel build
<Wizzup> I'm waiting for uvos to do it, but I can also do it if it takes too long
<sicelo> sure, thanks. the leste-config one can actually go in whether kernel's done or not
<sicelo> only status-area one depends on kernel (because we're no longer blacklisting the charger in batmon.c)
<Wizzup> uvos: I think I fixed the sphone build-dep in devel
<sicelo> and really nice work on the h-d rearranging issue :-)
<Wizzup> sicelo: yeah, I'm still not super happy with it, but it'll work for us for now I think
<sicelo> i haven't tested yet (my d4 still bork), but from the description and the little i understand of the code, it's quite elegant fix
<Wizzup> it'll work, but the whole .menu stuff is I think a bit ugly
<Wizzup> it seems both overengineered but in some ways underpowered
<Wizzup> freemangordon: I think I'm just going to release OMP to latest stable and see what doesn't work
<Wizzup> freemangordon: then I can fix the image builds
<Wizzup> uvos: the build failed now that it is actually building the voicecallmanager module, I'll make a merge request for it...
<Wizzup> uvos: ended up just pushing a fix, lmk if you don't want me to do that in the future
mdz has joined #maemo-leste
<k1r1t0> Amo11 yes
<k1r1t0> Arno11 yes
xmn has joined #maemo-leste
pere has quit [Ping timeout: 264 seconds]
<Wizzup> weird, openmediaplayer just apt upgrades it looks like on stable image
pere has joined #maemo-leste
k1r1t0 has quit [Quit: BelleChat © nokia 2023]
sch has joined #maemo-leste
<Wizzup> freemangordon: our image build is hitting this qemu bug again:
<Wizzup> scandir: Value too large for defined data type
<Wizzup> it might not be a problem, but just found it again
<Wizzup> maybe this is why we had the 32 bit builder