scarlettgamestudio / scarlett-editor Goto Github PK

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Problem

Let's say we have a class composition such as Text[DropShadow[Stroke[Color]]]

Where Color is the only class with a specific inspector editor.

How is inspector supposed to draw dropshadow properties?

Currently, it doesn't show its property Stroke because the inspector getPropertyContainers depth limit is 1. Going further one more level (see the example below) just makes Stroke appear in a different container.

function getPropertyContainers(object) {
            let propertyContainers = [];
            propertyContainers.push(createPropertyContainerFromObject(object));

            let ownContainerProperties = getObjectOwnContainerProperties(object);
            ownContainerProperties.forEach(function (property) {
                propertyContainers.push(createPropertyContainerFromObject(object[property]));

                const propertyOwnContainer = getObjectOwnContainerProperties(object[property]);

                propertyOwnContainer.forEach(function (subProperty) {
                    propertyContainers.push(createPropertyContainerFromObject(object[property][subProperty]));
                });

            });

            return propertyContainers;
        }

Which results in:

Expected Behavior

It's open to discussion, but showing the stroke properties inside dropshadow container is a possible solution.

Add internal animator editor.

Problem

Scarlett Editor not saving correctly, due to changes in the framework's ProjectFile that have yet to be reflected in editor's master and dev branches. See #9, particularly,

How to Reproduce

Try to save a scene in the editor (File » save)

Expected Behavior

Should be able to store and load a .ss file correctly.

Add internal visual scripting editor.

Add Text Object to Editor

Add an internal scripting editor.

Create a new window (or just split an existing one) with purely the selected objects. Helpful when the scene is crowded with objects.

It's basically a subset of scene hierarchy, that shows the selected objects.

Give https://github.com/ruhley/angular-color-picker another try. Seems to be a better option.

Add a specific Atlas Editor window/container.

Description

The project information should have its own folder at '/project_folder/.scarlett' and the project information should be divided into multiple files:

eg:
/.scarlett/project.json (contains project name and content files)
/.scarlett/workspace.json (contains the layout and editor related configurations)

Problem

The undo/redo hotkeys are being executed for both the scripting editor and the editor history commands when the scripting editor is focused.

How to Reproduce

Open the script editor and perform Ctrl+Z/Y

Expected Behavior

When the script editor is focused the hotkeys should not propagate to the editor history commands.