Some Suggestions about vis-ui

[kotcrab]

1. Not sure what JSON files you mean. In project, editor doesn't store scene in JSON but in binary format using Kryo. Though I intend to change this in VisEditor 0.3.0 so it would be possible to edit scenes as text file or for easier working with VCS. If you mean the exported JSON files that is already done, nothing more is stored than to eg. build a sprite. Why do you think they would be tied to VisUI?
2. Created #47 for this feature request

[mlipmanx]

Sorry, I was a bit unclear.

I was talking about the .scene exported files. It would be nice if there
was some way of reading the scene files into a typed data structure - with
no other functionality, so you could use that to populate the scene.

(a bit like JAXB does for XML)

Am I making sense?

Thanks

Mark

PS: I love your editor - it is the best

On 6 October 2015 at 02:05, Paweł Pastuszak [email protected]
wrote:

1. Not sure what JSON files you mean. In project, editor doesn't store
   scene in JSON but in binary format using Kryo. Though I intend to change
   this in VisEditor 0.3.0 so it would be possible to edit scenes as text file
   or for easier working with VCS. If you mean the exported JSON files that is
   already done, nothing more is stored than to eg. build a sprite. Why do you
   think they would be tied to VisUI?
2. Created #47 #47 for
   this feature request

—
Reply to this email directly or view it on GitHub
#44 (comment).

[kotcrab]

You can do it now. It's possible to deserialize scene file into SceneData object, checkout this. You will get entire scene structure without need to load anything.

[mlipmanx]

Thanks Pawel, that's exactly what I was looking for.

Is there any way to add a "Tag" to a component? That would be useful, for
example to indicate a custom class should be instantiated

Thanks

On 7 October 2015 at 02:57, Paweł Pastuszak [email protected]
wrote:

You can do it now. It's possible to deserialize scene file into SceneData
https://github.com/kotcrab/VisEditor/blob/master/Runtime/src/com/kotcrab/vis/runtime/data/SceneData.java
object, checkout this
https://github.com/kotcrab/VisEditor/blob/master/Runtime/src/com/kotcrab/vis/runtime/scene/SceneLoader.java#L141-L142.
You will get entire scene structure without need to load anything.

—
Reply to this email directly or view it on GitHub
#44 (comment).

[kotcrab]

You can configure JSON to instantiate some different class, like here. Of course that class would have to be compatible with original.

[mlipmanx]

Hi Pawel,

Yes, that's what I was thinking - but I would need a tag to work out which
class to instantiate - ie in the editor, it might be an image, but I want
to replace it with a button, or something else.

Regards

Mark

On 8 October 2015 at 06:46, Paweł Pastuszak [email protected]
wrote:

You can configure JSON to instantiate some different class, like here
https://github.com/kotcrab/VisEditor/blob/master/Runtime/src/com/kotcrab/vis/runtime/scene/SceneLoader.java#L88-L116.
Of course that class would have to be compatible with original.

—
Reply to this email directly or view it on GitHub
#44 (comment).

[kotcrab]

I see, that's not possible now. You can add VariablesComponent to Entity and then read them and transform Entity into something else but you can't skip default loading. I'm thinking of adding component that will cause to skip default entity loading (ie. creating SpriteComponent from SpriteProtoComponent) so you could manually handle such entity.

[mlipmanx]

Hi Pawel,

Actually, I think VariablesComponent will solve my issue.

Thanks

Mark

On 11 October 2015 at 05:27, Paweł Pastuszak [email protected]
wrote:

I see, that's not possible now. You can add VariablesComponent to Entity
and then read them and transform Entity into something else but you can't
skip default loading. I'm thinking of adding component that will cause to
skip default entity loading (ie. creating SpriteComponent from
SpriteProtoComponent) so you could manually handle such entity.

—
Reply to this email directly or view it on GitHub
#44 (comment).

[mlipmanx]

Hi Pawel,

If you add a variablesComponent, it is impossible to set the "Values" in
the editor - a bug

Regards

Mark

On 11 October 2015 at 07:27, Mark Lipman [email protected] wrote:

Hi Pawel,

Actually, I think VariablesComponent will solve my issue.

Thanks

Mark

On 11 October 2015 at 05:27, Paweł Pastuszak [email protected]
wrote:

I see, that's not possible now. You can add VariablesComponent to Entity
and then read them and transform Entity into something else but you can't
skip default loading. I'm thinking of adding component that will cause to
skip default entity loading (ie. creating SpriteComponent from
SpriteProtoComponent) so you could manually handle such entity.

—
Reply to this email directly or view it on GitHub
#44 (comment).

[kotcrab]

In "Add..." field you need to type key name and press enter, then you can set value.

[mlipmanx]

Yes, but then when you type in the value field, nothing appears

Thanks

On 11 October 2015 at 19:37, Paweł Pastuszak [email protected]
wrote:

In "Add..." field you need to type key name and press enter, then you can
set value.

—
Reply to this email directly or view it on GitHub
#44 (comment).

[kotcrab]

Works for me, are you using 0.2.5?

[mlipmanx]

Yes, on Linux

It almost seems to lose focus from the field.

Is there a log or something I can send you?

Regards

Mark

On 11 October 2015 at 20:21, Paweł Pastuszak [email protected]
wrote:

Works for me, are you using 0.2.5?

—
Reply to this email directly or view it on GitHub
#44 (comment).

[kotcrab]

Fixed it, you will have to use cutting edge build: http://dl.kotcrab.com/vis/editor/edge/VisEditor-edge-20151011-1.zip

Btw please use our forums next time for such discussions, thanks.