Sarah Schneider wrote:Squizz Caphinator wrote:Sarah, thanks for your feedback. Just so you know, we aren't going for "bigger is better". The bigger look is just a side effect of bootstrap.
Also, that battle report page will be getting some major love as it is far from complete. None of us are happy with the way it works atm, but its there as a placeholder until we get around to the presentation.
Nice mods on that PonyWaffe site, I haven't seen those before.
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.
zKB is a crazy performer, simply stunning, and it seems to only get faster, eventho we're filling it with more and more mails
As for you modifications of the tpl files, i really, really like them. Hell, i might even be willing to tell you to start making zKB look equally as good
As for your question, yes we plan on making the source public (open source but with a slight restrictive license, you can see it on the information page if you want).
As for using it as an pilot, corp or alliance killboard, you'll be out of luck. Atleast initially.
We are coding zKB specifically for EVE-KILL, and the usage it'll see there. So we havn't given any thought to people who want to use it for their corp or alliance.
That having been said, we want to rectify this down the road, but eve-kill is first priority atm, and will be so for quite some time.
HOWEVER! Everyone is free to help develop the project further, and make it even better in every possible way.
But we'll have way more information about how, when why etc. etc. etc. when we get closer to open sourcing it
