After upgrading to design support library 28.0.0-alpha1 as part of the Android P preview and updating my base app theme to extend from Theme.MaterialComponents.Light.DarkActionBar according to the documentation at https://github.com/material-components/material-components-android/blob/master/docs/getting-started.md all my textfields now show the filled version as show below.
Is there a way to change to the outlined version using the design support library instead of having to refactor to android.x and switching to using the new material components?
Yes, you can do that using support design library in your gradle
Add this line:
implementation 'com.android.support:design:28.0.0-alpha1'
Note: You should not use the com.android.support and com.google.android.material dependencies in your app at the same time.
Use com.android.support or androidx
You may get render error then add this line in style AppTheme
<item name="cardViewStyle">#style/CardView.Light</item>
you can refer this link readme
Related
Recently, I can't publish my new app to App Store due to the following error:
ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no
longer accepted. Instead, use WKWebView for improved security and
reliability. Learn more
(https://developer.apple.com/documentation/uikit/uiwebview).
Question 1, what is UIWebView and WkWebView? I can't even find a single word "UIWebView" in my project, how Apple knows I'm using it? The pages that I used are all xamarin based and Content Page only. You may refer to the code below in my xaml file.
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" >
<StackLayout>
</StackLayout>
</ContentPage>
That's it, no keyword "UIWebView".
Question 2, how to I set my entire project to WkWebView? I can't find any option in the settings page.
I've tried adding "--optimize=experimental-xforms-product-type" to Additional mtouch arguments in the iOS Build but no effect at all. Is there any other way? I just want to publish my app...
This seems an existing issue of Xamarin.forms on iOS .
Make sure that the version Xamarin.Forms is 4.7 or higher and Xamarin.iOS is 13.10.0.17 or higher.
Change the Linker Behavior to SDK Only or Link All and then add the
additional arguments: --optimize=experimental-xforms-product-type
Please check all of these have been set under the release
configuration and iPhone platform.
For more details you could refer
https://devblogs.microsoft.com/xamarin/uiwebview-deprecation-xamarin-forms/
I am using BottomNavigationView in my project and my application is not suposed to support pre-Lollipop devices, so I didn't use the large appcompat library.But when I run my application it told me "The style on this component requires your app theme to be Theme.AppCompat (or a descendant)."
So I want to know how can I get rid of Appcompat stuff and using Material components?
According to the Get Started instructions, using either AppCompatActivity or AppCompatDelegate is required.
Is there an easy way to modify an application that has been built using bootstrap4xpages so it now uses that same code that has become part of the extension Library? This would allow the application to get the updates as I guess the bootstrap4xpages plugin won'T be updated anymore.
Thanks :)
If the application uses the Select2 control, you'll still need both in the xsp.properties. That's because there are licensing issues that prevented the Select2 control being included in Extension Library plugin.
Otherwise, as Per says, you can just remove the org.openntf.xsp.bootstrap.library reference from the xsp.properties.
What are the steps required to make the two items available in the Add Portable Class Library dialog?
Please see my answer in Creating a PCL that targets Monodroid
In the meantime, there are quite a few blog posts around on how to get PCLs working unofficially - eg.:
http://blogs.endjin.com/2013/05/xamarin-platform-setup-gotchas/
http://slodge.blogspot.co.uk/2013/04/my-current-pcl-setup-in-visual-studio.html
There is an Eclipse plugin, that defines Node perspective in plugin.xml file.
I'd like to add default View to this perspective, that is implemented by Markdown Editor.
Namely Markdown HTML preview.
Will Eclipse behave nicely if user don't install Markdown plugin, that will be referenced?
I would also like to add Eclipse standard Error Log (for user to see if an error happened).
Update:
What do you mean by "add default view to this perspective?" You wish to modify the source code to add this view to the Node perspective? Or you wish to add a plugin that will add this view to the perspective using a perspective extension?
To log, you should use the StatusManager. See http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fworkbench_statushandling.htm for how to use this properly.