Release JSFX Library to make JSFX plugins look nicer (and easier to program) v0.Alpha.1

[PhilRangerQuebec]

No description provided.

[cfillion]

• Is the intent of this package releasing the demo script of the library, or the library itself? It's currently the former but the display name doesn't reflect that.

  (Since each JSFX is expected to be self-contained, just demo package seems the best way to release. Users of the library would ship their own copy rather than link to this one.)

• The URL at line 16 is broken.

• The library should use .jsfx-inc extension to not be shown in the FX browser.

• Is "Test Phil Ranger Library version Alpha.jsfx" the permanent name? The package filename identifies it forever and cannot be changed later (eg. when it's no longer "version alpha").

• The import path should include the relative subdirectory.

[PhilRangerQuebec]

Bonjour Christian, Your name sounds French. I’m from Quebec City, so French is my first language. My goal is to release the library, but I have made a plugin to show how to use it. The plugin uses 3 pictures. I think releasing them together makes more sense. Some may find the plugin useful by itself, but it’s not the goal. Your help and guidance would be greatly appreciated! I don’t know how versions are managed usually. I’d like to have some people test and comment so I can release a bug-free version, probably with more features if I get requests that make sense and match my programming level. Can you do the modifications or help me to do them properly? I had a hard time making a semi-working package! Thanks for your help and support. Phil Ranger Sent from my phone, please forgive typos and short answers On Feb 19, 2025, at 12:00 PM, Christian Fillion ***@***.***> wrote:  * Is the intent of this package releasing the demo script of the library, or the library itself? It's currently the former but the display name doesn't reflect that. (Since each JSFX is expected to be self-contained it's also the best way to release. Users of the library would ship their own copy rather than refer to this one.) * The URL at line 16 is broken. * The library should use .jsfx-inc extension to not be shown in the FX browser. * Is "Phil Ranger Library version Alpha" the permanent name? The package name identifies it forever and cannot be changed later (eg. when it's no longer "version alpha"). — Reply to this email directly, view it on GitHub<#409 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPTBHQC6GFLL4LWKC4PI7X32QS2BFAVCNFSM6AAAAABXOUREN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRZGIZTENJSGY>. You are receiving this because you authored the thread.Message ID: ***@***.***> [cfillion]cfillion left a comment (ReaTeam/JSFX#409)<#409 (comment)> * Is the intent of this package releasing the demo script of the library, or the library itself? It's currently the former but the display name doesn't reflect that. (Since each JSFX is expected to be self-contained it's also the best way to release. Users of the library would ship their own copy rather than refer to this one.) * The URL at line 16 is broken. * The library should use .jsfx-inc extension to not be shown in the FX browser. * Is "Phil Ranger Library version Alpha" the permanent name? The package name identifies it forever and cannot be changed later (eg. when it's no longer "version alpha"). — Reply to this email directly, view it on GitHub<#409 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPTBHQC6GFLL4LWKC4PI7X32QS2BFAVCNFSM6AAAAABXOUREN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRZGIZTENJSGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>