Announcements

Filters

 
Date
Date

CurseForge, WowAce, and the future

Posted by ckknight Mar 27, 2009 at 20:52 UTC

Hello friends, ckknight here.

Some of you may be wondering what the next step for CurseForge/WowAce might be. You may have seen the piles of tickets that the CurseForge project has and it can be disheartening.

So, I'd like to let you know that development absolutely has not stopped. We have limited resources with regards to manpower, as it has been essentially just one person (me, ckknight) doing nearly all the work on the site itself. Kaelten has been working furiously on the Curse Client, and I think we can all agree that it has blossomed under his guidance.

I've been working on the upcoming Author Rewards Program and Author Store, for when we launch Curse Premium and the Author Rewards Program soon.

The current gameplan is to completely overhaul the HTML and CSS on the website. While we previously had a frontend developer working with us, that is no longer the case and hasn't been for about a year, causing general bad practices to leak into our display code. This will lead to an overall greater polish for both WowAce and CurseForge. Things will also be very easy to change and add to in the future.

As it stands, if we want to add any new features, wrestling with the CSS has become a case of the Old Lady Who Swallowed a Fly, where anything we do can cause a ripple effect, leading to slower development and an overall lack of polish.

Once this is finished, the website should act a lot more consistently, provide a better user experience, and allow further extensibility in the future. Also, we'll be able to call ourselves "Web 2.0" if we have rounded corners and gradients, right? ;-)

For an idea of some of the future ideas we have, so you know that we actually have future ideas:

  • User-submitted guides
  • Web-based repository browser
  • Ticket enhancements
  • Various bugfixes and small features.

If you have any ideas, we're more than willing to hear them through CurseForge's ticket system. Also, if you see a good idea, feel free to vote it up. That's a big reason on how we prioritize the next thing to do.

  1. 5 comments

Curse Client 3.0 Release & New Mac Beta

Posted by Kaelten Mar 23, 2009 at 19:43 UTC

Curse Client 3.0 Release

I just wanted to take out a few moments and let everyone know that friday we released the 3.0 client to our entire userbase. It's been a long time coming, but I feel it fixes the majority of issues people have raised.

Some of the highlights:

  • Redesigned User Interface
  • More accurate addon identification
  • Revaluated Defaults settings
  • More features (including whether or not to use embedded libraries)
  • Numerous bug fixes and stability improvements

Not only that but....

Mac Client 3.0 Beta Release!

We managed to get you a mac client beta out on Friday as well! This was a personal victory for me as I'm now actively working on the code for the mac client. In addition to the above changes we are happy to announce that updates are now done through Sparkle (same update mechanism used by Adium, Textmate and many other mac apps).

We are still in beta here as wxWidgets' implementations can drastically differ on mac vs pc, as a result we're working hard to iron out issues, and will be putting out updates all this week until we're at a more stable point.

However, there are a few...

Known Issues

Upload mistakes

Over the last week we've had a few authors mistakenly upload either the wrong file or files with invalid layouts that have caused the client's fingerprinting to mistake people's folders for the wrong addon.

Two known examples of this are Ace3 and Auctioneer getting flagged as Tournament Realm Spy and epgp. We've fixed it server side however the client won't just 'forget'. You'll need to remove the false match and in some cases reinstall the new correct match.

Mac Issues

  • A crash that can happen on load in the sort routine
  • A soft crash where the client stops displaying data and buttons fail to do anything
  • Menu options being decidedly 'unmacish'

Reporting Issues & Discussion

Windows

Mac

General

  1. 12 comments

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