die() has never worked for me under xampp but exit() works just fine and one is meant to be an alias of the other
For some reason my portfolio site's source files folder weights more than 8GB. What the heck.
On the topic of domain names ( like two pages back, but whatever ), Valve must be pissed. As steam.com honestly isn't being used at all, even though Valve has probably offered them thousands for the domain.
oooh that's nice
not really waywo, but I found this while looking through MyBB codes
I don't really know why I'm posting, but I remember some sex joke codes from fp
however, this is php - where shit like exit is not a function but rather a fucking language construct (wtf)
Currently I have http://keysle.com/tagged/project as my layout for showcasing my projects.
How should I organize my projects page? I've thunk on this for 2 weeks straight.. holding off many of my projects. I'm just gonna ask for some help.
I just need a design concept. That's all
I want to be able to sort the projects by "importance", "type (game/website/software)" & "date"
So please consider that in your suggestion.
I want the projects to have a thumbnail for people to preview. So that's going to take up some space.
I want people to be able to click on one project and expand it on the same page.
There will be 5 data members to each project
download link / link to site
extra links (youtube, website redirects, fanpages, etc)
Also. What are some good colors for innovation? I was thinking white (majority) tangy orange hints and aquatic blue hints.
Consider having a look around here for a few ideas.
You might want to go with a brighter overall theme for your site, a light neutral background (with a texture if you wish) The structure of your page seems fine, it just needs to be easier to look at.
HTML email development is like stepping back 15 years in time.
- Snip -
Wrong WAYWO. Sorry, I don't belong in this dominion.
I have to say GIT is the shit. Now I can test locally, if successful push to the master and then run a git pull on the live web server. I take it most of the professional web devs have a similar method.
I'd love to hear how you test and push code.
Been working on a website to run those forum roleplay civ's they do over in Fast Threads. Little gif showing a days progress.
What exactly was the purpose of using a gif?
Been working on rewriting LethalDrive's control panel, in Ruby on Rails no less. My main goal is to use the latest technologies available and increase responsiveness as much as possible, so I've been using Faye pub/sub messaging for server<->server and server<->browser communication. All the logic for server types (e.g. Teamspeak, Minecraft, TF2) is defined in the code rather than in scripts and the database and such, all you have to do is derive from the main Service class and define your methods. Defining a job for a service, say the stop method for a Minecraft server, is as simple as this:
class MinecraftServer < Service extend JobManager # other definitions and crap. define_job :stop def do_stop(job) configure_screen if screen_started? job.send_message "Stopping server" screen_command "stop" # Safe stop command for Minecraft time = 0 while screen_started? and time < 10 do time += 1 if time == 5 then job.send_message "Forcing termination in 5 seconds." end sleep(1) end if screen_started? job.send_message "Server was terminated." screen_kill else job.send_message "Server safely stopped." end self.started = false self.save else job.send_message "Server is already stopped." end end end
Then I just call service.call_stop from my controller and it creates the job, messages the remote worker via Faye, and then the remote worker sends messages back to the browser which pop up as notifications. I've also implemented PJAX so only the middle content reloads with a fade, rather than the entire layout reloading. (GitHub's repo browser uses this, but with sliding)
Another cool thing I've put in is the live metrics of the node's performance, they smoothly shift to their values with new data coming in every second.
Right now the node statistics is an AJAX request that's running on an interval, with a worker collecting statistics every second on the node and saving them to the database. I'm thinking I could save both on database load and webserver load by having the statistics worker just send the data over a Faye channel to any subscribed browsers rather than querying the hell out of the database and having the webserver have to handle so many requests, so I'm probably gonna go implement that now. I'm planning on storing the statistics as well, but they don't need to be every second, so I'll likely just sample over time and save that every 10 seconds or so.
what about memcached?
The design looks pretty sweet, but I'm not feeling those black-on-black icons in the header of the content columns.
Simplpan by Kaasper. I did theme it a little bit for LethalDrive though.
I implemented the Faye message for node statistics and it works perfectly, the browser is constantly receiving new node statistics and slowly animating those bars to match it. Now to get the console working.