Customizing SMF > Forks Discussion

BBCode pre-parsing

<< < (4/5) > >>

Kindred:
no IE6 support, ever again

AngelinaBelle:
IE7

青山 素子:

--- Quote from: AngelinaBelle on August 19, 2011, 11:42:49 AM ---And I was thinking "semi-preparsed" was going to have to be the answer.
Though, I suppose, with appropriate embedded search strings (a special class string?) the pre-parsed text could be image-re-processed for some views.

--- End quote ---

Well, you could put the raw BBCode in comments inside the parsed post. That would preserve the tags for re-parsing when needed, but it would add to the size of data.

Personally, I see too many disadvantages and additional complexities from pre-parsing the posts to actually look into it seriously. It would be much easier to handle with caching so that you can reduce the database size and complexity of manipulation of data. With caching, the most popular posts would already be parsed and in nice fast memory or even a simple cache file (in the case of 2.0's basic caching support).


As for IE7, its market share is low enough that I wouldn't worry about it all that much, especially for minor features. Progressive enhancement and graceful degradation are the key phrases.

AngelinaBelle:
It would all depend on how soon you'd want to deploy the new implementation. And where.

If we were Chinese, we'd definitely want to support IE6.

青山 素子:

--- Quote from: AngelinaBelle on August 19, 2011, 12:28:17 PM ---It would all depend on how soon you'd want to deploy the new implementation. And where.

If we were Chinese, we'd definitely want to support IE6.

--- End quote ---

However, it also depends on the feature. Not many sites have put visible URLs for links on print editions. As such, it's not an expected feature. Therefore, using CSS that only works on newer IE and all other browsers would be acceptable. People with IE6 (possibly 7 as well) would get the usual behavior. People using newer browsers would get an enhancement.

Graceful degradation is all about not caring so much about older browsers as long as the base functionality is there. No CSS drop-shadows for older browsers? Are they crucial? If not, then don't worry about supporting that on older browsers.

A good example is the rounded corners on the SMF Curve theme. While they could be done with CSS, leaving IE to just show square corners, they were considered fundamental to the design and therefore a method was used to ensure that this feature worked on all browsers. If the rounded corners were merely incidental to the design, then CSS would have likely been the method used.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version