Posted by fabs on 21:47:00 04-20-2002
I was recently toying with the idea of a complete sasquatch rewrite. The problem with using the old code is that those parts which were valuable, like the authentication-mechamism are scheduled to be replaced anyway and everything else is simply getting data out of the dbase and displaying it somehow.
What do you guys think about a complete rewrite? Maybe we can take the opurtunity and also do a redesign
fabs
Posted by KaGez on 21:52:00 04-20-2002
A complete rewrite? that won't be bad
I mean, if you rewrite all that stuff you could create for example a new way of authentication, with the fact in mind that you want to use sessions for it or something. I think it's a good idea
If we're going to do a whole re-write, we could implement themes, sessions, cache, languages and much more rom the beginning, without much useless code hanging around as it is in most cases if you just re-write old code.
[addsig]
Posted by fabs on 21:54:00 04-20-2002
yes, if we indeed go for this, we should keep a list of features.
fabs
Posted by KaGez on 11:01:00 04-21-2002
true.
And, if we're really goin to re-write, I won't start with the new search engine for now. I mean, the old one works, and if we're going to do a total re-write then it won't be worth to improve it anymore
[addsig]
Posted by Peter on 17:49:00 04-21-2002
I support a rewrite. But there's the problem with the projects section, I'll have to rewrite that too. However, first I'll try making this version usable and upload it so that there is something we can use. What do you think?
Posted by KaGez on 19:37:00 04-21-2002
Peter:
yeah, I think for now we should get it working, since it will still take a while since we have a rewritte sasq, even if we start now.
The good thing about that (if you get it working now) is, that we can look at the sources of that, and improve that too, add features ,cut unneeded code and restructure it if necessary.
OK, here a idea what we could implement into sasq:
it's not something with a high priority, but I think we should write a little script that sends some sort of birthday card to the members who's bday it is. I think it's a cute function, and will also make the relation between the members and the YPN itself into a even better one
Another cool function would be to make a little script that gets news (dunno from where) about new software releases that would matter for a developer. You know, something like the one on the gnome project's front page. Not necessary, but good to have
Yet another idea would be to implement a filter for the link stuff, as I've also stated it in the general section (i think it was there). Maybe we should split the links into 2 groups:
1.) Site
2.) Page
If you link to a site you link for example to http://www.somewhere.org, and if you link to a page it's something like http://www.somewhere.org/somedir/somepage.x. I for example look for sites sometimes, but I don't want to go to a speciffical page in that site. You know what I mean? I think that this applies also for other members.
Anyways, these things are all not vital, but indeed good to have. Maybe we should start to compile a list of features to implement into sasq
[addsig]
Posted by fabs on 22:07:00 04-21-2002
ok, guys, make sure you get this thing rolling, please and make decisions without me cause I'm not gonna be here next week. It would make me feel less useless though if I knew you guys were progressing in YPN-development
fabs
Posted by KaGez on 14:18:00 04-22-2002
ok, this mornin fabs went away for 5 days. Let's see what we can do. Here's my schedule:
tomorrow (tuesday): Physics Exam
That's it! Then I'm available for coding again! Finaly, after 2 weeks
I could start of with making the base of the new sasquatch that has cache and sessions support from the beginning How about it?
[addsig]