B4A Library AppCompat - Make Material Design apps compatible with older Android versions

Discussion in 'Additional libraries, classes and official updates' started by corwin42, Dec 19, 2014.

  1. corwin42

    corwin42 Expert Licensed User

    This library is a wrapper for the Google AppCompat v7 support library.

    B4A V6.0 or newer is required!
    From V3.52 on B4A V6.80 or newer is required! If you still use B4A < V6.80, use V3.51 of this library.

    The main reason for this library is to make your apps compatible with older Android versions and to use features in old Android versions which were implemented in newer Android releases. One big advantage of this library is that you can bring Material Design to pre Lollipop Android devices.

    Setting up the library
    The library uses the Android Support Repository. Please install it from the Extras Section of the Android SDK Manager. If you upgrade from an earlier release you can deinstall the "Android Support Library" since it is outdated and marked as obsolete in the Android SDK.
    1. First copy the AppCompat.jar, AppCompat.aar and AppCompat.xml files to your additional libraries folder.
    2. Start the Android SDK-Manager and download/update the latest Extras->Android Support Repository. Use at least support repository 36!
    3. In Android SDK-Manager be sure that the "Android SDK Build-tools" 25.x.x is installed! Deinstall all versions prior to version 25! If you leave older versions than 23.0.3 of build tools installed, your compiled app may work on Android 5.0 and above but it will fail on older Android versions like KitKat.
    4. In the B4A IDE in your projects check the AppCompat library on the libraries tab.
    5. Make sure that you reference the latest android.jar in the IDE under the "Tools/Configure Paths" menu. Don't worry. The android.jar is only used for compilation. It does not mean that you can't run your app on lower Android Versions. The Support libraries require to compile against the same API version as the library itself. So for Support library 25.xx which is the current now you should compile with API25 android.jar.
    6. If you are updating from a version older than v3.20 then remove the b4a_appcompat resource folder delivered with older versions of this library.
    To use the AppCompat library your activities MUST extend android.support.v7.app.AppCompatActivity (extending the old android.support.v7.app.ActionBarActivity still works.)

    Code:
    #Extends: android.support.v7.app.AppCompatActivity
    Additionally you MUST use one of the AppCompat themes like Theme.AppCompat. You can set it directly in the manifest editor or create your own theme that has an AppCompat theme as its parent. The easiest way is to set the AppCompat theme in the manifest:

    Code:
    SetApplicationAttribute(android:theme, "@style/Theme.AppCompat")
    If you have upgraded this library from an older version than 3.20 then you have to remove the #AdditionalRes: attribute related to the AppCompat library from your projects. They are not needed anymore.

    Some Tutorials for this library
    Material Design 2 - Using the AppCompat library
    Material Design 3 - Using a ToolBar as ActionBar
    Material Design 4 - Modifyable and advanced Menu

    Troubleshooting Guide
    Because it is not so easy to setup this library I will try to give a troubleshooting guide here for the most common problems.

    1. Compile always with the newest android.jar file. This can be configured in the IDE under "Tools/Configure Paths". Download the latest platform version with the SDK Manager and configure it with the IDE. Don't worry, your app will still run on older platform versions. AppCompat support library needs this only at compile time.

    2. Be sure you have a correct theme file for your project. If the app seems to crash immediately without a stack trace it is most probably a problem with the theme file.

    3. If you post your issue in the forum please provide the stack trace of the error! And before you post, please do a forum seach. Most probably the same error was previously reported by another user. If you don't see a stack trace in the log window, please try the unfiltered logs. Unfortunately most errors only show when you have your device connected via USB in the unfiltered logs.

    4. If you post your issue in the forum please provide as many information as possible. The error you receive, screenshots if possible and most important: the stack trace.

    Version History

    V1.00
    • Object AppCompat - Utilities which are useful for working with AppCompat
    • Object ACActionBar - Like StdActionBar or StdActionBarHelper to control some features of the ActionBar.
    • Object ACEditText - Replacement for EditText with Material Design colors.
    • Object ACCheckBox - Replacement for CheckBox with Material Design colors.
    • Object ACRadioButton - Replacement for RadioButton with Material Design colors.
    • Object ACSwitch - Wrapper for a Switch.
    • Object ACFlatButton - Borderless Button for Dialogs etc.
    V1.10
    • New object ACToolBarLight - Toolbar for light themes
    • New object ACToolBarDark - Toolbar for dark themes
    • New object ACActionMenu - Create action menus (action items and/or overflow menu everywhere in your layout. (The view needs to have a minimum width of 56dip to work properly. This seems to be a bug and hopefully will change in later versions of the AppCompat library)
    • New object ACActionModeWrapper - Change ActionBar/Toolbar to an ActionMode ActionBar. Mostly used for multiselect lists.
    • New object ACMenu - Access and modify the ActionMode, ActionMenu or Toolbar menus.
    • New object ACMenuItem - Access and modify the ActionMode, ActionMenu or Toolbar menu items.
    • New object ACPopupMenu - Implements a popup menu.
    • New object ACSearchView - Add a search view to your ActionBar/Toolbar
    • Add: AppCompat object has new methods for getting height of system components like StatusBar, ActionBar and NavigationBar.
    • Add: AppCompat object has a new method for setting the elevation of every view. With this all views (like Panels) can cast shadows. Unfortunately the shadow is only visible on Android 5.0 or above.
    V2.00
    • #Extends: android.support.v7.app.AppCompatActivity should now be used (ActionBarActivity still works)
    • New object ACSpinner - AppCompat Spinner with additional support to show an icon in front of the text.
    • New object ACSubMenu - Adding Submenus to menus.
    • New Event ACSearchView_QueryChanged
    • Some internal changes (xml files for Views are not needed anymore)
    • Support for tinting Drawables.
    • Possibility to set a click effect to any view - This is experimental. It should add a ripple effect in Lollipop and above and a color change in previous versions.
    • To update from V1.xx to V2.00 delete the b4a_appcompat resource folder and copy the new one from the archive. The old xml files for buttons, edittext etc. are not needed anymore. Now there is only one xml for the spinner needed.
    V3.00
    • Requires B4A 6.0 or above
    • References AppCompat from Maven repository
    • Full designer custom properties support for all views
    • Fix: ACRadioButton now supports grouping in a panel
    • Desupport of the Activity Entry animation.
    • New: ACSeekbar
    • Fix: ACSearchview closed() event does not fire (AppCompat bug). Added workaround for this.
    • Fix: Fixed several minor and major bugs
    • New example App which shows main features
    V3.01

    • Fix: additionally depends on com.android.support:support-v4 which should make it work better if you mix old and new libraries.
    • Fix: ACSearchview_Closed event will not crash on API < 12 but it will not fire on these devices. Sorry, there is no workaround for this.
    V3.20
    • Moved resource files to aar library file - see new setup instructions
    • Fix: ACButton ButtonColor attribute now works on all Android versions.
    V3.30
    • Fix: Remove log output from ACSpinner
    • Fix: Hopefully fixed crashes with missing designer properties
    • Fix: Mixed case Eventnames in Toolbars now working
    • New: Support for ActionViews in MenuItems (Needed for CustomViews in NavigationView of DesignSupport library)
    • Change: Minimum Support Repository 36
    V3.41:
    • Fix: Change packagename to anywheresoftware.b4a.orbjects to reduce resouce fields
    V3.42:
    • Fix: ToolBars should raise their events correctly again.
    V3.50:
    • New: Support for CharSequences wherever possible.
    V3.51
    • Fix: Getters return String instead of CharSequence again to avoid problems.
    V3.52
    • Fix: Compiled against B4A 6.80 Core library to avoid some problems with CharSequences.
    V4.00
    • Change: Compiled against 28.0.0 Support library
    • New: Styles for most Views
     

    Attached Files:

    Last edited by a moderator: Aug 18, 2019 at 11:22 AM
    dbprogramer, Jmu5667, stanks and 56 others like this.
  2. FireDroid

    FireDroid Member Licensed User

    Great!
    This is really useful.
    Thanks for sharing it ;)
     
  3. ZPaul2Fresh8

    ZPaul2Fresh8 Member Licensed User

    Trying to implement this into my existing application, does this conflict with StdActionBar? Because I'm getting FCs ("at anywheresoftware.b4a.objects.StdActionBar.setIcon(StdActionBar.java:227)"

    Thanks in advance.
     
    Last edited: Dec 27, 2014
  4. corwin42

    corwin42 Expert Licensed User

    Yes, you cannot use StdActionBar with AppCompat. You have to use ACActionBar. This is because with AppCompat the way to get a reference to the ActionBar is not compatible with StdActionBar library.
     
    ZPaul2Fresh8 likes this.
  5. woniol

    woniol Active Member Licensed User

  6. DonManfred

    DonManfred Expert Licensed User

    rightclick and copy link
    [​IMG]
    If you use the underlying Link under the #17 in the thread you can directly call this post.
     
    MarcoRome and lemonisdead like this.
  7. corwin42

    corwin42 Expert Licensed User

    Version 1.10 in first post with many new features.
    Tutorials will follow.
     
  8. thedesolatesoul

    thedesolatesoul Expert Licensed User

    Nice!
    What is the difference between ACActionMenu and ACPopupMenu?
     
  9. corwin42

    corwin42 Expert Licensed User

    The ACActionMenu is a complete View you can add to your layout. It can have action items like an ActionBar or just the three dots for an overflow menu. It is the complete "action item part" from the ActionBar including the overflow menu. I think it is useful for creating UIs like the Play Music app where you have 3-dot menus everywhere.
    The ACPopupMenu ist just the popup. You will need an anchor object like a button to display a popup menu with it.
     
    thedesolatesoul likes this.
  10. Peter Simpson

    Peter Simpson Expert Licensed User

    Yes yes yes an update, thank you. I can now update my apps and update them on the play store.

    Actually you deserve 2 pints, cheers again, enjoy :D
     
    DonManfred likes this.
  11. woniol

    woniol Active Member Licensed User

    Hi.
    Will the FAB(FloatingActionButton) be possible with this library?
     
  12. corwin42

    corwin42 Expert Licensed User

    No, I'm working on a separate library for FAB.
     
  13. woniol

    woniol Active Member Licensed User

    Oh,
    that is great news :)
     
  14. woniol

    woniol Active Member Licensed User

    Hi,
    Is it possible to set the ACActionMenu theme to Light or Dark like ACToolBarLight, ACToolBarDark?
     
  15. corwin42

    corwin42 Expert Licensed User

    I haven't tried it now but it should use the App theme.
     
  16. ciarli

    ciarli Member Licensed User

    Hi,
    Is it possible to set NavigationMode to NAVIGATION_MODE_TABS ?
     
  17. corwin42

    corwin42 Expert Licensed User

    No. In AppCompat V21 Navigationmodes are deprecated and no longer supported.
     
  18. ciarli

    ciarli Member Licensed User

    Thanks.
     
  19. nadhiras

    nadhiras Member Licensed User

    Hi Corwin... how to handle spinner on appcompact
    if i place spinner on panel that have white background the arrow of spinner isn't see
     
  20. corwin42

    corwin42 Expert Licensed User

    Are you using a light or dark Theme? It should be ok if you use a light theme.
     
Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice