I'm looking for free themes to style my private Xamarin.Forms application which has a non commerical purpose. I tried Syncfusion already, but they let me to create a whole new application which I don't like.
I want to look my application a bit nicer than the standard look and feel.
Xamarin.Forms applications can respond to style changes dynamically at runtime by using the DynamicResource markup extension.
For more detail, you can refer to this https://learn.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/theming/theming
Related
I'm looking for a HTML editor to that can be used in a Xamarin Forms Project. I need both an iOS and Android implementation. Another option is to try and shoehorn one of the existing open source projects in to a custom forms control. Anyone have any ideas?
There is the "TEditor": https://github.com/XAM-Consulting/TEditor
Never tried but it does look good (though i dont know if its still in active developement)
I am starting a cross-platform project in Xamarin, and I have some doubts that are me to prevent development. Initially the project is only for android and UWP but in the near future it will be also for iOS.
Questions:
1. I want to centralize all resources (strings for labels like "Name", "Age") in order to be consumed in the 3 platforms and when you have to edit this string, the change is made on all projects. What better way to do this? I need to do DataBinding on UI in all plataforms
[Xamarin.Android] I researched and heard of anything like "MVVMCross" but this forces me to extend my activities other own the MVVMCross and for example, and uencessito to take Android one ActionBar and for that I need to extend a class that can extender "AppCompatActivity" being, however, can only extend an activity and that therefore can not extend the actitivties from the MVVMCross.
Video: https://youtu.be/_DHDMNB_IeY?list=PLR6WI6W1JdeYSXLbm58jwAKYT7RQR31-W
Like:
public abstract class BaseActivity: AppCompatActivity // (with MVVMCross use MvxAppCompatActivity )
public class MainActivity: BaseActivity // (with MVVMCross use MvxActivity)
For assets, the correct approach is to keep the assets in the project, and if they are common to pass the PCL? I ask this because the assets on Android, iOS and UWP, the dimensions are different. What is good practice?
Thanks in advance!
For string resources and translations located just in your PCL I would suggest to use this library (very simple to implement):
https://github.com/xleon/I18N-Portable/, but you can also try and implement Resx files from your PCL.
Adding MvvmCross to your project just for localization would be just crazy.
But if you already use MvvmCross in your project, there´s a plugin for translations that uses json files at the PCL level: https://github.com/MvvmCross/MvvmCross/wiki/MvvmCross-plugins#jsonlocalisation.
For question 2: You can embbed resources in your PCL and load them from platform projects (ios/android/etc), but it won´t be as obvious as loading platform resources (you´ll need additional code). Thus, your assets and images usually change across platorms (different resolutions, dpi and design style guides) so trying to put them all together may complicate things more than helping.
About using specific MvvmCross Activities: that´s the way it works.
Past, now irrelevant back story: I was trying to make some changes to BlueBand and get 'up and running pretty quickly' but after looking at it further this is no longer an option due to tables that a previous developer introduced into the layout. I'll have to live with this and make what tweaks I can.
So, looking towards future greenfields projects...
Are there any recommendations for CSS frameworks that work nicely with SharePoint publishing sites? (Examples are BluePrint, YUI.) They should not interfere with standard out-of-the-box controls such as the Site Actions menu, rich text editor, and publishing toolbar.
Real world experiences welcomed, please!
What would you like to use a CSS framework for? As far as I can tell you could use one for making a cross-browser reset but everything else just depends on your layout. If you're planning to throw out the standard SharePoint layout it means that you need to start from scratch. The good news is that it's not much different than creating a layout for any other website. There are some things you need (http://msdn.microsoft.com/en-us/library/aa660698.aspx) while working with SharePoint but as for CSS it's all up to you.
Heather Solomon has a great blog/guide on wiring up SharePoint CSS classes - take a look:
http://www.heathersolomon.com/content/sp07cssreference.htm
Cheers,
Adam
You will run into a lot of trouble trying to hack the blue band theme into a table less layout.
You may get some mileage from the free Accesibility Kit for Sharepoint.
It comes with layout pages, CSS and even control adapters for those who care about the HTML of thier site.
Still, getting rid of the tables produced by SharePoint is not really compatible with "up and running pretty quickly"
You should start with the minimal masterpage. That will be the masterpage that's connected to the publishing layouts. You can then add in all the html/css you desire to your masterpage and layouts to make them look like anything you want.
If the users who are browsing those same publishing pages also need access to your list forms (new,edit,display) you will have to edit those files and attach them to your masterpage (either through SP Designer or a Feature to do it automatically). Or, customize the application masterpage to be nearly the same as your publishing masterpage and deploy them both as a feature with an HTTP Handler that changes the masterpage for the application.master at runtime.
Also an FYI, there are many issues once you start customizing list form pages for a site accessible to anon users, so do your research first on that one if needed.
We have used 960.gs with some success. Just include it in your master page, and wrap the main content area with a - or use container_12/container_24. Then in your individual page layouts, you can leverage all the columns/push/pull/alpha/omega goodies that make 960 so great. This works in 2007 and 2010, just takes a bit more work in 2007.
You can use any framework you desire when working with Sharepoint, however, the primary concern is how much control you have over web parts. OOB web parts use table based layout. If you have full control over how the web parts use the markup they product then you are one step closer to using a framework with little headache.
To alleviate some of the table based layout used in web parts you can look at accessibility toolkits to convert the web parts appropriately.
I want to style the asp.net membership login control and I am too lazy to handcraft a professional looking one.
I couldn't find ready made css styles for the login control. Are there any available on the web?
The easiest thing to do would be extend the look of your current style sheet. More than likely any style sheet found on the web would look out of place in the context of your site.
That being said if you want a clean looking starting point with a lot of good built in styles take a look at Google Blueprint specifically their form demo page.
There are plenty of ways to provide a dynamic style/theme for a web site, but I am looking for some help on some best practices or techniques that have worked well for others.
I am creating a web site that needs to provide the ability for customers to create or specify their own colors, style, theme, or layout. I'm not convinced how much flexibility I need yet, but basically I need to provide Branding capabilities.
I will be using ASP.NET, and am open to any ideas that will fit within the ASP.NET framework.
Using Themes for ASP.NET 2 and greater will provide you everything you need for this.
Best way to handle it would be to make a nice CSS document that will specify all the areas that you would like to offer customization, such as header background image, background and text colors, etc. Then build application code to allow specification of which theme to load, and bring up that CSS file.
I'd personally go for a CSS-based solution.
You could define the elements' IDs and CSS classes for each page in the web application, so that customers can provide their own set of CSS files.
This approach is platform-agnostic, so that the developer who creates the custom themes is not forced to fit into the ASP.NET themes model - she might as well be a web designer with no programming knowledge.
Themes might be a good solution but having re-read your question I think you might be asking for a method for allowing customers to submit their own branding dynamically, i.e. without you having to modify any files, a hands-off approach? How about having an admin interface consisting of web forms where the customer can upload images and CSS themselves? You could then retrieve that content using a HttpHandler or similar.