public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New IPFire theme
Date: Tue, 10 Feb 2015 18:08:04 +0100	[thread overview]
Message-ID: <1423588084.2984.27.camel@ipfire.org> (raw)
In-Reply-To: <CAGouzNZqY3+Nz6o+4+GMw0NJPEKN+4pHVRgMQpy9TCPSHtMstA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

Hey,

thanks for the notice. I think this looks really great.

On Tue, 2015-02-03 at 10:22 +0100, houseofdreams wrote:
> Hi,
> 
> 
> On the IPFire forum page
> (http://forum.ipfire.org/viewtopic.php?f=27&t=12391) I have added a
> theme that I mady originally for myself, but other people seem to like
> it, 
> 
> 
> The original IPFire theme is nice, but I was looking for a full-width
> theme. As I couln't find that, I decided to see if I could make one
> myself, as I have a long background in webdevellopment.

We can of course include this these as an alternative to the default
theme.

> I also edited the clwarn.cgi file, but as it's not actually part of
> the theme itself, it could possibly be overwritten by a next update?

I am not too sure about this. The error messages generated by the URL
filter are using a perl template engine. If clwarn.cgi doesn't do the
same thing we should change that, too.

> I wanted to theme the proxy error page, but as this is located even
> further in the source code, I am hesitating to do this, for the same 
> reason of loosing changes by an update. I hope this makes sense?

Yes of course. We should work on getting these files into the
distribution them.

> Stefan Schantl mentioned I should send a mail to let the devellopment
> team know I was working on a new theme. 

Right. Are the sources for this available somewhere? The best option
would be a Git repository somewhere with a branch which I can pull from.

-Michael

> 
> 
> Kind regards,
> 
> 
> Broos Gert
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

           reply	other threads:[~2015-02-10 17:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAGouzNZqY3+Nz6o+4+GMw0NJPEKN+4pHVRgMQpy9TCPSHtMstA@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1423588084.2984.27.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox