archive/blender-cloud
0
1
Fork 1
Code Issues 24 Pull Requests Projects Releases Wiki Activity

Introduce setup_for_cloud #54463

New Issue
Open
opened 2018-03-30 00:42:06 +02:00 by Francesco Siddi · 3 comments
Francesco Siddi commented 2018-03-30 00:42:06 +02:00
Copy Link

In our quest to decouple Blender Cloud from Pillar, I suggest to:

  • move some node_types (such as texture, hdri, group_texture, group_hdri) from pillar to blender-cloud
  • introduce a setup_for_cloud function which would append specific node_types to every cloud project and mark a project as 'set up for cloud'

To further control which node_types are enabled within a project, a setting in the "Edit Project" section could be provided.

Note: this feature comes from the request of enabling HDRI node_types in private Blender Cloud projects. Enabling HDRI has consequences (regarding CORS) and should be discussed in a separate issue.

In our quest to decouple Blender Cloud from Pillar, I suggest to: * move some node_types (such as texture, hdri, group_texture, group_hdri) from pillar to blender-cloud * introduce a setup_for_cloud function which would append specific node_types to every cloud project and mark a project as 'set up for cloud' To further control which node_types are enabled within a project, a setting in the "Edit Project" section could be provided. Note: this feature comes from the request of enabling HDRI node_types in private Blender Cloud projects. Enabling HDRI has consequences (regarding CORS) and should be discussed in a separate issue.
Francesco Siddi commented 2018-03-30 00:42:06 +02:00
Author
Copy Link

Added subscribers: @fsiddi, @dr.sybren

Added subscribers: @fsiddi, @dr.sybren
Sybren A. Stüvel commented 2018-04-17 12:56:02 +02:00
Copy Link

Looks good to me!

Would setup_for_cloud() be automatically called when someone creates a project while the blender_cloud extension is loaded?

Looks good to me! Would `setup_for_cloud()` be automatically called when someone creates a project while the `blender_cloud` extension is loaded?
Francesco Siddi commented 2018-04-17 16:25:54 +02:00
Author
Copy Link

Yes, that's the idea.

Yes, that's the idea.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: Websites
legacy project
Infrastructure: blender.org
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
No Label
Priority::Normal
Status::Confirmed
Type::Design
legacy project
Blender Cloud
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
blender-admin
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archive/blender-cloud#54463
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?