On Tue, 21 Jan 2025 14:08:55 -0500 i...@bandshed.net said: > Hi, > > I recently discovered the optional 'Places' module for Enlightenment and > I really like it. It seems most projects deploying Enlightenment as > installable Live Media are depending on outside File Managers (Thunar > seems to be the first pick) and Places makes this much easier to > consolidate most functions and mounting of removable Media without > confusing the User with multiple FM's. I have done a bit of cosmetic
That'd be the problem of those distro maintainers not wanting to use e's file manager that's already there. It's not the intent for e so - no - not going to do this and make e extra confusing by having basically "2 file managers" both of which deal with listing mountable media or fs locations. That's what EFM already does out of the box by default and it's integrated so the icons can be dnd'd and behave like all other icons. i'm in the process of doing efm2 so DEFINITELY not adding places. efm2 is designed a bit differently (backend filesystem handling is a separate process the front wend talks to over stdin/out and *ALL* I/O is done by the backend (well if it's a .desktop file then whatever icon it points to the front end will show, or thumbnails will be local to the dir the files are in). efm2 has a much more fleshed out file view right now with detailed mode and columns as well etc. and it's thumbnailing is probably second to none in terms of how much it handles and how completely. it's in git if you want to play with it. there is more work to be done of course... > changes to Places because with Dark themes the eject Icon was not very > visible and I thought the Home and Module Icons should match but that's > just an opinion.. > > https://bandshed.net/images/screenshots/shot-2025-01-21_11-43-21.jpg > > A mild annoyance is the need to version-match the module with every > Enlightenment update but I would guess there is some wisdom in this that > I'm not aware of but in any case I think Places should just be part of modules are bits of code that are loaded into e. they rely on e's internal ABI. this ABI is not guaranteed to not break between releases, thus modules have to version to the E they are built for. > the main DE release (I believe Bodhi already does this) instead of kept > secret in a dark attic. It serves a valuable use and definitely opens up > E to more intuitive usage with other FM's. I know we have EFM2 in the > works but in the meantime Places would be a useful module to come in a > standard install. nope. as above. confusing with "2 file managers" duplicating functionality etc. etc. - it's against the whole idea of E to do this - efm is the official filemanager for e and it's there and does all of this. also i'm not going to just do things for people. after many decades, i'm kind of a bit old, tired and grumpy. :) i've learned if i do things for people they will NEVER get up and help. if you don't like something in efm - then get up, contribute and fix it. there never is any encouragement for anyone to do anything if i keep putting in half-through-through workarounds so they don't have any reason to bother. :) right now most of that effort would be best served contributing to efm2... :) > Anyone else have thoughts on this? > > -- > > > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
