-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native UI #69
Comments
The direction is to make it more Windows Phone native UI. We already did that for Settings pages using the panorama, we added appbar for frequently used functions and there are still couple of screens not implemented in SL. Keep in mind that in order to wire new SL screen to the existing code you will need to wire it to the C code too which is not trivial task. Take a look at the Settings SL screen for more info. |
Yes, that was my next question. What I have done is just modified some existing screens and replaced some custom styled text fields and buttons with native look/feel buttons/text fields. I was looking to see where I could see an example of how say the settings panorama is linked to bb_waze_code. Any pointers on where to look? Is there an IRC you hang in? |
ok, so it goes like this: First, install Cygwin. Choose devel, python and perl. Syscalls.cs is the actual bridge between the C code and the C#. Check out OnSettingsSaved inside syscalls to learn how to call C from C# (UIWorker.addUIEvent) Essentially the common way to communicate between C and C#, the C code uses NOPH_ function calls. These calls are implemented inside the syscalls.cs. |
I am trying to use Cygwin (noob to it), and the script is not running properly, perhaps a config issue on Cygwin. ./run.sh: line 13: syntax error: unexpected end of file Any idea? On Apr 18, 2012, at 10:45 PM, Meir Tsvi wrote:
|
Please make sure that when you install git / git extensions the settings are "check-out as-is, check-in as-is" |
I have been working on the UI, and an wondering where the direction of this project wants to keep this "custom UI", or to make a more native feel. If so, I will continue to work and submit a pull request. If not, I will re-evaluate my ideas.
The text was updated successfully, but these errors were encountered: