npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

vizor_gui_tools

v1.4.11

Published

GUI tools for vizor engine

Downloads

447

Readme

vizor_gui_tools

A series of GUI Tools to be used in the VIZOR ENGINE PLATFORM

  • windows
  • menus
  • toolboxes
  • controls
  • forms

VIZOR Collaborator instructions

FIRST TIME :

  1. Clone the project:

git clone https://github.com/your-username/your-repository.git

  1. Modify:

Make your changes in the codebase.

  1. Create a local branch:

    • NOTA : Como nombre del branch se puede usar la versión, ejemplo : release-vX.Y.Z

      Colocar en CHANGELOG.md el detalle de los cambios realizados.

      git checkout -b feature-branch-name

  2. Add and commit changes:

git add . git commit -m "Description of the changes"

  1. Push the branch:

git push origin feature-branch-name

  1. Create a pull request on GitHub.

  2. Ask the owner to accept and merge

NEXT STEPS (Continous Development)

  1. pull to have the lastest changes

git checkout main git pull origin main

  1. create a new branch (use a name that clearly comunicate the featur you ar working on)

git checkout -b new-feature-branch

  1. Make your changes in the codebase.

  2. push the new changes

git add . git commit -m "Description of changes" git push origin new-feature-branch

Managing Versioning

Determine the version update type: Decide whether the changes constitute a major, minor, or patch update based on the Semantic

Versioning guidelines:

Major: Incompatible API changes. Minor: Backward-compatible functionality. Patch: Backward-compatible bug fixes.

Update the version number: Update the version number in the relevant files (e.g., package.json for Node.js projects) based on the determined version update type.

  1. Create a release branch:

git checkout main git pull origin main git checkout -b release-vX.Y.Z Update the changelog: Document the changes in a CHANGELOG.md file, outlining the new features, bug fixes, and other relevant information for the release.

  1. Commit the version update and changelog:

git add . git commit -m "Bump version to vX.Y.Z and update changelog"

  1. Push the release branch:

git push origin release-vX.Y.Z

  1. Create a pull request for the release branch:

  2. Create a pull request to merge the release branch into the main branch.

  3. Merge the pull request:

Once reviewed and approved, merge the pull request.

  1. Tag the release:

  2. After merging, create a tag for the new release:

git checkout main git pull origin main git tag -a vX.Y.Z -m "Release version vX.Y.Z" git push origin vX.Y.Z

  1. Create a release on GitHub:

Go to the GitHub repository, navigate to the "Releases" section, and create a new release using the created tag. Provide the release notes based on the changelog.

By following these steps, you'll maintain a well-organized versioning system, ensuring that the codebase remains structured and that changes are properly documented and released.