Wedge

Stop computer viruses! Stop porn!
Get real viruses! Get real sex!

:niark:

My main point for wanting to provide a portal out of the box is that it'll help avoid the numerous portal systems in SMF. I'd rather have a unified system in Wedge, and then let people add plugins for specific features that would normally be in a portal package.

And yes I think it's best to put your best into things you do, but sometimes "your best is not good enough". Oh, I'm watching too much South Park these days, I keep quoting episodes. :lol:

Google has a 100% uptime, last time I saw, your jQuery file will be available long after your server died :P
But really, it's up to you. I did write this local option. I went as far as implementing the gzipping & caching stuff just to make sure it's as small as possible in local. So you might as well use it :P

Some people will think it's not necessary that Wedge has a forum system, you know :P

A few of the many, many SMF things I fixed... (Just retrieving keyword 'smf' from last month's SVN commits.)

- In the profile area, when issuing a warning, SMF has code whose purpose is to allow moderators to drag and slide to set the target percentage. Needless to say, it doesn't work at all.
- SMF uses time() in a few areas to determine how many seconds were spent on a task. Very accurate!
- SMF does something like this at some point: in_array('m', array('m,cd,cp')). Sounds like a joke.
- SMF shows a floattop class by default in template_button_strip. It doesn't even exist. Most of their calls request floatleft, they should have used that by default...

SMF does this, SMF does that... These are all bugs I found while reading/assessing/auditing the source code. We're not supposed to do that. The SMF team is supposed to. SMF beta testers, at worst.

Really, there is no way Wedge will be available in anything else than French and English during the alpha sessions. Maybe beta will introduce other languages but I doubt it -- we'll strongly discourage anyone from translating Wedge until we're done stabilizing the language files. There haven't been major changes since I implemented AeMe into Wedge, but it's clearly far from complete.

Opera is updated as language files go. 95% of all alpha/preview versions are only provided in English. They usually add other translations during the RC phase.

UTF8's only issues are: (1) slightly lower performance, (2) uses more space.
(1) isn't much of an issue because we only use UTF8-aware functions when necessary. There is no need to call a UTF8-aware strlen when we want to know the actual size in bytes rather than characters. Things like that...
(2) is more of a problem but really... It takes about 5% more space in a French language forum. It's not that much... And it's even less in an English-only forum (actually, 0%). Although if you have a Japanese board, it will use much more space than Shift-JIS or whatever. But that's the price to pay. If you have a Japanese board set to ISO-8859-1, it will use up way more space because all chars are converted to HTML entities.

rev 763
(8 files, 10kb)

! In some cases, the template footer wouldn't be called, and an error would be generated. (Subs.php)
! Why ask Wedge to do a simple addition on tag processing, when developers can do it once and for all? (Subs-BBC.php)
! Inline post edit could generate errors, and trigger yet another error when trying to announce it. (topic.js)
+ Added 'headline' class to the more tag, for themers to style post introductions. (Subs-BBC.php, index.css)
* Upgraded other jQuery 1.4.4 occurrences. (install.php, repair_settings.php, upgrade.php)
* ajax_in_progress box was too big. (index.css)
- Outdated documentation. (admin.js)