ADWLauncher EX 188.8.131.52
One or two weeks ago, some devices started to get Android 3.2 update…. and suddenly ADWEX ADWSettings menu stopped working….
As the summer is here and my job granted us some free time in the hot afternoons, I took the opportunity to make sohme other changes in addition to the 3.2 fix. Read next:
- Fix the incompatibility found within ADWSettings against android 3.2 (I still don’t know how, but it fixed while messing the xmls :P)
- In Android 3.x tablets, the top Actionbar now displays a customizable shirtcut to the left instead the ugly app icon. It’s set to “open app drawer” by default, but you can modify it by longpressing it and pressing “Edit” in the popup, like any other icon :)
- In Android 3.x tablets, the top Actionbar displays also a few menu items to the right (in the order set up by you with ADWSettings/General Behavior/System Preferences/Customize menu), because a lot of people wanted to get rid of the “Lock desktop” fixed item there.
- New dockbar (The secondary dockbar, the one you reveal by “swiping up” over the Main Dock) design thanks to @joshuas_79 :
- New option for the dockbar (yes, the secondary one, remember: you can put any number of icons in there, it has scrolling magic) can now be set as “primary“.
- Both docks are now always horizontally placed at the bottom on big screen devices (10″ tablets)
- If you have a folder within the main dock or the dockbar, you can (finally!) drag and drop items inside those folders.
- New “Quick Folder Popup” implementation:
- User folders now display in a horizontally scrollable/paginated icon list (usability/speed improvement IMHO)
- Custom app groups “Launcher Actions” can be set to be show in the same “popup” or in the full app drawer via a new option in the “Edit Shirtcut” screen (see screenshots).
- This popup can be themed (more info below)
- A bunch of other small tweaks and fixes, as usual, but nothing “big”, sorry :(
I’m sharing a few “hints” about how to properly put together some elements of an ADW theme, but hopefully soon, Master @klinster will be able to bring more in depth help to themers out there:
- The new “Quick Folder Popup” can be themed providing three drawables: qa_popup, qa_arrow_up and qa_arrow_down. The original pictures are attached in this post for you to use as reference.
- Make sure you place your drawables in the proper directories, or your theme will look ugly.
- For example, icons:
Icon sizes must respect the android guidelines, this is:
Why is this so important? Because if themes do NOT contain icons with the proper resolution/density, they will look distorted/pixelated/etc. And think about this: if you DON’T put HDPI icons within your theme, your tablet customers are going to be mad at you!
Also, putting a 96×96 icon within drawable-mdpi/drawable-hdpi will only cause the icons to be poorly scaled down to comply the standards…. just an advice.
- And different screen sizes/orientations:
Take for example the dockbar (the secondary one). It needs just one drawable to theme it: dockbar_bg.
- If the app is running in a phone, in protrait mode, this dockbar appears as an horizontal row of icons at the bottom of the screen.
- If the app is running in a phone, in landscape, this dockbar appears as a vertical column of icons at the right side of the screem.
- If the app is running on a tablet device, this dockbar appears as an horizontal row of icons at the bottom of the screen (in both portrait and landscape mode!)
So, for a proper Dockbar theming you should design at least 3 images!
But also, if you want to provide the better looking pictures for teh user, you should provide density dependant drawables in the proper directories!! So this could be something like…
So…. yes, this can be as complex as you may think of, but it ends in showing the properly sized/better quality images. And remember, NinePatch drawables are best to fit this kind of items in a bigger range of screen resolutions!!!
- For example, icons:
I know there are a lot of things to do to provide a better user experience and improve the overall quality of the app, so I apologize in advance for any issue you may find (or have found). I’ll try my best to improve things… I always try.