onebusaway / onebusaway-windows-phone Goto Github PK

In OBA iPhone and Android, there is an advanced setting were a user can change the server API URL. This has proven very useful in testing the apps with early versions of servers before they are ready for production and before they are added to the Regions API.

We'd like to include a similar API URL setting in this app.

The user input for Android and iPhone is in the form of:
api.tampa.onebusaway.org

...and the /api/xxxx is automatically appended to the URL.

As discussed on the OBA dev list, we'd like to support experimental regions in the OBA apps.

Per additional discussion here, we're going to leave the current Regions API (http://regions.onebusaway.org/regions.json) as a legacy API to be used by apps that haven't yet been updated to filter out experimental regions by default.

Therefore, when the app is updated to handle experimental regions, it should use the new Regions API v3 URL, which will contain experimental regions (http://regions.onebusaway.org/regions-v3.json). This also means that we can proceed with deploying an updated app that supports experimental regions without waiting for the other apps to be updated.

So, this would involve:

1. Consuming a new experimental boolean value for each region from the Regions API v3
2. Only use regions with experimental set to false AND active set to true, by default
3. Allowing the user to opt-in to including experimental regions (i.e., experimental set to true) for manual or automatic selection, via a preference

If the user chooses to enabled this option, a message is displayed " Experimental regions may be unstable and without real-time info. Go ahead?". If the user selects "Yes", then regions with experimental set to true AND active set to true are used in the app for both manual and automatic region selection. If the user deselects "Enabled experimental regions", or cancels out of the enabling dialog, then all regions with "experimental" set to true are again removed from consideration in the app (i.e., same as default setting). Note that if the user currently has an experimental region selected, then we should warn them that their current region will no longer be available if they deselect experimental regions.

I would suggest viewing the current Android experience on an actual device, if possible. Below is the experience on Android in screenshots, for visual illustration.

Default preferences screen:

User checks the "Experimental regions" box and sees this dialog:

If the user has an experimental region selected, and they try to deselect the "Experimental regions" preference, they will see the following dialog:

The "About" screen shows the URL of the Codeplex site. It should be updated to the new Github URL:
https://github.com/OneBusAway/onebusaway-windows-phone

Per the multi-region design, the main “Contact Us” email that is in-app should be changed to the contactEmail field from the Regions API (based on whatever region is currently selected).

We want to direct the majority of in-app feedback to the region (since feedback tends to be data or agency-related), and then they can forward the app-specific feedback to the main app developer email.

If there is a specific "Contact the developer" email listed somewhere, this email address should be changed to [email protected].

Reported by @mbraude (cc @Sinorm), as a result of c5f8864.

Compilation error is:

No XAML was found at the location '/MainPage.xaml'.

Below is email exchange reporting the issue.

From: Michael Braude
Sent: Saturday, November 02, 2013 11:42 PM
To: Rob Smith
Cc: Barbeau, Sean
Subject: Re: Cleaning up transition for OBA WP from TFS to Github

Yeah, VS 2013 only seems to support WP8, so when I converted the project I think it retargeted to WP8. I suppose we could leave it as a VS 2012 project, but I don’t know if that makes much sense. Anyways, I never do side by side VS installs so I only have 2013 on my machine right now

From: Rob Smith
Sent: ‎Saturday‎, ‎November‎ ‎2‎, ‎2013 ‎8‎:‎21‎ ‎PM
To: Michael Braude
Cc: Sean Barbeau

Did you upgrade the project to Windows Phone 8? I recall seeing this error a long time ago when I tried to upgrade the project and never got around to root-causing it. Let me try to talk to some folks internally, my guess is that something is weird with how the project is setup as we started this with a super earlier version of the WP7 dev kit long before it was ever released.

Rob

Hey Sean,

I synced, rebuilt and updated the project to VS 2013. But the app won’t run, and I don’t know why. Maybe Rob can help….I get this very strange error on launch:

No XAML was found at the location '/MainPage.xaml'.

I have no idea how that can be….I think it has something to do with Microsoft.Phone.Toolkit. I grabbed the latest off of NuGet but it still doesn’t work.

No idea what’s going on. I’ll push what I have up to the depot so somebody else might be able to figure it out.

Mike