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

    carlw

    07/21/2017, 5:29 PM
    It'll strip out all the signatures in a directory full of JARs and replace them
  • r

    Ruckus

    07/21/2017, 6:31 PM
    @edvin Did you say 
    by
    is already take (so we can't use 
    infix fun <http://Number.by|Number.by>(y: Number)
    )? I don't see where.
  • e

    edvin

    07/21/2017, 6:32 PM
    Isn't 
    by
    a reserved word?
  • e

    edvin

    07/21/2017, 6:33 PM
    val ctrl: MyController by inject()
  • r

    Ruckus

    07/21/2017, 6:56 PM
    Ah, yes, but only in places where delegation can happen. You can use it as an identifier without issue. Not sure if we want to though. It could be confusing.
  • c

    carlw

    07/21/2017, 7:00 PM
    @Ruckus I'd pass on overloading by. In this case, there would be by-s at the top of a TornadoFX file for CDI and by-s in the middle of the file creating coordinates.
  • r

    Ruckus

    07/21/2017, 7:02 PM
    Fair point. It could get ugly.
  • r

    Ruckus

    07/21/2017, 7:03 PM
    We could do 
    x
    , but I'm sure that gets overused a lot. (
    1 x 1
    , 
    2 x 4 x 8
    )
  • d

    dr.fornax

    07/21/2017, 7:05 PM
    @nimakro I have been away from the computer for a few hours. I post what I have right now. it is simply exactly the example from the webpage in Kotlin.
  • d

    dr.fornax

    07/21/2017, 7:06 PM
    @User uploaded a file: The Controller
    The_Controller.kt
  • d

    dr.fornax

    07/21/2017, 7:07 PM
    Should I make this a view and add the fxml code as Kotlin to it? Or waht is the right approach to deal with the problem? The fxml code it the first in this example http://rterp.github.io/GMapsFX/
  • c

    carlw

    07/21/2017, 7:23 PM
    @Ruckus do you think the infix overloading is worthwhile? i remember a lot of problems when I was a c++ coder. speaking about kotlin in general, not just tornadofx
  • c

    carlw

    07/21/2017, 7:25 PM
    ex 10 x 10 x 2 = scale a 10x10 rectangle. the first x is object creation, the second is multiplication
  • r

    Ruckus

    07/21/2017, 7:27 PM
    It's once of those things that, if used well, can be really sleek and nice, but it does tend to get way overused and misused. I tend to shy away from it for fear of making my code too confusing or unreadable, but every now and then it's quite nice.
  • c

    carlw

    07/21/2017, 7:28 PM
    it's in Swift now too...keeping an open mind
  • r

    Ruckus

    07/21/2017, 7:34 PM
    I got a bit carried away and made myself a loading bar...
    Untitled.kt
  • c

    carlw

    07/21/2017, 7:41 PM
    🙀 and i was patting myself on the back this morning for using the += operator!
    😁 2
  • c

    carlw

    07/21/2017, 7:53 PM
    I usually use the Stage's onShown instead of the runLater.
  • r

    Ruckus

    07/21/2017, 7:54 PM
    In this case I didn't want to pull 
    rects
    out to a member variable, but that's usually a good idea.
  • c

    carlw

    07/21/2017, 7:56 PM
    I've gotten some odd JavaFX results with runLater and also Task.call. Seems like code sometimes doesn't run. And I can't trace it in the debugger or reconcile printlns. Not saying this code is in the same boat, but I do Stage across-the-board now
  • r

    Ruckus

    07/21/2017, 7:57 PM
    Interesting. I haven't run into that, though I usually just use 
    runLater
    to move data from a thread to the UI.
  • c

    carlw

    07/21/2017, 7:58 PM
    also seen some unexpected behavior after a showAndWait
  • r

    Ruckus

    07/21/2017, 7:58 PM
    With just one helper function everything in the 
    runLater
    can be squashed to
    Copy code
    rects.mapIndexed { i, rect ->
    rect.init()
    SequentialTransition(
        PauseTransition((i * 0.1).seconds),
        rect.scale(0.67.seconds, Point2D(0.1, 1.0), play = false),
        rect.rotate(0.33.seconds, 90.0, play = false)
    )
}.playSequentioally { cycleCount = Timeline.INDEFINITE }
    👍 1
  • c

    carlw

    07/21/2017, 7:59 PM
    like a difference between stage.showAndWait() doSomething() and
  • c

    carlw

    07/21/2017, 7:59 PM
    stage.setOnShown( this::doSomething ) stage.showAndWait()
  • c

    carlw

    07/21/2017, 8:00 PM
    ...might have been just show()
  • r

    Ruckus

    07/21/2017, 8:02 PM
    That doesn't surprise me. I've had my fair share of headaches when mixing threading and GUIs together. I tell myself I'm getting better, but I'm not sure if it's true or I'm just instinctively avoiding complicated cases now 🤔
  • e

    edvin

    07/21/2017, 8:16 PM
    @Ruckus You can do 
    paddingAll = 20
    instead of 
    padding = Insets(20.0)
    and we have 
    runLater
    instead of 
    Platform.runLater
    now 😁
  • e

    edvin

    07/21/2017, 8:24 PM
    @Ruckus But man, that was a nice loading bar!
  • r

    Ruckus

    07/21/2017, 8:25 PM
    Ah, indeed. We have so many useful functions I keep forgetting them 🙂
1...130613071308...2007Latest