Hi all,
My partner (Roy Glasberg who is sitting next to me now) and I are taking a
project this semester for the Computer Networks Laboratory of the
Electrical Department of the Technion. We need to prepare a web-based
front-end for managing seminars around the Technion, such as those given
by clubs as the Haifa Linux Club, the Club-Net, the Pixel Club, and other
clubs whose lectures take place in the Technion or somehow related to it.
We were given a permission by our Supervisor, to find a ready-made
solution on the web, and customize for our needs. We will not
necessarily follow this path, but we wish to see what ready-made
solutions are available to us. We require the following of it:
1. Open-Source.
2. Allow us to customize it to suit our needs.
3. Preferably Perl Based.
- We'd rather not use a Zope-based solution as Zope is an architecture,
which very few seem to fully understand, and does not make a good use
of SQL or XML to allow it to work with the outside. If we base our
solution on Zope, we may have a hard time converting the data to
something that a different back-end can use or maniuplate.
The fact that Zope is written in very sophisticated Python does not
add to this record. We wish to have something as simplistic and as
lightweight as possible. And we don't have time to master Python too
well.
(Please don't start a flame war on this. This is our opinion and our
observation.
- We'd rather not use PHP if we can help it, since we don't like PHP
much, and it tends to be more error-prune than Perl. Nevertheless, a
well-written PHP solution is better than nothing.
(again, let's not start a flame war. Take it as a fact)
- Perl is our first choice anyhow, because we like it, it has lots of
good APIs on CPAN or otherwise, and we are familiar with it pitfalls.
- While we may use something that is written in C or C++ we think
writing such things in C/C++ is a Bad Idea<tm>.
4. Well-written code, the ability to add or modify fields easily.
5. X/HTML, HTML 4.01 and CSS Compliance.
6. Nice to have: fully uses relative links. (no href="/" or
href="http://mysite/";)
7. Not necessarily a seminars applet, but something similar that can be
tweaked and customized without too much trouble.
8. We are not looking for APIs that can make our job easier. Perl has
plenty of those, and assuming we have to engineer this thing from scratch,
we will go over CPAN and google ourselves. (or hack some things on our own
- in Perl simple things are simple and complicated are possible)
Here:
http://vipe.technion.ac.il/~shlomif/seminars/
One can find the SPEC of the project (or at least a large part of what we
have written yet), and some Dia diagrams summarizing the workflow of the
site.
Are plan for the behind-the-scenes organization of the site is as follow:
the site will have normal users, which will not login or need to login by
any means. Each club can have an arbitrary number of Club Admins which can
login to the site, and post/modify basic stuff about the club. The site
will also have a super-admin which can do everything all the club admins
does, as well as do stuff like add new clubs, modify the permissions of
the users, etc. (an account can be a club admin for more than one club)
We do not wish to default on the permission scheme given to use by
the database (permissions on tables, columns, records, etc) to maintain a
secure service. Everything will be done in user-land, with perhaps some
complementary layer of the database.
We were given a green light to use our choice of MySQL or PostgreSQL. We
need to compare the functionality given to us by the databases to
determine which one is more attractive. I am not aware of any
available InterBase Perl interface, and generally we can get more support
and Q&A for either Pg or MySQL.
Regards,
Shlomi Fish
----------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Home Page: http://t2.technion.ac.il/~shlomif/
Home E-mail: [EMAIL PROTECTED]
"Let's suppose you have a table with 2^n cups..."
"Wait a second - is n a natural number?"
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
