This thread discusses developing the PoserPython developer community to help startup and existing programmers design, make and maintain Python based projects for potential Poser friendly technologies to be used in their product pipelines sold here at Renderosity.

How it Works- Vendors and freelance developers submit products in the marketplace with links to the Snippet Library, which is a collaborative repository hosted at Github. The Snippet University is the knowledgebase of tutorials of each snippet hosted both on the main store site as well as YouTube.

Who Will Benefit?- Professional graphics vendors, graphics hardware developers and freelance artists, novice and hobbyist developers, code testers, beta users and any PoserPython user may benefit by using both the Library and University.

Is it Free?- Some of the scripts may be sold as any other product in the store, but the intent is to promote the PoserPython user base and their collective contributions to the Library.

Is There an Installable Version? At the discretion of the staff at Renderosity, a script version may be added to the existing Python Pallet scripts from within Poser/PoserPro.

How Can I Help?- Currently, by submitting any working Python script to be used with any UI element will help the Library.

Is There a Particular IDE or Text Editor Preferred?- In keeping with the traditional interface options, it is dependent upon which editor is selected as default from within the application.

Is There a Market Model or Category Selection?- Yes. The main categories consists of the most frequently used UI areas (ie. runtimes, libraries, figures, etc). The PoserPython Methods Manual is the main source of the categories and all of its elements.

As stated, the intent of this thread is to generate support for the existing scripts and the main application. If you would like to participate or contribute to this project, simply reply to this thread with the word support in curved brackets along with you title in the header as seen here (SUPPORT). Happy rendering.

You want these in raw code I assume?

Hi. I was leaning towards an upscale approach, featuring a product/project description page due to security and EULA concerns. But staff should have an unobstructed access to all scripts submitted. I have opened a Github account for the workshop. An admin invite will be waiting for you to see the progress thus far. Simply response via Sitemail.

UPDATE-

The repos are live! Accordingly, registered members may begin immediately to submit new or existing scripts. The file system and naming convention are still in development, but the infrastructure and thus workflow is active. Below is the workflow pipeline for each of the repos and acceptance criterion physics.

Introduction to the Snippet Library Please note that the library consists of two major types of scripts; software and hardware. Each type has a sub-branch in both the staging (initialization) block and the Snippet Library (complete) block.

1. Staging: The initial intake repo, used to document candidate scripts.

2. Trial Bench: The launch and load block used by script technicians in producing viability reports

3. Assembly Calibration: The first testing block used to calibrate script executions and build.

4. Prop Diagnostics: The 2nd testing block which hosts failed builds or build components.

5. Local Diagnostics: The final testing block used as a backlog for problematic or large scripts.

6. Engine Block: The final testing block used to complete script mergers and build pipelines to create the end product script. It produces documentation files, description sheets, promotional templates, etc.

7. Snippet Library: The permanent repo for all functional scripts.

Due to the necessity of resources, a decision has been made concerning a default editor. Visual Studio will be the official IDE for the organization, because of it's existing compatibility with Github. Extensions and plugins for the editor may be included in future threads.

Other default issues include the preferred GPU hardware. The organization will be partnering with NVIDIA based applications; due to their broad ray tracing and shader library API's.

Both OpenGL and DirectX technologies will be included in the library's build, so giving greater options in software based scripting.

Math implementations for Python will included SymPy, NumPy and IPython. Other software based components will include PyCollada and MyHDL; which is a collective of Python based hardware descriptive language libraries for embedded systems projects.

This thread will be updated regularly to keep all advancements posted herein.

Happy rendering!

UPDATE 101419.1

Quick note; the organization is currently auditioning new applications for the majority of its processing and IT networking ops:

UI Design: PAGE creates TCL based UI applications that are Python compatible and work well with PoserPython.

Linux OS: LinuxMint builds easily and blends well with most popular IDE's.

Rendering Firefly is still the renderer of choice due to its native environment and support from the PoserPython community.

Game Engine Unreal Engine hosts a formidable artist/developer community and industry grade User base.

Virtual GPU VirtualBox is conducive with basically all GPU extensions and flexible in working with Python scripting for scientific and R & D projects.

If you or your studio currently work with any of the programs above and would like to port your work into the Snippet Library, then simply post to this thread with the word support in curve brackets; exp. (SUPPORT) in the header.

Thanks in advance and happy rendering

Looks good. Can I suggest the possibility of the group "buying out" PhilC's Python for Poser book (sold on the Rendosity store, but never seen on a discount), and thus making it available at a more nominal price such as $1.99? Access to that would be a big encouragement for learners and absolute beginners with PoserPython.

UPDATE 122419.1

Quick note; We are now on LinkedIn! If you would like to participate in any of the discussions or publish a VSP-3 tutorial or extension there you must contact the moderator. Keyword, VSP-3 at LI. Here are our current directives:

UI Design: We are working closely with Visual Studio's parent group, Microsoft"s family of applications to produce one consistent theme using VS and Poser's UI. Color, elements, icons and accents are being mapped and one fluid design is the intent. A sample screen shot will be added to the next update.

Repositories: Github is currently hosting all of the project's operating files and VS is already kitted to use most of Github functions. Pipelines constructed from the IDE are being directed into Github with CI/CD presets making automated tasks easier.

Rendering The primary renderer, Firefly is still the top choice, both VS and NVIDIA have render engines as well, with NVIDIA also offering a full 3D SDK; including shaders, physics engines and other resources. A file of candidate additions currently is hosted at our group at Github.

Cloud Storage: Poser by nature consumes space on hard drives, our quick fix is cloud storage. By default, we are including three stock cloud storage options; Dropbox, OwnCloud and OneDrive. A link/folder within the extension will open to the cloud provider.Each individual user will have open an account with a provider before using.

Poser Pro: A nice member of the Renderosity community gave a link to a very well prepared script which compliments the Poser environment very nicely. The script; for licencing reasons, will not be mentioned in these notes yet will be used by the group in future extensions. Thx again to the author(s).

If you or your studio currently work with any of the programs above and would like to port your work into the Snippet Library, then simply post to this thread with the word support in curve brackets; exp. (SUPPORT) in the header.

Thanks in advance and happy rendering