@tieskedh yes, for single-step operations just using collection operators is leaner. But if you have to do multiple steps like

myList.map { }.filter{ }.flatMap { }

you are going to be much better off using an

asSequence()

call first.

forEach()

does not warrant being counted for a multi-step operation though

I like to think of Sequences as assembly lines, processing items one-at-a-time on a conveyor belt. RxJava/RxKotlin does the same thing but it also pushes events through the operators, not just data.

@edvin my PR accidently has two big changes in it... I thought I referted one part, but it seems not... If this will be a problem, let me know PR created

this must the only kotlin-related library that doesn't start with a K or end with -kotlin simple smile

@Dalinar Yeah sorry, we missed the boat on that one.

@tieskedh It will be allright! Will merge review/tonight 🙂

@dr.fornax The second option "Floating drawers" will expand the drawers over any existing component on the side, instead of pushing it out of the way.

@edvin then please don't change nodes until then, otherwise we get big merge-conflicts...

@tieskedh OK 🙂

An edit to @tieskedh?

@tieskedh It has been arranged 😎

I wonder how many times I've done that.

With my name, never that I know of

I guess the other Thijs knows.. haha 🙂

I'd like to add a "Create" button to the Workspace.

I'm a bit afraid that a

onCreate

callback in

UIComponent

could be misunderstood as having to do with the component life cycle.

It would compliment

onRefresh

,

onSave

,

onDelete

etc.

it does...

onCreateClicked

?

That doesn't really match up well with the others. I'll just add documentation to it.

@edvin We don't have anything for lookup with selectors? and if not, is it something we could do?

@tieskedh Check

select

, I think that's it.

I'm looking at workspace,

lookup(".container") as? HBox)?.apply{...}

How would I rewrite that using selectors? It would be great to have it as something like:

lookup<HBox>{...}

With maybe an addition of

lookup<Hbox?>

where

lookup<Hbox?>

trows an error if HBox is not found

if that matches the rest of of the framework

I push my current refactoring and go to school...

I think it makes more sense to support CssRule as parameter to an extension version of lookup.

Ok, but i have to go now. Will be back this evening, if I don't have to much homework 😉

Huh.. why don't we have a

rowFormat

function for TableView?!