Unless they own Italy now, we should be safe.

iTaly.

Haha, they did try to patent the rectangular touch screen if I recall. But I doubt there will be any issues considering the origins you highlight...

@carlw Did you want to rename

replaceWith

or where did you want to use the term Segue?

I went through the Thesaurus for "Transition" and "Segue". Nothing else sounds good.

I think Segue is good, Apple paved the way for it so now most people (programmers) will have some kind of understanding of what it means.

I agree, let's go with that. That was always in the back of my mind when @Ruckus introduced this feature

I'm still unclear on where it should be used.

Seque is part of the framework so it's not tied to the programming language. I have swift for Linux and there isn't a segue in sight

Seque as a concept speaks to a separate entity that can have endpoints and behavior like the tornado transition

But I think tornado might be missing some of the extra stuff like passing data in the transition or lifecycle like a pre transition event

That's what I thought. You wrote " in Swift there is something called a Segue", that's why I asked 🙂

I lump it al together like apple developers (though I'd like to try app code)

Passing data might be just the right fit for Scope now, don't you think?

App code seems nice. My concern would be how well it integrates with the rest of the stack. Hopefully it's all seamless.

I'll pack it in for the night. I will do more tests with the scope and see if I can make a small screencast. It's been a while, need to get back in the game 🙂

Scope helps because both sides of a transition have access to all the data, Might need just a single arg to be passed as user data like a key into the scope's structure for a selected item

@Ruckus @edvin should I get deprecation warnings or compile errors if I'm using old CSS style? Going through the guide right now and verifying it's up-to-date.

I noticed @Ruckus or @edvin made some edits to update CSS. Thanks guys. Can you guys sign off on this chapter before I cover mixins? Are there any other features I am missing besides that?

@carlw isn't that what models and controllers are for? Although my mind might be corrupted by #C0B8Y8BHC... I would use a replay(1) in a CompositeObservable to pass data from one view to another. I suppose you could just use a mutable var as well in a backing Controller of sorts.

@thomasnield - it's scope in the angular sense of the word

@thomasnield the scope discussion is about there being several of your mutable vars (in whichever layer) in an app. -at-Singleton would only give you one. -at- prototype would give you a mutable var for every injection point

Regarding scope…I’m writing only about an enhancement to the find() function. I think the change is needed because TornadoFX is doing the object wiring. I don’t think that apps should use scope if they don’t need it because singleton will be sufficient.

This diagram depicts the proposed change to find() involving scope. The top left “Singleton C” shows a shared object C available throughout the application to all objects. The right “Scoped C” shows a pair of shared objects Ca and Cb which are available to certain segments of the app (the scope). The bottom left “Prototype C” shows how the other form of object wiring — prototype — works.

@User uploaded a file: and commented: Enhacement to find()

@thomasnield Just finished watching the O'Reilly course... not bad, basic, but pretty nice. I hope his "advanced" course comes out soon.

@jchildress There is a part II coming out next week he told me.

@thomasnield - just reading your rxjavafx guide - some good stuff in there 🙂

@gtnarg I'm glad you're liking it! I only have one more chapter on decoupling with CompositeObservable. Trying to get TornadoFX guide done too.

your efforts are appreciated on both fronts