Hi, I try convert value to byte size to Gb and set to TextWidget in UnitItem. But in block text = data.map { ... } I get an error. And I don't understand how add in this block value + "String" like text = data.map { it.total.desc() + "Gb" as StringDesc() } Always return Error. In Android I use android.text.format.Formatter.formatShortFileSize and all works.

Value("total" in Kb):

My List:

My fun TableUnits:

Class unit items where I create TextWidget:

Convert fun to Mb/Gb:

Hi, I run pod install but console show Failure: Build failed But Pod installation is complete!

And them Xcode show build failed too:

How I fix it?

How fix it?

Android:

iOS:

Constraint Item:

Constraint:

And one more question why button style in iOS another? How fix it too? Left iOS, right Android:

Style Cancel button:

Style Save button:

Hi, I try add MutableLiveData use Database, but I don't understand how.

My List in database:

Database class:

My old MutableLiveData in ViewModelClass:

UnitItem class:

And use in ListWidget:

I updated my project based on the recent commit of moko-widgets-template, so using 0.1.0-dev-18 now. And my code previously working with -dev12 throws an exception on Android run now.

E/AndroidRuntime: FATAL EXCEPTION: main
    Process: org.example.app.debug, PID: 18128
    dev.icerock.moko.widgets.utils.AndroidIdConflictException: id 0x7F081AB9 already used by org.example.mpp.MainScreen$createInput$1$2, it conflict with org.example.mpp.MainScreen$createInput$1$2
        at dev.icerock.moko.widgets.utils.IdExtKt.getAndroidId(IdExt.kt:45)
...

I stripped down the test case to minimum for reproducing the error:

• use the current moko-widgets-template
• replace MainScreen.kt with:

/*
 * Copyright 2019 IceRock MAG Inc. Use of this source code is governed by the Apache 2.0 license.
 */

package org.example.mpp

import dev.icerock.moko.fields.FormField
import dev.icerock.moko.fields.liveBlock
import dev.icerock.moko.resources.desc.StringDesc
import dev.icerock.moko.resources.desc.desc
import dev.icerock.moko.widgets.*
import dev.icerock.moko.widgets.core.Theme
import dev.icerock.moko.widgets.core.Widget
import dev.icerock.moko.widgets.screen.Args
import dev.icerock.moko.widgets.screen.WidgetScreen
import dev.icerock.moko.widgets.style.view.SizeSpec
import dev.icerock.moko.widgets.style.view.WidgetSize
import org.example.library.MR

class MainScreen(
    private val theme: Theme
) : WidgetScreen<Args.Empty>() {

    private fun createInput() : Widget<*>{
        return with(theme) {
            input(
                size = WidgetSize.WrapContent,
                label = const(MR.strings.hello_world.desc() as StringDesc),
                field = FormField(initialValue = "", validation = liveBlock { null }),
                id = object : InputWidget.Id {}
            )
        }
    }

    override fun createContentWidget() = with(theme) {
        constraint(size = WidgetSize.AsParent) {
            val scroll = +scroll(
                size = WidgetSize.Const(SizeSpec.MatchConstraint, SizeSpec.MatchConstraint),
                id = object : ScrollWidget.Id {},
                child = linear(
                    size = WidgetSize.Const(SizeSpec.AsParent, SizeSpec.WrapContent)
                ) {
                    +createInput()
                    +createInput()
                    +createInput()
                })

            constraints {
                scroll.topToTop(root.safeArea)
                scroll.leftRightToLeftRight(root.safeArea)
                scroll.bottomToBottom(root.safeArea)
            }
        }
    }
}

• run in Android emulator

The input fields are generated dynamically, the id of the returned input field is a new object, but it seems that the moko-widgets lib thinks it's the same. Or is the code just wrong and it's not the right way to do it?

Hi, how I can check value in override fun createWidget like if/else or something like that and select one or another image.

I use List Widget and Table Units:

My ListWidget:

Fun Table Units:

My class Unit Items where I make image:

Result:

min. requirements:

background (bg color), text customisation (size, color) left icon customisation (margin, resource) right icon support and customisation (margin, resource)

maybe immediately add customisation status bar? (light/dark + bg color and opacity)

For now Screen have property parentScreen to communicate between screens in navigation. It's done this way because android side can't pass lambda/interface to another screen - Screen is Fragment on android, and can be recreated on orientation change or application restart.

Current version of navigation:

class RootNavigationScreen(
    screenFactory: ScreenFactory
) : NavigationScreen(screenFactory), SplashScreen.Parent {
    override val rootScreen = SplashScreen::class.rootNavigationScreen()

    override fun routeToMainScreen() {
        setScreen(MainScreen::class)
    }
}

class SplashScreen(
    private val theme: Theme
) : WidgetScreen<Args.Empty>(), SplashViewModel.EventsListener, NavigationItem {

    override val navigationBar: NavigationBar = NavigationBar.None

    override fun createContentWidget(): Widget<WidgetSize.Const<SizeSpec.AsParent, SizeSpec.AsParent>> {
        val viewModel = getViewModel {
            SplashViewModel(createEventsDispatcher())
        }
        viewModel.eventsDispatcher.listen(this, this)

        // some widget here
    }

    override fun routeToMain() {
        getParentScreen<Parent>().routeToMainScreen()
    }

    interface Parent {
        fun routeToMainScreen()
    }
}

class SplashViewModel(
    override val eventsDispatcher: EventsDispatcher<EventsListener>,
) : ViewModel(), EventsDispatcherOwner<SplashViewModel.EventsListener> {

    init() {
        viewModelScope.launch {
            delay(1000)
            eventsDispatcher.dispatchEvent { routeToMain() }
        }
    }

    interface EventsListener {
        fun routeToMain()
    }
}

here we should declare navigation event multiple times - first in EventsListener of SplashViewModel (it's source of event), next in Parent interface of SplashScreen - it's will be called when ViewModel call own routeToMain. and routing implemented in RootNavigationScreen.

new version of navigation should:

• allow use same screen in different navigations containers (for example UserScreen as tab in BottomNavigation and as independent screen in nested navigation when open different user profile;
• not require duplication of interfaces (remove Parent interface and child-parent communication);
• have compile-time typecheck - compilation should failed if we try show SplashScreen from RootNavigationScreen which can't recognize navigation events of SplashScreen;
• allow use deep navigation - BottomNavigationScreen => NavigationScreen => PostScreen should can navigate to other tab of BottomNavigationScreen.

Hi, I generate iOS app and ListWidget dont show items. In Android all works I dond understand why.

My ListWidget:

TableUnits:

UnitItem class:

Value in Xcode:

Result iOS:

Android:

And round button on iOS is strange =)

Now android id set from hashcode of Id object class name and android can't recognize part. As result we see:

java.lang.ClassCastException: android.widget.TextView$SavedState cannot be cast to android.widget.ScrollView$SavedState

and invalid constraintlayout work:

How implement item list click listener? I create list on widgets like codelabs(MOKO Widgets #7 - lists on widgets), all works, but i dont understand how add listener from item click.

My code: My ViewModel:

UnitItem:

maintaining Kotlin version of iOS UI code is painful (rebuild kotlin framework is long, full debugging still unsupported). We should migrate to Swift version of ios WidgetFactories to boost changes of ios side ui code.

Will create swift cocoapod and this pod will be used from kotlin side

now in some ui code used displayLink for valid update view properties. it's very bad for perfomance and i think it create some memory leaks, so we should remove usage of it

Hi,

this is draft of support for custom fonts in TextStyle. My main concern now is about how to ( or even should we ) support custom font with and ** fontStyle** at the same time. Basically we can include different types of fonts with only one text style, or with multiple font styles. I think that currently there is no even easy way to do it on any of the platforms. We can use typeface on android and symbolicTraits on iOS and add some fallbacks to default font. But personally it think that (at least for now) we should skip fontStyle when custom font is set. Main reasons for that:

• mocko-resources requires adding font files with single fontstyle
• combining both properties will add additional complexity
• in most cases developers will add/set custom font with given font style directly ( not by combining both properties)

What do you think ?

I will continue my work, when there will be decision which path should we follow.

How disable scroll from ListWidget inside Scroll Code: scroll( id = Ids.RootScroll, size = AsParent, child = linear( id = Ids.RootLinearId, size = WidthAsParentHeightWrapContent ) { ... }

My ListWidget inside Constraint:

I try change Size from List but scroll is enabled too.

Server Status Block:

1)How implement push notification on common code? Or I use only native android/ios code? How about MOKO-Notifications? =) 2) What database can I use in common code? And SQL Database implement MOKO in future?