This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
16
Off-Topic / Re: ORACLE begins patent-trolling with Java.
« on: August 28, 2010, 07:30:52 pm »
Fede-lasse stop goddamn reporting things that don't need to be
17
Announcements / Re: Enigma on all platforms
« on: August 20, 2010, 07:23:09 am »whereas Apple is still updating their first iPhone.What
18
General ENIGMA / Re: Someone should
« on: August 20, 2010, 06:32:30 am »
How about doing something like what Adobe does with Flash?
19
General ENIGMA / Re: MacOSX problems
« on: August 13, 2010, 08:48:22 pm »
I thought Apple doesn't allow intermediary wrappers or something like that for iOS apps?
20
I already signed some non disclosure agreement with Valve and have access to the steamworks sdk.
In fact I'm part of Lime Entertainment which has made a wrapper for steamworks with game maker and is about to release a game on steam using that.
If you want more info on steamworks before you sign stuff...
https://partner.steamgames.com/
@a2h - No you do not need a license, you just need to sign the NDA and convince Valve you can actually make a game with it by showing a demo of your already existing game.
What the holy crap?
22
Off-Topic / Monkey Island 2 SE
« on: July 24, 2010, 07:23:16 am »
Anyone got it and played it? I loved it throughout, and the graphics are a fantastic improvement over MISE as well. The ending part (making your own voodoo doll) and ending were major letdowns, though.
23
General ENIGMA / Re: Markdown
« on: July 18, 2010, 09:27:30 pm »I have yet to find a lightweight markup language that I like, but BBCode has come pretty close, sadly.
Markdown is horrible for trying to put HTML in a codebox.Code: [Select]<div>
<span>
<a href="http://www.google.com">Link 1</a>
|
<a href="http://www.google.com">Link 2</a>
</span>
</div>
Use your fancy ~~~ trick, and the above code will become actual html, so you will actually see 2 links, rather than the raw html code like you should.
Adding 4 spaces before each line seems to solve it, but it's annoying as hell, especially when you start pasting in long segments of html code.
Not to mention if a user decides to use html and forgets to end one of the tags... the rest of the page is screwed up.
http://daringfireball.net/projects/markdown/dingus
That's a Markdown testing page. Simply type in <del>, click "Convert", and scroll down to observe the mayhem.
That's because ~~~ isn't part of the original Markdown specification and instead part of "PHP Markdown Extra", and I mentioned that in the OP quite clearly.
24
Announcements / Re: Bugtracker trial
« on: July 13, 2010, 07:06:17 pm »
Uh it's actually called spray but the repo is still called bugspray
25
Announcements / Re: Bugtracker trial
« on: July 13, 2010, 05:48:26 am »
Why isn't anybody using the starring functionality?
26
General ENIGMA / Markdown
« on: July 11, 2010, 03:21:33 am »
Ever since coming across Markdown, thanks to its usage on Stack Overflow, I'm liking it quite a bit.
I'm thinking about getting the issue tracker to use Markdown instead of BBcode.
In case you don't know what Markdown is, you can check out its syntax here, or have a look at the below example. It's a bit like Wikipedia's markup, actually.
Which in BBcode (NOT SMF FLAVOURED, THIS IS GENERAL) would be:
And what it looks like:
That's somewhat inconvenient though for things like code blocks, so I'm looking at PHP Markdown Extra.
I'm thinking about getting the issue tracker to use Markdown instead of BBcode.
In case you don't know what Markdown is, you can check out its syntax here, or have a look at the below example. It's a bit like Wikipedia's markup, actually.
Code: [Select]
> No I'm not insane
**READ THIS!**
You're all *\*insane\** people, proof:
function are_insane(what)
{
are_insane('[b]yes[/b]');
}
**You guys are therefore all insane.**
Here's some more reasons:
1. You're all stupid
2. Stop huffing kittens
3. Unicorns don't exist, really
/faints
Which in BBcode (NOT SMF FLAVOURED, THIS IS GENERAL) would be:
Code: [Select]
[quote]No I'm not insane[/quote]
[b]READ THIS![/b]
You're all [i]*insane*[/i] people, proof:
[code]function are_insane(what)
{
are_insane('[noparse][b]yes[/b][/noparse]')
}[/code ]
[b]You guys are therefore all insane.[/b]
Here's some more reasons:
[ol]
[list][li]You're all stupid
[/li][li]Stop huffing kittens
[list][li]Unicorns don't exist, really
[/ol]
/faints[/list][/list]
And what it looks like:
Quote
QuoteNo I'm not insane
READ THIS!
You're all *insane* people, proof:Code: [Select]function are_insane(what)
{
are_insane('[b]yes[/b]')
}
You guys are therefore all insane.
Here's some more reasons:
- You're all stupid
- Stop huffing kittens
- Unicorns don't exist, really
/faints
That's somewhat inconvenient though for things like code blocks, so I'm looking at PHP Markdown Extra.
Quote
Fenced Code Blocks
Version 1.2 of PHP Markdown Extra introduced a syntax code block without indentation. Fenced code blocks are like Markdown’s regular code blocks, except that they’re not indented and instead rely on a start and end fence lines to delimit the code block. The code block start with a line containing three or more tilde ~ characters, and ends with the first line with the same number of tilde ~. For instance:Code: [Select]This is a paragraph introducing:
~~~~~~~~~~~~~~~~~~~~~
a one-line code block
~~~~~~~~~~~~~~~~~~~~~
Contrary to their indented counterparts, fenced code blocks can begin and end with blank lines:Code: [Select]~~~
blank line before
blank line after
~~~
Indented code blocks cannot be used immediately following a list because the list indent takes precedence; fenced code block have no such limitation:Code: [Select]1. List item
Not an indented code block, but a second paragraph
in the list item
~~~~
This is a code block, fenced-style
~~~~
27
Announcements / Re: Bugtracker trial
« on: July 09, 2010, 05:04:37 am »Well, this is an old problem but...
I unchecked the "Allow users to email me" box, but they still can.
And it isn't a problem with the tracker.
I've tried copying over some code from the default theme, see if it's fixed now.
EDIT: I apologise to anyone who has previously gotten used to the "View New Posts" position, I've been thrown off as well
28
Announcements / Re: Bugtracker trial
« on: July 08, 2010, 08:37:15 pm »Yes, it now correctly detects that I'm logged in.
You should now implement bug categories, like "Bugs", "Feature Requests", etc.
Also, you could have "recommended" tags, such as "regression", "wanted-r5", "blocking-r4", etc. Think of it as some sort of autocomplete system.
You could also have bug templates. For instance, when creating a new bug, it'd show in the content box "Steps to reproduce", "Expected result", etc.
I think that's pretty much the essential for now.
Recommended tags are something I want to implement after implementing changing ticket severity/tags.
Ticket templates? Later.
You could do much more with the tracker. I've suggested what I thought was the bare essential to make it usable.
Additionally, you'll need:
1. The ability to vote for bugs
2. The "email me when this bug is modified" checkbox (off by default)
3. The "Assigned To" field
4. Division in components(is it a bug in the parser or in the drawing code?)
5. Filters (show only Linux bugs, don't show Linux bugs, etc.)
6. Associate bug with URL(such as forum discussion, game that exposes the problem, etc.)
7. Submit files (test cases, patches, etc.)
THEN, it'll stand a chance to be a good tracker. But I believe my previous suggestions are more important.
1. I'm using Google's idea of starring, although I'm going to try and make it more visible
2. I haven't looked into how to email users
4. Probably will be part of suggested tags
5. Already planned
6. Won't implement
7. I haven't looked into how to upload files
1. I say this one because everybody hates "+1" posts.
Also, regarding "Feature Requests", you already have a feature request tracker, you just don't know it yet.
If anything, a feature request type would make it easier to ignore them.
Also, auto-assign would be interesting. If different people are working on different parts of ENIGMA, then assigning a bug to those parts of ENIGMA would automatically assign it to the person that's working on it, who could then redirect it to someone else if he/she wanted to.
Set the severity to none. There's a reason why I don't explicitly name the tracker the "bugtracker".
Auto-assign? You can remind me when spray's at a later stage of development.
30
Off-Topic / Re: Sandy Duncan and clan
« on: July 08, 2010, 03:46:47 am »
Eww at the new GMC theme.