SMF 2.0 Release Candidate 2 is out for Charter Members!

[Arantor]

I've only ever known it to say alt-s and alt-p...?

[WiredStorm]

Whats Charter members?

[IchBin™]

Charter Member

[Ben_S]

I've only ever known it to say alt-s and alt-p...?

Check the changelog or an RC2 forum

[Arantor]

It's recent then, I checked an SVN build a few days old before posting...

[Ben_S]

Not that recent, it's certainly in 20090719.

[Arantor]

Does it browser sniff? I just went to a 20090926 build and it says:

shortcuts: hit alt+s to submit/post or alt+p to preview

But I am using IE7.

[Ben_S]

Of course, it would be silly to display the wrong text in IE

[Arantor]

According to index.english.php in latest SVN:

Code Select Expand

$txt['shortcuts'] = 'shortcuts: hit alt+s to submit/post or alt+p to preview';

[Ben_S]

May be one for the bug tracker then as they are defined in post.english.php

$txt['shortcuts'] = 'shortcuts: hit alt+s to submit/post or alt+p to preview';
$txt['shortcuts_firefox'] = 'shortcuts: hit shift+alt+s to submit/post or shift+alt+p to preview';

[Antechinus]

Yeah... No, they're not.

Basically, there are people who only code with tables, preferably with border=1 and red text on brilliant green backgrounds.
Then you have the CSS zealots who will work for days on a single table because it refuses to align correctly when it's turned into a div.
And inbetween, you have the regular users who respect standards, but who don't give a damn about whether it's a table or a div and use what makes most sense.
Really, tables ARE standard. They're just frowned upon by many semantics activists who think a table should only be used on tabular data.

Recently, I pointed out to the team that with Curve, the "Report to a moderator" link could be in the middle of a post, and thus have an exposure that is probably not wanted, as opposed to Core where it sticks to the bottom of the message and thus remains quite discrete.
http://dev.simplemachines.org/mantis/view.php?id=3794

This is where CSS reaches the end of its capabilities, I believe. I couldn't find a way to make it work (and I tried hard -- look at the comments).
The same thing happened to me when I wanted to add a left-floated div with a sidebar on my board. Guess what? The regular contents had a clear:both setting at some point, and the rest of the page showed below the sidebar. Woohoo. Couldn't get it to work. After 5 minutes I got rid of my div and replaced it with a table. Now, it worked straight out of the box. Weird, uh? No, not that weird-- tables do what they're asked to do. You can place a sidebar somewhere, tell it how it will align horizontally and vertical, and so on. Divs don't do that. Maybe they do (display: table-cell, maybe?), but I don't know how.

So, basically -- Curve is not "ready for prime time", as I like to say. It's a very nice improvement over the basic Core, and I have to say the team's desire to go all the way sematics can only force my admiration, but beyond that, it has to work. That's the bottom line. So, tables.

(Okay, seriously, this topic is going to be to be split into several topics at some point...)

I agree with you actually. Tables certainly have their uses if you are sensible about how and where you use them.

[Akyhne]

May be one for the bug tracker then as they are defined in post.english.php

$txt['shortcuts'] = 'shortcuts: hit alt+s to submit/post or alt+p to preview';
$txt['shortcuts_firefox'] = 'shortcuts: hit shift+alt+s to submit/post or shift+alt+p to preview';

$txt['shortcuts_firefox'] is a completely new entry in the RC2 language pack.

[DarkGênesis]

When you go out the version published?

[Norv]

DarkGênesis: if you mean when RC2 will be out for the public, that is not fullt certain, however within a couple of weeks would be a rough estimate.

[Arantor]

$txt['shortcuts_firefox'] is a completely new entry in the RC2 language pack.

Indeed. But the $txt['shortcuts'] is *also* in index.english.php without its Firefox related version.

[Nao 尚]

The clear: both; is something that should be avoided. Many errors with floats can be fixed using overflow instead.

The problem is that simply transferring the rigid setup of Core theme isn't gonna work that well in Curve's css setup all the time. But, its solvable.

How do you propose we/I solve the two problems I mentioned?
- Sidebar next to the message list
- Report to a Moderator link
The only fix I can find for #2 is to simply remove the link... (lol.) Or move it to an icon and put it next to the icon list above (split, quote, etc.)
Sidebars-- no go for now, because of the numerous clear:both uses. And position:absolute is not a solution either, except by forcing the rest of the page to have extra padding (probably the only logical solution.)

[bloc]

The clear: both; is something that should be avoided. Many errors with floats can be fixed using overflow instead.

The problem is that simply transferring the rigid setup of Core theme isn't gonna work that well in Curve's css setup all the time. But, its solvable.

How do you propose we/I solve the two problems I mentioned?
- Sidebar next to the message list
- Report to a Moderator link
The only fix I can find for #2 is to simply remove the link... (lol.) Or move it to an icon and put it next to the icon list above (split, quote, etc.)
Sidebars-- no go for now, because of the numerous clear:both uses. And position:absolute is not a solution either, except by forcing the rest of the page to have extra padding (probably the only logical solution.)

Thats what I mean, because of the clearings its impossible to add sidebars without using a table. I removed many of them, but it seems many are left.

Also, for your own use, it can help to use clear: right where clear: both is defined - without looking at it more thoroughly.

The report to moderator thing needs some looking into. It might be needed to shuffle around the whole markup for display there.

[Oldiesmann]

Ok, np.  So will just use ALT+SHIFT+S than.

Easy fix:

Type "about:config" in the address bar (no quotes). Acknowledge their silly warning.
In the "filter" box, type "ui.key" (again without the quotes)
Double-click on "ui.key.chromeAccess" and change its value to 5
Double-click on "ui.key.contentAccess" and change its value to 4

That will force the content access keys to be more important, thus making things work like you'd expect them to.

[Kenny01]

I don't like the catcha, is it possible to disable it, or to use a less complicated catcha?

[Oldiesmann]

I don't like the catcha, is it possible to disable it, or to use a less complicated catcha?

In 1.1 you can change the settings from the Registration Settings area of the admin center. In 2.0 it's in Admin -> Server Settings -> Security -> Anti-Spam.