LÖVE

Robin wrote:

BlackBulletIV wrote:I don't by "Build" nevon meant compile? (Is this what you were thinking of?)

No, I didn't mean that. I simply meant to raise the issue of disk space.

It shouldn't be too much of an issue if you set an expiration time on every executable produced, like 24 hours or something, afterwards deleting them.

Robin wrote:

BlackBulletIV wrote:Also, this would most certainly need to be implemented as a side task, as in, spawned by the request, not part of the request processing. The user would then be notified with a download link by some means.

Interesting. I think that depends on how long the processing typically takes. Especially for only a single platform, it could be ready within the blink of an eye.
Also, congrats on the 700!

It'll most likely be very quick for a single platform, although copying the LOVE executable doesn't happen instantaneously, for me anyway.

And thanks! I didn't even notice, lol.

Alright. Version 0.1 of the front-end is done. I've only made styles for the actual form part. The download page (if any) will have to be done later. There's no Javascript written, because I hate Javascript. I've based the whole shebang off of Paul Irish's HTML5 Boilerplate + 960 grid (16 column version). There's quite a bit of crap that can be cleaned out, but I'll leave that up to someone else.

Anyway, enjoy! If you're too lazy to download, you can view it here.

EDIT: Apparently it looks like shite in Firefox 3.6. I'll have to have a look at that.

Is it planned to have a option to make a .love as zip file only creation (no exe/binary attached) ?

TsT wrote:Is it planned to have a option to make a .love as zip file only creation (no exe/binary attached) ?

Why? You already have a .love.

Fixed the Firefox issue.

nevon wrote:Fixed the Firefox issue.

Excellent.

Got the first little bit of Javascript in there. You can now add and remove icon upload inputs dynamically.

There's a weird bug where the first icon upload list item is like 2px wider than the rest. If anyone could figure out why the hell that is, I will give them a virtual high five.

I couldn't see it. It's probably something in the css?

I did find a bug though! If you remove the default icon field and then try to 're-add' it, the "that's enough icons" dialog shows. Fix = remove the remove button for the default icon field?

Shouldn't the binary selection be a radio button?

Lafolie wrote:I did find a bug though! If you remove the default icon field and then try to 're-add' it, the "that's enough icons" dialog shows. Fix = remove the remove button for the default icon field?

Will fix when I get home.

thelinx wrote:Shouldn't the binary selection be a radio button?

Maybe. My reasoning was that you might want both an SELÖVE version and a vanilla version (and possibly other version in the future). But now that I think about it, that's probably unlikely, and enforcing a single binary version may be a good idea for the sake of the server. If you really, really want both, I suppose you could just do it twice.