Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Comparing changes

Choose two branches to see what's changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
base fork: jalcine/jalcine.me
base: ace76d82c4
...
head fork: jalcine/jalcine.me
compare: 98d711deff
Checking mergeability… Don't worry, you can still create the pull request.
  • 4 commits
  • 23 files changed
  • 0 commit comments
  • 1 contributor
View
2  .local.vimrc
@@ -1,4 +1,4 @@
set wildignore+=_site,bin,css,js
set wildignore+=tags
-nnoremap <silent> <F3> :call system("bundle exec jekyll build")<CR>
+nnoremap <silent> <F3> :Dispatch! bundle exec jekyll build<CR>
View
14 _config.yml
@@ -2,7 +2,7 @@
name: "jalciné"
author: "Jacky Alciné"
url: "http://jalcine.me"
-description: "A little ol' collection of text and images."
+description: "A little collection of text and images."
timezone: "America/New_York"
source: src
@@ -14,7 +14,7 @@ post:
# Blog specifics.
future: true
-show_drafts: false
+show_drafts: true
relative_permalinks: false
lsi: false
permalink: "/weblog/:title"
@@ -28,7 +28,15 @@ gems:
# Markdown engine.
pygments: true
redcarpet:
- extensions: ["footnotes", "autolink", "strikethrough", "superscript", "subscript", "no_intra_emphasis", "fenced_code_blocks", "with_toc_data"]
+ extensions:
+ - footnotes
+ - autolink
+ - strikethrough
+ - superscript
+ - subscript
+ - no_intra_emphasis
+ - fenced_code_blocks
+ - with_toc_data
# Don't bother with theses.
exclude:
View
5 src/_drafts/age.markdown
@@ -15,4 +15,7 @@ hands or do you attempt to make do with what you have?
Though a bit graphic of an example, the message conveyed is clear: **age is
the leading factor in a lot of decision making**. It can bar
-otherwise-brilliant people from plac
+otherwise-brilliant people from places that could evolve in or prevent those
+requiring the necessary training to grow from obtaining it. There is a bit of
+an evolutionary aspect to things, having them learn on their own, but we've
+mitigated the need for that when we started using medicine.
View
11 src/_drafts/application_design.markdown
@@ -0,0 +1,11 @@
+---
+layout: post
+categories:
+ - development
+ - opinion
+date: 2014-02-21 15:05:08 EST
+---
+
+Creating an application, be it for the Web, mobile or desktop, is easy.
+Creating a *useful*, *focused* and *functional* application for those
+platforms isn't.
View
3  src/_drafts/dotfiles.markdown
@@ -20,4 +20,5 @@ provided below.
I use GNU Bash, the kind of Bash you'd get when shipping with a particular
Linux. I haven't made the attempt to try another shell out of the time capital
it'd require but a few compelling features in shells like `fish` and `zsh`
-pique my curiousity enough to give them another look.
+pique my curiousity enough to give them another look; definitely worth a
+follow up post.
View
8 src/_drafts/everyone.markdown
@@ -1,8 +0,0 @@
----
-layout: post
-title: "Everyone's a Coder"
-date: 2014-02-06 00:28:33 EST
-categories: personal
----
-
-
View
55 src/_drafts/mer.markdown
@@ -0,0 +1,55 @@
+---
+layout: post
+title: "Getting Started With Mer"
+date: 2014-02-18 15:50:32 EST
+categories:
+ - mer
+ - code
+---
+
+[Mer][mer] is an operating system designed for mobile phones and it's the one
+planned for use for [Plasma Active][plasma_active], the OS I'd like to get
+running on my Nexus 4. I've decided to take a dive into building an image for
+my phone in hopes of tinkering and writing apps for the device. Let me tell
+you; this was *not* easy, at least starting off. Getting the **Platform SDK**,
+the SDK required to build the sources of Mer itself, is a bit tricky and isn't
+that straightforward IMHO. Note that [there's two SDKs][mer_sdks], get
+acquainted to this; it really threw me off at first. In my opinion, it should
+be named the **Platform Development Kit**, or a toolchain if anything; but
+hey. There's a brief overview on how to get the platform SDK installed on your
+computer but I've wrapped it into some helper scripts for those who use
+`bash-it`. You can download the [plugin][mer_install_plugin] and
+[aliases][mer_install_alias] from my fork of the [bash-it][bash_it] project.
+With that intact, all one would need to run to get into the SDK is:
+
+```
+mer-sdk-chroot mount
+mer-sdk-chroot enter
+```
+
+I've noticed that sometimes when I run this; I get some issues with `su` not
+being able to access `/bin/bash`. This hampers the SDK and the only way I've
+managed to resolve this is by restarting my system. Right now, I think it has
+something to do with my `/etc/fstab` and `mount` but only more experimentation
+will tell.
+
+## Building An Image
+
+@TODO: Work on building images for ARM devices (i.e.: Nexus 4 & Nexus 7).
+@TODO: Work on using Plasma Active as the base image
+
+## Moving Forward
+
+With this under my belt, I'm looking forward to continue a little project. One
+thing that'd set the biggest chance for Plasma Active would be a means of
+ominpresent storage. It's called `KIO::Cloud`, a series of extensions that
+would make it easy to connect remotely hosted file services like Google Drive
+and Dropbox.
+
+[mer]: http://merproject.org/
+[plasma_active]: http://plasma-active.org/
+[pdk]: https://wiki.merproject.org/wiki/Platform_SDK#Using_the_platform_SDK
+[bash_it]: https://github.com/revans/bash-it
+[mer_sdks]: https://wiki.merproject.org/wiki/Platform_SDK#Mer_platform_SDK
+[mer_install_plugin]: http://url.jalcine.me/1cnipOn
+[mer_install_alias]: http://url.jalcine.me/1kTjAdp
View
12 src/_drafts/minecraft_intro.markdown
@@ -0,0 +1,12 @@
+---
+layout: post
+title: "Minecraft: How I Love Thee"
+date: 2014-02-28 23:56:30 EST
+categories:
+ - gaming
+ - minecraft
+---
+
+I have a confession; probably obvious from the title of this post. I
+absolutely **love** [Minecraft][]. The idea is so awesome and I've spent four
+hours a day just
View
31 src/_drafts/mpris_and_kde.markdown
@@ -0,0 +1,31 @@
+---
+layout: post
+title: "MPRIS and KDE Playing Nice"
+date: 2014-02-23 12:28:08 EST
+categories:
+ - kde
+ - mpris
+ - code
+---
+
+I use [KDE][] and I have a collection of music playing as well as video
+playing applications on my machine (sometimes running at the same time, but
+not playing). For example, I might have [Amarok][] open when I'm offline to
+play my offline collection of music and listen to podcasts as well; but
+switch to [Spotify][] when I get reconnected to play the tracks I have
+in my Spotify collection. The only issue here is that my media control keys
+are currently hard-wired to work with Spotify (since I spend quite a bit of
+time online). That's changed and I've been spending more time offline
+in order to encourage me to go online when necessary. Thus, came the idea of
+creating a sort of multiplexer for all of the `org.mpris.MediaPlayer2`
+services there is.
+
+ * **TODO** Speak about the UI for the multiplexer. It should use QML/Plasma.
+ * **TODO** Speak about hooking it into KRunner's system via a plug-in system
+ * **TODO** Provide a notification icon for the application to embed into the
+ status bar.
+ * **TODO** Provide a plasma widget to show statuses of playing files.
+
+[kde]: http://kde.org
+[amarok]: http://amarok.kde.org
+[spotify]: http://spotify.com
View
19 src/_drafts/rpc.markdown
@@ -1,19 +0,0 @@
----
-layout: post
-title: "Remote Procedure Calling"
-date: 2014-02-09 22:58:00 EST
-categories: development
----
-
-Working on [Wintermute][] has me doing quite the bit of research. That's
-always welcome since I don't do as often as I should. The current bit is on a
-resourceful yet flexible means of [remote prodecure calling][] or RPC, for
-short. Now, the reason why Wintermute would need something like this is mainly
-due to its nature. I want Wintermute to be able to not only run in multiple
-threads (as most modern applications should do), but also in separate
-dedicated processes. They wouldn't also be running on this local machine but
-also hopefully on remote machines and mobile devices as well. Remember the
-idea behind this project to begin with?
-
-[wintermute]: http://wintermute.jalcine.me
-[remote_prodecure_calling]: http://en.wikipedia.org/wiki/Remote_procedure_call
View
33 src/_drafts/shortspeak.markdown
@@ -0,0 +1,33 @@
+---
+layout: post
+title: "Introducing An Idea: Shortspeak for KDE"
+date: 2014-02-21 15:02:40 EST
+categories:
+ - projects
+ - kde
+---
+
+There's quite a few Twitter clients for Linux, more specifically for the GNOME
+desktop, and none really catering (and up to relatively modern standards) to
+KDE. Thanks to the flexibility of choice and an itch to play with the Twitter
+API; I've worked on a dedicated Twitter client using Qt4 and KDE4 APIs. A
+few differences between Shortspeak and Choqok are:
+
+ * **Focused on Twitter**: [Choqok][] aims to be flexible with the ability to
+ add and remove different micro-blogging services. Out of the box,
+ Shortspeak doesn't do this although it'll have the ability to do so once
+ Twitter and the streaming nature is down-packed.
+
+ * **Modern extensibility**: As far as I know, you can only extend [Choqok][]
+ with C++. I'd want to use [SMOKE][] to extend the application using all of
+ the languages that SMOKE can handle. No reason to constrain it to C++.
+
+Below is a light mock-up of what the main stream view would look like:
+![Layout](/images/shortspeak_mockup.png)
+
+The relative layout of the window is fixed to a maximum width of about
+320px; the height's indefinite. The user's avatar is the reference point of
+measure; bearing a square of 64px in length.
+
+[Choqok]: http://choqok.gnufolks.org
+[SMOKE]: http://lmgtfy.com?q=SMOKE
View
1  src/_gist_cache/3930079--22768bb19b1132b30fc003438bb2e061.cache
@@ -1 +0,0 @@
-<html><body>You are being <a href="https://github.com/gist/3930079">redirected</a>.</body></html>
View
1  src/_gist_cache/4618184--2217ec012baeaa673e558c973e39f124.cache
@@ -1 +0,0 @@
-<html><body>You are being <a href="https://github.com/gist/4618184">redirected</a>.</body></html>
View
12 src/_includes/head.haml
@@ -5,17 +5,17 @@
%link{rel:'stylesheet', href:'/css/syntax.css'}
%link{rel: :author, href: 'https://plus.google.com/118415769922038925979/posts'}
%link{rel:'alternative',href:'http://jalcine.me/feed.xml',title:'jackyalciné',type:'application/atom+xml'}
-%meta{itemprop:'name',content:'{{page.title}}'}
+%meta{itemprop:'name',content:"{{page.title}}"}
%meta{itemprop:'description',content:"{{(page.excerpt || site.description) | strip_html}}"}
-%meta{property:'og:title',content:'{{page.title}}'}
+%meta{property:'og:title',content:"{{page.title}}"}
%meta{property:'og:description',content:"{{site.description}}"}
-%meta{property:'og:url',content:'{{ site.url }}{{ page.url }}'}
+%meta{property:'og:url',content:"{{ site.url }}{{ page.url }}"}
%meta{name:'twitter:card',content:'summary'}
-%meta{name:'twitter:url',content:'{{site.url}}{{page.url}}'}
+%meta{name:'twitter:url',content:"{{site.url}}{{page.url}}"}
%meta{name:'twitter:creator',content:'@jackyalcine'}
%meta{name:'twitter:site',content:'@jackyalcine'}
-%meta{name:'twitter:title',content:'{{ page.title }}'}
-%meta{name:'twitter:domain',content:'{{site.url}}'}
+%meta{name:'twitter:title',content:"{{ page.title }}"}
+%meta{name:'twitter:domain',content:"{{site.url}}"}
%meta{name:'twitter:image',content:'{{ site.url }}/favicon.jpg'}
:javascript
var analytics=analytics||[];(function(){var e=["identify","track","trackLink","trackForm","trackClick","trackSubmit","page","pageview","ab","alias","ready","group"],t=function(e){return function(){analytics.push([e].concat(Array.prototype.slice.call(arguments,0)))}};for(var n=0;n<e.length;n++)analytics[e[n]]=t(e[n])})(),analytics.load=function(e){var t=document.createElement("script");t.type="text/javascript",t.async=!0,t.src=("https:"===document.location.protocol?"https://":"http://")+"d2dq2ahtl5zl1z.cloudfront.net/analytics.js/v1/"+e+"/analytics.min.js";var n=document.getElementsByTagName("script")[0];n.parentNode.insertBefore(t,n)};
View
2  src/_layouts/bare.haml
@@ -2,5 +2,5 @@
%html
%head
= "{% haml head.haml %}"
- %body{class: "{{ page.classes }} foo"}
+ %body{class: "{{ page.classes }}"}
= "{{ content }}"
View
10 src/_drafts/kde-and-networking.markdown → src/_posts/2014-02-15-kde-and-networking.markdown
@@ -1,7 +1,7 @@
---
layout: post
title: "KDE and Networking - Thoughts"
-date: 2013-09-03 07:55:15 EDT
+date: 2014-02-15 07:46:34 EST
comments: true
category: kde
@@ -66,7 +66,7 @@ only with Samba, for the moment.
I'm working to bring other remote document storage solutions like Dropbox and
Google Drive natively into KDE using KIO so it's something to look forward
to in coming months. The code will be available on its 0.1 release sometime in
-November.
+March.
## Security
@@ -84,6 +84,12 @@ doesn't happen enough to the casual desktop user of Linux or BSD (given our grow
size) to not be safe. With `clamav`, one can stay relatively secure and
prevent their systems from known infection streams.
+---
+
+When it comes to networking, KDE does it right. KIO is fantastic for
+abstracting network resources as a local file system and the use of Avahi and
+Samba only further enhances that.
+
[1]: http://kde.org
[2]: http://zeroconf.org
[3]: http://telepathy.kde.org
View
21 src/_sass/_colors.sass
@@ -1,4 +1,6 @@
@import 'compass/css3/transition'
+@import 'compass/css3/text-shadow'
+
/** yanked from https://github.com/mrmrs/colors **/
$aqua: #7FDBFF
@@ -25,20 +27,25 @@ $black: #111
$lavender: #9A8FC8
-$background-color: mix($white, $lavender, 70%)
-$foreground-color: mix($black, $lavender, 70%)
+$background-color: mix($white, $lavender, 70%)
+$foreground-color: mix($black, $lavender, 70%)
+
+$link-color: darken($background-color, 75%)
+$link-hover-color: mix($link-color, $black, 60%)
body
background-color: $background-color
- color: $foreground-color
+ color: $foreground-color
a
- @include transition(color 0.2s)
- color: $lavender
+ @include transition(all 0.2s)
+ color: $link-color
text-decoration: none
&:hover
- color: darken($lavender, 50%)
+ @include text-shaodw(2px 2px 2px $link-hover-color)
+ color: $link-hover-color
&:active
- color: darken($orange, 30%)
+ @include text-shadow(2px 2px 2px $orange)
+ color: $orange
View
7 src/_sass/pages/_index.sass
@@ -7,8 +7,8 @@ body.index
text-align: center
width: 100%
height: 100%
- border-left: 0.2rem solid darken($background-color, 40%)
- border-right: 0.2rem solid darken($background-color, 40%)
+ border-left: 4rem solid darken($background-color, 40%)
+ border-right: 4rem solid darken($background-color, 40%)
h1
margin: 0rem
@@ -20,6 +20,8 @@ body.index
border-radius: 49%
width: 14rem
height: 14rem
+ min-height: 14rem
+ min-width: 14rem
margin: 0.5rem
ul
@@ -29,6 +31,7 @@ body.index
li
display: inline-block
+ text-transform: small-caps
&:after
content: '\2014'
color: $gray
View
8 src/humans.txt
@@ -1,8 +0,0 @@
-/* Foundation was made by ZURB, an interaction design and design strategy firm in Campbell, CA */
-/* zurb.com */
-/* humanstxt.org */
-
-/* SITE */
- Standards: HTML5, CSS3
- Components: jQuery, Orbit, Reveal
- Software: Coda, Textmate, Git
View
BIN  src/images/kcm-ufw-shot.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN  src/images/sharing-public-folder.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN  src/images/shortspeak_mockup.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
7 src/js/page.js
@@ -1,17 +1,16 @@
(function(){
- "use strict";
+ 'use strict';
var WebFont = {
google: {
- families: ["Lato"]
+ families: ['Lato']
}
};
var jalcine = {
stickyHeader : {
header: null,
- init : function(){
- jalcine.stickyHeader.header = $('')
+ init : function() {
}
},
init : function() {

No commit comments for this range

Something went wrong with that request. Please try again.