<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Refactoring on The Mole&#39;s OpenNMS (TM) Dev Diary</title>
    <link>/tags/refactoring/</link>
    <description>Recent content in Refactoring on The Mole&#39;s OpenNMS (TM) Dev Diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 Mar 2019 10:00:00 +0100</lastBuildDate>
    
	<atom:link href="/tags/refactoring/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Running OpenNMS inside Karaf - Some Thoughts</title>
      <link>/posts/development/11-opennms-inside-karaf-first-try/</link>
      <pubDate>Tue, 12 Mar 2019 10:00:00 +0100</pubDate>
      
      <guid>/posts/development/11-opennms-inside-karaf-first-try/</guid>
      <description>The other day I found my self in the lucky position to upgrade Karaf to a newer version. While doing that I also wrote something about our Http Bridge and why it was not be the best decision to integrate Karaf inside Jetty instead of the other way around.
 While implementing the Upgrade I asked my self how hard could it be to get some components of now running from within Jetty to running in Karaf.</description>
    </item>
    
    <item>
      <title>Bootstrap 4 Finetuning</title>
      <link>/posts/bootstrap-4-migration/post-2/</link>
      <pubDate>Wed, 13 Feb 2019 14:00:00 +0100</pubDate>
      
      <guid>/posts/bootstrap-4-migration/post-2/</guid>
      <description>The Bootstrap 4 Migration is about to be finalized. When we showed the work to the community (and also around internally) the feedback was mostly positive. Some pages did not render properly, but besides that the most commonly reported issues were:
   Card Headers use up too much space
  Elements use up too much space in general
  Concerns about the blue as this is supposed to be reserved for OpenNMS Meridian</description>
    </item>
    
    <item>
      <title>Bootstrap 3 to 4 Migration</title>
      <link>/posts/bootstrap-4-migration/post-1/</link>
      <pubDate>Sun, 20 Jan 2019 13:29:25 +0100</pubDate>
      
      <guid>/posts/bootstrap-4-migration/post-1/</guid>
      <description>In OpenNMS we use Bootstrap 3 as a library to help styling web pages. However the style sheets are customized in a way, that they are not bootstrap-compatible anymore.
  Figure 1. Bootstrap 3 Default Theme   Figure 2. OpenNMS customized Bootstrap 3 Theme  As you can see, the custom stylings do not follow the bootstrap &#34;schema&#34;, so each component is either not fully provided (e.g. list stylings or panels), or they are using a different context (The OpenNMS color&amp;#8217;s indicate the severity context, whereas the bootstrap *-info, *-warning, etc.</description>
    </item>
    
  </channel>
</rss>