Ok seeing as I'm bored with nothing really to do it could make use of some features:
- Little or no tables, mainly CSS.
- Some AJAX (with Mootools)
- Preview a Post
- New layout but making similarities to this layout.
- Mobile Phone support
- Proper Admin Panel.
- Template System
I built an ikkle template system for CloudCMS, it works very nice. I dunno about mobile phone support, maybe supporting stuff less than 320px wide?
i've been making plans in my mind for 1.5 and 2.0, but that's about it.
as far as execution, i'm obviously not very good at finishing even 1.0.
It's secure, fast and easy to use, what is the problem.
All I hate about it is everything is lowercase, but it looks nice, however if I want it on my site I'd have to convert everything to proper grammar.
Would you mind releasing a milestone version (ie. ttf milestone 1) or something so if I refer it to my mates to download they wont have to get TortoiseSVN or something.
Also I will build you an admin panel one day if you want for ttf, using your guidelines (which I have fully read) on google code.
I think lucas is a bit of a perfectionist :). not that I can't totally relate.
> what is the problem
i just made the
issues listing a bit more useful. i want all of the issues marked as "critical" for "milestone-1.0" to be resolved for ttf v1.0.
> All I hate about it is everything is lowercase
i hope to migrate all of the text to $ttf_msg in
this file. then it would be extremely easy to change. a lot of it is there, but certainly not all of it.
> Would you mind releasing a milestone version
i'll release the source in an archive when we hit v1.0. in the meantime, can you just make them a zip? if you really want me to, i can. i just hate building zips of random revisions. that's what an svn client is for. :)
> I will build you an admin panel one day if you want for ttf
dbrown has already produced some scripts for this. check out the branch
here. one day i'll review his code and merge it into trunk.
> I think lucas is a bit of a perfectionist
i think so too. i also think it is mostly a disadvantage for the lead dev of an oss project. i should be more quick and willing to incorporate others' code. i can forgive many stylistic differences. however, i read web apps like a mathematical proof. i rarely qa--i just read the script and make sure it's perfect. i'm a mathematician in this regard--they won't attempt to validate a proof by running a few numbers through it to see if it works. it's the one or two special cases that especially need to be tried. so i don't attempt to qa by running the scripts with a ton of different variables. i just read them. but that takes time.