[Setup] update doc and changelog for 0.0.7

Author: fuzzagrosner

CHANGELOG.md

@@ -1,3 +1,34 @@
+## [0.0.7] - 1/2/2018
+
+NEW - Upgrade to Flutter 1.1.4
+
+NEW - all widgets are now marked private imports, meaning switch imports from:
+```dart
+import 'package:platty/widgets/alert.dart';
+import 'package:platty/widgets/button.dart';
+```
+
+to:
+```dart
+import 'package:platty/platty.dart';
+```
+
+This will clean up the imports and make it easier to use the library.
+
+NEW - Library now utilizes new `CupertinoTheme` and `MaterialBasedCupertinoThemeData` to bridge styling gap between widgets finally.
+
+`androidTheme` -> `unifiedTheme` and no longer a function. The app will utilize the material theme and properly bridge it to 
+Cupertino world.
+
+`buttonColor` for `Theme` is now reflected in `PButton` iOS as well.
+
+`bottomAppBarColor` for `Theme` now actually works with android and iOS `PTabBar`. 
+
+`caption` from `TextTheme` used in `Theme` now propagates to `PTabBar` as the inactive color on iOS and Android, to match behavior expected.
+
+`iconColor` for a `PNavBar` utilizes the `IconTheme` if no `iconColor` specified. Defaults to `CupertinoColors.ActiveBlue` if all missing.
+
+
 ## [0.0.6] - 12/29/2018
 
 Fixes issue where `PSliverNavigationBar` on iOS, when specifying title and `iosLargeTitle`, displays both a `middle`

README.md

@@ -15,25 +15,25 @@ Want to use bottom tabs in your app that resolve to platform specific UI? No pro
 
 List of Widget Files:
 
-[Alerts](/lib/widgets/alert.dart)
+[Alerts](/lib/src/widgets/alert.dart)
 
-[Back Button](/lib/widgets/back_button.dart)
+[Back Button](/lib/src/widgets/back_button.dart)
 
-[Buttons](/lib/widgets/button.dart)
+[Buttons](/lib/src/widgets/button.dart)
 
-[Navigation Bars](/lib/widgets/navigation_bar.dart)
+[Navigation Bars](/lib/src/widgets/navigation_bar.dart)
 
-[Progress](/lib/widgets/progress.dart)
+[Progress](/lib/src/widgets/progress.dart)
 
-[Routing](/lib/widgets/routing.dart)
+[Routing](/lib/src/widgets/routing.dart)
 
-[Scaffold](/lib/widgets/scaffold.dart)
+[Scaffold](/lib/src/widgets/scaffold.dart)
 
-[Slider](/lib/widgets/slider.dart)
+[Slider](/lib/src/widgets/slider.dart)
 
-[Switch](/lib/widgets/switches.dart)
+[Switch](/lib/src/widgets/switches.dart)
 
-[TabView](/lib/widgets/tabs.dart)
+[TabView](/lib/src/widgets/tabs.dart)
 
 
 ## Getting Started
@@ -54,10 +54,8 @@ class MyApp extends StatelessWidget {
   Widget build(BuildContext context) {
     return PlatformApp(
       title: 'Flutter Demo',
-      
-      // specify Android Material Theme data here. it's a lazy evaluated function, only rendering if platform is Android.
-      androidTheme: () => ThemeData(
-            
+      // specify our app theme here. We do the leg work of bridging it to Cupertino.
+      unifiedTheme: ThemeData(
             primarySwatch: Colors.lightBlue,
             bottomAppBarColor: Colors.red,
           ),
@@ -68,14 +66,8 @@ class MyApp extends StatelessWidget {
 
 ```
 
-`PlatformApp` unifies all of the same properties between `MaterialApp` and `CupertinoApp` to allow you to choose.
-
-_NOTE_: Not specifying a `renderPlatform` will render a `CupertinoApp` on `iOS`, and might cause issues with widgets that expect 
-a material app instance. 
-
-_NOTE_: There is not a `CupertinoTheme` just yet in Flutter. Check out this [pull request](https://github.com/flutter/flutter/pull/23759) . 
-once that is in the main flutter releases, we can then create `PTheme` that merges `MaterialTheme` and `CupertinoTheme` 
-instances. For now it is highly recommended to specify `targetPlatform: TargetPlatform.android` in the constructor of `PlatformApp`. 
+`PlatformApp` unifies all of the same properties between `MaterialApp` and `CupertinoApp` to allow both instances of widgets in the hiearchy and 
+switching styling based on platform.
 
 Now you replace widgets that are included in this library with their "P" counterparts:
 
@@ -101,13 +93,17 @@ Now you replace widgets that are included in this library with their "P" counter
 
 `AlertDialog`/`CupertinoAlertDialog` -> `PAlertDialog`
 
+### Properties Specific to a platform have a prefix
 Any widgets that have ios-only or android-only counterparts, they are prefixed to `android`/`ios` accordingly:
 
 For example `PButton`, `androidShape` applies to `RaisedButton.shape` property. It does not exist on a `CupertinoButton`. 
 However `CupertinoButton` has a `borderRadius` and `pressedOpacity`. Those two props become `iosBorderRadius` and `iosPressedOpacity`.
 
 ## Helpers
 
+This library bundles a few standard functions to easily return code that is unique for each platform. Instead of checking  
+and switching on the result of `Theme.of(context).targetPlatform`, utilize the following methods:
+
 ### Specific Platform Instance
 
 To have a specific `P`-Widget utilize a specific platform theme only, such as Material or Cupertino, you can wrap
@@ -226,4 +222,4 @@ Column(
   ],
 ),
 
-```
+```

pubspec.yaml

@@ -1,6 +1,6 @@
 name: platty
 description: Platform Conforming Widgets for Flutter!
-version: 0.0.6
+version: 0.0.7
 author: Andrew Grosner <andrew@fuzzproductions.com>
 homepage: https://github.com/fuzz-productions/platty