"According to Mozilla release page Mozilla will officially release Firefox 5 on June 21st. Firefox 5 will not bring any GUI changes instead the design interface will be almost same as Firefox 4. Most of the plugins will not compatible now with Firefox 5."
A very hard English, at least for me.
Where is the 'Mozilla release page'? The link redirects to another technobolt.com article where again is written "Now according to Mozilla release page..."
Searching on the Mozilla's site, there isn't such a 'release page'. Also, Google failed to find such a thing.
Can someone point another source for this news?
Also, "Most of the plugins will not compatible now with Firefox 5." means what? ...that most of the plugins indeed won't work or it is a writter error?
Kudos. But if you are a newbie, then perhaps it would be more useful for you, in order to learn how to use an actual DSLR in the field, to reduce the 'Lighting' to more difficult situations ('Overcast', 'Bright Indoors' etc.) and...
1.) set up the simulator to Tv mode and play with the 'Shutter Speed' and ISO primarily
...and after this:
2.) set up the simulator to Av mode and play with the 'Aperture' and ISO primarily.
In this way you will learn how far you can go in real situations and what results you might expect.
HTH
(EDIT: Ok, you can play with the distance & focal length but I think that for the 1st step it is better to concentrate on the points above).
thanks,
so why would Tv mode be more educational than M (which I am guessing stands for Manual) which also allows for playing with shutter speed and ISO ?
Indeed there are cases in which one can use the M (Manual) mode. But usually these cases are rather corner cases, especially for us, the beginners. Basically you ditch the DSLR's photometric engine which does most of the time a very good job, (except some rare situations in which the illumination is very tricky, you want to achieve very special effects etc.).
Besides that, it is enough more difficult to play with four variables (Aperture, ISO, Speed AND the exposure indicator (usually a vertical beam in viewfinder)) compared with two variables (ISO & Aperture or ISO & Time respectively) or with just one (Aperture or Time - if you have the ISO set to Auto).
The main difficulty here isn't that someone (you) can cope (or not) with four variables in a simulator but to adjust them quickly and exactly in the field given the very short amount of time which you (the photographer) have at your disposition to take "the shoot".
That's why the most photojurnalists (from which, more or less, is your truly also) avoid the M mode. OTOH, I have very close "brothers" which are 'studio creatures' which prefer the M mode.
And now to respond directly to your question, having the Tv (or Av mode) will give you a much 'closer to real' simulation (especially if you are on-field, on-street, on-sports etc. photographer) and will allow you to concentrate rather on the effect you want to achieve (for ex. how to simulate a good moving effect of the child's rotating toy) in the smallest amount of time (think that in the real world, the children aren't so frozen like the one in our simulator :-) ) and not to concentrate so much in obtaining a correct exposure. Usually the metering system does the job rather well. These systems have enough advanced features today to help you in avoiding the M mode with its quirks: exposure modes, over/underexposing by 1/2, 1/3 EV etc.
HTH
PS: Disclaimer: No, I'm not against the M mode. But I want to stress its limited usage today. Of course IMHO.
Fix the Internet connection problems for the systems behind proxies / firewalls which requires authentication.
It's a big pain to mess with the config files to set up all shipped programs to work ok in such an environment. The System | Preferences | Network Proxy... Manual Proxy Configuration, [Details] button (...enter here your username, pwd) has a very 'fuzzy' effect (even if we press [Apply System Wide...] button) - some programs work, some don't (including apt-get) etc.
The majority of the arguments are just FUD. They might have applied in 2001, but to write this post now is just silly. He complains about breaking changes between 1.1 and 2.0 -- 2.0 came out in 2005. My guess is that he's really just angry because Microsoft (and most developers) have moved on from Delphi.
Some of the arguments are reasonable when applied to desktop development, but they're still pretty light on facts. None of them are particularly reasonable when applied to web development.
He laments that GDI+ isn't hardware-accelerated, but if I recall correctly, WPF (the newer UI toolkit that came out in 2007) is.
"Almost every programmer said you have to write XAML by hand" -- I won't defend Microsoft's obsession with visual tools, but I learned that I have to write HTML by hand years ago, and I'm not complaining.
String processing is slower? Probably because .NET strings are immutable, which actually creates large performance gains in the vast majority of cases.
If your performance concerns are so stringent that you need to worry about whether the type system in a language is rooted, you're either over-optimizing or you should be working with C.
I rather think that he's looking from another perspective. Using Delphi, speaking about speed, complex GUIs which need a visual designer (etc.) means that he is a desktop developer.
I don't know how they could succeed without a solution similar to Kylix. And I can't really envisage anything on the subject. Cross platform native apps is too good to be true :) (that is with third party support as abundant in Delphi, else FPC is actually there.)
A very hard English, at least for me.
Where is the 'Mozilla release page'? The link redirects to another technobolt.com article where again is written "Now according to Mozilla release page..."
Searching on the Mozilla's site, there isn't such a 'release page'. Also, Google failed to find such a thing.
Can someone point another source for this news?
Also, "Most of the plugins will not compatible now with Firefox 5." means what? ...that most of the plugins indeed won't work or it is a writter error?