chicisimo/propane-theme

one does not simply like Campfire's UI

Propane Theme

one does not simply like Campfire's UI

Setup

First, clone the repo:

$ git clone https://github.com/chicisimo/propane-theme.git <target directory>
$ cd <target directory>

Then, run this command to deploy the default theme to Propane (you'll have to reload the room):

WARNING: This command will remove your current propane files, so backup them if you will.

$ script/bootstrap

And you're done!

Customization

Besides, you can add your own style customizations to the default theme and make it more personal

$ script/new_person <your nickname>

The command above creates a folder into people with your nickname and creates all the style files that are in the default folder, ready to be extended (using scss). Once you have added your customizations, run this command to deploy them to Propane (you'll have to reload the room):

$ script/bootstrap <your nickname>

You will need to run the bootstrap command after each customization to deploy it.

For example, if I wanted to change the background color to a darker one, this would be the flow:

$ script/new_person juanxo # Only necessary the first time to create my personal folder
$ vim people/juanxo/styles/cf_chat.scss

@import "../../default/styles/cf_chat"; // This is there by default to import the default styles

$main-dark: #333;

.night-mode {
  background-color: $main-dark !important;
  color: #fff !important;

  .Left .col, #Container {
    background: $main-dark !important;
  }

  table.chat {
    tr, td.person, tr.kick_message td, tr.enter_message td {
      background: $main-dark !important;
    }

    td.body, td.person, tr.kick_message td, tr.enter_message td {
      border-color: $main-dark !important;
      border-left-color: lighten($main-dark, 5%) !important;
    }
  }
}

$ script/bootstrap juanxo

Then, share your theme 🤘

Enjoy hacking!

propane-theme's Issues

Allow script customization

Now that we have styles customization rolled out, we should focus on how to do the same for scripts.

I envision separating all the responders and things like that in each own module, with common modules, like JsonP requests and things like that.

How would someone customize his scripts?

I would like to have something like this in the custom file:

Campfire.featureToggles = {
  avatars: true,
  linkExpander: true,
  audio: false,
  ...
};

// require/concat/whatever modules

// Custom modules go here
...

This allows to, in the future, get the featureToggles out of this and into a centralized system where they can be toggled and added

Walle say "good day" at night

I`ll try to fix it :)

Theme history messages window

Is it possible to theme the window which appears when I click in "See messages from earlier today" ? (on the top)

It has the default theme.

Auto-install npm

When I run the script/bootstrap, I get this:

script/bootstrap: line 10: npm: command not found
script/bootstrap: line 11: npm: command not found

We should auto-install npm as we're doing with bundler.

ping @juanxo

Transform `code` blocks ala Markdown

e.g:

I think we should check this: `userOfId(new TenantId())`

should be transformed to:

I think we should check this: userOfId(new TenantId())

maybe different font (fixed one), whatever

change architecture to allow for modularization and customization

Currently, customizing propane to your own preferences sucks a little bit. You are rather much stuck with the design and modules this theme ships with (and everybody knows that @pedrogimenez knows shit about design...)

My plan is to shamelessly steal the boxen idea of having people specific files, where you extend or modify the default settings.

Also, to improve modularization, I would like to use scss and browserify or something similar to concatenate files and create custom builds. I will post an example of the process

Improve design of messages directed to me

Update README

gem install bundle

Error running the script

When I try to use the script to add the theme to Propane I get this error:

script/bootstrap: line 5: bundle: command not found

Should I install that gem before?