Imma rewrite ttf based on the current code and my own geniousness, things it shall contain are:
- Admin Panel
- Cleaner code with template system
- Language system
- Config stuff in a MySQL table (allows modify via admin panel easier)
- Mobile site which (should) be compatible with most mobile resolutions.
- You can lock forums.
It'll have cleaner code formatting (imo anyway) and Lucas will be fully credited, I just want to do it for the lulz, also when I use ttf again I want to be able to customise it better.
y/n?
- Admin Panel
- Cleaner code with template system
- Language system
- Config stuff in a MySQL table (allows modify via admin panel easier)
- Mobile site which (should) be compatible with most mobile resolutions.
- You can lock forums.
It'll have cleaner code formatting (imo anyway) and Lucas will be fully credited, I just want to do it for the lulz, also when I use ttf again I want to be able to customise it better.
y/n?
Go for it!
> Config stuff in a MySQL table (allows modify via admin panel easier)
this is an extremely bad idea for performance. configuration settings do not benefit from a relational database. editing a text file with php shouldn't be very difficult.
ttf actually used to store configuration variables in the database (see r294). you can simply revert this revision if you like. they were moved to a flat text file for the aforementioned reasons.
dst data are stored in a flat text file for the exact same reason (see include_dst.php). generating these data on demand would hurt performance, and pulling such a large number of rows from mysql on each script call would be very costly as well.
i feel that storing fairly static, non-relational data in flat text files is ideal.
> y/n?
go for it.
this is an extremely bad idea for performance. configuration settings do not benefit from a relational database. editing a text file with php shouldn't be very difficult.
ttf actually used to store configuration variables in the database (see r294). you can simply revert this revision if you like. they were moved to a flat text file for the aforementioned reasons.
dst data are stored in a flat text file for the exact same reason (see include_dst.php). generating these data on demand would hurt performance, and pulling such a large number of rows from mysql on each script call would be very costly as well.
i feel that storing fairly static, non-relational data in flat text files is ideal.
> y/n?
go for it.
I see, I know how to edit the config file from the admin panel I just thought it would be easier to do it from a db, I'll go with flatfile config though, they will be in a seperate file from config.php (which will be reserved for DB stuff only)
Perhaps something moar beneficial would be a forum software which is designed for Mobiles such as Blackberry but uses the same template (which uses percentages) so it can be used on computer.
I started on the common.php file yesterday and I've been tweaking the design for it all, looks pretty nice.
I started on the common.php file yesterday and I've been tweaking the design for it all, looks pretty nice.
Mobile ttf would be mucho appreciated! I rarely ttf on my laptop anymore.
I'll try and cook something up based on the same theme, jus' wanna know what the absolute minimum resolution should be.
320x240
that big? I was thinking like 250px width.
Alright then I can add a couple of changes I had to take away :D
Alright then I can add a couple of changes I had to take away :D
128x128 minus browser chrome.
Sorry I wanted 240 width