|Page 1 of 1||[ 6 posts ]|
Is YUI 3 my best choice for Mobile, Tablet & Desktop Web Pages?
I am new to YUI, in fact I haven't yet started. I'm told that YUI 3 knows which device the browser is running on, and can/will change the CSS to accommodate that device. This is very appealing to me as I assume I can write one set of code which will run on all of the desktop, tablet and phone browsers, and change the look and feel of the page to fit the device. So on an IOS browser my page will look like an IOS app, and on an Android browser that same page will look like an Android app, etc.
Is this true?
If so, I will download and start learning YUI. Then my question will be "where can I find some good tutorials to show me how to do this in YUI".
My hope is that once I standardize on YUI, I will not need other libraries such as JQuery Mobile, etc.
I would appreciate guidance and advice.
Thanks much for your help and suggestions,
I found this yui slideshow about mobile usage.
Has some interesting features. (It very faintly explains pros, but no specifics) YUI is considered by most developers to be a heavy-overhead library.
This has some interesting ideas on combining libraries into one js, something I am definitely going to look into at some point.
You might want to consider using YSlow to tweak your server.
(On my server I used ETags with Apache, Gzip compression, and 1-minute ExpireByType rules for ico files, 1-second expire on css, and js files.) I always want the fastest data for my php files, so those are set to 0 second expire tags.
ETags: (MTime most reliable, Size so so, INodes only works on single web host disk with no clustering)
Good stuff between ETags, and Gzip as both of these allow caching on advanced browsers that support caching. If your using apache (with CentOS/Redhat), you always want to run this after running vhost.conf/httpd.conf
"service httpd reload"
Having said that, does YUI do everything for you? End all, be all? Probably not. This is always a battle between balancing;
-Web Server (ISAPI/CGI/FastCGI) + Bandwidth
-Database (assuming you use one)
Your mileage will vary, but saying that. YUI is designed to make some abstract things easier to do, and is used partly by some rather large companies;
YUI isnt going away anytime soon, and they seem to release updates pretty often.
Can you develop multidevice apps with YUI3? Definitely!
You don't need other libraries anymore, that's for sure.
So, is it a good choice to step over to YUI3? It sure was for me. But, of coarse, there are more libraries around that are very good. The choice is up to you. You must invest in the technology though, but there are a lot of examples, the API is great and in this forum people are willing to help.
Once you know how to work with YUI3, you can even boost your multidevice-apps by start using Mojito on the serverside http://developer.yahoo.com/cocktails/mojito/, This is quite new and creates a powerfull webserver based on node.js and using full yui3-power.
The sky is the limit, but as I've said before, don't expect to create a full app in a couple of weeks when you are new to YUI3.
Marco and FastCars gave a few nice pointers, but I think you need a little extra information. YUI does a lot of things but it doesn't (yet?) solve everything for you.
YUI does conditional loading based on feature detection. That means that if the browser has a certain feature (for example, cross-domain Ajax) it loads less code than if it doesn't. YUI doesn't however load stuff based on the device type or the OS.
Yahoo's Mojito project is a lot like what you describe. They keep versions of templates and scripts based on the context (server or client but can be extended based on any criteria you like). Mojito is very powerful but that also means it's a little complex. It takes time to master. It's written on top of YUI so if you want to use it, you should start learning YUI.
jQuery Mobile is very different to many UI libraries. It's like Twitter Bootstrap for mobile, a series of widgets that are automatically connected to your markup. YUI does progressive enhancement in very a similar way, but it doesn't connect your markup automatically. You still need to write some code (not a lot though). Another member of the community (@jshirley) and me were working on something like that and Caridy published a similar tool in the Gallery.
To summarize, there are many ways to have a website working in a range of devices (custom views, responsive design...) and they all take a lot of effort. YUI has an infrastructure that will help you and that is an active goal of YUI, but it isn't magical.
Ok, I'm definitely the grumpy one around here.
About 4 weeks ago I was using jQuery. It was my first time with a framework and I was very excited. For a few days we did everything together - she showed me things I didn't know where possible in JS, and in return I gave her my full time and attention. I was young and naive I suppose.
And then one day I just woke up and thought - 'I wonder if this is as good as it gets...'
Perhaps jQuery wasn't "the one", just "the first one", and there were more frameworks out there to see...
Soon after, I cheated on jQuery with mooTools - she had some excellent transitions and graphic processing. We made some really sublime user-interfaces together. Everything with moo was exciting and new - like falling in love for the first time all over again.
But one day, moo let me down. I needed an autocomplete feature that moo just wasn't able to provide. I didn't want a pretty accordion, or any more seizure-inducing colour transitions - I guess I just grew up and we grew apart...
That's when I found YUI.
It's funny really, because at first we hated each other. I guess I wasn't completely over moo at the time, and truth be told I wasn't ready to commit to something that was similar but not quite the same.
But now, a few weeks down the line, i'd say that things between YUI and I are pretty good. Sure there aren't as many thrills to be had, but every now and again YUI really surprises me. Like, chaining transitions in YUI is a lot more logical than in moo. In fact everything is a lot more logical in YUI than other frameworks.
And at the end of the day, i'd rather be with a framework that 'gets me', than a framework that just wants to use me for my server cycles to show off to other developers.
Learn YUI. Love her. Hate her. Make awesome websites.
You posted this question on the YUI Forum, hosted on yuilibrary.com.
Are you really expecting an unbiased opinion here? Really?
(Maybe a visit to stackoverflow or elsewhere may find a more objective opinion.)
Grumpier than jdopazo, as usual
|Page 1 of 1||[ 6 posts ]|
|You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum