Search This Blog

Jazoon 2007: Magnolia product presentation

The chronology of this post isn't entirely correct, but I went to one product presentation last night, being Boris Kraft's Magnolia presentation. There weren't too many attendees (mostly likely because of late announcement), but it was still a nice presentation.

I spent a lot of time with Magnolia last year and the year before, and I have to say it is quite impressive to see how far they have come since Magnolia 2.0 in the recent 3.1 version. The user interface is much nicer, Document Management, lots of new paragraph types, workflow stuff, as well as a pretty slick site-designer for the enterprise version, just to mention a few new features.

And in my personal opinion, the price isn't bad compared to other proprietary CMS'es, and you still get a long way with the open source version. From a few years back their number of reference projects has been multiplied by the hundreds, and traffic on Magnolia-powered sites all in all is probably sky-high by now.

I've exchanged a fair number of mails with Boris and Magnolians in the past, so it was great to finally meet him. After the presentation we got some free beer (and expensive cola) and talked about open source, system development, Switzerland and puppetry, amongst other things. After he had to go home to Basel, we (the Objectware lads) headed out to town! Zurich by night is a fun place indeed :)

Get link

Facebook

Twitter

Pinterest

Google+

Email

Other Apps

Labels

Popular posts from this blog

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

config-atom.git -> ~/.atom/*

config-mr.git -> ~/.mrconfig -> ~/.config/mr/*

config-tmuxinator.git -> ~/.tmuxinator/*

config-vim.git -> ~/.vimrc -> ~/.vim/*

config-bin.git -> ~/bin/*

config-git.git -> ~/.gitconfig

config-tmux.git -> ~/.tmux.conf

config-zsh.git -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…

Disclaimer: I do not recommend using earphones while on your bike, but there are times or roads where I think it's OK. Pull out your earphones when nearing potentially dangerous situations (like intersections). At least pause the audio.
These tips also apply to anyone unable to look at and touch their device, leaving voice commands their only option (useful for visually impaired people, people wearing thick gloves, etc).
First of all, you need an Android with a fairly new version of Google Now installed, like Lollipop. You'll need a headset with a microphone button. I’ve got an iphone headset that works great with my old Moto G, excluding the volume control.
You need to make sure that a connected headset can bypass the device’s lock mechanism. It’s in:
Settings -> Language & input -> Google voice typing -> Hands-free
Your audio playback software has to work with the Google Now commands. I’ve tried Google Music and BeyondPod successfully.
So, off we go! You’…