cLinux [now with OPTIONAL Desktop Envirome...
Piorjade 12 Feb 2017
exosceleton, on 12 February 2017 - 08:51 PM, said:
I think one should be able to customize (change the BG/FG color) but not hide them.
That's a nice idea! In this pic, the entire bottom line (containing the buttons) is dedicated to these buttons, which means they are black/white.
Everything above will be the actual screen available for apps to modify.
So I think I'll figure out some functions to change each buttons backgroundcolor and textcolor
But I'll wait for other suggestions too
クデル 13 Feb 2017
How can I create an alternate desktop environment? I didn't find doorx in the cc-packman repository so I was a little confused.
Edit: You should implement the command below.
Edited by クデル, 13 February 2017 - 09:57 AM.
Edit: You should implement the command below.
cd ~
Edited by クデル, 13 February 2017 - 09:57 AM.
Piorjade 13 Feb 2017
クデル, on 13 February 2017 - 09:52 AM, said:
How can I create an alternate desktop environment? I didn't find doorx in the cc-packman repository so I was a little confused.
Edit: You should implement the command below.
Edit: You should implement the command below.
cd ~
You probably need to update your packagelist, just run "sudo packman fetch"
Also "cd ~" is already implemented, just enter "cd". That's it
Regarding the question:
There are many ways of making a DE.
The easiest I can think of is just make a program which does your DE stuff and run that program after the commandline pops up.
The more efficient way (and how I did it with doorX) is to make your DE-program, which gets run as core service.
(When you're done coding your DE, just enter "service core /path/to/DE_startupFile". This way the commandline simply does not exist. (Well it does... but it's not executed at all....you get the point tho))
If you have any other questions, feel free to ask them here or send me a PM
Edited by Piorjade, 13 February 2017 - 12:00 PM.
Cross_Sans 09 Mar 2017
If you are (re)making Android, you should implement /vendor.rc or a file called like this that contains informations about the OS and the "Vendor".
Piorjade 12 Mar 2017
Redall, on 09 March 2017 - 11:04 AM, said:
If you are (re)making Android, you should implement /vendor.rc or a file called like this that contains informations about the OS and the "Vendor".
That probably causes confusion.
FYI craftAndroid is already out and is basically an OS for Pocket Computers using cLinux as its "kernel", but I unfortunately currently cannot update it.
Piorjade 26 Apr 2017
Small Update:
- Added 'addusr' :
addusr <name> <password>
It doesn't need root privileges - Added 'rmusr':
rmusr <name>
DOES need root privileges - Fixed some bugs with the perm library