Page 5 of 6
Posted: 26 Oct 2015, 19:33
by zslane
Round 5 Honey needs an entry badly. Carbon is out in the wild now too, right?
Posted: 01 Feb 2016, 12:01
by 7bit
Any chance you can repair your website, so it shows all pre-view images?
Ragnarok was born as a spin-off of the famous 7bit’s Round 4. After the “Blood” keyset was excluded from Round 4, user (Ragnorock)[GK] rescued it and ran a successful group buy.
The color scheme is inspired by the Terran keycap from the StarCraft 2 group buy that the same user organized the year before.
The main set was an 88 keys kit for tenkeyless keyboards but more options were available to cover full, ISO and winkeyless keyboards.
This was probably one of the first sets to include a Windows 8 logo (not common in 2012). It also featured an extra custom enter key reading “Execute”.
This is not really correct.
I've included the BLOOD-style to Round 4, but the original idea was from Ragnorock, so he ran it himself when it became clear that running too many styles and colors are undoable.
Back at the time, I've "sold" group buys from the originally planned Round 4 to other people, who where capable of running them.
Posted: 01 Feb 2016, 14:25
by matt3o
thanks for the heads-up. I'll update that
Posted: 01 Feb 2016, 21:26
by 7bit
Problem solved:
Here is the last visible image:
Code: Select all
<img
width="480" height="300"
src="http://cdn.keypuller.com/2015/01/h22bs7A-480x300.jpg"
class="attachment-thumbnail wp-post-image"
alt="Oktoberfest" />
And here the first non-visible:
Code: Select all
<img
width="480" height="300"
src="http://keypuller.com/wp-content/themes/kp/images/empty-thumb.png"
class="inview wp-post-image"
alt="bluetrade"
data-src="http://cdn.keypuller.com/2015/01/bluetrade-480x300.jpg" />
What I had to do, is removing this element:
Code: Select all
src="http://keypuller.com/wp-content/themes/kp/images/empty-thumb.png"
and replacing
data-src by
src
and replacing
inview by
attachment-thumbnail.
Posted: 02 Feb 2016, 00:11
by matt3o
update your browser
Posted: 02 Feb 2016, 00:27
by 7bit
You wrote bad code and blame other peoples browsers!
This is lame!
Posted: 02 Feb 2016, 00:52
by Muirium
Of course it's lame. You haven't installed a software update in 10 years!
Posted: 02 Feb 2016, 09:02
by matt3o
7bit wrote: You wrote bad code and blame other peoples browsers!
This is lame!
I'm not blaming your browser. I'm blaming your laziness!
Posted: 02 Feb 2016, 09:12
by 7bit
No matter if old or new, but you typed the source code (or copy pastaed it) and deliberately ensured that images are not loaded the normal way, but using some weird JavaScrapt code to load them when scrolling down. Even if I had the latest generation browser, this would be wrong!
We don't use 56k modems anymore, so loading a bunch of higher resolution images is no problem anymore.
Also, your code violates 2 of the UNIX philosophies:
- Keep It Simple Stupid!
- Do one thing and do it well (in this case, your website wants to be fancy, but fails to fulfil its purpose to show fancy keyboards instead)
I really don't understand what your website should be for:
- experimenting whith the HTML and JavaScript
- showing key caps and keyboards
Posted: 02 Feb 2016, 11:11
by matt3o
7bit wrote: We don't use 56k modems anymore, so loading a bunch of higher resolution images is no problem anymore.
this is true, we live in a mobile world where sometimes connection is worse than 56k
(not to mention capped data plans)
btw, I'm working on a code rewrite to make it easier for me (and others) to update the entries. I'll see if I can find a way to be bandwidth conscious keeping JS out of the way (very low priority).
Posted: 02 Feb 2016, 12:29
by 7bit
What is this good for:
Code: Select all
<link
href='http://fonts.googleapis.com/css?family=Oswald' rel='stylesheet' type='text/css'>
And what about this:
Code: Select all
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-53600883-1', 'auto');
ga('send', 'pageview');
</script>
BTW: one way would be: split it up into 6 instead of 3 pages and make a button for "all in one page"-view.
Or make a text browsers version (very simple to create, no CSS and JS required, just use the <a>, <img>, <div> and <html> tags.
This way, the website would be super highly scalable, with extremest speed rendering on any HTML-browser ever made and on any screen resolution you could ever imagine!
Posted: 02 Feb 2016, 12:40
by matt3o
even better, would be nice to have APIs so you can get txt or json only if you want
Posted: 02 Feb 2016, 13:19
by 7bit
I appreciate your attempt to have a catalogue of all key caps ever produced (at least in group buys), but functionality should come before fanciness. But maybe (similar tho the wiki) I'm almost alone when it comes to really using them.
You get extra points if it is possible to list all pages which have a specific color involved.
Posted: 02 Feb 2016, 13:50
by matt3o
working on it... you know... not that anyone is paying or even helping me
Posted: 02 Feb 2016, 14:37
by 7bit
I kiss your feet!
Posted: 02 Feb 2016, 14:40
by Spikebolt
Javascript ain't that bad
Posted: 02 Feb 2016, 15:19
by 7bit
JavaScript should never be used, if the goal can be achieved otherwise. Using JavaScript for everything, shows the lack of being able to use the right tools for the task!
Posted: 02 Feb 2016, 15:28
by matt3o
the world is moving on, 7bit. let's go gopher! Even better, full ascii bbs! Fidonet FTW!
Posted: 02 Feb 2016, 15:33
by 7bit
You are too young to understand the beauty of simplicity!
Posted: 02 Feb 2016, 15:41
by Spikebolt
7bit wrote: JavaScript should never be used, if the goal can be achieved otherwise. Using JavaScript for everything, shows the lack of being able to use the right tools for the task!
It's not that simple, but it's a decent principle. I feel not having to refresh an entire page to update a small part of it is a huge plus.
We don't (and shouldn't) use 56k modems anymore and we shouldn't use ancient browsers as well
Posted: 02 Feb 2016, 16:17
by matt3o
at the core, I agree with 7bit.
Posted: 02 Feb 2016, 16:52
by Spikebolt
At the core pretty much everything can be done without the use of JavaScript! No JavaScript should be added for the sake of adding, but most times you'll either be sacrificing usability or using ancient technology like Flash or... Java Applets
JavaScript is the future guys, don't be afraid to embrace it!
Posted: 02 Feb 2016, 19:05
by Compgeke
matt3o wrote: Even better, full ascii bbs! Fidonet FTW!
That can be done.
Posted: 27 Nov 2016, 17:44
by livingspeedbump
Is there any way to get this back up to date? KeyPuller is definitely a great resource.
Getting keycap sets up to date would be pretty easy I think, artisan caps are a totally different story. Not even sure if that is something you want to do with it still.
I'm more than happy to help/do anything needed if you do want to update it a bit as well!
Posted: 27 Nov 2016, 17:46
by matt3o
I agree, we should bring this back to life!
I'm actually working on a version that it's easier to update, if you have any suggestion for v2 now it's the right time!
Posted: 27 Nov 2016, 17:59
by livingspeedbump
Awesome! Fortunately it has actually managed to remain quite relevant as it does a great job of documenting sets that aren't very easy to find info on these days.
The only thing I can really think of off the top of my head is making a decision on if you even want to keep up with artisan stuff, or really just keep the "archived" stuff already on the page, or just keep up with Clack, etc. I feel like these days you can't open a forum without seeing 3 new people crafting keycaps, so it really may be like treading water trying to maintain that part.
Posted: 27 Nov 2016, 18:00
by livingspeedbump
If you'd like I can try to compile a list of sets and color codes/profiles/etc for you though so you don't have to worry about reworking the site and content all at the same time.
Posted: 27 Nov 2016, 20:17
by matt3o
I agree it is very hard to keep up with the artisan stuff, ideally each designer should post its own stuff... I'd say to give priority to more "official" stuff but don't close the doors to artisans.
by all means if you want to start compiling a list of the missing sets, please proceed
Posted: 28 Nov 2016, 22:50
by livingspeedbump
matt3o wrote: I agree it is very hard to keep up with the artisan stuff, ideally each designer should post its own stuff... I'd say to give priority to more "official" stuff but don't close the doors to artisans.
by all means if you want to start compiling a list of the missing sets, please proceed
Will do, I will get all the information I can, including some pictures with permission where possible and dump them into a dropbox or google folder I can share with you.
Posted: 06 Jan 2017, 17:57
by GEIST
matt3o wrote:
I'm actually working on a version that it's easier to update, if you have any suggestion for v2 now it's the right time!
It would be great if you could tag and search for color names instead or additional to the SP color codes.
