Announcements

Filters

 
Date
Date

WikiCreole markup

Posted by ckknight Mar 06, 2009 at 21:51 UTC

Hello, friends.

Up until now, CurseForge and WowAce (since the transformation to the CurseForge codebase) have used "Curse Wiki" as the default wiki type. We have implemented the feature-rich WikiCreole markup and plan to make it the default on Monday (March 9, 2009).

What's wrong with Curse Wiki?

Curse Wiki is a custom implementation of the MediaWiki markup. The code we use for it is rife with issues, including lack of readability, inherent slowness, potential security issues and general bugs, and lack of extensibility.

The developer of the Curse Wiki format has no longer been with us here at Curse, Inc. for a year now, and no one can read his code, and when anyone tries, it's impossible to cringe.

Why choose WikiCreole over something else?

We agree with the philosophy of WikiCreole, the code is clean and readable, it's fast enough for our use cases, and the library we use (CreoleParser) is very extensible.

Due to the awesome extensibility, we were able to add nice relative links, e.g. [[Some page]] or [[Project:Some page]] rather than forcing full links as we have. We also support images nicely, e.g. {{4}} or {{Some image}} or {{Project:4}} (and so forth).

We were also able to add syntax highlighting with the <<code>> macro.

print("Syntax highlighting is awesome: " .. 42)

See Markup Types / WikiCreole for the full syntax examples of WikiCreole.

Will I still be able to use Curse Wiki?

Yes, this will still be an option, just not the default one.

We may eventually disable creating new pages/comments using Curse Wiki (likely if a security issue arises), but we would still allow old pages using it to continue to be editted as Curse Wiki.

Are you getting rid of any of the other markup formats?

Probably not. We've cleaned up the code for plain text and Safe HTML, and made BBCode a thin wrapper around WikiCreole, so we see no reason to remove those three at all.

We may eventually support more formats, such as Textile, Markdown, Restructured Text, etc.

  1. 23 comments

Forum and Site email fixes

Posted by Kaelten Feb 25, 2009 at 20:54 UTC

We've had a bug in the forum's login script that was accidently clearing emails from accounts. This would prevent people from receiving emails or any other notifications.

Also I've revamped several chunks of our dns records, reverse dns, and spf records.

This should help increase the reliability of receiving email in general.


  1. 0 comments

Knowledge Base articles reorganized

Posted by Ackis Feb 24, 2009 at 18:33 UTC

Hello everybody.

All of the knowledge base articles have been reorganized to be nested. This will make them easier to browse, however some links in the articles themselves may not work anymore. We'll be fixing those up over the next little while.

  1. 2 comments

Heads up! We're giving away a Reactor

Posted by Kaelten Feb 18, 2009 at 21:18 UTC

Just wanted to make sure all of our authors had a chance to signup to win the Reactor by Hardcore Computers we're giving away on curse.com.

I've signed up, but I'm probably not eligible :(

Anywho, signup here if you're interested.


  1. 12 comments

Curse Client 2.1 RC1 Release!

Posted by Kaelten Feb 04, 2009 at 00:52 UTC

I know it's been a while since I posted my last status update for the project. I apologize for the silence, but we're nearing payday!

So now, after several months of intensive development I want to bring to you guys the first release candidate for the 2.1 line.

What's New‽

Well, almost everything! Well, almost.

What were the issues again?

Here is a brief recap of what I posted in my last announcement as some of the major issues.

   * Ignoring manual deletions
   * Installing over addons
   * Downgrading addons
   * UI feedback failures
   * Poorly worded options and button text
   * Too much automation in some places, too little automation in others
   * Lack of features that are considered defacto standards
   * General reliability 

Now let's talk about what we did about them.

What we did about them!

UI Changes

The UI has gone through some major overhauls. Hrm, how can I explain this......

The old client

The new client

There are more changes than can be seen in that screenshot, but I think it gives a rough idea.

New Features

Well we didn't get everything I talked about in the last message done. Here's the list. I've struck through things we've finished. Things that are works in progress I'm marking with italics.

   * Alternate Packages - It's back!
   * Dependency Resolution
   * Manual Deletion Detection
   * Alpha Support
   * Multiple Game Support - Even over network drives!
   * Version Pinning
   * Submodule support 
   * Saved Variable Scrubber - It's not 100% tested and polished yet.
   * Automated and Manual Backups 
   * Real Configuration Box - The game manager takes the place of most options.
   * Deletion before upgrade
   * Uninstalled Package Listing - It's the unknown addon listing.

We'll be finishing things up as soon as possible.

Changed Behaviors & Methods

Discovery and Detection of versions
If anything we're too conservative now. We've gone through extraordinary pains to make sure that we know exactly which version of the addon you're using. If we don't know, we don't touch it. It can still get a little confused sometimes, mainly if an addon is shared by more than one project. We'll be working out a tweak for that situation shortly.
Changes to Defaults
Yep they got changed. You may not like some of them, but you shouldn't find them offensive!
Popup Questions
Well, 99% of the time you'll never see a popup question. Unless you're doing something that you can't undo. Like deleting an addon. We don't want a misclick to make you a sad panda...

The Mac Version

Do you want the good or the bad news first?

I'll start with the bad. It's not here.

The good news is, we're now actively getting it ready for it's first night out. I can't promise exactly when just yet, but Soon has never been so close. I hope to start leaking alphas out next week, but again I can promise nothing!

Conclusion

The one thing I don't think anyone can argue with is that this client is hands down superior to it's predecessor. There is not a doubt in my mind regarding that.

Is it perfect? Of course not. Are there bugs? Sadly, yes I'm sure there are. However, there was no way we could justify continuing to hold back this update and letting people continue to use the old version.

We're looking for feedback as we're getting ready to put this out there to all 700k+ users in the next few weeks. Please use the ticket tracker I'm going to link below to report any feedback. But please, try and see if the ticket already exists.

I also want to apologize to all you guys who've been struggling with the 2.0.0.14 client for so long. Support on it has been weak to non existent, I'm going to be keeping a tabs on things much much closer with the new client in order to ensure that the same backlog doesn't happen with this one.

So guys, last thing I'm going to tell you is how to get the new client. So make sure to check the link section below!

  • 2.1 Installer: Use this link to get the latest client installer.
  • Feedback Tracker: Please try not to put up a bunch of repeats!
  • Forum Thread: I'm keeping the old thread, also linking to the current page. not the first one.
  1. 32 comments