We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Verge3D version advice for plugin devs

Home Forums Plugins Verge3D version advice for plugin devs

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #42501
    GLiFTeK
    Customer

    Hi,
    As versions of Verge3D continue to expand, as a plugin developer, I have a question.

    What would be the best prerogative regarding this?

    Develop specifically for OFFICIAL releases?
    Ie: you’re developing, and a pre version comes out.
    You update,
    So then your puzzles example project is created with that update, which may not be compatible with most.

    Should you hold off and have a version set up within the most OFFICIAL release?

    What’s the staff’s opinion on this, if I’m being clear.

    Thanks :good:

    P.s perfect example of this being tat anything before 3.6 pre wouldn’t allow custom plugins etc.
    B-)

    • This topic was modified 1 year, 5 months ago by GLiFTeK.
    • This topic was modified 1 year, 5 months ago by GLiFTeK.
    #42504

    Hi,
    I believe you should divide your target audience in two groups – testing team of passionate Verge3D users (who might already use pre-release version or ready to install it to test your plug-in) and general audience (most of Verge3D users). This way you can share preliminary release first, get feedback, fix possible issues, and then make a stable public version.

    Verge3D’s Tech Chief
    FB | Twitter | VK

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.