Is WinRT Pivot control dynamic binding possible? - windows-runtime

As the question says, can we bind items dynamically to a pivot control in WinRT? i.e. instead of static pivot items, I have varying number of pivot items. We could do this in WP 7.5/8. I want to port my app to WinRT and stuck with this. I can't find any example on the net. So any help is greatly appreciated.
Also, can we do it in WinJS?

I am currently doing that in WinJS using KnockoutJS, basically doing the bindings inside the WinJS control for each hub item.
Here's a nice walkthrough of the pivot on WinJS.
http://msdn.microsoft.com/en-us/library/windows/apps/dn615002.aspx

Related

What's the difference between using widget and owl to develop a frontend element in odoo?

I want to develop a search panel for my module. And odoo provides me with two ways. Which one should I choose? Is there anything I should notice?

Partial viewmodel in Prism

I'm trying out Prism for WP 8.1 Runtime (Microsoft.Practices.Prism.Mvvm.Store). Is there any way to implement partial viewmodel? For example, I would like to implement different VM for each item in Pivot control.
P.S. This can be done in Caliburn.Micro using Conductor class.
Well you could do Lazy/AsnycLazy where T is your sub-viewmodel. Then just bind the selected page, and load the subVMs when required. Currently PRISM doesn't offer any built-in solutions for this.

Custom controls in WP8

i would like to know if it's possible to define a new user control on the basis of the pre-defined ones in WP8. For example, if i wished to define a custom Application Bar (like the one in the Windows Phone Store) starting from the standard one, or a custom Context Menu, would it be possible?
Thanks
The simple answer is "yes." For instance, a vast majority of the controls in the Windows Phone Toolkit are derived from their base-level analogs, such as the most obvious example of PhoneTextBox.
Regarding ApplicationBar specifically, you will note the class is sealed and cannot be inherited, but you can create predefined templates in XAML for application bar configurations you wish to reuse. As a custom control, that specific construct does not make sense as it is a baked-in OS element. Instead, depending on your use case, it may be better to completely disable the ApplicationBar and create an entirely new control that implements the custom functionality you desire.
The controls are skinned using a convention in Windows Phone development by generating a Generic.xaml file in the Themes folder that is compiled as a library resource. One such example can be found at the link inside the Windows Phone Toolkit's WP8 library.

Creation of BitmapSource objects no longer possible in WinRT apps?

BitmapSource does not have the Create method in the .NET API for Windows Store apps. I assume dynamically creating images is no longer possible (if so, why?). Or does anyone know how to create images programmatically in a Windows Store app?
See http://winrtxamltoolkit.codeplex.com/ and the Imaging extensions.
WriteableBitmap is the answer. It has a constructor that takes with and height and allows writing to it and updating.

Best Practice for Developing Core Functions in Symfony2?

I am an experienced Symfony user and have started using Symfony2 and absolutely love it. A big thank you to Fabien and the guys over at Sensio.
I am pretty much there now in terms of developing in Symfony2 thanks to the documentation available, but there is one area in particular that I am still not 100% sure on.
I have a number of core functions that I want to use in different areas of the application and just want to know what the best practice for this is?
I am currently creating a bundle that has a number of functions in that handles the processing of images.
Is this the best way to do this and if so how do I then use or include these functions across other bundles?
You could just import the classes you want to use from your image handler bundle, but the way I would go about it is to register one or more services (like an image manager or thumbnail generator or whatnot) from your bundle so that the functionality you are creating will be available through the DIC for the entire application to use.