of course, you might want to just pass that data class into your Portal class instead of creating it...

# announcements

[Steve]

of course, you might want to just pass that data class into your Portal class instead of creating it inside the Portal class

[frank]

Thx for the feedback, You say to send it as an argument to my class?

[frank]

it does not convince me

[Nir]

well, the idea is dependency injection

[Nir]

but in this particular example I'm not really sure if it's applicable or not.

[Nir]

I'm not really sure what InputChooseFolder gives you at all, in your example

[frank]

@Nir, it's not applicable in this case. I don't need use implementations or subclass of InputChooseFolder.

[Nir]

I don't actually see why you need InputChooseFolder at all though

[frank]

It is Simple form with multiples inputs: label + input + btn(select folder) and I created a function that returns InputChooseFolder for avoid boilerplate code*.*
Sample:

row {
    inputRoot = inputChooseFolder("Root Path:", "inputRoot")
}
row {
    inputDest = inputChooseFolder("Dest Path:", "inputDest")
}

[Nir]

Okay, if that's the case I'd probably just make InputChooseFolder a private nested class of Portal