And all that Yoga crap is just about getting it light and small. To do that they throw away quad core and install a crappy keyboard and trackpad and remove the trackpoint. Incredible.

I have a Yoga for my Windows 10 testing. At the time, I thought I'd use the tablet mode. I ended up supporting an Objective-C app so usually travel with a Yoga and an iPad in a neoprene sleeve i7-4500U is passable

i'm running a Skylake which really brings my build times down

I had the Yoga 900 with the i7-6600U, but I just felt it was too sluggish and that the trackpad was very inacurate. Coming off of the MacBook Pro is not easy 🙂

i have a 6700 (linux) it's brought my build times on a larger project down from 5 mins+ on the Yoga to 1 min

kotlin feels a little starting up. have you noticed any difference with the laptop?

little=little slow

@carlw I was used to the i7 Quad in the MacBook, so going to dual was actually pretty noticable. Even scrolling some web sites was sluggish. This one feels pretty nice, about the same speed as the MacBook I think. My home office computer is a 6 core monster with 20MB L2 cache, so if the difference is too big I'll go crazy! hehe

The keyboard on this one is also much nicer than the Yoga. The row of buttons to the right of enter was really in the way, and the arrow keys were too small IMO.

I'm working on the SmartListCell, and I want it to be able to instantiate a Fragment. I have that part down, but it would be nice if the Fragment could be aware of a value being passed to it. I don't know if we should go this route but I'ld like to explore it a little.

We have managed to stay away from typing View and Fragment, and I want to keep it that way. I'll make sure that onDock is called for the Fragment, so it could easily get to it's parent cell/item, but that might be too decoupled to feel useful.

It has another nice feature though. You can override

fun updateItem(item: Item)

- a version of updateItem where you don't need to check if item is != null or empty == true. It will only be called if there is an actual value, and in any other case, text and graphic is automatically set to null.

Maybe it's not worth it... (typed Fragment)

i'm with you on the yoga keyboard...about the only thing worse is the surface's

i like the 60% mechanicals for laptops too

Yeah.. I actually found an MSI "laptop" with a 18,4" screen and real mechanical keyboard, but it was craaazy expensive!

Before that I tried the new Dell XPS 15", but it had similar issues with the trackpad. The keyboard was decent, but this one is way better.

yeahh well for 1500 euro starting price it better have

I never understood the whole mechanical keyboard stuff

It's just nice.. Hard to explain.

my favourite keyboard is the mac extended

That's a good keyboard. I was quite fond of the laptop version as well. I used the same on my iMac.

I'm playing with a small class called

ItemFragment

which is an extension of the default Fragment. It can be very useful for supporting Cells in data driven components. I don't know if this will pan out as a good idea, but it's worth exploring.

@User uploaded a file: Untitled

That's all that is needed really. I'm trying to create specialized support for this in ListView now.

could you hook this up to a ListCell with Kotlin delegation? updateItem() looks very familiar

i saw the properties delegation and was wondering if there was something like that for functions

@carlw I don't understand exactly what you mean, but the way I use it right now is like this:

@User uploaded a file: Untitled

looks good. It seemed similar to javafx.scene.control.Cell was wondering about interop...using ItemFragment outside of the builder