Danny Terweij | LxCenter
unread,Sep 25, 2013, 2:50:40 PM9/25/13Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to lxd...@googlegroups.com
* Moved from github.
Op 25-9-2013 17:22, semirke schreef:
>
> In hypervm/httpdocs/img/loginskin/login_page.css:
>
> > @@ -0,0 +1,81 @@
> > +body {
> > + margin: 0px;
> > + padding: 0px;
> > + color: #333;
> > + background: url(/img/loginskin/polaroid/polaroid.png) repeat;
>
> Danny,
>
> I do not think moving things together will make the project less
> scattered.
> There are and there should be the place for every kind of files we
> use. like I used the image directory to store the image. I put the css
> file there only because Im thinking about letting the user change the
> skin. Which could be easily done by changing loginskin directory to a
> symlink.
>
> Other than that, moving code together fits my opinion. Do you agree?
>
I think all should be at one place, think forward. A theme/skin, in
whatever app you look, had its own dir and from there a standard structure.
We have a dir named /login/ from there the loginpage is started.
Now it loads many from different places.
So make /login/themes/default
.*.html pages
*.php pages
./css
./img
Everything at one place with a structure.
Symlinking is not the way. Ugly.
Just use /login/themes/someother/
You might can do it statictly for the moment, from the main index, set a
variable $loginTheme="default";
Or do it right at once and make a login theme selection at the
Apeariance (that word has a typo hehe) page.
When all files scattererd then skinning is not easy to do for the user.
Make it easy for them.
Danny