I've been dilly-dallying in emacs today, browse around the first half of a
really simple dependency database here:
http://oeh.network-electronics.com/~olegil/dependencies/index.php
Adding/changing people, projects and dependencies work
Deleting isn't implemented on anything yet.
Adding roles (connecting people to projects), listing/searching the
database is still on the todo, and I'll be adding a simple "latest
additions" to the front page.
It's supposed to be using CSS for all pages, the menu is going to be
sitting on the left if you have CSS, top if you don't. I absolutely will
not design without CSS any more ;-)
The CSS that actually places the menu and body divs next to each other is
missing, though. I have to look it up :-P
To log in, use the username aooo. The password is tricky. (let's see who
figures THAT one out :-P )
--
We'll pedal off that bridge when we get there.
Ok, can everyone give me some feedback on what they're working atm?
I noticed* *Rene W. Olsen is working on SANE, did you manage to resolve
those issue's you mentioned earlier?
Did you ever get an awnser about that parrallel device?
What's the status of libusb? Is Aspell fully debugged?
Seems the first mail got lost...
Heya!
Piyush Khengar schreef:
> Dear all,
>
> The time has come when our projects coordinator has asked for us to
> submit our project descriptions for students to choose from.
Cool! Let's get these guys some work :D
> Following the brief meeting I had with Olegil et. al. at AmiGBG, I
> would now like to enlist your help in formulating some of these
> descriptions so that we can get my students involved in this project.
> I cannot do this myself, as I do not know the current status of the
> project, nor do I know what needs to be done so far.
Going of the top of my hat:
- We have libUSB
- We have pthreads
- We have aspell & various other small dependencies
> While thinking up these descriptions, please keep the following 5
> points in mind:
> 1. These are 3rd year Electronic Engineering students who have covered
> C/C++ in their 1st two years of study - they are NOT computer science
> or software engineering students.
> 2. From start to finish, they would have only about 6-8 months (2
> semesters and a bit) in order to complete their work.
> 3. They should be spending about 5-10 hours a week on this (remember
> they have other courses to study too).
> 4. The projects should be realistic for students of this level.
> 5. The description should contain enough detail/pointers for the
> student to be able to make a good start. I.e. they should know where
> they should begin to do their research in order to proceed with the
> actual coding.
Does their tasks need to be within a certain field? eg device drivers?
Or does any coding project go?
> I hope that descriptions will start to fly in soon after this email. I
> am looking to supervise at least 4 BEng individual projects, and at
> least one 4th year MEng GROUP project. A few descriptions (on a bigger
> scale) for group projects would also be great.
>
> Many thanks,
> Piyush (Captain Moo Moo)
Sorry for not replying earlier, like you might have noticed, i've been
missing in action ALOT lately, work's a bitch.
Hello,
Is there any library for IEEE1284 support (parallel device) for OS4? SANE uses it for Parallel
scanners, if no one planning it I maybe chould be tempted to do a wrapper for OS4.
Kind regards
Rene W. Olsen
Hello,
I have been doing some coding on SANE now that my Python project was mindless...
I have almost got all the MainFunction compiled there is just two files that dont work...
the first is a file with SCSI support commands in it, I have just skip it as I have no SCSI to test
it with.
The second is Thread support and a more serious problem. They have been so nice to make two versions
one with fork() and one with PThread.. When I try to compile the file it complains about some
sigaction structure/function. (see below)
static void
restore_sigpipe( void )
{
struct sigaction act;
if( sigaction( SIGPIPE, NULL, &act ) == 0 ) {
if( act.sa_handler == SIG_IGN ) {
sigemptyset( &act.sa_mask );
act.sa_flags = 0;
act.sa_handler = SIG_DFL;
DBG( 2, "restoring SIGPIPE to SIG_DFL\n" );
sigaction( SIGPIPE, &act, NULL );
}
}
}
In this code its first definded sigaction as a structure and then call it as a function ?! Its not
the only place where they do that trick.
This is what the compiler writes to me
2.Work:CVS-Home/sane-backends> make
gcc -Wall -mcrt=clib2 -Os -Iwork:cvs-home/sane-backends/include -c -o sanei/sanei_thread.o
sanei/sanei_thread.c
sanei/sanei_thread.c: In function `restore_sigpipe':
sanei/sanei_thread.c:310: error: storage size of 'act' isn't known
sanei/sanei_thread.c:312: warning: implicit declaration of function `sigaction'
sanei/sanei_thread.c:312: error: `SIGPIPE' undeclared (first use in this function)
sanei/sanei_thread.c:312: error: (Each undeclared identifier is reported only once
sanei/sanei_thread.c:312: error: for each function it appears in.)
sanei/sanei_thread.c:310: warning: unused variable `act'
sanei/sanei_thread.c: In function `sanei_thread_begin':
sanei/sanei_thread.c:356: error: storage size of 'act' isn't known
sanei/sanei_thread.c:360: error: `SIGPIPE' undeclared (first use in this function)
sanei/sanei_thread.c:356: warning: unused variable `act'
sanei/sanei_thread.c: In function `sanei_thread_sendsig':
sanei/sanei_thread.c:411: warning: implicit declaration of function `pthread_kill'
make: *** [sanei/sanei_thread.o] Error 1
Any vice person that know what to do?
Ohh ya almost forgot they seam to use pthread_kill() is there an easy way to emulate that function?
Kind regards
Rene W. Olsen
