Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
Is there a way to preview before finally submitting my persona?
Speaking of which, have you taken a look into the new personas feature? They're just so totally cool!
www.getpersonas.com
I can barely read the tabs. Is there any way to adjust the opacity or specifically select a text color?
And damn, why don't they skin the title bar too. **** my title bar looks like shit.
About 75% of the time, when switching or previewing a different skin, it will never load.
Also if you untick the 'use text colors' it will stay whatever text color your last skin had forever, or until you tick the box again and select a skin with a different text color.
Buggy bastard child
lol. This guy is trying to get some feedback and maybe some advice about a problem he is experiencing. Someone must have urinated in his breakfast cereal.Dude you're such a friggin' nay-sayer. Who pissed in your cheerios?
I didn't realize that it was mostly the fault of the skin I was using. This one looks pretty clean and readable. I do hope they add some more features to Persona, like the ones I mentioned, because with some skins, the text is about the same color as the skin.Unfocused said:I use the Viva persona now, everything is nice an readable with it.
Dude you're such a friggin' nay-sayer. Who pissed in your cheerios?
The new Javascript engine is nice, but not yet useful in practice as web applications still have to be programmed for the lowest common denominator (IE) which means the potential is wasted and the difference only shows in synthetic benchmarks, not in real life. The same goes for Chrome, it might be faster but there's no web applications that make the difference apparent because those web applications still have to be fast on IE.
Why does that make any sense? Programming for IE is a pain because some of the DOM is implemented differently, which means some methods or objects have different names, which means you sometimes have to write specific code for IE compared to all the other browsers. But it's still basically doing the same thing, and if you write a Javascript engine that's more efficient than IE's, like Chrome's or Firefox 3.5's, it's going to be faster.
Been a bit disappointed with FF3.5 so far. I'm getting regular crashes, encountering bugs (admittedly some of these might be due my addons, but they worked fine under FF3) and the whole thing just feels less polished.
For example, I wanted to clear my saved passwords so I went "ctrl-shift-del", checked all the boxes and hit clear just as I would in FF3. Turns out that option no longer exists there, or in any obvious place in the options menu. To clear saved passwords you have to;
Options Menu > Privacy > Use custom settings for history > Check Clear history when Firefox closes > Settings > Check Saved Passwords > Ok > Close Firefox > Open Firefox > Revert settings to what you actually want.
For a standard security feature that is ridiculous.
Just go to Tools - Clear recent history
You can clear either your entire history (select everything) or something from the past hour or two.
The new Javascript engine is nice, but not yet useful in practice as web applications still have to be programmed for the lowest common denominator (IE) which means the potential is wasted and the difference only shows in synthetic benchmarks, not in real life. The same goes for Chrome, it might be faster but there's no web applications that make the difference apparent because those web applications still have to be fast on IE.
"ctrl-shift-del" is the shortcut for "Clear recent history"
Yeah, any JS in Chrome will be faster than in IE. However, does it matter in real life? Synthetic benchmarks are one thing, but if you're writing something that makes heavy use of JS, it has to run smooth on IE. This means that it doesn't matter whether or not Chrome is 10x or 100x faster than IE, because there isn't going to be any application where this is noticeable because all applications have to be fast enough for IE. If opening a window takes 100ms in IE, because that's how fast you need it to be, it will take only 20ms in Chrome, but does that matter?
You have to program for the weakest link, especially when the weakest link holds ~70% of the market.
At work, I'm working on a webapplication that makes use of ExtJS, where literally all HTML in the application is generated by the library, and honestly: there's no noticeable difference between Chrome, Firefox and IE. At all.
Fact of the matter is, as long as IE doesn't have a Javascript engine that's in-the-ballpark-of-Chrome fast, all these advancements with Javascript engines are worthless in practice.
One idea that occurred to me recently is that perhaps Microsoft can use the Managed Javascript for the .NET DLR for Javascript acceleration in IE somehow.
I cleared the history once and in like 2 steps, your description seems ridiculous and unnecessary.
For example, I wanted to clear my saved passwords so I went "ctrl-shift-del", checked all the boxes and hit clear just as I would in FF3. Turns out that option no longer exists there, or in any obvious place in the options menu. To clear saved passwords you have to;
Options Menu > Privacy > Use custom settings for history > Check Clear history when Firefox closes > Settings > Check Saved Passwords > Ok > Close Firefox > Open Firefox > Revert settings to what you actually want.
For a standard security feature that is ridiculous.
Being upfront about it, I do not understand these steps.Ok > Close Firefox > Open Firefox > Revert settings to what you actually want.
Yes, you have to sure your stuff runs smoothly in all the commonly used browsers... but making something run smoothly in IE doesn't mean it will run like shit in Chrome or FF3.5 or anything else. It'll run smoothly in IE, and it'll run even better in browsers with better javascript engines. The other thing making competatively performant javascript engines does it up the ante for Microsoft. If all the completing browsers are kicking their ass, they're going to need to get their shit together and make IE better. Developers can foster this by suggesting to their users to change their browser if their app runs better in Chrome or FireFox.
Personally, I'd suggest having a "It is recommended to run this site in FireFox v3.5 or Chrome [why?]" blurb at the bottom, with the [why?] being a hyperlink to a page explaining why the other browsers are faster.
Doesn't Clear Recent History > Details > 'Active Logins' checkbox clear what you want? Just asking, I genuinely don't know....:O
Never said that it would be slower than in IE, in fact: it will be faster in Chrome. It's just that it doesn't make any difference whatsoever.
My whole point is that the advent of faster JS in Chrome/Safari/Firefox is not going to let you build a hugely complex and demanding JS application because then it won't be fast enough in IE. It really doesn't change anything at the moment. Yeah, useless synthetic benchmarks like raytracers.
And yeah, I do hope that this is an incentive to improve JS performance.