topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Tuesday March 19, 2024, 4:22 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Recent Posts

Pages: prev1 2 3 4 [5] 6 7 8 9 10next
41
Kynlo's Software / Kynlos Python Packager
« Last post by KynloStephen66515 on March 06, 2024, 05:58 PM »
Kynlos Python Packager

Kynlos Python Packager is a powerful tool crafted to streamline the process of packaging Python projects into standalone executables. Leveraging the capabilities of PyInstaller, this script empowers developers to bundle their Python applications and scripts into self-contained executables, eliminating the need for users to install Python or any dependencies.

Key Features:

  • Versatile Packaging Options: Kynlos Python Packager offers both command-line interface (CLI) and wizard-based packaging options, catering to users with varying preferences and levels of expertise. Whether you prefer fine-grained control through the CLI or a guided experience with the wizard, Kynlos Python Packager has you covered.
  • Extensive Customization: With a plethora of customizable options, users can tailor the packaging process to their specific project requirements. From specifying additional files and directories to including custom icons and license files, the script provides flexibility to accommodate diverse project needs.
  • Platform Agnostic: Whether you're developing applications for Windows, macOS, or Linux, Kynlos Python Packager ensures cross-platform compatibility by generating executables that can run seamlessly on different operating systems. This enables developers to reach a wider audience without worrying about platform-specific issues.
  • Automatic Dependency Resolution: Kynlos Python Packager automatically resolves and bundles dependencies required by the packaged Python project, ensuring that the executable remains self-contained and portable. This simplifies distribution and deployment, as users no longer need to manually install dependencies.
  • Comprehensive Documentation: To facilitate ease of use, the script comes with comprehensive documentation that explains each parameter, option, and customization feature in detail. Whether you're a novice user or an experienced developer, the documentation serves as a valuable resource for understanding and harnessing the full potential of Kynlos Python Packager.
Getting Started:

To begin using Kynlos Python Packager, simply clone the repository and follow the instructions provided in the README. Whether you're packaging a simple Python script or a complex application, the script's intuitive interface and extensive customization options make the packaging process a breeze.

Usage

Using Command Line Interface (CLI)

python packager.py [-h] [-w] [path] [-d] [-o OUTPUT_DIR] [-i INCLUDE] [-a PYINSTALLER_ARGS]
                   [-n OUTPUT_NAME] [-c] [--icon ICON] [--hidden-imports HIDDEN_IMPORTS]
                   [--version VERSION] [--binaries BINARIES] [--license LICENSE]
                   [--env-vars ENV_VARS] [--python PYTHON] [--no-compress] [--hooks HOOKS]
                   [--bootloader BOOTLOADER] [--manifest MANIFEST] [--splash SPLASH]
                   [--runtime-hooks RUNTIME_HOOKS] [--exe-format {exe,directory}]
                   [--system-path SYSTEM_PATH] [--upx-level {0..9}] [--eula EULA]
                   [--spec-file SPEC_FILE] [--runtime-hook-spec RUNTIME_HOOK_SPEC]
                   [--template TEMPLATE] [--compile-pyc] [--icon-mac ICON_MAC]
                   [--package-data PACKAGE_DATA] [--build-mode BUILD_MODE]
                   [--custom-hooks CUSTOM_HOOKS] [--custom-upx CUSTOM_UPX]
                   [--bundle-stdlib] [--exclude EXCLUDE] [--bootloader-conf BOOTLOADER_CONF]
                   [--verbose] [--external-modules EXTERNAL_MODULES] [--bundled-icon BUNDLED_ICON]
                   [--temp-dir TEMP_DIR] [--upx-conf UPX_CONF] [--resource-files RESOURCE_FILES]
                   [--app-name APP_NAME] [--log-dir LOG_DIR] [--app-version APP_VERSION]
                   [--additional-files ADDITIONAL_FILES] [--user-hooks USER_HOOKS]
                   [--file-version FILE_VERSION] [--custom-library CUSTOM_LIBRARY] [--upx-path UPX_PATH]
                   [--no-confirm] [--custom-commands CUSTOM_COMMANDS] [--freeze-imports] [--clean-build]
                   [--warn-project-version] [--warn-no-version] [--name NAME]

Using Wizard
python packager.py PATH -w

Follow the wizard prompts to guide you through the packaging process.

Parameters

  • `-w`, `--wizard`: Launches a wizard to guide you through the packaging process.
  • `path`: Path to the Python project directory.
  • `-d`, `--directory`: Flag to indicate if the path is a directory.
  • `-o`, `--output-dir`: Output directory for the packaged executable.
  • `-i`, `--include`: Additional files or directories to include in the package (format: `source_path:destination_path`).
  • `-a`, `--pyinstaller-args`: Additional arguments to PyInstaller.
  • `-n`, `--output-name`: Custom name for the output executable.
  • `-c`, `--clean`: Clean build and dist directories before packaging.
  • `--icon`: Icon file for the executable.
  • `--hidden-imports`: Additional hidden imports.
  • `--version`: Version information for the executable.
  • `--binaries`: Additional binaries or data files to include.
  • `--license`: Custom license file for the packaged executable.
  • `--env-vars`: Environment variables for the packaged executable (comma-separated).
  • `--python`: Custom Python interpreter to bundle with the executable.
  • `--no-compress`: Disable compression of bundled files.
  • `--hooks`: Additional PyInstaller hooks.
  • `--bootloader`: Custom bootloader file.
  • `--manifest`: Custom manifest file.
  • `--splash`: Splash screen file.
  • `--runtime-hooks`: Runtime hooks file.
  • `--exe-format`: Specify whether to generate a single executable (`exe`) or a directory with bundled files (`directory`).
  • `--system-path`: Additional paths to include in the system PATH environment variable.
  • `--upx-level`: Specify the UPX compression level.
  • `--eula`: End User License Agreement (EULA) file.
  • `--spec-file`: Custom PyInstaller spec file.
  • `--runtime-hook-spec`: Custom runtime hook specification.
  • `--template`: Custom template directory for PyInstaller.
  • `--compile-pyc`: Compile Python files into bytecode (.pyc) files.
  • `--icon-mac`: Custom icon for the packaged executable on macOS.
  • `--package-data`: Additional package data files.
  • `--build-mode`: Specify whether to generate a debug or release build.
  • `--custom-hooks`: Custom hooks directories.
  • `--custom-upx`: Custom UPX binary.
  • `--bundle-stdlib`: Bundle the standard library into the executable.
  • `--exclude`: Custom exclusion patterns for file/directory inclusion.
  • `--bootloader-conf`: Custom bootloader configuration file.
  • `--verbose`: Enable verbose output during the packaging process.
  • `--external-modules`: External Python modules.
  • `--bundled-icon`: Custom icon for the bundled files on Windows.
  • `--temp-dir`: Custom location for the PyInstaller temporary directory.
  • `--upx-conf`: Custom UPX configuration file.
  • `--resource-files`: Additional resource files.
  • `--app-name`: Custom app name for macOS bundles.
  • `--log-dir`: Custom output directory for logs.
  • `--app-version`: Custom version number for the bundled application.
  • `--additional-files`: Additional files to be included in the application bundle.
  • `--user-hooks`: Custom path for user hooks.
  • `--file-version`: Custom file version for the bundled executable.
  • `--custom-library`: Custom library files.
  • `--upx-path`: Custom path for UPX compression.
  • `--no-confirm`: Skip confirmation prompts during packaging.
  • `--custom-commands`: Additional custom commands for PyInstaller.
  • `--freeze-imports`: Freeze imports and disable packing.
  • `--clean-build`: Clean build directories before packaging.
  • `--warn-project-version`: Enable warnings for project version mismatches.
  • `--warn-no-version`: Enable warnings for missing version information.
  • `--name`: Custom name for the packaged executable.

Examples

To package a Python project into a standalone executable using the CLI:

python package.py "\path\to\my_project.py" --icon my_icon.ico --output-dir dist --no-compress --verbose

With more options:

python package.py -d "\path\to\my_project" \
    --output-dir dist \
    --no-compress \
    --verbose \
    --icon my_icon.ico \
    --hidden-imports pandas \
    --env-vars "KEY=VALUE,ANOTHER_KEY=ANOTHER_VALUE" \
    --additional-files "data_folder:data_folder" \
    --upx-level 9 \
    --custom-commands="--add-data 'resource_folder:resource_folder' --exclude '__pycache__'" \
    --name NAME \
    --custom-upx C:\path\to\custom_upx.exe \
    --bundle-stdlib \
    --clean-build \
    --warn-project-version \
    --warn-no-version \
    --app-version 1.0 \
    --file-version 1.0 \
    --no-confirm

(Single line)

python package.py -d "\path\to\my_project" --output-dir dist --no-compress --verbose --icon my_icon.ico --hidden-imports pandas --env-vars "KEY=VALUE,ANOTHER_KEY=ANOTHER_VALUE" --additional-files "data_folder:data_folder" --upx-level 9 --custom-commands="--add-data 'resource_folder:resource_folder' --exclude '__pycache__'" --name NAME --custom-upx C:\path\to\custom_upx.exe --bundle-stdlib --clean-build --warn-project-version --warn-no-version --app-version 1.0 --file-version 1.0 --no-confirm

This will package the my_project.py script into a standalone executable with the specified options.




Link: https://github.com/Kynlos/KPyPackager
42
I'm afraid this is a very long post. It seemed worth giving enough details for anyone else to be able to follow what I'm currently doing; it does assume some knowledge of outliners, Workflowy, zettelkasten and Luhmann.

I haven't done much with zettelkasten in the past - my usual need is for longer notes - but I have started one with Workflowy, and thought I'd explain it here.
  • The first point I need to make is that, despite "Smart Notes", Luhmann's zettelkasten is not a system designed for students - at least not until they are following their own streams of thought; Luhmann was always a researcher who published articles and books. But, if the phrase honing stage is ignored, it is a perfectly applicable system for anyone who is following their own streams of thought whether that be RPG, making bookcases or tracking health. It ought to help develop expertise in anything.
  • Second point is that it is a high effort system. Part of the productivity gain is from the repeated pondering when trying to locate the best place for a new zettel. The rest of the gain comes from the structure enabling brick to be placed on brick until a building emerges.
  • The third is that Luhmann's practice (aka "the rules") does matter.

  • Zettels have to be placed with time-consuming care in a sequence. Some may be new starters (for different subjects), but they need at least the same amount of thought before that decision.
  • Zettels have to be brief and to the point: they're not a string of sequential thoughts - if they're worth it, sequential thoughts need to be sequential zettels. This is hard and requires discipline. If a thought isn't worth that effort, it should not be put into the zettel. I don't put my frequent long notes into the zettelkasten, but I do write a zettel fo each one, with the the reference. It's worth emphasising that a brief atomic note implies two conditions that have to be met, not just one.

  • Workflowy supports this to a degree because it works best when each zettel is a bullet/paragraph.
  • I find that, for the purpose of future linking, it is useful to append a time/date stamp to each zettel. My sequence is title (in bold) + time/date, then the note/thought. All in a single mass of text. I have a time/date stamp as my (most used) shortcut in a text expander so that it can be used in any program. I put references and #tags in the bullet note (#tags are used as a form of index entry)
  • (Technically, all the content could be put into the note rather than the bullet - and I might do that if Workflowy offered the same viewing options for notes (show, hide, 1st line) as Dynalist - but it has no options, and always shows 1st line only.
  • I also find it useful to have an external library/hoard (which is part of the usual zettelkasten system anyway), Items can be highlighted & referenced. Zettels need the essence and not the clutter.
  • I'm aware that it's easy to add a zettel to the head of the list in an outliner. It should also be possible in a card index: idk if Luhmann ever did it; I doubt it since he was probably restricted by his numbering scheme, but I do sometimes.
  • If I want to see, or play, with the zettelkasten in a mindmap, I do OPML export to Mindomo. And export back again if necessary. Most mindmap programs should be able to do this. (Many might be able to work as the outliner too. I simply prefer to use Workflowy).
  • Workflowy doesn't have a wordcount. Which is fine for zettels, but is a pain for anything longer.
  • There's also the possibility of using notes or comments to add detail or successive reflections. At some point the comments could be made into zettels of their own.

Luhmann's phases are essentially: read/think - write zettel - refine note language - place in zettel sequence. Every note placement is an opportunity for further thinking, refining language and adding links/references.

The system I am describing has neural pathways through folgezettel outlines/mindmaps, wikilinks and backlinks, tags as well as optional structure notes. Plus search and filters.

There are a number of reasons why systems like the daily notes and wikilinks of Roam and Obsidian don't create a functional zettelkasten.
  • They encourage verbosity and lack of focus. (A frequent reflection from Roamans after leaving the cult.)
  • (Everything should NOT go into the zettelkasten; the thinking about exclusion is important.)
  • There's no targeted review.
  • The long folgezettel debate on forum.zettelkasten.de largely compares the use of alphanumeric folgezettel with numeric date/time stamps as links. The latter's review system is based on Structure Notes (aka index notes, or Maps of Content in ObsidianSpeak); but folgezettel placing can take place multiple times a day and cover all areas potentially receiving new notes, whereas Structure Note review will be infrequent and partial (I've seen weekly recommended apparently with an acceptance that most users won't manage it that often). The debate made me think of angels pogoing on an needle: everyone is righteous and no-one changes position.
  • No mental effort is used to find the precise place for a zettel/note. Everything relies on links, the automated backlinks and a graph.
  • Structure is expected to be self-emergent (ie automated) rather than the consequence of reflection during placement. There's an assumption that note value is demonstrated by its link density.

In use, I find that this system highlights trains of thought rather than individual notes, and that going through it later does sometimes stimulate further thoughts. Not only are thoughts/notes not islands, but they have active (or inactive) trading networks in a way that graphs of wikilinks don't. I therefore use it for all topics where I am interested in the chain developing (and, maybe especially, branching).

If I write a long note, I decide whether I'm interested in a chain, and, if I am, I add a zettel to reference it. I write as many long notes as I did; the type of mental focus used when writing a long note is quite different to working on the zettelkasten. Sometimes I might write the zettel and then the referenced longer note later.

I happily mine old notes, highlights, webclips, articles, books and add a zettel to reference them when it seems right. I never directly add an old note to the zettelkasten.

Everything is written, described or summarised in my own words. When I don't like my words or phrasing, I have never been able to stop myself working on the language whenever I read something I've written.
43
Find And Run Robot / Re: where are scoring rules stored?
« Last post by kireta on March 06, 2024, 03:37 PM »
Nod5...

Thank you!!

Super helpful  :)
44
PublicDomainVic / Re: AddressBooker - Webpage to Address Book
« Last post by publicdomain on March 06, 2024, 02:33 PM »
No worries AMIGO :up: I just want to see where your Linux box is at (the full list of commands is larger; the AddressBooker program is a Node script at this time hence it needs you to have a suitable runtime set-up).

Realistically, it'll be until Friday & the weekend when I devote full days to finishing DC programs entirely so go at ease

(Thank to you for accepting the penguin for a platform as it streamlined things)
45
Hello!

Any good Chrome Extension to autofill job applications in popular platforms?
Like Workday, SuccessFactors, ICIMS, Taleo, Brassring, etc.
These platforms unfortunately have tricky web controls probably to prevent automated filling of forms.

Most I tried either want you to store your info on their server which I am not keen to do or they simply do not work.
Thanks!
46
PublicDomainVic / Re: AddressBooker - Webpage to Address Book
« Last post by sphere on March 06, 2024, 01:03 PM »
Worrying about portable later makes sense. I will try and run it tonight when I get home, but it will be pretty late. Otherwise I might not get to it until tomorrow.
Hope that does not delay you to much.
Thanks
47
N.A.N.Y. 2022 / Re: N.A.N.Y. 2022 - KeyLoop v0.1.0
« Last post by publicdomain on March 06, 2024, 06:04 AM »
Hello @publicdomain

Great tool , do everything I want except few things :)

May I ask for enhancements if possible :

- ability to change Hotkey
- set infinite loop
- Don't bring focus on the windows it is supposed to key in. (like Auto-keyboard by Murgee), key in the background

Thx

Hello & good day @orlith! Glad you're liking the program  :Thmbsup: Do feel free to call me Vic  :)

Regarding the last one, please be aware that unfocused key "presses" are sent via direct Windows API so it depends on how each individual program handles the messages. This mostly works with "traditional" applications that use normal windows; it is the more elaborated ones taking over full screen and doing custom event processing that I've seen having issues. Just wanted to inform about this, in case you're planning to use the feature in a game or some other app with a non-standard window events processing.



Okay! Your request is acknowledged & I begin to add to KeyLoop's code. Please "ping" when you're around again :up:

Cheers!
48
N.A.N.Y. 2024 / Re: TIMP - Tray Icon Music Player [N.A.N.Y. 2024]
« Last post by publicdomain on March 06, 2024, 05:46 AM »
Other than that minor glitch though, I would put my paw of approval on integration with shutdown B!     This is awesome!

Glad you're liking it! :-*

I'm addressing your reported glitch & the "persistent settings" feature to call it done (so your latest configuration is kept).

...There's still one more version/release to proceed to the integrated "ShudownTIMP" :Thmbsup:

(We'll handle it as a new program with its own GitHub repository + thread)
49
PublicDomainVic / Re: AddressBooker - Webpage to Address Book
« Last post by publicdomain on March 05, 2024, 11:54 PM »
That is pretty large, but totally doable.  You had mentioned it being portable. So I am assuming if need be I could run it off of an external USB 3.0 or more.

Currently doing all development on Linux. Portable looks doable, but I'm only focused on getting it going (and doing it right, including userDataDir for consistent profile + xPath definitions).

Please tell me if this command runs on your end (Mint):

npm i puppeteer

That should do the setup to run the program cloning from GH.

(Let's handle making it portable later).
50
General Software Discussion / Re: Any Break Reminder freeware?
« Last post by sphere on March 05, 2024, 12:17 PM »
I worked someplace that had workrave installed.  It was a small company.

Some alternatives. I do not know the volume is a thing)
https://hovancik.net/stretchly/about/

I also saw https://www.eye-saver.net/

I have used neither of the alternatives above
Pages: prev1 2 3 4 [5] 6 7 8 9 10next