Menu
▾
▴
core-lan-org-devel — Developers and feature-requests overhere please
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(12) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(50) |
Aug
(15) |
Sep
(6) |
Oct
(16) |
Nov
(11) |
Dec
(7) |
| 2003 |
Jan
(10) |
Feb
(8) |
Mar
(11) |
Apr
(3) |
May
(1) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
| 2006 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dennis F. <de...@co...> - 2002-08-04 11:38:10
|
Hello again, Well I -think- (sort of a disclaimer) that the code is getting stable = again. I've updated the db_update.sh scripts and it works here on = serveral production databases. The scripts are also self-securing now so = your data should be safe. Can you guys please test the scripts ? After this we might best be looking into the code to get it to a stable = release: version 2.00. Greetings, Dennis Fleurbaaij |
|
From: Dennis F. <de...@co...> - 2002-08-04 09:36:02
|
Hi, Good work! The cvs db_update seems to be quite ok. There are just a few things I'd = like to see otherwise (and will probably code it that way ;) ) - the subdir has to go, I'd prefer an update script and the database = creation script. - lots of missing indexes but I'll fix that. For the rest this is real good work !! Thanks, Dennis |
|
From: Andrew S. <and...@pa...> - 2002-08-04 05:43:33
|
Hi all, I've cobbled together a database upgrade script. It upgrades a version 1.11 (and before) into the correct format for the database in CVS. I've run a back-up of my production system through it a few times and it has been sweet! However, I'm not 100% confident that I've got it right yet..., and there's a few areas I'm uncertain about too. Anyway, it's in the CVS. Took the opportunity to clean up the database script and give the unnamed triggers some names. Contact_tasks doesn't appear to do anything, but I left it in for backward compatibility. The CVS is looking good. I think we are realistically not too far from a stable release. Andrew |
|
From: Andrew S. <and...@pa...> - 2002-07-31 08:57:58
|
Hi all, I've added the missing database columns to SQL dabase dump. This fixes the errors/bugs in the time accounting. I've also fixed the referential integrity errors in the database when a task is deleted. Spent a long while trying to fix the database, before realising that I just had to change the order in which the rows are deleted :-( Will now continue thrashing the code until something else breaks :-) Dennis - did you like the graphics that I sent you? Having some graphics does make the app look more professional. I'm running the graphics model(!) CoreAPM on my production machine. I'll add them into the CVS if you're agreeable. Marshall - are you happy for me to (try and) add your task_summary file into CVS? Andrew |
|
From: Andrew S. <and...@pa...> - 2002-07-26 08:42:36
|
On Thu, 25 Jul 2002 14:53:07 +0200 "Dennis Fleurbaaij" <de...@co...> wrote: > Hey guys, > > Okay it's in, changed more then 90% of the files in the process. > Looks very good. Loaded it up and gave it a quick spin. Remarkably stable compared with the last week, or two. Some small problems after a very quick test: - Fixed a problem with showing users details (minor html script problem). - task_time_report (line 62) the query looks for the column users_id in the table time_account. (Doesn't exist). - Can't delete tasks/projects - constraint error. I guess these last two will be covered when you look at the database scripts. Andrew |
|
From: Dennis F. <de...@co...> - 2002-07-25 12:53:19
|
Hey guys, Okay it's in, changed more then 90% of the files in the process. cvs log: date: 2002/07/25 12:49:04; author: fleurbaaij; state: Exp; lines: +35 = -8 Massive update. - Fixed project listing page - Added missing files from Bo's time-registration hack - Made them actually work ^ - Fixed showing of different modes (we now have deadline based and time = registration mode) - Fixed LOADS of bugs - Added GNU header to every file - Added the todo list - Added the time registration and implemented it into the show-task - Lots more probably but I've forgotten it. Tree is now somewhat sane and stable again. PLEASE TEST ! IF this works I'm going to add the databasescripts and get = the thing to work again. Dennis |
|
From: Dennis F. <de...@co...> - 2002-07-24 14:09:26
|
Hi, Okay, I've found the files send by bo again. They really look nice and = after some work this can be very cool. Started coding and porting them = (Bo has a bit of a different codebase) and I'll insert them tonight if = gf allows ;-) The rest of the code is also coming along nice and after a bit more work = this will be stable again and ready for the world (yay!). Greets, Dennis |
|
From: Dennis F. <de...@co...> - 2002-07-24 10:28:40
|
As I'm trying to get it to work I'm stuck on some of the things Bo = added: - time accounting is in a different table in the database but there is = no code to support it. How do you do it ?!? Shall I write a module that = can manage the time someone has worked on a task or is it enough just to = be able to fill in the time. If so the time_accouning table is wrong and = it should be a column in the tasks table. - If a user goes over the esimated time, do you increase that ? - Can multiple users work on a single task ( that is something = core-lan-org was not designed for !! ) ? Please enlighten me on how you've implemented it. Also please send the = missing files from your patch (todo and such). Dennis |
|
From: Dennis F. <de...@co...> - 2002-07-24 10:06:41
|
Hi, I'm back from vacation and I'll be looking into the core-lan-org code = again. As far as I can tell it's a mess now after syncing in to many = things from too many people. I just didn't test it well enough.=20 Initial report: - time accounting functions totallly broken, no accounting done as it's = not in the source - lots of missing variables (set errorlevel in php to E_ALL when you = code ! ) - project listing works but is quite crappy right now - 0-100% bars broken - 2 different systems (time accounting and done-busy accounting is not a = good situation :/ ) - slow and inefficient ( 20+ queries for simple showing of a task ) todo (for me that is right now): - get the task-time registration on track again - fix up all those small variable bugs - try to get the CVS back to a sane state done: - fixed all the file-headers to the GNU licence and a cvs header tag, so = it looks professional now ;) - coding on the show-projects list but it's going to take a while and we REALLY ( I know I'm pushing ) should consider going to another = tree as this is a dying monster :-( I've made significant progress again = on the field of gantt only task management and even if it still will = take weeks to get anything sane online I think that that is the way to = go as we're missing lots of nice features here: - workflows - defining a workflow as a task ( so you get layered views ) - graphics - much better time registration - different workflow outcomes - resouce usage etc. Met vriendelijke groet, =20 Dennis Fleurbaaij Voorzitter stichting CORE ---------------------------- Tel : +31 (0) 6 54 21 53 65 Mail: de...@co... www : http://www.core-lan.nl Adres: Marco-pololaan 22 4562 AC Hulst |
|
From: Marshall R. <mr...@db...> - 2002-07-16 00:24:32
|
> Hello, > > I'll be on vacation to Salou, Spain for the following 8 days. I'll think about the > problems posted and if possible i'll sneak my laptop along to send you guys patches and > emails :) > > mtr: I know that I've polluted the CVS, I'm sorry for it. no worries. enjoy your vacation, and we'll resync after you return. /mtr |
|
From: Dennis F. <de...@co...> - 2002-07-15 16:58:15
|
Hello, I'll be on vacation to Salou, Spain for the following 8 days. I'll think = about the problems posted and if possible i'll sneak my laptop along to = send you guys patches and emails :) mtr: I know that I've polluted the CVS, I'm sorry for it. Cheers, Dennis |
|
From: Andrew S. <and...@pa...> - 2002-07-14 05:44:49
|
> 1. search function > > what would people think if i added a search box that looked at the > various fields and returned a page o' pointers? since folks are making > good use of the forum functionality, this makes things more like a > "knowledge base". Yes, particularly on forums. Other fields, hmmmm... Not fussed. > 2. embedding html > > what would people think if we treat the multiline fields as HTML > fragments? so users can do things like <B> and <A>? > I thought Dennis had done this on forums? I could be wrong. Again, it's a 'not fussed' item for me. > 3. mail notices > > what would people think if we add a link that triggers a scan of the > datbase that mails deadline notices to people, e.g., "here are the > tasks you own that are due to tomorrow" or "here are things you own > this month that are due"? My first thought was; 'Oh no, not one of these nagging programs that everyone hates'. But I see you've refined it to a manually activated nag. On that basis, yes it sound good. Marshall - I don't have a copy of your 'task_summary' file (it's not in CVS), and I would like a copy, please. Regards Andrew |
|
From: Marshall R. <mr...@db...> - 2002-07-11 22:28:26
|
> I can confirm the latter. I've just been attempting to debug the userid > problem. There are a few other things broken in the CVS (I've fixed a > few, but not updated the CVS yet), and a couple of files missing for 'to > do' and estimates. thanks for the updates. as the fng here, can i please ask that folks commit to cvs ONLY when they know things work. i don't mind lots of stuff showing up in the tree, but any time i do a "cvs update", it ought to work. /mtr ps: so, can anyone figure out the database movement issue? |
|
From: Andrew S. <and...@pa...> - 2002-07-11 07:22:09
|
On Wed, 10 Jul 2002 23:58:18 -0700 Marshall Rose <mr...@db...> wrote: > > third, when i tried to edit myself, the (emailed) error being > The erroneous component: Missing values > The error message: No userid was given > Page that was called: /org-cvs/users.php > Called URL: > /org-cvs/users.php?x=024296d12454e636355d97c76f319988&action=show > Browser: Mozilla/5.0 (compatible; Konqueror/2.2.2; NetBSD) Time: > July 10, 2002, 23:44 IP: 64.168.10.253 > POST vars: > > when i ran the newdb.sh script, no errors were reported. > > so, what am i doing wrong or is the code in CVS just really, really > broken? > I can confirm the latter. I've just been attempting to debug the userid problem. There are a few other things broken in the CVS (I've fixed a few, but not updated the CVS yet), and a couple of files missing for 'to do' and estimates. Andrew |
|
From: Marshall R. <mr...@db...> - 2002-07-11 06:59:21
|
hmmm... so i ran the attached newdb.sh, which codifies the commands you suggested (for postgres 7.1.2) and the attached database-munge.pl. the create_database.sql file is taken from the current cvs.
first, the usertable was reset back to "admin".
second, although i could login as "admin", i couldn't view any tasks.
third, when i tried to edit myself, the (emailed) error being
The erroneous component: Missing values
The error message: No userid was given
Page that was called: /org-cvs/users.php
Called URL: /org-cvs/users.php?x=024296d12454e636355d97c76f319988&action=show
Browser: Mozilla/5.0 (compatible; Konqueror/2.2.2; NetBSD)
Time: July 10, 2002, 23:44
IP: 64.168.10.253
POST vars:
when i ran the newdb.sh script, no errors were reported.
so, what am i doing wrong or is the code in CVS just really, really
broken?
/mtr
|
|
From: Marshall R. <mr...@db...> - 2002-07-11 00:18:46
|
hi. after getting some feedback from users, here are three topics that i'd like folks comments on: 1. search function what would people think if i added a search box that looked at the various fields and returned a page o' pointers? since folks are making good use of the forum functionality, this makes things more like a "knowledge base". 2. embedding html what would people think if we treat the multiline fields as HTML fragments? so users can do things like <B> and <A>? 3. mail notices what would people think if we add a link that triggers a scan of the datbase that mails deadline notices to people, e.g., "here are the tasks you own that are due to tomorrow" or "here are things you own this month that are due"? /mtr |
|
From: Dennis F. <de...@co...> - 2002-07-10 18:15:09
|
Hi Andrew, The postgres 7.2.1 database is just far superior to the 7.1 release. No doubt about it. I think as a matter of fact we can start to demand that users have the 7.2 database as that just has too many advantages above the 7.1 database. Therefor I opt to only support the 7.2 and start forgetting about the 7.1. Upgrading is easy and can be done is such a way that no data is destroyed. Um clean-up release sounds pretty good. But I think that the changes are not too severe and that we can get it stable in a short period of time.The real question is: are the graphics allready in CVS because I'd really like to see them :) Greets, Dennis ----- Original Message ----- From: "Andrew Simpson" <and...@pa...> To: <cor...@li...> Sent: Tuesday, July 09, 2002 11:11 AM Subject: [Core-lan-org-devel] 1.12 Release? > Hi all, > > I'm in the process of updating my production machine at work. > Obviously, I can use a current CVS snapshot; the database is changed and > it's still a bit too unstable at present. > > So I've been packaging up a stable CVS snapshot from a week ago. This > has got a number of worthwhile improvements over Ver 1.11 (released > early June): > > - Works with Postgres 7.2. As I found out Ver 1.11 doesn't :-( > > - Checks dates (Ver 1.11 does not), and has improved formatting. > > - Few minor bugfixes for Netscape rendering and the like are included. > > - I've put some basic graphics in (IMHO they look good). > > - Probably other things I've forgotten that are vitally important :-) > > My feeling is that the Postgres 7.2 compatibility is important for our > users (new and current). I found out about the problem when I upgraded > to Red Hat 7.3, and I guess others will be encountering the problem > too... > > What I'm getting to saying is: Should we do a 1.12 'clean-up' release - > it can be based on what I've got - and then get stuck into stabilising > the new stuff? If so, then I'll forward a tarball to Dennis for > assessment in a few days. (I want to finish testing it out first). > > Regards > > Andrew > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Stuff, things, and much much more. > http://thinkgeek.com/sf > _______________________________________________ > Core-lan-org-devel mailing list > Cor...@li... > https://lists.sourceforge.net/lists/listinfo/core-lan-org-devel > |
|
From: Dave C. <da...@cr...> - 2002-07-09 11:21:36
|
On Mon, 2002-07-08 at 19:19, Marshall Rose wrote: > suppose i want to make a copy of my existing database and apply the modifications to that copy, so i can test things out without screwing up my production system. > > what commands/scripts, exactly, do you suggest i run? Following assumes that you're the "right" user, that your production database name is $PRODUCTION (or is in that shell variable), and that, most importantly, the schema hasn't changed except for the DRI - no new columns, etc. Oh, and your new database is $TESTING. 1) Take a full dump of your production database: pg_dump $PRODUCTION --quotes >production-backup.sql 2) Create testing database: createdb $TESTING 3) Put the dump into the shiny new database: psql $TESTING <production-backup.sql 4) Run the hacky perl script as follows: perl database-munge.pl /path/to/new/source/create_database.sql | psql $TESTING 5) Now we have the right data, but without the DRI in the schema. So we backup the data only: pg_dump -a $TESTING >testing-data.sql 6) Now we drop the database: dropdb $TESTING 7) And recreate it, blank: createdb $TESTING 8) Now add the schema: psql $TESTING </path/to/new/source/create_database.sql 9) And finally add the data: psql $TESTING <testing-data.sql You now should have a "new" database in $TESTING which works. Dave. |
|
From: Andrew S. <and...@pa...> - 2002-07-09 09:12:12
|
Hi all, I'm in the process of updating my production machine at work. Obviously, I can use a current CVS snapshot; the database is changed and it's still a bit too unstable at present. So I've been packaging up a stable CVS snapshot from a week ago. This has got a number of worthwhile improvements over Ver 1.11 (released early June): - Works with Postgres 7.2. As I found out Ver 1.11 doesn't :-( - Checks dates (Ver 1.11 does not), and has improved formatting. - Few minor bugfixes for Netscape rendering and the like are included. - I've put some basic graphics in (IMHO they look good). - Probably other things I've forgotten that are vitally important :-) My feeling is that the Postgres 7.2 compatibility is important for our users (new and current). I found out about the problem when I upgraded to Red Hat 7.3, and I guess others will be encountering the problem too... What I'm getting to saying is: Should we do a 1.12 'clean-up' release - it can be based on what I've got - and then get stuck into stabilising the new stuff? If so, then I'll forward a tarball to Dennis for assessment in a few days. (I want to finish testing it out first). Regards Andrew |
|
From: Marshall R. <mr...@db...> - 2002-07-08 18:20:32
|
hi. i'm having some difficulty following this. let me suggest the following: suppose i want to make a copy of my existing database and apply the modifications to that copy, so i can test things out without screwing up my production system. what commands/scripts, exactly, do you suggest i run? thanks, /mtr |
|
From: Dennis F. <de...@co...> - 2002-07-08 05:33:01
|
Hi Andrew, > Firstly, the problems in security.php and time.php were mine. Apologies > for wasting everyone's time, I independently fixed the bugs and > committed them to CVS a couple of days ago. They were actually > corrected here, but I stuffed up my file commits to CVS - and then > didn't realise for a week. Sorry. No problem. > Secondly, I've been out of touch from the mailing list and didn't see > the sudden upsurge in activity. Nice to see! Yups, with the addition of Marshall Rose things got back to life. And even Dave is commiting lots of code so we're sure heading in the right way. > Anyway, I've been making a few changes to the CVS over the last week, or > so. Changes to dates (as you've found), code clean ups, better defining > projects vs tasks and a few bugfixes. The CHANGELOG is up to date with > what I've done. Fortunately, all seems to merge with the new stuff > pretty well. Yep, saw it and it looks good, > Also been adding some small graphics into my source tree. Graphics are > 'new', 'updated' etc. They make the pages a bit more readable at a > glance. I'll add them to CVS a bit later. Yes please ! I've got some easy graphics-updates too that are for coreapm.sourceforge.net but that I can commit with ease. It'll change the looks of the boxes. To a more rounded design. > I've downloaded the new code, looks impressive. I'll start bug testing > and generally knocking it around. I think I could be of use doing that. > A couple of 'to do' files are missing? Yes. I'm expecting them from Bo Lorentson. They came from his diff file. So the tree is currently broken. > Do we need stable/unstable repositries in the CVS? I've been thinking of that for some time now but I think the best way (still) is just to mark a release in CVS and release the files. That way we have one code-tree that is both stable and unstable depending on what branch you check out. > Nice to see activity on the project. I'm using it in my workplace, and > believe to have potential as a real killer app. As I've said before, I'm working (hard) on something totally different (but also a web-based project manager). I'll put a demo up this week and I'm pretty sure you're all going to like it :-). It's a generation ahead of core-lan-org and features: - auto edit/update/delete boxes - totally graphical project layout - workflows - subworkflows - tasks - projects - resource management - better time handeling and plotting of gantt charts - time/calendar lists - releases/phases (and graphical marking) - better gui More info soon. Greets, Dennis |
|
From: Andrew S. <and...@pa...> - 2002-07-08 04:06:12
|
Hi all, Firstly, the problems in security.php and time.php were mine. Apologies for wasting everyone's time, I independently fixed the bugs and committed them to CVS a couple of days ago. They were actually corrected here, but I stuffed up my file commits to CVS - and then didn't realise for a week. Sorry. Secondly, I've been out of touch from the mailing list and didn't see the sudden upsurge in activity. Nice to see! Anyway, I've been making a few changes to the CVS over the last week, or so. Changes to dates (as you've found), code clean ups, better defining projects vs tasks and a few bugfixes. The CHANGELOG is up to date with what I've done. Fortunately, all seems to merge with the new stuff pretty well. Also been adding some small graphics into my source tree. Graphics are 'new', 'updated' etc. They make the pages a bit more readable at a glance. I'll add them to CVS a bit later. I've downloaded the new code, looks impressive. I'll start bug testing and generally knocking it around. I think I could be of use doing that. A couple of 'to do' files are missing? Do we need stable/unstable repositries in the CVS? Nice to see activity on the project. I'm using it in my workplace, and believe to have potential as a real killer app. Andrew Simpson |
|
From: Marshall R. <mr...@db...> - 2002-07-07 17:20:27
|
thanks. i've done two things: first, i've changed the style used on conditionals. second, i've enclosed a version (task_summary_list.php) with one new feature: it shows flags (created,modified,posting,file). this answers the age old question "so i got this email from core-lan-org telling me to go to the website, but where do i look from there?") i also patched the helpfile. if folks have already applied the first patch, then apply only the second; otherwise, apply both. regardless, use the new version of task_summary_list.php. enjoy! /mtr ps: suggestions welcome, but outside of bugfixes (or making it work with the new schema), i think it's been featured-out... |
|
From: Dave C. <da...@cr...> - 2002-07-07 13:14:24
|
On Sun, 2002-07-07 at 12:21, Dennis Fleurbaaij wrote: > - get the data to a file > - erase the database > - insert the new database scheme > - change the 0's into NULLs in the file > - put the data back. Right... That script intends changing the data in-place, such that it fits the constraints. Actually, not even that, it just generates the SQL to do so. I wouldn't want to attempt changing the data while it's not in the database - that's what the database is there for. :-) Specifically, the SQL it generates changes any invalid reference to NULL, not just a 0. It's easy to change it to handle only the 0 special case, though that might still leave bad data. But it could easily form the basis for the upgrade path you suggest above, for example: 1) Dump database, use dump as backup. 2) Run data correction SQL, as output by this script. 3) Dump database data. 4) Erase database. 5) Create new database. 6) Create new schema. 7) Insert data from dump made in step (3). I can build a sh script to do this easily enough, if you want. It would actually look like the following, although I'm leaving the old database present and creating a new one. -- #!/bin/sh OLDDATABASE="oldcore" NEWDATABASE="newcore" # 1) pg_dump $OLDDATABASE --quotes >core-lan-org-backup.sql # 2) psql $OLDDATABASE <database-munge.sql # 5) createdb $NEWDATABASE psql $NEWDATABASE <create_database.sql # 6) pg_dump -a $OLDDATABASE | psql $NEWDATABASE # 3) and 7) -- Again, totally untested, and this rather assumes that the schemas are identical other than the new constraints. Dave. |
|
From: Dave C. <da...@cr...> - 2002-07-07 11:29:03
|
On Sun, 2002-07-07 at 12:08, Dave Cridland wrote: > As I say, I haven't tested it *AT ALL*. If someone wants to send me a > suitable candidate test database to run it on, I'll happily do so. *ahem* This version: a) Outputs SQL that stands a chance of working. (It's parsed and handled by psql, anyway, even if I have no data in the database) b) Doesn't have the CREATE TABLE parsing stuff that it previously had, which wasn't used anyway. I'll try to blame this on "release early, release often", and then hide in embarrassment. Dave. |
11 messages has been excluded from this view by a project administrator.
