From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Updated Updxlrator and other changes
Date: Sun, 23 Dec 2012 13:43:47 +0100 [thread overview]
Message-ID: <1356266627.8107.60.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAAiW7Af9ifdV4xW3NonEq9QDkj=-wHgiP43NN3eTqwD5mQdqwA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2961 bytes --]
Hi Jörn,
could you please provide patch files against the current development
tree, so we can review the changes you made more easily.
On Sun, 2012-12-23 at 02:55 +0100, Jörn-Ingo Weigert wrote:
> Hello List,
>
>
> I would like to introduce a "little" modified updxlrator wui for
> actual ipfire 2.11 Core65.
> Because of the changes I made to optimize the code in functionality
> and more conformity to the xhtml 1.0 web-standard to speed up
> rendering process in the browsers, the attached zip-file affected not
> only updxlrator but also the followed parts:
Well, the WUI is not conform to any HTML standard, because too many
people have put their code into it without agreeing on a coding style.
I personally consider this as a full-time job to fix all problem that
there are and so, I don't want to put more time than necessary into it.
Developing a new WUI from scratch is more important to me.
> 1. apache:
> Modified /etc/httpd/conf/loadmodules.conf - enable mod_deflate for
> compression the output files (except graphics) if browser supports it.
> Modified /etc/httpd/conf/vhosts.d/ipfire-interface-ssl.conf - enabling
> compression for whole SSL-Web interface
Yeah, we can accept that one. Please send the patch.
> 2. Theme "ipfire" & "maniac":
>
> Due to performance problems with browser google chrome when in
> maintenance view and having lots of files in updatecache,
> these problems results from some missing and/or not correct declared
> tags in the begin of each page.
> These changes are:
>
>
> - Sending Request-Header Content-Type instead of <meta Content-Type
> [..]> (Recommend by microsoft for IE >= Ver 8)
> - Modified Declaration:
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN'
> 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
> <html xmlns='http://www.w3.org/1999/xhtml'>
> <head>
> ....
>
>
> These changes let perform google chrome like a charm rendering the
> pages within ~15 secs like other browsers (tested with IE9, Opera,
> Firefox in actual versions)
> instead of waiting for minutes ...
In case that does not break anything with older browsers, send a patch
as well.
> 3. Web-UI in general and addons which use the "age"-function from
> general-functions
>
>
> - modified age function to show the time translated, in single and
> plural terms, but only the parts, which make sense.
> Example instead of showing: 0d 0h 47m 15s, it will show now: 47
> Minutes, 15sec. in connection time
I don't think that it makes any sense to print "minutes" instead of "m"
because there is not enough space to do so.
I agree that it makes sense to omit "0d" and "0h".
> The attached file contains the complete folder structure (etc/srv/var)
> and only contain the files I changed / added, so there should be no
> problems when you copy it over / .... hopefully.
Yes there is, because those files have been changed recently.
-Michael
next parent reply other threads:[~2012-12-23 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAiW7Af9ifdV4xW3NonEq9QDkj=-wHgiP43NN3eTqwD5mQdqwA@mail.gmail.com>
2012-12-23 12:43 ` Michael Tremer [this message]
[not found] <CAAiW7AdEsKJB0AKM+x8zBy5Vf5HFEkSstO_hrSMbO8nkX7NrgA@mail.gmail.com>
2013-01-05 12:37 ` Michael Tremer
[not found] <CAAiW7AemvOF5y_pxnSsmy98mJmjOveGfSK2jCZhven1bh=bqwg@mail.gmail.com>
2013-01-28 13:11 ` Michael Tremer
2013-01-28 14:13 Jörn-Ingo Weigert
2013-01-28 15:33 ` Michael Tremer
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=1356266627.8107.60.camel@rice-oxley.tremer.info \
--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