Is it possible to extend just picker builder to implement custom UI?

[VladanRandjelovic]

Is It possible to extend just picker builder and use existing picker just with custom UI, if possible i would not use Navigator and routing in my UI...

Thank You in advance

[AlexV525]

I've reconsidered the part of overriding the delegate, maybe there can be a singleton or a static member for AssetPicker like AssetPicker.delegate for a permanently override:

class AssetPicker<A, P> {
  //...
  static AssetPickerBuilderDelegate? delegate;
}

Or we can split methods into two pick methods:

• AssetPicker.pickAsset(...)
• AssetPicker.pickAssetWithDelegate(...)

@VladanRandjelovic Would this implementation fit with your case?

/cc @yanivshaked

[VladanRandjelovic]

I think second one would be great, so we could actually do just the custom builder delegate and use pick method as it is (and just pass the delegate), which btw I think is great. And one more thing, thanks for the quick response mate, keep up the good work!

[AlexV525]

This will be updated with #108 if possible.

[VladanRandjelovic]

Cool. Thanks again!

[AlexV525]

It's been release with 6.0.0-dev.1 version.

[VladanRandjelovic]

cool thanks mate! :)

[yanivshaked]

Use 6.0.0-dev.2 and above (it contains a fix related to this feature)

[VladanRandjelovic]

it's still a must to use Navigator push, or the navigator is only used for pushing the data to the UI? I'm not sure i got that part right

[AlexV525]

Is It possible to extend just picker builder and use existing picker just with custom UI

Previously you asked about minimized delegate extends and usage, so I guess new changes are perfect for this request.

if possible i would not use Navigator and routing in my UI

Internal navigator usage is required and not exempt for that.

[VladanRandjelovic]

ok, now it's much clearer, thanks again mate.