Hey, Fabs, I didn't know you were writing SASQ 2!!! How come, when did you decide that? And what is the concept? I mean, do it if you wanna, but I was planning to revamp the system. Don't get me wrong, I'm not trying to knock you off this, I will have a lot other stuff to do, but anyway, tell me about it... [addsig]

well, I don't wanna knock of your plans either but I decided to code sasquatch 2 and not only fix the old system but also add a lot of features. I'm also installing apache/php/mysql on my gnu/linux-box so that I can throughly offline test this.
The point is, since you're in hungaria now, I wanted to code sasquatch 2 beta now, then hand it to you guys for some tuning and then finally getting it to run
I'm not gonna start from scratch if that's what you're afraid of, I'm gonna enhance just like you wanted.
Why I wanna do this is because I've worked a lort with fixing this dbase, a lot of times when people didn't even notice. I know what's wrong about the structure and how it has to be improved, I've learned a lot more about php/mysql and I'm just soooo excited about coding this =)
But of course, if it's possible, I'd wanna share it. I mean, we're a team, we've always been. And coding with you is defenatelly fun

fabs

and what is going to be improved?

you said 'search function'...

but that can't be all.

I'd like to help, too, so it would be nice to know what your plans are.

Ok, first of all, the structure as a whole. Fields that we do not need will be removed. It's shit that points are saved in sasq_user and read from there. Points should be read out of sasq_votes. That's not too slow, Hall of fame does it for example. That way, if we deleted a vote, we wouldn't have to change the points somebody has. Same thing with sasq_docs which saves not only its points but also the number of votes. These can all be calculated and it'll make mantaining much easier if we calculate them.

Then of course search-function, a way to submit links, better ways of editing, that is editing votes, and submited documents. Also, there's a bug which I wanna fix: sasq_docs reads the votes out of sasq_votes by URL! That means, if a user changes the url, all votes of that document are lost. We;ve had that before and I quietly fixed it, not telling anyone.

fabs

ok, here are my suggestions:

we should display on the code and tut list the vote average on a tut or code, so that users can see how good it is just by looking at the name.

Also we should remove that opening a new page so we don't need javascript anymore. The javascript is causing porblems with textbrowsers, and i think it would be cool to have compatibility with as many browsers as possible.

Better editing capabilities are important, as you said.

then, perhaps better integration of sasq with phpbb, as userinfo is stored twice right now, once in phpbb's users and once in sasq_users. THat's not necessary. Either make phpbb read user data from sasq or vice versa.

i actually had mroe dieas, but i forgot these...
i'll port later when they come back to mind.

we do need javascript anyhow, even if we don't open a new window. that shit is just for keeping the visitor on our site. the javascript is needed for submitting forms.

Fabs, it's okay, I know what you mean. And I am gonna let you into a secret: I was going to re-write the thing from scratch. DON'T scream yet though! I was going to cut-past a lot but I wanted to put a new structure to it all. This script-caller thing we have is good.

Actually, our "GUI" is not very good. Having editing links all over the shit is not an effective way. We would need an actual unified "GUI" - I can demonstrate what I mean for you later.

Anyhow, just proceed with the work, Fabs and then we'll do it. I'm also going to install PHP and MySQL when I return home. (in fact I am gonna make my computer a 99% linux box, gonna need some help from Fsvara)

About the by-url bug, do it as you said. Under cover, mafia shit, get it done discretely .

See you!! [addsig]

oh, and multi-language feature too. for the tuts and perhaps also for the gui. [addsig]

yeh, but text browsers support posting with forms.
but logically, they can't open new windows =) and if in the future sasq uploads the tuts and code, that getting off-site is no problem, either. If space is a problem, we could host the tuts on another server.

It would be strange tho, splitting the page among a lot of servers...

well, just being compatible with textbrowsers would be cool, as links and lynx fail miserably on our site, and sometimes you do enjoy using those.

hehe. I am not very keen on complying to lynx standards. But we'll do our best .

I want to sign up for some unlimited space screwup for the source code. the tuts don't take much space usually. [addsig]

may i remind you that lynx is one of the most standards compliant browser after w3?... hehe... btw, about standrd compliance, on the w3c page they have a html standrds-compliancy checka... i ran it on our site and it found a lot of stuff...

hehehe, sure did I bet it did, I mean, hell, our system only worx with javascript
fabs

well, i guess it was only checking the actual html, as it only displayed errors for missing stuff in html tags and some shit... i don't think it's very important tho.

I still don't understand why we need javascript. the phpbb works well in text browsers, and it uses forms and cookies and whatever.

That is because we use links and images for submitting a form. phpBB does not. When you click an image link like "Reply" it already has the syntax in it (like reply.php?forum=3452345&topic=242423) and shit... But I will think about this and see if I can dfo something about it. [addsig]