'Re: [Owncloud] Theming and Formfactors'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       owncloud
Subject:    Re: [Owncloud] Theming and Formfactors
From:       Tom Needham <tom () owncloud ! com>
Date:       2012-02-01 15:34:58
Message-ID: EA834CA3-D48A-4CA1-9F89-F99C6743E421 () owncloud ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

> The idea is to support theming in ownCloud to make this kind of =
changes easiert.

This would be very handy :)

> Formfactors:
> All parts of the core and every app has a template, a js and a css =
folder. We could extend the templating and the js/css loader that it =
first looks for a foo-mobile.php template if the app wants to load the =
foo.php template and the current formfactor is "mobile". If it finds the =
file it loads it. If not if falls back to the default foo.php. The same =
logic for the js and css files.
> By doing this we don=B4t have to implement the complete interface =
right now for all formfactors. We can do this over time. And if one App =
developer want=B4s to provide a special tablet optimized css he just add =
an additional css with this special name and it=B4s automatically used.

I was thinking along similar lines too. Are we still looking to use =
jQuery mobile for the mobile framework?

> Theming:
> I propose a similar system for the theming. We add a "theme" config =
option to the config.php so that the theme can be configured during =
deployment and controlled from the outside without the need to =
understand our database structure.
> We add "themes" directory into /core where every theme has a directory =
named after the theme name.
> The template and css loader looks into the selected theme directory =
first for templates and css files and loads them if a file is present. =
If not it just falls back to the default files in the individual app =
directories. This has the benefit that the person who creates the themes =
can override what ever has to be changed but don=B4t have to provide a =
complete new frontend.
> The directory structure inside the themes folder is the same as the =
rest of owncloud. This means that a theme developer can just put a =
different "apps/contacts/css/styles.css" in the theme directory to =
change the style of the contacts app.

Sounds good. Where should we store / develop themes? Something similar =
to app.owncloud.com would be cool, but maybe just a git repo would do =
for now.

Also should we have a similar interface to 'Apps' in the admin where =
users can select the theme and/or upload new ones?

Tom

Tom Needham
tom@owncloud.com

[Attachment #5 (unknown)]

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space; "><blockquote type="cite"><div>The idea is to \
support theming in ownCloud to make this kind of changes \
easiert.<br></div></blockquote><div><br></div>This would be very handy \
:)<div><br></div><div><blockquote type="cite"><div>Formfactors:<br>All parts of the \
core and every app has a template, a js and a css folder. We could extend the \
templating and the js/css loader that it first looks for a foo-mobile.php template if \
the app wants to load the foo.php template and the current formfactor is "mobile". If \
it finds the file it loads it. If not if falls back to the default foo.php. The same \
logic for the js and css files.<br>By doing this we don´t have to implement the \
complete interface right now for all formfactors. We can do this over time. And if \
one App developer want´s to provide a special tablet optimized css he just add an \
additional css with this special name and it´s automatically \
used.</div></blockquote><br></div><div>I was thinking along similar lines too. Are we \
still looking to use jQuery mobile for the mobile \
framework?</div><div><br></div><div><blockquote type="cite"><div>Theming:<br>I \
propose a similar system for the theming. We add a "theme" config option to the \
config.php so that the theme can be configured during deployment and controlled from \
the outside without the need to understand our database structure.<br>We add "themes" \
directory into /core where every theme has a directory named after the theme \
name.<br>The template and css loader looks into the selected theme directory first \
for templates and css files and loads them if a file is present. If not it just falls \
back to the default files in the individual app directories. This has the benefit \
that the person who creates the themes can override what ever has to be changed but \
don´t have to provide a complete new frontend.<br>The directory structure inside the \
themes folder is the same as the rest of owncloud. This means that a theme developer \
can just put a different "apps/contacts/css/styles.css" in the theme directory to \
change the style of the contacts app.</div></blockquote><br></div><div>Sounds good. \
Where should we store / develop themes? Something similar to <a \
href="http://app.owncloud.com">app.owncloud.com</a> would be cool, but maybe just a \
git repo would do for now.</div><div><br></div><div>Also should we have a similar \
interface to 'Apps' in the admin where users can select the theme and/or upload new \
ones?</div><div><div apple-content-edited="true"><br></div></div><div \
apple-content-edited="true">Tom</div><div apple-content-edited="true"><br></div><div \
apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: \
separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; \
font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: \
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; \
white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: \
0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; \
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; \
">Tom Needham<br><a href="mailto:tom@owncloud.com">tom@owncloud.com</a><br><br><br></span>
 </div>

<br></body></html>

_______________________________________________
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud

[prev in list] [next in list] [prev in thread] [next in thread] 