I was thinking of working on a admin side of phpix. nothing fancy but just having the ability to change themes and latter when the security stuff gets figured out the ability to admin users.
I think it would be nice to move everything that the user can configure into one file. Table size, colors, fonts, blah, blah. The reason I suggest a template.inc instead of a style.css is becuase you can define more. For example in a template.inc you could define all the variables like a header, footer stuff, table variables, as well as theme type stuff. You could also have the ability to set different security setting in that file.
I would suggest have a template.inc in the root of phpix, then have the ability to have a different template.inc in subdirectory to define a different look, different security, etc. Phpix could say if template.inc exists in subfolder blah, blah and if it's not there just use the main one.
I really like the stylesheet idea, I just think we could fit more, and make it alittle simpler by using something besides a style sheet.
Either way I'd like to start messing around with a admin interface after it gets alittle more solid.
Keith
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure this is a good idea myself. I _like_ the current setup. Sure, config.inc could be expanded to include some more control over the actual construction of the page, but I don't see why it should also replace style.css. It would be difficult to give all the power of a stylesheet without using one, and if you had to include stylesheet info in the config.inc, why not just make it a seperate file.
config.inc could be expanded to include stuff like headers and footers, templates to include etc. Those things cannot be done with a stylesheet. But then you still want to be able to control how it _looks_ with a stylesheet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Keep in mind I'm by no means an expert. It might be I just don't understand that structure that well, or it might be my preferance, but I like to keep things as simple as possible.
Right now the way I understand it we have these files:
config.inc = it defines some phpix variable, locations and that sort of thing.
style.css = From what I understand this can only define html type variables that do with style. Like color, font, background, etc. From what I understand it can't define table size, weather to inlcude a header, footer, or php type variables.
?? = I've also heard chatter about having other configuration type files for security, or additional configuration options, either site wide, or on the sub folder level.
What I propose is this:
config.inc = for backend function type stuff. Basically what it's doing now.
template.inc = This to replace style.css. If we do this we have 2 major advantages. The first is we can make it easier to understand. For example:
####Background Color for Page#####
bgcolor = #ffcc99
####Table width (you can define pixel or percent
tbwidth = 90%
That to me is alot easier to understand than a style sheet. Then we have the additinl benifit of adding php type information, for example:
####Open to public 1=yes 0=no#####
public = 1
####Image Sizes avaliable######
size=640X480,800X600,origional
I think in the longs run this might be better becuase we won't have to worry about a buch of additional files. This can also easily work on sub direcoties, we just tell it to look at the root/template.inc if not defined in current directory. That would give us the ability to have a template.inc in a sub folder that just said "public=0" or only change one item rather than having a full style.css.
Anyways that's just my suggestions. It might be more trouble that it's worth but it would definalty make it easier in the long run to control things, and for crappy hackers like me to edit. It would also make a web admin.
My 2 cents :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You don't see though. CSS is not just colour, font and background. It's a full layout language. Without changing a line of html, I could enable and disable sections of the display, move them around, etc.
take a look at http://wuzzle.org/photos and click on the halloween2000 set, to see what I mean. This is using the same config as the rest of the site, but a different stylesheet. I removed the navbar, and the size adjust, etc. (I'm not sying it's a good change, it's just to show you what can be done, and it's not even scratching the surface)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-01-09
Yes, what Bryan said :-)
The style sheet should control how it looks visually: if you changed all the letters and pictures into single-color blocks, the style sheet should determine what the page would look like (where the blocks would be, how big, what color, whether or not they're visible). config.inc would control what the letters and pictures actually *are*.
Of course, this analogy fails for certain aspects of the visual presentation, such as how many pictures there are per page, etc., but that's more a content decision than presentation, anyway.
Think of it this way: if you didn't like the default "google-y" looking colors and layout, and you wanted your album to look more like the one on wuzzle.org, you could just steal his style sheet (and a few graphics) and not have to change anything at all about your config.inc. As a matter of fact, it would be spiff if I could include a couple of style sheets with the distribution, so people could play with that.
What would be *really* cool is if the user could select what style sheet they want, and have PHPix remember that in a cookie. But based on the comments I've seen, what would be cooler is a way to have PHPix just be installed once, and work for multiple users. :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was thinking of working on a admin side of phpix. nothing fancy but just having the ability to change themes and latter when the security stuff gets figured out the ability to admin users.
I think it would be nice to move everything that the user can configure into one file. Table size, colors, fonts, blah, blah. The reason I suggest a template.inc instead of a style.css is becuase you can define more. For example in a template.inc you could define all the variables like a header, footer stuff, table variables, as well as theme type stuff. You could also have the ability to set different security setting in that file.
I would suggest have a template.inc in the root of phpix, then have the ability to have a different template.inc in subdirectory to define a different look, different security, etc. Phpix could say if template.inc exists in subfolder blah, blah and if it's not there just use the main one.
I really like the stylesheet idea, I just think we could fit more, and make it alittle simpler by using something besides a style sheet.
Either way I'd like to start messing around with a admin interface after it gets alittle more solid.
Keith
I'm not sure this is a good idea myself. I _like_ the current setup. Sure, config.inc could be expanded to include some more control over the actual construction of the page, but I don't see why it should also replace style.css. It would be difficult to give all the power of a stylesheet without using one, and if you had to include stylesheet info in the config.inc, why not just make it a seperate file.
config.inc could be expanded to include stuff like headers and footers, templates to include etc. Those things cannot be done with a stylesheet. But then you still want to be able to control how it _looks_ with a stylesheet.
Keep in mind I'm by no means an expert. It might be I just don't understand that structure that well, or it might be my preferance, but I like to keep things as simple as possible.
Right now the way I understand it we have these files:
config.inc = it defines some phpix variable, locations and that sort of thing.
style.css = From what I understand this can only define html type variables that do with style. Like color, font, background, etc. From what I understand it can't define table size, weather to inlcude a header, footer, or php type variables.
?? = I've also heard chatter about having other configuration type files for security, or additional configuration options, either site wide, or on the sub folder level.
What I propose is this:
config.inc = for backend function type stuff. Basically what it's doing now.
template.inc = This to replace style.css. If we do this we have 2 major advantages. The first is we can make it easier to understand. For example:
####Background Color for Page#####
bgcolor = #ffcc99
####Table width (you can define pixel or percent
tbwidth = 90%
That to me is alot easier to understand than a style sheet. Then we have the additinl benifit of adding php type information, for example:
####Open to public 1=yes 0=no#####
public = 1
####Image Sizes avaliable######
size=640X480,800X600,origional
I think in the longs run this might be better becuase we won't have to worry about a buch of additional files. This can also easily work on sub direcoties, we just tell it to look at the root/template.inc if not defined in current directory. That would give us the ability to have a template.inc in a sub folder that just said "public=0" or only change one item rather than having a full style.css.
Anyways that's just my suggestions. It might be more trouble that it's worth but it would definalty make it easier in the long run to control things, and for crappy hackers like me to edit. It would also make a web admin.
My 2 cents :)
You don't see though. CSS is not just colour, font and background. It's a full layout language. Without changing a line of html, I could enable and disable sections of the display, move them around, etc.
take a look at http://wuzzle.org/photos and click on the halloween2000 set, to see what I mean. This is using the same config as the rest of the site, but a different stylesheet. I removed the navbar, and the size adjust, etc. (I'm not sying it's a good change, it's just to show you what can be done, and it's not even scratching the surface)
Yes, what Bryan said :-)
The style sheet should control how it looks visually: if you changed all the letters and pictures into single-color blocks, the style sheet should determine what the page would look like (where the blocks would be, how big, what color, whether or not they're visible). config.inc would control what the letters and pictures actually *are*.
Of course, this analogy fails for certain aspects of the visual presentation, such as how many pictures there are per page, etc., but that's more a content decision than presentation, anyway.
Think of it this way: if you didn't like the default "google-y" looking colors and layout, and you wanted your album to look more like the one on wuzzle.org, you could just steal his style sheet (and a few graphics) and not have to change anything at all about your config.inc. As a matter of fact, it would be spiff if I could include a couple of style sheets with the distribution, so people could play with that.
What would be *really* cool is if the user could select what style sheet they want, and have PHPix remember that in a cookie. But based on the comments I've seen, what would be cooler is a way to have PHPix just be installed once, and work for multiple users. :-)
ok. it was just a suggestion. Man I need a bandaid now.
I'd still like to mess with a admin interface though but i'll continue that discussion in the mailing list