tutos-devel Mailing List for TUTOS

SSBoYXZlIGVuY291bnRlcmVkIHRoZSBzYW1lIHByb2JsZW0uICBJdCBpcyBjYXVzZWQgYnkgYnVn
Z3kgUEhQIGludGVyZmFjZSB0byBBcGFjaGUgU0FQSS4gIFNvIHlvdSBjYW4gc29sdmUgdGhlIHBy
b2JsZW0gYnkgdXNpbmcgQXBhY2hlIENHSSBpbnN0ZWFkLg0KDQpSYXkNCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IHR1dG9zLWRldmVsLWFkbWluQGxpc3RzLnNvdXJjZWZvcmdl
Lm5ldCBbbWFpbHRvOnR1dG9zLWRldmVsLWFkbWluQGxpc3RzLnNvdXJjZWZvcmdlLm5ldF1PbiBC
ZWhhbGYgT2YgdGF3ZWUyMDAwQGNsaWNrdGEuY29tDQpTZW50OiBXZWRuZXNkYXksIEFwcmlsIDMw
LCAyMDAzIDk6NTMgQU0NClRvOiB0dXRvcy1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNClN1
YmplY3Q6IFtUVVRPUy1kZXZlbF0gcGhwIGNhdXNlZCBhbiBpbnZhbGlkIHBhZ2UgZmF1bHQgaW4g
bW9kdWxlIFBIUDRUUy5kbGwNCg0KDQpoaSwNCkknbSBydW5uaW5nIHRoZSB0dXRvcyBpbiB3aW5k
b3dzJzk4IGVudmlyb25tZW50LiBTZXR0aW5nIGlzIGFjY29yZGluZyB0byB0aGUgDQppbnN0YWxs
Lmh0bWwgaW4gLi50dXRvc1xob21lcGFnZS4gSSBnb3QgdGhlIG1lc3NhZ2UgZHVlIHRvIHRoZSBp
bGxlZ2FsIG9wZXJhdGlvbiBhcyANCnBocCBjYXVzZWQgYW4gaW52YWxpZCBwYWdlIGZhdWx0IGlu
IG1vZHVsZSBQSFA0VFMuZGxsLiBBZnRlciBjbG9zZSB0aGUgcG9wLXVwIA0Kd2luZG93cyBidXQg
dGhlIGxvZ2luIHNjcmVlbiBpcyBhdmFpbGFibGUgdG8gbG9naW4uIEJ1dCB0aGUgbG9naW4gc2Vl
bXMgbm90IHdvcmsuIA0KQW55IHBvc3NpYmxlIGNvcnJlY3Rpb24/IA0KDQpCeSB0aGUgd2F5LCBJ
IGNoZWNrIHRoZSBlcnJvci5sb2cgaW4gDQouLmFwYWNoZVxsb2dzXGVycm9yLmxvZywgaXQgc2hv
d3MgIltUdWUgQXByIDI5IDEwOjI4OjIxIDIwMDNdIFtlcnJvcl0gW2NsaWVudCANCjEyNy4wLjAu
MV0gbWFsZm9ybWVkIGhlYWRlciBmcm9tIHNjcmlwdC4gQmFkIGhlYWRlcj1IVFRQLzEuMCA0MDEg
DQpVbmF1dGhvcml6ZWQ6IGM6L2FwYWNoZS9waHAvcGhwLmV4ZSIgDQphbmQgLi5hcGFjaGVcbG9n
c1wgc2hvd3MgIjEyNy4wLjAuMSAtIC0gWzI5L0Fwci8yMDAzOjEyOjE1OjQzIA0KKzA3MDBdICJH
RVQgL3R1dG9zL2h0bWwvYmx1ZS5jc3MgSFRUUC8xLjEiIDIwMCA0MzczDQoxMjcuMC4wLjEgLSAt
IFsyOS9BcHIvMjAwMzoxMjoxNTo0MyArMDcwMF0gIkdFVCAvdHV0b3MvaHRtbC90dXRvc19zbWFs
bC5naWYgDQpIVFRQLzEuMSIgMjAwIDE3MzINCjEyNy4wLjAuMSAtIC0gWzI5L0Fwci8yMDAzOjEy
OjE4OjU2ICswNzAwXSAiR0VUIC90dXRvcy9waHAvbXl0dXRvcy5waHAgSFRUUC8xLjEiIA0KMjAw
IDM2MjQiDQoNClRoYW5rIHlvdSBpbiBhZHZhbmNlLA0KVGF3ZWUNCg0KDQoNCg0KLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGhpcyBzZi5u
ZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5OlRoaW5rR2Vlaw0KV2VsY29tZSB0byBnZWVrIGhlYXZl
bi4NCmh0dHA6Ly90aGlua2dlZWsuY29tL3NmDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KVFVUT1MtZGV2ZWwgbWFpbGluZyBsaXN0DQpUVVRPUy1kZXZl
bEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCmh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xp
c3RzL2xpc3RpbmZvL3R1dG9zLWRldmVsDQo=

hi,
I'm running the tutos in windows'98 environment. Setting is according to the 
install.html in ..tutos\homepage. I got the message due to the illegal operation as 
php caused an invalid page fault in module PHP4TS.dll. After close the pop-up 
windows but the login screen is available to login. But the login seems not work. 
Any possible correction? 

By the way, I check the error.log in 
..apache\logs\error.log, it shows "[Tue Apr 29 10:28:21 2003] [error] [client 
127.0.0.1] malformed header from script. Bad header=HTTP/1.0 401 
Unauthorized: c:/apache/php/php.exe" 
and ..apache\logs\ shows "127.0.0.1 - - [29/Apr/2003:12:15:43 
+0700] "GET /tutos/html/blue.css HTTP/1.1" 200 4373
127.0.0.1 - - [29/Apr/2003:12:15:43 +0700] "GET /tutos/html/tutos_small.gif 
HTTP/1.1" 200 1732
127.0.0.1 - - [29/Apr/2003:12:18:56 +0700] "GET /tutos/php/mytutos.php HTTP/1.1" 
200 3624"

Thank you in advance,
Tawee

Hi all,

Usually this list does not respond to anything interesting (I am ask to
similar questins, about current release and some functionality).

	My opinion that the last release (both on 1.1 and main branch) contain meny
interesting functionality that need some tweaking work (i.e. make some minor
changes that helps to make program more usable). I am ask Gero, that may be
better to not split version to release 1.1 and main brunch, because it is
slightly hard to make corresponding changes on the both bracnhes. Instead of
this may be better to make last _release_ brunch as active brunch and make
the all final fixes only on it. Of course we need to stop any seriouse
developing on the main bracnh. For me it is resanoble to make this at one or
two month.

	Concerning task, I found very usefull your changes, but in addition I have
one request. It concerns task and subtasks. For now if I am make subtask of
some tasks, the time for subtask are not changed, while time for entire proj
is increased, for me is not good I.e. I can make task "USER UI", and
subtasks "toolbar (2 hours)", "status bar (4 hours)", "main view( 2 hours)".
Total proj will be 8 hours, while USER UI will 0. But in reality norlmal
when both the proj and "USER UI" is also 8. If I am manually change the
"USER UI" to 8, the total proj time will be 16 hours, that is not right.
	Of course I can leave time for "USER UI" as 0, but in such case this is
never ending task, even if I am change it status to finished.
	What I am suggest, is it possible to calculate time for task as its time +
summ of subtasks. I am not working with this things, and seems that you make
lot of things with tasks, so you must know better. Thanks.

Sergey Korotkov

Hi list,

As you may have noticed in the CVS commit messages, we added
informations to manage the amount of work done on a task, and to be
able to re-evaluate the amount of work to do without losing the planed
volume.

This modification is a non-destructive one, it allows tutos user to
continue using it as before. But we'd like to change that, in order to
change labels and get a more accurate interface.

So here's what's all about :

   . The volume of a task should become the planned volume and should
     not be editable once the task begins.

   . When this volume is no more accurate, while working on the task,
     the tutos worker should fill the volume_todo field of the
     timetrack. The task volume_todo will then be set accordingly,
     then updated either automatically or manually...

   . That implies changing the 'Volume' label to 'Volume planned'.

The goal of this mail is to get your opinion on such a change before
to make it real for tutos.

We (CVF) plan to merge those last changes in tutos-1.1 and package it,
either only for internal use or as a minor official release.

Regards,
-- 
Dimitri.
http://dim.tapoueh.org

Contrairement aux chasseurs qui, eux, ne sont pas des lapins, les
pollueurs, eux sont des ordures.
	-- Philippe Geluck

Hello tutos-dev,

A while ago I coded some features into tutos as was necessary for a company 
where TUTOS is used for groupware. I only now got around to making patches 
for them. These patches are for tutos version 1.0.20021113. I dont have time 
right now to try to port them to 1.1, and hope that it will be easy should 
you decide to do so. The patches are pretty unintrusive, introducing 3 
functionality/usability benefits.

More info at:
http://sourceforge.net/tracker/index.php?func=detail&aid=721545&group_id=8047&atid=308047

tar with patches and readme is attached.

hope you find this useful,
//Artem

Hello to all,

	I am make in main branch of tutos some functionality that I call "Web
stack". I am made it because, as I am think, TUTOS have very unintitive
navigation functionality. e.g. you open project, click on address link,
modify it, and after thrown to address page, why? usually user need to
return back to the page from which he start modifiing. I as I am believe
"web stack" funcionality will help to fix this issue.
	From some point of view its similar to session history functionality, but
have some differences. On every page that should be pushed into web stack
needed to call function web_StackStart (id, url, text, info). Based on this
call web stack is supported.
	The main fucntions of web stack are folowing:
	1. at the top of the window navigation path is provided. I.e. some sort of
history: where the user now, and how he cam here. He can quicly return back
clicking on some link on the top.
	2. xxx_ins.php pages uses the stack to return not on fixed page, but on
some pages back. If object modified 3 pages back, if inserted 1 pages back.
That mean that if you modify bug comming from project you will be returned
to project page, if from bug ovrview to overwie page. This seems little
"hard coded" but works in 80% of cases. And also if such functionality will
be interested for all, later need to support it, providing logic that
correctly returns on the page back.
	3. Local for page session array is automaticaly supported. This is not used
now, but for me is interesting functionality. The description is folowing.
Usually needed to store in session some variable intended only for this
page. Need to be sure that they will be correctly destroyed on session
cleanup, and names will be unique. For that "Web stack" associate with each
page some array of variabled, which will apeera after web_StackStart as
$_SESSION['web_local']. Web stack start automaticaly restoes this array when
user someway back onto the page that is in the stack. For example, we have
overview page, where we setup sorting and other settings. After we call any
link from this page, we come to other page, and after we return we can loose
such seeting. Or we need special actions to store them in session. Now will
be enought to store them in $_SESSION['web_local'], and do nothing more.

	Please, if possible review this functionality and give me some comments.
For now I am add support only for basic objects (task, bug, project, addres,
team), if this functionality will be interesting I am add into all modules,
and we will support it in the future.

	Thanks,
	Sergey


Some question about release 1.1.

	I am want to make some minor fixes into last release (like preset year
month for track time). In what bracnh better to make this, 1.1 or head
branch?
	Currently I am want to make chenges in last release, but also I am want
that they appears in head branch.
	And also, other issue. I am try to make such small fixes some time ago, but
in that time you actively develop last release, and usually I am simple can
not launch it (or its work very buggly). The fact is that I am try to really
use last (head) branch and make fixes in it, but due it work bad I am stop
this work.
	Possible for this time will be better to stop (for some time) develop
extremly new functionality on head branch, and make only small fixes and
improvements. That helps to make fixes only on main branch, and do not merge
them (release and main branch). For now version have many new very usefull
and great fucntions, but in same time (as you can read in the list) there
are many small things that prevent (or make not comfort) its real using.
	What you think?

Thanks,
Sergey

Hello Gero,

Some question about release 1.1.

	I am want to make some minor fixes into last release (like preset year
month for track time). In what bracnh better to make this, 1.1 or head
branch?
	Currently I am want to make chenges in last release, but also I am want
that they appears in head branch.
	And also, other issue. I am try to make such small fixes some time ago, but
in that time you actively develop last release, and usually I am simple can
not launch it (or its work very buggly). The fact is that I am try to really
use last (head) branch and make fixes in it, but due it work bad I am stop
this work.
	Possible for this time will be better to stop (for some time) develop
extremly new functionality on head branch, and make only small fixes and
improvements. That helps to make fixes only on main branch, and do not merge
them (release and main branch). For now version have many new very usefull
and great fucntions, but in same time (as you can read in the list) there
are many small things that prevent (or make not comfort) its real using.
	What you think?

Thanks,
Sergey

On Fri, Apr 04, 2003 at 06:58:15PM +0200,
Gero Kohnert <gok...@us...> wrote:

> as promised (for two month now) here is the new 1.1 release.

Congrats!

Is the migration of the database from 1.0 is easy ?

Thanks,

makoto
-- 
Kikutani, Makoto

Hi List,

as promised (for two month now) here is the new 1.1 release.

As small (not complete) list of changes

* better LDAP support that will allow the import of huge datasets via lda=
p
* birthday reminder via a watchlist when setting an adress on the watchli=
st
* attachments on email
* new newsticker module
* some old well known stuff is now handled as a module
  (installations,documentmanagement,mailbox)
* conflict check on appointment creation
* new emaillink to all project members
* move of bug/task between project subproject=20
* pop before smtp support

Structural changes:
* auth modules are now located in an auth subdir
* updated layout mechanism that will allow an more easily change of the u=
ser=20
interface. Currenly only a test_layout is supported.
* updated layout mechanism that will allow an more easily change of the u=
ser=20
interface. Currenly only a test_layout is supported.

As you seen a lot of changes are behind the scenes. The motivation for th=
e=20
structural changes were the hope that some guys will start to write

* modules that will give us new features
  see the module API ( in TUTOS since 1.0)
  (FYI: modules can have another non GPL license)=20

* new or modified layouts
  see the layout engine stuff in php/layouts and the test_layout
  it should be more or less easy to make a Corporate L&F when using TUTOS=
 in=20
some intranet

* auth mechanism
  see LDAP X509 ClassicLogin in the php/auth subdir

Please tell us here if you have a new Module/Code so I can announce it on=
=20
SourceForge (if wished). Also we can avoid some reinventions.



have a nice weekend

Gero

Hi List,

FYI

In preparation of a 1.1 Release I created a new Branch
in CVS called BRANCH-1-1 which will host the  future
1.1 releases and fixes.

If you run a 1.1 CVS installation you should perform a

cvs update -r BRANCH-1-1

in order to get the latest and greatest software


regards

Gero