I am doing the same for View.. breaking up complex views into several views not fragments

@anidotnet - probably because views are singletons and are already constructed

not necessarily, you can still change properties in view..

where we have add(View::class), we need to have lambda to set some properties

@gtnarg probably predates scopes too

so if that view is used in multiple places - it will get updated everywhere?

that's the thing, you should not use view in multiple places

but for single place, we should have ability to set properties.. don't we?

I am not certain about that @anidotnet when used in multiple places I use Fragments, when used in a single place I use a view and I dont need properties as the view will only be used there and does not need extra settings.

@anidotnet That's just an oversight, let's add it 🙂

(that is how I do it, like in wicket)

@ron I wanted to set a view in the controller, so that I can offload some logic from views to controller. if I don't have a lambda, I can't even set that too. And sometimes, I need to change the visibility and managedProperty() of a child view

@edvin I'll add it.

@anidotnet - the controller shouldn't have access to the view (ideally)

@gtnarg ideally yes. View should call controller methods. I wanted to keep my view logic free as much as possible...

I think we don't even need to have separate versions for Fragment and View anymore

yes.. my idea exactly, only UIComponent will do

@edvin I'll send a PR by tonight (IST) 🙂

@anidotnet I think I have it now, hang on.

Running some tests.

okies

I use this website to keep me up-to-date with iOS stuff. They're moving into Kotlin via Android and looking for Kotlin content. I think they're focused on mobile for now, but branching out. They do cover core programming like Swift where the courses just go over language constructs.

@anidotnet Committed a fix 🙂

great

@amanda.hinchman-dominguez uploaded a file:

I ran a local version of the contents for osgi console view, and I was wondering: how can the Activator class be null if it's already in the library (unless it requires an import from the same folder and maybe there's a missing line in OSGISupport.kt), and how essential is bundling for OSGI?

It's not the Activator class that is null, it's the result of the call to

fxBundle

. The

fxBundle

variable is configured to return in instance of

Bundle

, but calling

FrameworkUtil.getBundle()

in your case actually returned null. That means that you're probably not running in an OSGi context perhaps?

perhaps not, I reading through the documentation and making sure all the requirements are in my project now

@amanda.hinchman-dominguez You should have a solid understanding/prior experience with OSGi before you attempt this, or you're just going to pull your hair out 🙂