https://kotlinlang.org logo
Channels
Powered by
#tornadofx
  • e

    edvin

    02/04/2018, 4:59 PM
    @amanda.hinchman-dominguez If you choose to put observable properties in a class that implements JsonModel, those can be bound to input fields of course, but that has nothing to do with the fact that you implement JsonModel.
  • a

    amanda.hinchman-dominguez

    02/04/2018, 4:59 PM
    use case: JSONSupport is creating my tiles and grids. I customize the grid with a GUI interface, and upon saving the work, I was thinking I could translate the result of the new grid to JSON to be able to convert the work to generate code
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:01 PM
    Other than drag and drop, the user must have the ability to customize each tile by their properties to their liking, by text fields and otherwise. At the end, I can take those properties of the individual tiles and grid and save that information
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:01 PM
    @edvin I can try to make it observable and go from there. Currently, I'm not sure what would be a better way to save the information
  • e

    edvin

    02/04/2018, 5:03 PM
    @amanda.hinchman-dominguez I'm not sure I understand the issue, sorry 🙂
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:06 PM
    @edvin I don't know if what I'm describing is not quite an issue - it's more me trying to figure out the best way to connect customization from models to JSON
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:07 PM
    If you give me a little time I will come back with a much clearer idea with how I have structured the problem to the solution 🙂
  • e

    edvin

    02/04/2018, 5:07 PM
    @amanda.hinchman-dominguez The reason I don't understand is that the way I read it, you're describing a use case that is solved with the intended way to use JsonModel 🙂
  • e

    edvin

    02/04/2018, 5:07 PM
    So I don't see an issue 🙂 hehe
  • e

    edvin

    02/04/2018, 5:07 PM
    @amanda.hinchman-dominguez OK, great 🙂 Sorry, I'm a little thick when it comes to understanding stuff 🙂
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:09 PM
    @edvin I totally get what you're saying. It sounds like I can definitely make the JsonModels observable so it can be further customized by various inputs, even with text fields
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:09 PM
    And I probably could, I will try that.
  • e

    edvin

    02/04/2018, 5:09 PM
    Exposing observable properties is always the easiest/preferred way of interacting with ui elements in JavaFX at least.
    👍 1
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:10 PM
    But I also wanted to take a step back and verify that it is the best direction to go for an idea this complicated
  • e

    edvin

    02/04/2018, 5:10 PM
    And since you don't want to try to alter an in-memory json object as the ui changes, the best way to deal with that is to read in a json object, set the values into observable properties and then create a new json object from the result when you're ready to push changes to the server. That's what JsonModel is designed to help you with.
  • e

    edvin

    02/04/2018, 5:10 PM
    OK
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:10 PM
    I'm still new to designing whole solutions - I'm getting better at it, but I know that sometimes I'm limited by the knowledge I have
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:14 PM
    @edvin okay, that does sound like where I'm going is the best solution. When they become observable properties, how are those changes being actively made by the user stored somewhere in the run until I'm ready to store that information (with the 
    toJSON
    method)
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:15 PM
    just by the jsonmodel itself?
  • e

    edvin

    02/04/2018, 5:15 PM
    @amanda.hinchman-dominguez They are stored in the observable properties you define. Let me show you the simplest example possible.
  • e

    edvin

    02/04/2018, 5:16 PM
    @edvin uploaded a file: Untitled
    -.kt
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:16 PM
    @edvin thanks! I think I need to study observable properties in themselves, I wasn't sure if I ever remember reading across such information. I know you can interact with them, but I don't know what they truly are so I know when to take full advantage of it
  • e

    edvin

    02/04/2018, 5:17 PM
    You bind 
    nameProperty
    to your ui. The REST client will automatically call 
    updateModel
    when you do 
    someJsonObject.toModel<Person>()
    and when you pass the JsonModel object to 
    api.put
    or 
    <http://api.post|api.post>
    . You can also call 
    person.toJSON()
    manually to get to the json object.
  • e

    edvin

    02/04/2018, 5:18 PM
    @amanda.hinchman-dominguez Really? Almost every example in the guide that interacts with the ui uses observable properties. Every UI element in JavaFX relies on them.
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:46 PM
    @edvin I agree, it does - From the documentation I can make assumptions about what observable properties do
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:48 PM
    In TornadoFX, is it simply Kotlin's Observable Properties or does it defer slightly in any way?
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:49 PM
    https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.properties/-observable-property/index.html I read this, but I think from my impression of TornadoFX, it is easier to apply these observable properties in so many different ways
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:52 PM
    The last week has really blown me away with what TornadoFX takes advantage of - I wasn't sure that you could bind observable properties to jsonmodels
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:52 PM
  • a

    amanda.hinchman-dominguez

    02/04/2018, 5:52 PM
    I know there's a library solution for it
1...168316841685...2007Latest