EVE Technology Lab

Haha, lovely that people want to use it

But to answer your two questions.
1. The domain tracker isn't ~exactly~ working. Background stuff is sorta, but it's coded like stale ass (i wrote it, so, yeah.. karbocode) And Squizz has been more busy with his girlfriend and the killmail parser.
He'll get to it eventually :)

2. There will be a tutorial on how to use it somewhere. If not on the page, then under the FAQ. If the latter, there will be a link to it.
As for the cname, you just cname it to the main domain itself. zkillboard.com is only a temporary thing. When we're done, it'll all be moved to eve-kill.net


--

To everyone interested, i had a terrible idea earlier tonight, about 30 minutes before Top Gear came on, did it, watched Top GEar, and did some more. This is the result (Yes, it loads slow as ****) http://edkzkb.karbowiak.dk/

zKB with an EDK esque theme. Still working on it, so it looks terrible, biggest issue is making bootstrap do as i tell it, without interfering. Easier said than done

I had already added my api to the site before that kill (just to let you know for eventual debugging purposes).
Btw, now I can see it, everything is updated :-)

Ty

I recently disputed a mail on EVE-Kill and it was removed from there but it still shows up on zKillboard. Is there somewhere else to make a petition/dispute for zKillboard or will all that eventually update as your work progresses?
Absolutely love what you've done with it so far!

First of all great work so far. But there are a few things i miss: (if you already answered them, forgive me i didnt read all Pages carefully and could missed something)

1. I really like the monthly Summary in eve-kill were i can see the Sum of Kill/Losses of this month. I found it really useful and i cant find anything similar in zKillboard.

2. A Total Number of Solo Kill. I can see a list of all solo kills but i cant find the total number wich i should be not to hard for you to calculate.
(I also think that a solo kill is a KM with only 1 player and npc dont count. But since you made you position about this clear i will shut up now :) )

3. As other people sad before i find most of the icons to big and also some space to large. In overall i have to scroll a lot to get the same amount of information as in eve-kill.

But keep up the good work, i really like what you did so far :)

1. The monthly views are coming back, they are already available in the code, but there are still no way to access it from the ui (you can add /month/01/year/2013/ to the end of the url if you want)

2. Total number of solo kills would be a cool idea, if you can suggest it via userreport it'll not be forgotten! :)

3. Big icons are a part of what makes zKB, zKB.. We will however provide an EDK look-alike theme for the site at some point.



a dime a dozen these days? what other killboards are there? lol

pyKB is not exactly working, Kingboard works but only API, BC is horrible, GW is equally terrible and then theres EDK which requires so many modifications just to work.

Not really a lot to choose from :P

But if you like the visuals of zKB, then i'm glad

---

Yesterday we ran into some issues with HDD space starting to dwindle on our database partition, so we added more space, moved zKB to that, but even then, zKB was crazy large.

So Squizz set out to find ways to make it all smaller, some table chances (some int to tinyint etc.) and an innodb row change (From dynamic/compact to compressed) and we went from 92GB in size, to 59GB. 33GB saved

A nice side bonus, it gave the site a little more speed.

edit://
Updated the API documentation for the site, with a few more modifiers and some extra reminders for people using it.

Also we fixed a few bugs with it, pastSeconds, startTime/endTime and orderDirection. Big thanks to Risingson (Creator and developer of Eveeye.com)

edit2://
Risingson discovered yet ANOTHER bug with the API. The expected behaviour without kills or losses set, was to get combined info, which you did unless you added specific arguments. Then it'd return only kills.

Silly error which is now fixed :)

The board will be opensourced, and we will bring more people in to help make more themes (i am currently working on an EDK variant for it for example)

And who knows, we might even devise a system that allows you to use your own self made theme.

And yeah, it's very superior to EDK, in every single way

One of things about the way we've desgined zKB is that the more users using zKB, the faster the site gets overall.

I'm impressed by the new zKB engine and all kudos to the devs and every other contributors whom has participated/participating on the development.

However, without any disrespect towards the web designer. The presentation bothers me a lot (please note that this is merely an opinion, not a fact), it has very low readibility (zKB has literally no focal points placed for readibility) and usability in terms of overall layout goes. The presentation elements/blocks are not placed efficiently and a lot of those elements, including texts are too big to skim quickly. Hopefullly this is not how it'll be in the end, I was looking forward to see how it'll go.

I'll give you an example by comparing two battle report layout from different engine :
Random Battle Report from zKB main site
Random Battle Report from PonyWaffe kb site running EDK 4 with custom theme & modified engine
The point I'm trying to show here is simply that "bigger" isn't always easer to read, and contrast and color distinction can be important to easily separate and applying priority tiers to information presented.

Hope this helps.

Regardless, awesome work!

I was really impressed by the zKB performance in comparison to EDK, so I honestly hope the presentation is going to be far better than EDK as well. I realized it's still in beta, so I'm expecting alot more to come! Great work! (I can't say this enough :P)

As for the PonyWaffe KB, I didn't write those as mods (unfortunately) so it was a direct modification to the .tpl and some of the template process files and minor alteration to the core as well.

Question though, would you guys be releasing the source to public or better yet do you guys have any plans on packing the engine for public consumption later on? I'm sure a lot of us would very much like it if there are plans for doing so.

I understand, and I think it's the right way of doing it. I also think you guys know what you're doing, so there's not much to add there (hence why I only addressed my point of view regarding the layout). Regardless, if you guys need any help with that particular aspect, just give me a poke.