Suggestion: Re-arrange the project file(s)

[GoogleCodeExporter]

An idea - separate the code itself from any styling and settings.

1) Offer to users to place the project into a single folder, i.e. "phpLiteAdmin"

2) Move all the settings into a separate file, i.e. "config.php".
   Require the settings by:
   require("./config.php");

3) Add a "Theme setting" into the configuration:

   // Theme (Skin) Style
   $theme = "default"; // Available: "default" or "retro"

4) Create a separate CSS file, i.e. "default.css",

5) Move the built-in style rules into the "default.css" file.

6) Create an additional style file: "retro.css" and fill it with the "retro" 
theme rules.

7) Connect the "Theme" setting to the HTML code:

<!-- begin the customizable stylesheet/theme -->
<link href="<?=$theme?>.css" rel="stylesheet" type="text/css" />

8) Create a "index" redirector file in the "phpLiteAdmin" folder:

index.php:
<?php
require("./phpliteadmin.php");

Original issue reported on code.google.com by vvotintsev@gmail.com on 14 Apr 2011 at 7:40

[GoogleCodeExporter]

2) Yeah, this will become available in v2.0 of phpLiteAdmin, as outlined in the 
roadmap.
3) We also plan on having the theme system more modular to allow different 
layouts/colors/etc
8) We could do that...

Original comment by ian.aldr...@gmail.com on 15 Apr 2011 at 5:16

[GoogleCodeExporter]

Hi.
Look at the attached archive.
May be this can help just a little...

Good luck!

Original comment by vvotintsev@gmail.com on 15 Apr 2011 at 1:36

[GoogleCodeExporter]

I don't see any attachment.

Original comment by ian.aldr...@gmail.com on 15 Apr 2011 at 3:18

[GoogleCodeExporter]

These are good suggestions for the project if it were to become like phpMyAdmin 
- many files, lengthy installation, slightly bloated.

But I think phpLiteAdmin should stay as a single file, portable, quick solution 
for people who want to quickly manage their SQLite databases. SQLite is a 
flat-file, lightweight database system, as should be the tool to manage it. 

I want people to be able to download the file, make some quick variable 
assignments, upload it to their server, and start using it right away. It's the 
way I would want my software to work.

I implemented a theme system where the user optionally uploads phpliteadmin.css 
alongside phpliteadmin.php, but that's as far as I want to go in terms of more 
than one source file. 

Original comment by daneirac...@gmail.com on 2 Jun 2011 at 7:38

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by daneirac...@gmail.com on 8 Jun 2011 at 3:05

• Changed state: Done