lebao3105 / libtextworker

Hi there 👋

I'm Le Bao Nguyen, a 15 y/o Vietnamese. I have interests in:

• Programming
• Operating systems: Historical/Hobby OSes are quite beautiful:>
• Beautify my desktop
• Any other cool stuff:3

I often look for projects around and outside GitHub, and have contributions for some of them!

What's here?

My (forked) code, of course:)

There are some iOS tweaks such as SBarOverride (selfmade) and Little12 (forked from Ryan Nair). All debs are placed in my repo, try!

Also my desktop projects - in Python, C#, C++ (just one), Pascal.

My personal website, outdated: https://lebao3105.github.io/.

This lebao3105/lebao3105 repo? Not only this profile README, I also have dotfiles for Linux desktop!

There are also many projects in GitLab, for example: JADGenerator for BlackBerry OS 7-, TextWorker (moved from this GitHub profile).

Contact me

Our local time zone is UTC +7. Whatever just contact me if needed:)

• GitHub/GitLab profile (@lebao3105)
• Twitter: @lebao_roofs
• Discord: @lebao12

libtextworker's Issues

Json support for GetConfig class

Fix spaces on path

Use os.path.normpath instead of os.path.abspath

Finally I've found out why CraftItems output starts with the current folder that it's running from lol.

This: https://stackoverflow.com/questions/68210148/os-path-abspath-from-where-is-executed

I don't know what to say about this:) Anyway this will be closed in my next commit

Remove ColorManager usage from all UI widgets?

Not all users want to have a custom theme on their GUI - they want vanilla, just like the reason I switch my textworker to wxPython - get the OS's native controls.

Sv-ttk, which is a Tcl/Tk theme, has been removed from the requirements in the 0.1.3 release. ColorManager.configure() now also doesn't call ColorManager.autocolor_run() anymore.

This will definitely be a big change for the ongoing libtextworker.