Which specs has this machine? (Ram, cpu)
After to finish fixing and improving everything seen, before to release more publicly these alphas, the biggest issue will be that the desktops are not so ready for end users “experience”, they will of course miss the nicesses of e17
So what do you think about how is this actually explained on 3.7.1? I know that users don’t read messages but they must know about the desktops status and details for each one, for example, lots of people could try to use the e17 option as normally and this is wrong (so many bugs)
Suggestion for improving this provided information?
I prefer e16 to e17
But that’s one opinion
What do you think about making e16 available to more people. ?
And let’s give yourself a timeframe of « 3 months » for e17 ?
Just thinking outloud...
maybe add that to the options in the light-dm-greeter, i.e '' e16(stable) e17(unstable, bugs), e22(working on it)'' or so.
and still want an option for ''onboard'' to be opened if necessary. Without a keyboard you're lost there.
1 Like
Remove the options then.
People will ! play with it as long it is there
Result:
Less constructive feedback of alpha testing for the release needed.
It just leads into waste of time and Energy.
Conclusion:
This is a useless feature for bringing the project forward.
Sounds harsh, but we have to think in a productive way.
That's stupid as long as it's just in the testing phase. Once released and still not ready: OK, remove it, but not now.
I mean ATM there are only a few of us, so how distracting can it be?
I think that I saw it also on the official installer.
Must check again for being honest.
But still no need to handover a version
of e17 or whatever when we want to reach a final stage of an official release.
Wasting I dont know with how many words meanwhile and time with comments and explanations for a possible variant which is not any ready yet.
Like this conversation right now, by the way.
Just a reminder:
We want to get the 64bit done.
With a big and professional Press Release
for leaving the image
"Elive is good for 32bit nerds only"
behind.
Since Elive is getting mature now
no time for useless actions.
@Thanatermesis
While reading e16 Help and trying misc features I happen to also play with Themes
How to I bring back the default defaut Theme when we 1st install ELive ?
I tried them all and can't come back
OK I've got it
apug and "elive-skel upgrade .e16" (or just read the updated file from /etc/skel/.e16/bindings.cfg),
@Thanatermesis I am getting pretty good with e16, keybinding features etc
but I lost the resizing window with middle button feature and I think it's not trough e16 keyboard binding we do that..
IF you know, let me know how
Else, I'll have to reinstall my station anyway when 3.7.2 becomes available, so the resizing feature will come back..
1 Like
when using the ELive multiScreen tool I get this
~ ❯❯❯ elive-multiscreens
(zenity:5320): GLib-WARNING **: 08:40:03.880: ../../../glib/giounix.c:410Error while getting flags for FD: Bad file descriptor (9)
I: running: xrandr --output VGA-1 --mode 1920x1080 --pos 0x0 --rotate normal --output DP-1 --primary --mode 2560x1440 --pos 1920x0 --rotate normal --output HDMI-1 --off
~ ❯❯❯
IN case it could be usefull for you
My recommendation is having a disclaimer or note somewhere that That using Elive with 2 screen may not work perfectly for some.
For me, it's always weird / random .
Could we simply use some WIndows Manager / display manager already available for Debian ? Now that we are on 64 bits & Buster, I am sure there should be one ?
Also, I don't think e16 or E17 were meant to work properly with 2 scree... From my test at least.
so cool
I know have my resize with right mouse button
MouseDown CA 3 wop * sz ptr
Just have to save your config in bindings.cfg then CTRL + ALT + END
OR
FYI The Restart in the menu on the desktop (Right Click Desktop), is not reboot but a restart of E16...
nice! interesting..
what makes you like it more, btw?
related: E16 Elive derivative system
you are optimistic 
good point, will try that
you should try to install a "virtual keyboard" package and open it with "alt + esc", or assign some hotkey fast combo, otherwise this is not possible, only for e22 probably
thats true, by other side stills "beautiful" desktop, maybe is good to keep it available just to see it? or better to remove it? 
BTW there's always a message showing up if you run e17 when installed, saying that is buggy
You mean the darkone theme? is not showing up on the list of themes if you try others?
ctrl + alt + middle-mouse-click-while-dragging
I assume you have middle-click mouse?
don't worry about these messages, not important
what is not working?
well, e16 seems like to not manage so well xinerama (multiscreens)
done, added
of course, you can even install gnome if you preffer it
api task-gnome-desktop
e17 should work without problems
already done that. Easy enough: api onboard.
It needs to be in lightdm-greeter as an option, otherwise one cannot login on tablet i.e without keyboard
.Just offer it in the accessibility, drop down menu.
looks good
is there a way to detect your touch hardware? (lspci / lsusb / lshw / dmidecode / hwinfo )
does lightdm supports onboard by default?
I didn't bring any laptops along, only my phone. Doesn't something like that show up in the bug report during install?
Anyway I can confirm touch always works in the greeter...
so that is not the issue.
what is needed is simple a button to start ''onboard''. Prolly is in /usr/bin/ but will need to be added during install. I would help but don't know how you setup crosscompiler, etc.
Updates related to next 3.7.2 build (among others):
- .config/elive issue seems fixed now
- installer MANY improvements / fixes:
- reiser4 support
- extra partition didnt asked correctly for filesystem and failed
- full EFI support
- "bios" partition support (for gpt disks + legacy boot mode)
- migration mode should work now (tested with manjaro)
- windows IOS included & compatible (shared / boot thingy)
- suggestion to reboot in EFI mode shows up if the hardware / setup is detected that should use it
- manjaro is also included as boot system (but it doesn't boots, i assume its not an elive issue but about the boot parameters required for it)
- mbr / legacy install working and tested
- efi install working and tested
- mbr + gpt install working and tested
- efi + gpt install working and tested
- efi existing partition autodetected and used, and the option to create a specific one for your disk if more than 1 disks are detected
- mbr / gpt / legacy / efi: all these requires a different disk management / configurations, all these combinations are tested from my side so should work correctly in any combination that you use
- (much other small things fixed / improved)
- autopartition in legacy mode
- autopartition in EFI mode - WIP
- autopartition in "big disk" mode (auto extra /home partition)
- low ram analysis of resources + temporal swap files + improvements / tests - WIP (mentions: @zbd)
- migration mode tests with encrypted disk (mint) - WIP
- autologin = "no" is ignored in autopart - WIP
- hibernation settings improvements - WIP
mentions: @yoda @triantares @Rebel450
2 Likes
mmh, i dont think so
my idea is to: if "a touchscreen is detected on computer", run the command:
onboard -T Droid -e -D 4
in every "destkop started"
I prefer the " look " of the menus, more sober / less flashy...A s simple as that.
Alt + Esc too, what we have to do to access, lauch apps, access settings and so on, I find it more serious / more easy on e16... Just a personal feeling toward the GUI.
