Forwards

DropShadow and "glow" on WP7

2012-01-27T12:26:00.001Z

Doing background glow on WP7...

Proper blog post to follow

But in the meantime, the app is: http://www.windowsphone.com/en-US/apps/9ea0ba3d-7d73-4325-9d5c-a9aca3802ad2

And the source is... to follow... soon....

MonoCross - a different kind of WP7 project approach

2011-11-19T14:21:00.001Z

Just thought I'd drop a note about MonoCross. The first Wp7 code was only made available this week and so I've only had a few days to play with it. So far I'm finding it fascinating as an alternative way of thinking about how to construct an app.

I know not everyone is doing multiplatform... and I'm already finding that MonoCross gets in the way of some MVVM and data binding stuff, but I'm also finding that there are some very interesting parts to the way MX approaches development - in particular:

MX splits the Model and Controller out into one class library, then puts the Views into the app project
MX Views are ultimately PhoneApplicationPage's but you inherit via an MXView<TModel> class - it's quite nice that this means you always get a Model to use
The navigation framework intercepts the calls to "routes" like "{Controller}/{Action}/{Id}" - so you no longer have to navigate to urls like "Views/EditThing.xaml?ThingId=12" and the navigation framework also takes care of the Model creation/selection for you.

There's plenty of "rough parts" in there - plenty that will get done differently in the future (e.g. there are static class and static member variables everywhere - Mx desparately needs an injection of IoC) and I'm not sure how blendable this approach is - but overall it's very interesting to see an application structured differently - something other than yet another Mvvm platform.

If you're interested, check it out on http://bit.ly/smT0Di

Stuart

P.S. Just in case you were wondering - I've nothing to do with the MX project - it's got some sort of book publisher behind it. I'm just one of the first 1.0 users (I think!)

If you want to see the code for the MonoCross monodroid tab example

2011-11-16T06:39:00.001Z

Head over to https://github.com/slodge/monocross-tab-activity-view

Using MXTabActivityView in MonoCross (MonoDroid flavour)

2011-11-15T20:31:00.001Z

1. In your application project, add your model - this model will be *shared* by all views within the tabs, plus also shared by the parent tabview itself:

public class FirstModel

{

public List<string> Items1 { get; set; }

public List<string> Items2 { get; set; }

public FirstModel()

{

Items1 = new List<string>()

{

"one",

"two",

"three"

};

Items2 = new List<string>()

{

"hello",

"world",

"monocross"

};

}

2. Again in your application project, add your controller:

public class FirstController : MXController<FirstModel>

{

public override string Load(Dictionary<string, string> parameters)

{

Model = new FirstModel();

return ViewPerspective.Default;

}

3. Finally in the application project, make sure you have a route setup for the controller - e.g. a default route like:

NavigationMap.Add("", new Controllers.FirstController());

4. In your Android container, add the activity views which will sit inside the tabs - e.g.:

[Activity(Label = "First View!")]

public class FirstView : MXListActivityView<FirstModel>

{

public override void Render()

{

ListView.Adapter = new ArrayAdapter<string>(this, Android.Resource.Layout.SimpleListItem1, Model.Items1.OrderBy(x => x).ToList() );

}

and:

[Activity(Label = "Second View!")]

public class SecondView : MXListActivityView<FirstModel>

{

public override void Render()

{

ListView.Adapter = new ArrayAdapter<string>(this, Android.Resource.Layout.SimpleListItem1, Model.Items2 );

}

5. In your Android container project, set up your tab activity view - this is a bit like http://docs.xamarin.com/android/tutorials/User_Interface/tab_layout

Set up the xml resource - e.g.:

<?xml version="1.0" encoding="utf-8"?>

<TabHost xmlns:android="http://schemas.android.com/apk/res/android"

android:id="@android:id/tabhost"

android:layout_width="fill_parent"

android:layout_height="fill_parent">

<LinearLayout

android:orientation="vertical"

android:layout_width="fill_parent"

android:layout_height="fill_parent"

android:padding="5dp">

<TabWidget

android:id="@android:id/tabs"

android:layout_width="fill_parent"

android:layout_height="wrap_content"/>

<FrameLayout

android:id="@android:id/tabcontent"

android:layout_width="fill_parent"

android:layout_height="fill_parent"

android:padding="5dp">

</FrameLayout>

</LinearLayout>

</TabHost>

Also, add the tab icons if you want them (see notes in http://docs.xamarin.com/android/tutorials/User_Interface/tab_layout)

Then for the MXTabActivityView:

[Activity(Label = "A TabView!")]

public class TabView : MXTabActivityView<FirstModel>

{

protected override void OnCreate(Bundle bundle)

{

base.OnCreate(bundle);

SetContentView(Resource.Layout.TabHost);

TabHost.TabSpec spec; // Resusable TabSpec for each tab

Intent intent; // Reusable Intent for each tab

// Create an Intent to launch an Activity for the tab (to be reused)

intent = new Intent(this, typeof(FirstView));

intent.AddFlags(ActivityFlags.NewTask);

// Initialize a TabSpec for each tab and add it to the TabHost

spec = TabHost.NewTabSpec("first");

spec.SetIndicator("First", Resources.GetDrawable(Resource.Drawable.ic_tab_artists));

spec.SetContent(intent);

TabHost.AddTab(spec);

intent = new Intent(this, typeof(SecondView));

intent.AddFlags(ActivityFlags.NewTask);

spec = TabHost.NewTabSpec("second");

spec.SetIndicator("Second", Resources.GetDrawable(Resource.Drawable.ic_tab_artists));

spec.SetContent(intent);

TabHost.AddTab(spec);

}

public override void Render()

{

// nothing to do here currently!

}

6. That's it! run and enjoy :)

Storage scopes cannot be created when _AppStart is executing.

2011-11-09T08:01:00.001Z

If you see this error when running ASP.Net MVC apps:

Storage scopes cannot be created when _AppStart is executing.

Then don't panic - it seems this is just a Cassini problem - if you switch across to IIS express or to a real IIS server then the problem doesn't exist

(phew)