In my Angular 6 SPA, I want to use multiple themes for different modules of my project.
Is it possible to do so? If yes how? An example will be very helpful.
Also, I want to achieve this using lazy loading.
Related
So the Material Design 2 components are out there, waiting to be used in your app but my question is how would you structure your layout in which they rest?
Do you use https://github.com/angular/flex-layout?
Write the layout manually?
Using CSS Grid, Flexbox or both?
This is for a brand new web app, and I prefer writing it using modern technologies that are here to last (as much as this is possible with Web technologies...).
You should use Angular's Flex Layout. It's also specified in the docs for Angular Material:
Layout -> See angular/flex-layout
I need develop SPA with angular and angular material, but I need this SPA to be responsive, but I do not know if I need to use the bootstrap libraries or if it is possible to do everything with material, it confuses me with the issue of using those md-12 with bootrstrap, my idea is not to use bootstrap and do everything with material.
What do you think?
Material doesn't deal with screen responsiveness. If you want to stay within the Angular family, use angular/flex-layout
Hi I want to know what is the easiest way to create smooth,simple and attractive,
light weight theme for website ?
so I have confusion in choosing many css, js framework.
can any body tell me which is better and best to create theme ??
it depends on many factors such as what type of theme you want to create. If the theme is just going to be dealing with UI Controls, Then checkout
jquery ui at http://jqueryui.com/ as it provides excellent themese for you.
Since you mentioned CSS you should also check
Blue Print CSS Framework
as it comes with a huge variety of styles that you can add readily.
You can also download some HTML 5 light weight themes that are compatible with mobile devices also and then you can customize them to their content.
http://creativecan.com/2012/05/html5-and-css3-templates/
Check that out as well.
This post has been 'somewhat' addressed (see links at bottom of post) but not to it's full extent.
I am working on building a mobile site in Rails 2.3 (I know, I'm going to migrate to Rails 3 soon). Either way, as I continue developing this mobile site (and I am using Mobile Fu - works great), I'd like to understand best practices around configuring and managing the mobile site:
Where should I redirect to the mobile domain (in application controller)? What is the best logic for doing this?
Should I build the .mobile.erb files in the same folder as the .html.erb files? Or in a separate mobile folder?
What kind of routes/controller/etc logic do I need for my mobile site (if I decide to not embed the mobile rendering inside my current application structure, but instead have a separate controller and mobile view folder)?
I appreciate it.
Other links:
Web and Mobile views best practices same controller or namespace?
http://www.arctickiwi.com/blog/mobile-enable-your-ruby-on-rails-site-for-small-screens
Rather than answer your question directly, I am going to suggest that best practices have moved on somewhat.
Concepts like Mobile First, Adaptive Design, Responsive Design, and Progressive Enhancement are replacing the split site approach as best-practice.
These concepts revolve around building out your site for mobile first (so you can work out what the most important things are) and then extending the design for screens that are larger.
It removes the need to determine if it is a 'mobile' accessing the site and instead relies on various techniques (adapt.js or CSS media queries) to target different layouts to the variou screen sizes. It also means you do not have to maintain multiple views and routing - you have one view and change the CSS.
When you move to Rails 3.1 (with the pipeline) this allows the creation of CSS (and JS) manifests, and you can (potentially) have one manifest for each screen size.
There are issues with the above approach (just as there are with split sites), but if you Google the key terms above you'll find tons of advice. Best of luck either way!
Edit: Here are some links I found useful.
http://www.lukew.com/ff/entry.asp?933
http://www.netmagazine.com/features/mobile-first
http://www.alistapart.com/articles/responsive-web-design/
http://coding.smashingmagazine.com/2011/01/12/guidelines-for-responsive-web-design/
http://www.alistapart.com/articles/taking-advantage-of-html5-and-css3-with-modernizr/
http://www.sitepoint.com/regressive-enhancement-with-modernizr-and-yepnope/
There are some that think that this is bad though:
http://nefariousdesigns.co.uk/archive/2011/05/sniff-my-browser-the-modernizr-inadequacy/
I have been developing a simple app using HTML pages that are interlinked. They will be using some form of data persistence. I have not decided yet. They will be displayed on an iPad in both landscape and portrait modes.
I could wrap them in a UIWebView and roll my own app that way, but to me it seems that others must have come across this requirement before and there might be a simple framework to do this.
I don't need any special access to location data, accelerometers etc. Just plain HTML, some CSS and Javascript. The most complex of which will need to store a series of name value pairs (circa. 150 items) that will need to be available to all pages within the application. I have no need to call the Javascript from the app or vis versa.
I will need to insert inApp purchasing in future to the application, whereby I will load a larger set of HTML files. It might be nice to be able to trigger that from inside the HTML pages but that is not necessarily a deal breaker.
There are a number of frameworks for writing apps in HTML5 etc. and converting. I don't really need this either.
But I would rather use some framework that will take the lessons learned by others and let me deploy my app on an iPad with minimal risk.
Can anyone give me advice regarding the best framework for this use case?
Thanking you in advance,
Andrew
I would use phonegap. It works on the iPad no problem.
You can use the camera and accelerometer and all that with phonegap-plugins.
I am using it on a few iPad projects, and since you can use HTML/CSS/JavaScript, you can pretty much just configure phonegap with your web address and your web app is now an iPad app (that or just add static html files to the phonegap project directory). Then it's just 'modify the design and layout HTML/CSS'.