gergely/gergelypolonkai-web-symfony2
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Added new static blog entry. Added new design elements

Browse Source 
Signed-off-by: Gergely POLONKAI (W00d5t0ck) <polesz@w00d5t0ck.info>
This commit is contained in:
Polonkai Gergely 2012-06-26 22:18:26 +02:00
parent 40fee41b41
commit 4728bd29ca
13 changed files with 40 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
src/GergelyPolonkai/FrontBundle/Resources/views/Default/front_base.html.twig
View File

@ -9,10 +9,23 @@
<body>
<div id="content-wrapper">
<div id="header">
<h1>Gergely Polonkai</h1>
<h1><a href="{{ path('GergelyPolonkaiFrontBundle_homepage') }}">Gergely Polonkai</a></h1>
<h2>developer, systems engineer and administrator</h2>
<div id="contact-list">
<a href="mailto:gergely@polonkai.eu" target="_blank"><img src="{{ asset('images/email_16.png') }}" alt="E-mail" /></a>
<a href="http://www.linkedin.com/in/gergelypolonkai" target="_blank"><img src="{{ asset('images/linkedin_16.png') }}" alt="LinkedIn profile" /></a>
<a href="skype:w00dhun" target="_blank"><img src="{{ asset('images/skype_16.png') }}" alt="Skype" /></a>
<a href="http://facebook.com/Polesz" target="_blank"><img src="{{ asset('images/facebook_16.png') }}" alt="Facebook profile" /></a>
<a href="https://plus.google.com/u/1/112207716393987962329/about" target="_blank"><img src="{{ asset('images/google_plus_16.png') }}" alt="Google+ profile" /></a>
<a href="gtalk:chat?jid=gergely@polonkai.eu" target="_blank"><img src="{{ asset('images/googletalk_16.png') }}" alt="Google Talk" /></a>
<a href="http://twitter.com/W00d5t0ck" target="_blank"><img src="{{ asset('images/twitter_16.png') }}" alt="Twitter" /></a>
<a href="http://tumblr.w00d5t0ck.info" target="_blank"><img src="{{ asset('images/tumblr_16.png') }}" alt="Tumblr" /></a>
<a href="msnim:chat?contact=polesz@w00d5t0ck.info" target="_blank"><img src="{{ asset('images/windows_16.png') }}" alt="Windows Live" /></a>
<a href="http://w00d5t0ck.deviantart.com" target="_blank"><img src="{{ asset('images/deviantart_16.png') }}" alt="deviantArt" /></a>
</div>
</div>
<div id="content">
<div id="content-padding"></div>
{% block content %}{% endblock content %}
</div>
</div>

5
src/GergelyPolonkai/FrontBundle/Resources/views/Default/index.html.twig
View File

@ -1,5 +1,10 @@
{% extends 'GergelyPolonkaiFrontBundle:Default:front_base.html.twig' %}
{% block content %}
<h3>Upgrades requiring a reboot on Linux? At last!</h3>
<p class="article-date">22 June, 2012 :: 22:04 by Gergely Polonkai</p>
<p>I've recently received an article on Google+ about Fedora's new idea: package upgrades that require a reboot. The article said that Linux guys have lost their primary adoo: "Haha! I don't have to reboot my system to install system upgrades!" My answer was always this: "You should..."</p>
<p>I think this can be a great idea if distros implement it well. PackageKit was a good first step on this road. That software could easily solve such an issue. However, it is sooo easy to do it wrong. The kernel, of course, can not be upgraded online (or could it be? I have some theories on this subject, wonder if it can be implemented...), but other packages are much different. From the users' point of view the best would be if the packages would be upgraded in the background seemlessly. E.g. PackageKit should check if the given executable is running. If not, it should upgrade it, while notifying the user like "hey dude, don't start Anjuta now, I'm upgrading it!", or simply denying to start it. Libraries are a bit different, as PackageKit should check if any running executables are using the library. Meanwhile, PK should also keep a notification somewhere telling the users that some packages could be upgraded, but without stopping this-and-that, it can not be done.</p>
<p>I know these things are easier said than done. But I think (a) users should tell such ideas to the developers and (b) developers (mostly large companies, like Microsoft or Apple) should listen to them, and at least think of these ideas. Some users are not as stupid as they think...</p>
<h3>Wordpress madness</h3>
<p class="article-date">14 June, 2012 :: 08:40 by Gergely Polonkai</p>
<p>I'm a bit fed up that I had to install <a href="http://www.mysql.com/">MySQL</a> on my server to have <a href="http://wordpress.org/">Wordpress</a> working, so I've Googled a bit to find a solution for my pain. I found this: <a href="http://codex.wordpress.org/Using_Alternative_Databases">http://codex.wordpress.org/Using_Alternative_Databases</a>. I don't know when this post was written, but I think it's a bit out of date. I mean come on, PDO is the part of PHP for ages now, and they say adding a DBAL to the dependencies would be a project as large as (or larger than) WP itself. Well, yes, but PHP is already a dependency, isn't it? Remove it guys, it's too large!</p>

21
web/css/front.css
View File

@ -19,6 +19,8 @@ body {
height: 120px;
background-color: #4d4d4d;
color: #ffffff;
position: absolute;
width: 960px;
}
#header h1 {
@ -29,6 +31,11 @@ body {
padding-top: 45px;
}
#header h1 a {
color: #ffffff;
text-decoration: none;
}
#header h2 {
text-align: right;
margin: 0 10px 0 0;
@ -37,10 +44,24 @@ body {
padding-top: 5px;
}
#contact-list {
position: absolute;
right: -22px;
width: 20px;
}
#contact-list a {
display: block;
}
#content {
padding: 8px;
}
#content-padding {
height: 120px;
}
#content h3 {
margin: .5em 0 .2em 0;
}

BIN
web/images/deviantart_16.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 660 B

BIN
web/images/email_16.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 608 B

BIN
web/images/facebook_16.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 502 B

BIN
web/images/google_plus_16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 529 B

BIN
web/images/googletalk_16.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 867 B

BIN
web/images/linkedin_16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 714 B

BIN
web/images/skype_16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 801 B

BIN
web/images/tumblr_16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 748 B

BIN
web/images/twitter_16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 684 B

BIN
web/images/windows_16.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 805 B