https://www.linuxliteos.com/forums/ Fri, 03 Apr 2026 21:59:08 +0000 MyBB https://www.linuxliteos.com/forums/showthread.php?tid=9844 Thu, 19 Feb 2026 09:01:29 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=9844
]]>
]]> https://www.linuxliteos.com/forums/showthread.php?tid=9658 Sun, 05 Oct 2025 13:59:34 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=9658
3 applications ported today:

]]>
3 applications ported today:

]]> https://www.linuxliteos.com/forums/showthread.php?tid=9636 Mon, 15 Sep 2025 18:13:48 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=9636
I'm certainly no Python/GTK expert, but I am learning fast. The application when running uses 172mb of memory and the entire applications weighs in at 28kb!

A.I. is mind-blowing. I would like to eventually convert all existing Linux Lite applications to Python/GTK.

Currently testing with Series 6 to Series 7. Once that ticks all the boxes, will move onto testing with Series 7 to Series 8.

Really hoping to make this ready for deployment at the start of Series 8.

After a few hours of bug squashing, the first build was ready for a test drive.

]]>
I'm certainly no Python/GTK expert, but I am learning fast. The application when running uses 172mb of memory and the entire applications weighs in at 28kb!

A.I. is mind-blowing. I would like to eventually convert all existing Linux Lite applications to Python/GTK.

Currently testing with Series 6 to Series 7. Once that ticks all the boxes, will move onto testing with Series 7 to Series 8.

Really hoping to make this ready for deployment at the start of Series 8.

After a few hours of bug squashing, the first build was ready for a test drive.

]]> https://www.linuxliteos.com/forums/showthread.php?tid=9581 Mon, 01 Sep 2025 01:36:26 +0800 Distroware]]> https://www.linuxliteos.com/forums/showthread.php?tid=9581 https://gitlab.com/users/linuxlite/projects but I don't see stuff related to iso building or profiles]]> https://gitlab.com/users/linuxlite/projects but I don't see stuff related to iso building or profiles]]> https://www.linuxliteos.com/forums/showthread.php?tid=9231 Fri, 02 Aug 2024 12:38:20 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=9231
Sent from my Mobile phone using Tapatalk]]>
Sent from my Mobile phone using Tapatalk]]> https://www.linuxliteos.com/forums/showthread.php?tid=9201 Mon, 01 Jul 2024 10:19:51 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=9201
]]>
]]> https://www.linuxliteos.com/forums/showthread.php?tid=9163 Wed, 05 Jun 2024 02:35:31 +0800 Simon Crawford]]> https://www.linuxliteos.com/forums/showthread.php?tid=9163 https://www.linuxliteos.com/forums/showthread.php?tid=8956 Sat, 21 Oct 2023 08:56:30 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=8956


]]>


]]> https://www.linuxliteos.com/forums/showthread.php?tid=8632 Sun, 25 Dec 2022 08:33:47 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=8632
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
]]>
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
]]> https://www.linuxliteos.com/forums/showthread.php?tid=8551 Wed, 09 Nov 2022 12:57:53 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=8551
I've recently quit my full-time job and taken on a new job that is part time. This will allow me to contribute more time to this project  ;D

The easiest and less time demanding way to tackle translations, is to translate the Menu entries or .desktop files. This will address much of the feedback I have received to date about incomplete translation in the OS.

The root of the project is here - https://www.transifex.com/linux-lite/ (Sign in or Sign up first).

From there, you can choose a Lite application and it's .desktop file and begin translating (you will need to register first and then request to join the Linux Lite Team).

Once you've done all that, the website is pretty intuitive. At some point, I'll get around to doing a full tutorial, but to be honest, from what I've seen in other projects, if you have performed translations before, you can work the other stuff out too.

A good place to start is the Lite Autologin or Lite Desktop projects. These already have all the languages in place, Lite Tweaks does not.
For me, adding just one new Lite application to Transiflex takes a long time, so you can imagine adding all of the Lite apps will take a very long time, but I will chip away at it and get them all up eventually.

Have fun translating!

Thank you

========================================================

Quick tutorial:

- Register on the site (see above)

- Click on a Lite app on the left hand side:



- Click on Translate on the right side:



- Select a Language to translate to:



- You ONLY need to translate the Description. Please DO NOT translate anything else for the Menu entry files:



- To finish, click on Save Translation on the right.]]>
I've recently quit my full-time job and taken on a new job that is part time. This will allow me to contribute more time to this project  ;D

The easiest and less time demanding way to tackle translations, is to translate the Menu entries or .desktop files. This will address much of the feedback I have received to date about incomplete translation in the OS.

The root of the project is here - https://www.transifex.com/linux-lite/ (Sign in or Sign up first).

From there, you can choose a Lite application and it's .desktop file and begin translating (you will need to register first and then request to join the Linux Lite Team).

Once you've done all that, the website is pretty intuitive. At some point, I'll get around to doing a full tutorial, but to be honest, from what I've seen in other projects, if you have performed translations before, you can work the other stuff out too.

A good place to start is the Lite Autologin or Lite Desktop projects. These already have all the languages in place, Lite Tweaks does not.
For me, adding just one new Lite application to Transiflex takes a long time, so you can imagine adding all of the Lite apps will take a very long time, but I will chip away at it and get them all up eventually.

Have fun translating!

Thank you

========================================================

Quick tutorial:

- Register on the site (see above)

- Click on a Lite app on the left hand side:



- Click on Translate on the right side:



- Select a Language to translate to:



- You ONLY need to translate the Description. Please DO NOT translate anything else for the Menu entry files:



- To finish, click on Save Translation on the right.]]> https://www.linuxliteos.com/forums/showthread.php?tid=8506 Fri, 07 Oct 2022 12:18:42 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=8506
]]>
]]> https://www.linuxliteos.com/forums/showthread.php?tid=8419 Thu, 28 Jul 2022 16:41:53 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=8419


New end dialogue...



All fully tested and ready for the 6.2 release.]]>


New end dialogue...



All fully tested and ready for the 6.2 release.]]> https://www.linuxliteos.com/forums/showthread.php?tid=8089 Wed, 19 Jan 2022 09:19:25 +0800 Neozeon]]> https://www.linuxliteos.com/forums/showthread.php?tid=8089
Thanks]]>
Thanks]]> https://www.linuxliteos.com/forums/showthread.php?tid=7840 Mon, 19 Jul 2021 18:05:58 +0800 paulus]]> https://www.linuxliteos.com/forums/showthread.php?tid=7840
Next to my main desktop, I have a few laptops of Dell Latitude D620. Although they are all 64 bit, it is too heavy to run a 64 bit Linux distro on them, because they only have 1 GB of ram.

I know that the latest 32 bit version of Linux Lite is 3.8, but that has been discontinued since April 2021!

1. Are there any plans to resume the creation of a 32 bit version of Linux Lite?
2. If not: is it still recommendable to make use of LL 3.8 32 bit?
3. If not: what would be your suggestion to use instead?

Thanks in advance for answering!

paulus]]>
Next to my main desktop, I have a few laptops of Dell Latitude D620. Although they are all 64 bit, it is too heavy to run a 64 bit Linux distro on them, because they only have 1 GB of ram.

I know that the latest 32 bit version of Linux Lite is 3.8, but that has been discontinued since April 2021!

1. Are there any plans to resume the creation of a 32 bit version of Linux Lite?
2. If not: is it still recommendable to make use of LL 3.8 32 bit?
3. If not: what would be your suggestion to use instead?

Thanks in advance for answering!

paulus]]> https://www.linuxliteos.com/forums/showthread.php?tid=7789 Sun, 23 May 2021 07:10:35 +0800 valtam]]> https://www.linuxliteos.com/forums/showthread.php?tid=7789
Web browser
Email client
Firewall
Office Suite
Partitioner
PDF viewer
Media player
Photo editor
Photo manager
Scan software
Back up software
etc

Base files and drivers will stay intact as per usual - to ensure wide hardware compatibility.
Start up and shutdown as you could imagine are ridiculously quick.

Should I do this? Main Linux Lite release will remain unchanged.

]]>
Web browser
Email client
Firewall
Office Suite
Partitioner
PDF viewer
Media player
Photo editor
Photo manager
Scan software
Back up software
etc

Base files and drivers will stay intact as per usual - to ensure wide hardware compatibility.
Start up and shutdown as you could imagine are ridiculously quick.

Should I do this? Main Linux Lite release will remain unchanged.

]]>