Visitar URL original
Algorithmic Typography · Issue #114 · processing/processing-contributions · GitHub
Skip to content

Algorithmic Typography  #114

Description

@MichailSemoglou

Properties File URL

https://github.com/MichailSemoglou/AlgorithmicTypography/releases/latest/download/AlgorithmicTypography.txt

Home Page URL

https://github.com/MichailSemoglou/AlgorithmicTypography

Guidelines Confirmation

  • I confirm that my library follows the guidelines.

Additional Remarks

Re-submission with corrected properties file (fixes from #113).

Activity

  1. mingness commented on Feb 20, 2026

    @mingness
    Collaborator

    @MichailSemoglou Thank you for this submission, and thanks for your patience. Usually a successful action creates a new PR for adding the new library to the contributions database. Since that's not happened, I'm going to poke around a bit to see if it triggers the action.

  2. changed the title [-]Algorithmic Typography[/-] [+]Algorithmic Typography [/+] on Feb 20, 2026
  3. changed the title [-]Algorithmic Typography [/-] [+]Algorithmic Typography[/+] on Feb 20, 2026
  4. github-actions commented on Feb 20, 2026

    @github-actions
    Contributor

    Your properties file was successfully parsed.
    A pull request with your contribution has been successfully created.

  5. linked a pull request that will close this issueAdding Algorithmic Typography #115on Feb 20, 2026
  6. changed the title [-]Algorithmic Typography[/-] [+]Algorithmic Typography [/+] on Feb 20, 2026
  7. github-actions commented on Feb 20, 2026

    @github-actions
    Contributor

    Your properties file was successfully parsed.
    A pull request with your contribution has been successfully created.

  8. mingness commented on Feb 20, 2026

    @mingness
    Collaborator

    Hello @MichailSemoglou , thanks for your work on this library. To get a sense of the library, I was looking through the extensive examples, but a few don't run. Specifically the CustomFont and WaveAngle examples return an error when run. Also I expected the CulturalStyles example to change the font with each setting, but nothing is changing. Do you mind looking at these examples, and either updating the documentation to fix any configuration issues, or to fix the errors causing the examples not to run? Many thanks!

  9. MichailSemoglou commented on Feb 23, 2026

    @MichailSemoglou
    Author

    Hi @mingness
    Thank you for taking the time to work through the examples so carefully.
    You make a great point about CulturalStyles too. Having the font visibly change with each setting would make the example much more intuitive. I'll update that alongside fixing the two errors this week, and will let you know once everything is live so you can take another look.

  10. MichailSemoglou commented on Feb 26, 2026

    @MichailSemoglou
    Author

    Hi @mingness
    We've updated the Library to version 1.1.1. After thorough testing in both the office and the lab, everything is running smoothly with no unexpected issues. That said, we’re still treating this as a work in progress, so keep an eye out for any quirks.
    CulturalStyles and the PerformanceMode examples are temporarily unavailable.
    We’re also excited to share that a dedicated website is in the works! We’ll circle back when version 2.0.0 is ready and the site is live. In the meantime, if you spot any bugs or hiccups, please don’t hesitate to reach out. We’d love your feedback!
    Thanks for the support!

  11. mingness commented on Feb 26, 2026

    @mingness
    Collaborator

    Hello @MichailSemoglou thanks, I'll take a look. Just a thought about version numbers, are you familiar with Semantic Versioning? In case not, that's a recommended standard for how to version, https://semver.org/. In the guidelines, they recommend

    Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

    Since the library is under development, it might be more intuitive to start your versioning with a major version of 0.y.z.

  12. mingness commented on Feb 26, 2026

    @mingness
    Collaborator

    Also, regarding the dedicated website, you might have seen my comment about it in Discord? I was referring to the recommended documentation website. You can see this example of this for the processing-library-template. We generally recommend using this template, since we've tried to automate much of the process as possible. Happy to answer any questions you might have about it.

  13. MichailSemoglou commented on Feb 27, 2026

    @MichailSemoglou
    Author

    Hi @mingness
    Thank you so much for the thoughtful feedback and for taking the time to look into it.
    I’m actually familiar with Semantic Versioning, though I'll admit I haven't been applying it as systematically as I should. I'll update the version number to follow the 0.y.z convention over the weekend.
    I did see your comment on Discord about the dedicated documentation website, and the processing-library-template looks like a great starting point. I'll explore it over the weekend as well and will definitely reach out if I have any questions. Thanks again for all the guidance, it's really helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions