| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 7,893
» Latest member: marcocc
» Forum threads: 9,453
» Forum posts: 62,359
Full Statistics
|
| Online Users |
There are currently 658 online users. » 0 Member(s) | 654 Guest(s) Applebot, Baidu, Bing, Google
|
|
|
| How we build and release software |
|
Posted by: valtam - 12-25-2022, 12:33 AM - Forum: Linux Lite Software Development
- Replies (1)
|
 |
I wanted to document for people, the process in which an application gets from point A to point Z. Transparency to the community, is always good too. Other than Step 1 from below, this process is exactly the same for any changes to an existing application to.
1. The formulation of the idea:
The first step is the idea, the first thought. Usually this stems from seeing something that people are doing and making that process easier with software. It could be a Forum or Social Media post about an issue someone has. It could be an idea from an existing piece of software that is either clunky, of poor UI (user interface) design, bad implementation, or a combination of some or all of these.
2. Time to plan:
This usually takes the form of a piece of paper that I start to lay out the UI and ideas about how people will use this software. I like to write and draw, and in this day and age, that activity alone is rare and has been mostly replaced by technology.
3. Write the code:
I'm not big into IDE's (integrated development environment) which is just a fancy way of saying the editor in which we write code. I think for me, it's a visual thing. Syntax highlighting is too distracting. So I use a plain text editor like Mousepad. IDE's also can make people lazy. I think it's a good idea to do your own indentation as an example and to be familiar with best practice in programming, rather to rely on any type of automation.
4. Test the code:
I don't use a debugger. Shock, horror! For me, programming and fixing code is one of the fun parts. Ambiguity has a certain attraction. The challenge of figuring out why something doesn't work, draws you closer to a greater understanding of the how and the why, and I like that.
5. The Test drive:
Do I like the clicky? How does the UI function, do I need to tweak it? Let's get a friend to test drive it. Let's test it on more than one machine, including hardware and in a VM.
6. Ready for mass production?
Test, test and then test again. We're ready for release. But not before we upload the new package to a test repository (a new Linux Lite implementation and the inspiration behind this thread and the recent Lite Patch issue), then perform an update via both the command line and Install Updates.
7. All's well that ends well:
Everything works as we expect it to. Maybe some Social Media announcements, but generally I'll just upload the new package to the main Linux Lite repository for everyone to download via Install Updates.
The work flow:
IDEA > PLAN > WRITE THE CODE > TEST THE CODE > TEST DRIVE THE 'FINISHED' APPLICATION > WRITE THE CHANGELOG > PACKAGE THE APPLICATION > UPLOAD THE PACKAGE TO A TEST REPOSITORY > TEST THE UPDATE FROM THE TEST REPOSITORY > RELEASE TO MAIN LINUX LITE REPOSITORY > REACT QUICKLY TO ANY OVERSIGHT
|
|
|
| autostart a virtualbox vm on boot |
|
Posted by: donbrew - 12-23-2022, 10:42 PM - Forum: Other
- Replies (1)
|
 |
Evidently I am the only one. I have Home Assistant OS in a virtualbox virtual machine. It would be very convenient to have it start up at boot.
I have found the Application Autostart tab in Session and Startup. The ADD button wants the startup command.
What is the command to start virtualbox and the particular VM?
Is this correct: VBoxManage startvm HAOS --type gui
HAOS is the name of the VM.
|
|
|
| Christmas |
|
Posted by: vint - 12-23-2022, 05:23 PM - Forum: Off Topic
- Replies (3)
|
 |
Howdy y'all,
Winter's chill has invaded Texas and it is 20 degrees here at the Ponderosa with a 20 mph North wind. I just want to thank everyone who has helped me along with my Linux Lite challenges and gave top notch advise. Merry Christmas and Happy New Year from me and mine here in the great Republic of Texas, USA and may all your wishes come true.
Best regards,
|
|
|
| Hello LL-community |
|
Posted by: joshy - 12-23-2022, 12:14 AM - Forum: Introductions
- No Replies
|
 |
Hi my name is Alex,
i am curious what will happen here in the near future | (• ◡•)|
I've choosen LL for my second "LTS-Distribution", i'm of good spirits.
|
|
|
| Non-trivial RDP sessions |
|
Posted by: supp0rtmail - 12-19-2022, 07:57 AM - Forum: Other
- No Replies
|
 |
Hi all!
Here an idea came to mind, but I have not yet understood whether it can be implemented and how.
There is a PC with linux lite 3.8-32bit and two outputs for monitors (vga, hdmi), keyboards (scanners in keyboard mode), mice, monitors, also in the amount of two pieces, freerdp is configured. I would like to start two freerdp sessions at system startup and authorize two different users on the terminal server under Windows (there is no problem with this, you can write a script), but the main catch is that each session opens on its own monitor and only with its own a set of keyboard and mouse, for good, there was a binding to the USB port, and not to the device, so that in which case it was possible to hot-swap the device. If anyone had experience with similar implementations or can give good advice, I will be glad to help.
|
|
|
| Install Update Error Lenovo W510 - Could not get lock |
|
Posted by: jpaston - 12-17-2022, 07:33 PM - Forum: Updates
- Replies (1)
|
 |
============ Log ===========
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3711 (apt-get)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Hi.
I'm new to Linux. Any advice appreciated!
|
|
|
|