tutos-devel Mailing List for TUTOS

sorry, i should mention it.

apache 2.0.50, tutos -- latest cvs branch 1.2

the problem is really the getBaseURL() func here: when the port is not set
(just the htpps://... url without port specification), PHP (4.3.8) probably
fills it with default (80) without making any assumptions.

the first request is sent to https://...:443 directly, so the port is set to
443.  other requests are just with the htpps://... -- and the port is set to 80
-- this is no problem for normal work -- the actual port used is 443 indeed, so
the communication is encrypted, but when i try to logout, TUTOS sends me to
$_SERVER["SERVER_PORT"] which is set to 80 (thanks to PHP).

i dont find it a very big problem, but i thought that not just me is having
such a behaviour -- it is due to my non-typical configuration.

if my www server (not secured) would be on 80 port, everything would be fine --
the logout page would send me to 80, where i would find my redirection script
that will bring me back to 443 and everyone would be happy :), but the
non-encrypted version runs on 8008 (80 is occupied) and the logout page sends
me to 80, where no TUTOS awaits me :(.

getBaseURL_special() solves this problem, but testing the $_SERVER["referer"]
field would do the job also -- it contains the whole uri scheme.

and also, the getBaseURL() makes tests against $_SERVER["HTTPS"], which i cant
find in the docs of php 4.

m.

P.S. try a simple script

<?php

header("Content-Type: text/plain");

$tmp = "";
foreach ($_SERVER as $key => $val) {
    $tmp .= sprintf("%s => %s\n", $key, $val);
}
echo $tmp;

?>

to see what i mean -- connect to this script with

https://localhost/~martin/prac/test_port.php (just https:// scheme without
port)

https://localhost:443/~martin/prac/test_port.php (port spec included)

you will see $_SERVER["SERVER_PORT"] once as 80 and once as 443, though both
pages are encrypted.

On Wed, Jan 19, 2005 at 09:26:29PM +0100, Javier Linares wrote:
> On Wed, Jan 19, 2005 at 08:22:40PM +0100, ma...@ce... wrote:
> > im about to make one ugly hack and i am asking if i should make it also to 1.2
> > branch and above.
> 
> I don't know what server you're using, but I am using TUTOS with https://
> and I had no problems at all in the installation nor had I to hack
> anything (.I'm using Apache2).
> 
> Before hacking, have you tryied to get it working using another web
> server? Maybe in another server?.
> 

----- End forwarded message -----

----- End forwarded message -----

----- End forwarded message -----

Id=E9zet Javier Linares <de...@ja...>:

> I don't know what server you're using, but I am using TUTOS with
> https://
So do I.

> and I had no problems at all in the installation nor had I to hack
Neither did I. :)

> anything (.I'm using Apache2).
I have Apache 1, and everything is fine. And the same TUTOS is accessible=
 on the
same server with http and https as well (on different URLs), without any =
hacking
in TUTOS itself - but I had to spend some time with apache's and bind's c=
onfig...

Bye
Boobaa
---------------------
http://boobaa.ajrg.hu

On Wed, Jan 19, 2005 at 08:22:40PM +0100, ma...@ce... wrote:
> im about to make one ugly hack and i am asking if i should make it also to 1.2
> branch and above.

I don't know what server you're using, but I am using TUTOS with https://
and I had no problems at all in the installation nor had I to hack
anything (.I'm using Apache2).

Before hacking, have you tryied to get it working using another web
server? Maybe in another server?.

-- 
 .''`.   Javier Linares
: :'  :  javier at javierlinares.com
`. `'`   http://javierlinares.com  
  `-

hi,

im about to make one ugly hack and i am asking if i should make it also to 1.2
branch and above.

it is going to be a getBaseURL() ('webelemts.p3') modification.

current implementation does not recognize that im using https instead of http.

$_SERVER["SERVER_PORT"] says im using 80
$_SERVER["HTTPS"] is not set nor documented in PHP (4.3.8)

my https runs on 443 (default)
my http runs on 8008

the getBaseURL()

now i just modified the getBaseURL_special() function to return the proper
value, but i want to ask if there is some more general way?

i was thinking about using even the referer field, which hold complete url
altogether with scheme (https):

if (startswith("https", $_SERVER["referer"]) redirect to https

m.

P.S. a sub-question

i set the $GLOBALS["tutos"][baseurl] to st like:
"https://<domain>/<tutos_path>, but in admin page (admin_show.php) the baseURL
field is filled with non-sense == "h/php/".  anyone knows why?

snip from admin_show.php:

echo $this->showfield("BaseURL");
echo $this->showdata(makelink(getBaseUrl(true),getBaseUrl(true)),6);

why is that? why just dont simply show $tutos[baseurl] value?

thx.

On Tue, Jan 18, 2005 at 10:03:21PM +0100, martin wrote:
> hope my mail was not an arrogant one.
> 
> i was just saying the same -- i think that support and develop TUTOS (if we
> like its functionality) is better spent time than to develop similar project
> from scratch.
> 
> I must agree that good documentation is key of success.
> 
> i would like to see some broader discussion on future TUTOS design -- I
> downloaded BRANCH-2.0 some time ago, but its hard and time consuming to browse
> the source and get the ideas from there.  Few comments would be welcome and it
> does not need a great amount of time to write down a list where the project is
> aiming and what has to be in TUTOS 2.0.
> 
> m.

Le Mardi 18 Janvier 2005 22:03, Martin Slouf a =E9crit=A0:
> i was just saying the same -- i think that support and develop TUTOS (if =
we
> like its functionality) is better spent time than to develop similar
> project from scratch.

In fact, we've studied our options here, and had this very same problem whi=
ch=20
seems to occur again right now.

The facts are simple ones : TUTOS is an overall good product, but some part=
s=20
of it are limiting its usability (presentation, notifications, some code=20
organization, etc...)

The solution is one of them :
 . consider the work done and try to make TUTOS a better system
 . consider it's high time for complete rewritte

Here, we've bet on the first alternative, which has bring us (even if i'm t=
he=20
only developer involved, this concerns other people here) to BRANCH-2-0.

> I must agree that good documentation is key of success.

The wiki is a good tool for documenting, the first step would be to report=
=20
back in the admin guide and the user guide we have in docbook in the CVS.

> i would like to see some broader discussion on future TUTOS design

I'd really appreciate such a discution to happens, and would love to see so=
me=20
developers to participate in the work involved.

> I downloaded BRANCH-2.0 some time ago, but its hard and time consuming to
> browse the source and get the ideas from there.

Please don't hesitate asking your questions, I'll try and take time to answ=
er=20
them as best as I can.

> Few comments would be=20
> welcome and it does not need a great amount of time to write down a list
> where the project is aiming and what has to be in TUTOS 2.0.

I may understand you're awaiting words from me ;)

Before starting the real discussion, what about a TUTOS 2.0 wiki subpart?
I'd like to keep the two major branches of TUTOS as common as possible, but=
=20
the facts are that the two branches are far from being mergeable by now, fo=
r=20
different reasons :
 . Gero does not have the time to handle it
 . For the merge to happen once, TUTOS 2 must provide all existing modules


You may already know what TUTOS 2 is about by reading my previous mails on=
=20
this list, as I'm doing some effort to be clear on what's going on in my CV=
S=20
branch.
Let's state it one more time :
 We want TUTOS to be a great tool for company usage, allowing for project a=
nd
 resource management.

 Such a goal implies a lot of work:
  1 redesign the code responsible for the HTML generation, possibly offerin=
g a
    way to easily edit the output without being confronted with TUTOS code

  2 adapt the existing layout to provide a better user experience

  3 rework some modules which slightly miss the point

  3.1 task volume management deserve some rethought (volume planned/done/to=
do)
  3.2 bugtracking module does not allow time booking
  3.3 notifications are often duplicated (watchlist and bugtracking)
      and imprecise

  4 provide a way for easy TUTOS integration with other products, or for us=
ing
    TUTOS without it's HTML interface

  5 projects hierarchy should worh the same as tasks one

  6 task dependencies, with auto volume calculation and date handling

  7 we still need to rewrite scheme.php for TUTOS 2 to have a TUTOS 2 relea=
se,
    I hope to be able to do this by this very month

  ...

Some parts are already available in the CVS :
 1 is done, we are using the Smarty template engine for easy edition of
   HTML output

 2 is done too, as a matter of facts our users have enjoyed the new TUTOS
   layout and presentation, although they had simply refused to use the old
   one

 3.1 and 3.2 are done, the rewritte of the bugtracking lose data
   compatibility, so a php migration script has been written to handle the
   migration automatically for you.
   Please try it!

Next points are already planned for development here, and of course the cod=
e=20
will be in the CVS as soon as possible.

 3.3 and 5 will be done soon, they're the next on my TODO list
 4 will be done (hopefully by spring) by providing an XMLRPC interface


If you see some other points to add to the list, please let me know, as=20
there's big chances those will have some interest for us to handle.


I also have some ideas about SQL management. I'm not sastified with any of =
the=20
code level database abstraction systems. I'd like to provide a new model=20
using templates.
You would have to provide a template for each SQL interaction, or if needed=
=20
several SQL requests for one function. We'd have a php base sql class,=20
specialized for each supported RDMBS, and a template set to be called.

Of course the database creation would be an SQL script template to be calle=
d=20
by the code...

Then a DBA would be able to optimize each and every request and the schema,=
=20
and we could support specific RDBMS features (think about integrity=20
constraints, complex queries, views and stored procedures, and mysql suppor=
t,=20
for example).


Any ideas welcome, of course,
=2D-=20
Dimitri.
http://dim.tapoueh.org

Un journal d=E9coup=E9 en morceaux, =E7a n'int=E9resse pas une femme.
Mais une femme d=E9coup=E9e en morceaux, =E7a int=E9resse les journaux.
 -- Coluche

> it has maybe nicer design, but you have an idea what it will take you
to
> bring it to TUTOS functionality (project roles, documents, companies
with
> contacts, references, ...)  and its community base?

Main things are already in place. Actually it is not long to make all
other. As I said before TUTOS (historically) have lot of code not
directly linked with it's main functionality. We use as much as possible
all code that can be found at pear.php.net. These are the translation,
localization (locale date and time), db abstraction and so on. Some code
that GERO coded manually is just already exist and maintained by others
at pear net. Sure, when GERO was started this, pear net just absent. But
why not use it now?

> TUTOS has about: 160 000 SLOCs (source lines of code, cvs 1.2 branch)
> 		 more than 30 business layer classes
> 		 more than 40 db tables

Well, many, not mean _good_. I think all agree with this :). Any way, at
some moment it is required the "fresh look", rather than maintaining of
some old code and db structure.

And the last. For the last 2 years I never see there any discussions
about tutos developemnt, future plans and so on. It mostly _inactive_.
Why? May be because nobody need more functionality? Or may be because
actually not so easy to modify it? I believe that 95% of TUTOS made
_only_ by GERO.
 

> Most of the sources say they are under GPL, but I am not sure. Your
> homepage is not clear about this, and there is some blurring with
those
> licenses (for free programs as well). Is SEMA really GPL'ed?

Sure, it is GPL'ed, we just published is in most simple for us
environment. 
Actually, right now we just show what we make, and looking for those who
interested in ideas of SEMA. If we find that there is enough interest to
contribute to project it will be published at sf.net, or at tigris.org.
I like the last the much, since they have more tools for OSS
collaboration (voting on issues and so on). However code already opened,
and fully GPL'ed.

> You are declaring SEMA to be fast enough on "inexpensive hosting" - I
> would be interested on the hardware which the demo runs on, to be able
> to compare the runtimes.

This is VPS (virtual private server) hosting with guaranteed 128 Mhz CPU
and 128 RAM. We also have some on linux box p2-233. Just for comparison
TUTOS need 3-4 s for page generation there, while SEMA about 1-1.5. And
this without any specific optimizations.

> I think the most important thing for any particular project to a
wannabe
> developer is good documentation.

Well, it's really missing now. However ideas are clear, code is simple
and opened. Goals are also clean.
With enough interest to project we will have it. If no, not problem
also, since it suits our needs.

And the last, to not disturb TUTOS list, I will appreciate if any other
discussions will occurs at sema mailing list:
http://pushok.com/mailman/listinfo/sema_pushok.com

WBR,
Sergey Korotkov

Hi,

Unfortunally I hadn't done a lot with tutos the last months,
since I was ill and had to focus on my customer wishes.

But I want to say a few things.

As Martin says, it's TuTos is not a small one day programm.
It's a complex software for a lot of business modells.

Also I don't like the code of the 1.x brunches not very much,
(cause you couldn't change the layout easily), it has a good structure
and. 

If I would look at the disadvantage fo TuTos I would say it's
A) no (real) possibility to change the layout
B) it hasn't a good usability. You need to work for a longer time with
it, to know
   how to work with, and there could be a lot of steps easier.
C) No marketing is done, also a big community is there and should do it
;-)

No disadvantage is for me, the point that it doesn't run with 1) euro
packages
TuTos isn't as slow as you need an own server for it, but you need the
possibility
To create a .htaccess file for changing filetypes.

But you get this for example in germany for 9.90 Euro (
www.domainfactory.de ) and 
even cheaper.

BUT!!!

IMHO you won't find a software with such a lot (and good)
functionallity.
It's easy to include own modules with a nice API.

You could also write you're own application when you've understand
databasemodel
behind, without using the TuTos itself. For example to implement it in
you're
customer Frontend. (I've written a proove of concept 2 years ago).

So writting it new, just to run it on an 1 Euro hosting, instead of 
working together with the 2 main programmers and maybe 3 or 4 other
programmers working
on it.

I think if it is possible to clear A & B tutos could be an really wide
used software,
and could use for project Management even in bigger (not IT) companies.

You could sell services or just be happy that bigger companies will
sponsor
the developing so it could get better and better.

So come on and work on tutos instead of working on other systems :-)
If we've 10 systems where 20 people are working on, none of them
will get an real opportunity for a commercial solutions, but
if all 20 are working together it could be one very soon :-)

Greetings Volker

hope my mail was not an arrogant one.

i was just saying the same -- i think that support and develop TUTOS (if we
like its functionality) is better spent time than to develop similar project
from scratch.

I must agree that good documentation is key of success.

i would like to see some broader discussion on future TUTOS design -- I
downloaded BRANCH-2.0 some time ago, but its hard and time consuming to browse
the source and get the ideas from there.  Few comments would be welcome and it
does not need a great amount of time to write down a list where the project is
aiming and what has to be in TUTOS 2.0.

m.

Martin Slouf =EDrta:
> looking at sema now,
I also had a quick look at SEMA, and shot a glance at the source as=20
well. UI looks impressive (I have seen this kind of arrangement here and=20
there, eg. PHProjekt), DB abstraction and multi-tiering sounds good, but=20
I have some questions.

Most of the sources say they are under GPL, but I am not sure. Your=20
homepage is not clear about this, and there is some blurring with those=20
licenses (for free programs as well). Is SEMA really GPL'ed? If so, why=20
don't you make it available here on SF.net? If it is not really GPL'ed=20
(needs those licenses to run, etc.), then why do you advertise it as=20
"free of charge basis"?

You are declaring SEMA to be fast enough on "inexpensive hosting" - I=20
would be interested on the hardware which the demo runs on, to be able=20
to compare the runtimes.

I think the most important thing for any particular project to a wannabe=20
developer is good documentation. I have spent quite some time on your=20
pages to have a closer look at eg. the multi-tiering ideas, but could=20
not found anything - besides, there are some ad words, but I wouldn't=20
call it documentation. How is it implemented? What if I want to write a=20
standalone (ie. not web) frontend for SEMA? (TUTOS lacks this kind of=20
documentation as well; if I want to write a new module, I wouldn't know=20
where to start. But at least TUTOS has a wiki - which I should append,=20
too...)

I appreciate your work, and would be interested in it, but hey guys,=20
wouldn't it be easier to help Gero and the TUTOS team to make TUTOS more=20
clear? Both for customers and programmers? Er, you wrote it wouldn't...

And in turn: hey we, TUTOS guys: why do we look angry at PushOK if they=20
write another CRM or anything? If TUTOS lack some features which they=20
always wanted to use, but cannot be implemented in its current design,=20
and that is why they wrote SEMA, it is their time, their decision how to=20
spend it.

At last: methinks both projects can learn from the other, then why are=20
you/we so arrogant? There are some very good ideas in both projects=20
which the other should implement - and both has disadvantages as well.=20
And neither will loose profit because of the other, since they are both=20
free software.

Anybody is welcome to correct me if I'm wrong anywhere.
--=20
Bye
Boobaa (Cs=E9csy L=E1szl=F3)
----------------------
http://boobaa.ajrg.hu

(sorry, just forwarding it, i have a spam mail problems :(, hope it wont get
posted twice)

On Tue, Jan 18, 2005 at 11:19:08AM +0100, martin wrote:
> looking at sema now,
> 
> it has maybe nicer design, but you have an idea what it will take you to bring
> it to TUTOS functionality (project roles, documents, companies with contacts,
> references, ...)  and its community base?
> 
> for the 1st view it looks much simpler. (i just created one task, the
> connection is not good and page reloads take centuries -- more than a
> minute. :)
> 
> say it again, better help to improve TUTOS than writing your own program.  at
> least i would welcome your activity and if we can conclude to implement some
> changes, i would be glad to help redesigning such a good system.
> 
> TUTOS has about: 160 000 SLOCs (source lines of code, cvs 1.2 branch)
> 		 more than 30 business layer classes
> 		 more than 40 db tables
> 
> Regards, martin.
> 

Le Lundi 17 Janvier 2005 19:09, Sergey Korotkov a =E9crit=A0:
> we do not have success. Many reasons there: hard navigation, serious
> resource requirements
> (it just not work on cheap hosting),  bad notifications and so on. All
> that things prevent us to
> use it for longer that 3-4 weeks.

Those problems are the one we are trying to solve in BRANCH 2.0, which we h=
ope=20
to be able to merge some day...

=46or information, a complete review of notifications (watchlist and=20
bugtracking) is already planned here, development should happen shortly (sa=
y=20
by next month).

> It makes tutos more nice, and much more resource dependant.

Smarty has a nice caching system, which you may want to use :
  http://smarty.php.net/manual/en/caching.php

>  So, as the result we tried develop prototype of new, TUTOS like system
> that claimed to solve all
> current issues. It also published under terms of GNU GPL.
> http://www.pushok.com/soft_sema.php

Have a nice time writting this software,
=2D-=20
Dimitri.
http://dim.tapoueh.org

Il est exact que =E7a porte malheur de se marier un vendredi 13,
car il n'y a pas de raison pour que ce jour fasse exception.

hi,

glad someone posted such a mail.

first, i use TUTOS quite extensively for a daily work and it meets my
requirements.  im quite content with it.

i dont much get the resource complains, 'cause all you need is http server with
php and mysql database (among others).  for a company with up to 25 employees
and normal connectivity to the net the load is ok as far as i can say.

the installation manual is clear and i found no problems, though, opinions may
vary.

second, a time ago i have registered myself as a TUTOS developer and before any
serious updates (im working on syncML and some custom modules on filtering mail
and auto assign of email messages to projects as files) i spent some time with
analysis.

i also discovered several naughties i dislike, especially in presentation
layer, but for my part, TUTOS offers great functionality that (if written from
a scratch) could be time consuming to implement and hard.

so much more reasonable for me seems to help with the TUTOS redesign and
improvements than to strat a new project (i guess also in PHP?)

TUTOS db layer is reasonably good and all the object references are nice
feature.

- - - - next up are some comments on my analysis - - - -

motivation was to:

1. pass the exam :) (i did)
2. provide quality documentation for me, and eventually for the community

i have written a thesis on TUTOS (two weeks ago i just got finished it). it
includes some UML diagrams and comments on how TUTOS internals work and
suggestions how should they work (in my opinion).

the bad news is i have to write in my native langugae (czech), due to some
requirements.  nonetheless, i may publish some basic UML diagrams, while im
working on some more detailed ones in my free time as well as on a brief
translation.

have a look at: http://www.justlogin.cz/martin/prac/tutos/img/ , without
commenst it wont be much of use, but i reccommend:

(all diagrams use TUTOS class names)

conception diagram -- basic TUTOS entities
http://www.justlogin.cz/martin/prac/tutos/img/conception.jpg

separation into layers:
http://www.justlogin.cz/martin/prac/tutos/img/layersbrief.jpg

application layer:
http://www.justlogin.cz/martin/prac/tutos/img/modulesbrief.jpg
http://www.justlogin.cz/martin/prac/tutos/img/modulesbrief2.jpg

current presenation layer:
http://www.justlogin.cz/martin/prac/tutos/img/preslayer.jpg

new design of the presenatation layer:
(use case)
http://www.justlogin.cz/martin/prac/tutos/img/preslayerusecase.jpg
(object model)
http://www.justlogin.cz/martin/prac/tutos/img/preslayerom.jpg 

in case of any czech speaking person here :), see the whole thesis at:
http://www.justlogin.cz/martin/projekty/diplomka.tgz

- - - - conclusions i have made on TUTOS design and new suggestions - - - -


abstract of the thesis:

This thesis presents analysis of TUTOS, the web information system.  TUTOS is
sf.net project licensed under GPL.  It can be used as a project management
tool, while providing also other functionality.  The main objective is to
provide description of the system design using OMT method as well as present
detailed view on problematic parts of the system and suggest an appropriate
solution.  First part of the thesis describes the system.  Second part suggests
and discusses the solutions.  Description of the system is based on system
layers --- presentation, application (business) and database layer.  Database
and application layers have very few failures and all of them could be safely
fixed.  The most complicated solution is suggested for presentation layer,
which lacks support for alternative outputs formats, such as XML.  Significant
part of the thesis is dedicated to the new presentation layer design.

conclusions (brief, pls have a look at the layersbrief.jpg picture
http://www.justlogin.cz/martin/prac/tutos/img/layersbrief.jpg):

* database layer should avoid using its own db library and use some major
supported one -- ADOdb for example

benefits:
	- more supported databases
	- easy to work with (it designed based on proved concepts (JDBC etc.))
	- no need to care of db code anymore

probleID' method
	  . 'getObject(objectID): TutosBase' method

* application layer should separate and clarify the associations between
Tutos_Module and Tutos_Base classes.  Tutos_Base could be slightly redesigned
in order to work with new presentation layer.

benefits:
	- better and clearer design, with MVC design pattern
	- module creation would be easy and separated from application class
	creation (ie. Invoice is an application class as well as a module)

problems:
	- code rewrite (more than in database layer)

* presenation layer is completely new.  one of the worst things in TUTOS and
what frightened me when i first saw it was the HTML page generation.

reasons for redesign:
	- overall bad class structure (sorry to say that)
	- separation of application layer services from presentation layer
	services to enable more output formats transaparently -- ie. XML, PDF
	and more

benefits:
	- separation of business logic from presentation (MVC)
	- transparent output to other formats

prblems:
	- many

- - - -

also, any comments would be welcommed.

for example it would be nice (for the start) if each active developer made some
proposals and made them open here, in this list.

regards, martin.

On Mon, Jan 17, 2005 at 09:07:50PM +0300, Sergey Korotkov wrote:
> Hello list,
>  
>   I am learned about TUTOS long time ago, and even trying to take part
> in it's development.
>   However, even we have tried to use it several times in production (not
> with nice play around)
> we do not have success. Many reasons there: hard navigation, serious
> resource requirements
> (it just not work on cheap hosting),  bad notifications and so on. All
> that things prevent us to
> use it for longer that 3-4 weeks.
>  In the same time, we consider that ideas of TUTOS is very good and
> required for some groups 
> like ours. Also, it is really nice that some development in branch 2.0
> are done, however for me it
> just cosmetic and usage of intermediate template engine does not change
> current architecture
> and not fixes current problems. It makes tutos more nice, and much more
> resource dependant. 
>  So, as the result we tried develop prototype of new, TUTOS like system
> that claimed to solve all 
> current issues. It also published under terms of GNU GPL.
> http://www.pushok.com/soft_sema.php
>  
> Any comments are welcome.
>  
>  
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Tutos-commits mailing list
> Tut...@li...
> https://lists.sourceforge.net/lists/listinfo/tutos-commits

looking at sema now,

it has maybe nicer design, but you have an idea what it will take you to bring
it to TUTOS functionality (project roles, documents, companies with contacts,
references, ...)  and its community base?

for the 1st view it looks much simpler. (i just created one task, the
connection is not good and page reloads take centuries -- more than a
minute. :)

say it again, better help to improve TUTOS than writing your own program.  at
least i would welcome your activity and if we can conclude to implement some
changes, i would be glad to help redesigning such a good system.

TUTOS has about: 160 000 SLOCs (source lines of code, cvs 1.2 branch)
		 more than 30 business layer classes
		 more than 40 db tables

Regards, martin.

Le Mardi 18 Janvier 2005 08:08, John Joseph a =E9crit=A0:
>     I found in  tutos , exatly what I needed , excpet I am finding
> difficult in configuring for LDAP authetication , In fact this problem is
> because of my lack of knowledge in LDAP and PHP module

There's documentation in the TUTOS admin guide, and since the easiest way t=
o=20
find out documentation and keep it up to date is using our wiki, I've just=
=20
added this part in :

  http://wiki.tutos.org/index.php/Admin_ldap

>      You could have involved in tutos and to make it an excellent tools or
> do some documentation of LDAP authentication ,

Please have a look at the documentation of TUTOS in the cvs, and if any lis=
t=20
reader has some time, it seems a good idea to incorporate existing=20
documentation in the wiki...

Regards,
=2D-=20
Dimitri.
http://dim.tapoueh.org

Les fonctionnaires sont les meilleurs maris : quand ils rentrent =E0 la
maison, ils ne sont pas fatigues et ont d=E9j=E0 lu le journal.

Hello 
    I found in  tutos , exatly what I needed , excpet I am finding difficult in configuring for LDAP authetication , In fact this problem is because of my lack of knowledge in LDAP and PHP module 
      
    I had given the refernce of this software to all of my friends in UAE
  Sanjeev:-
     You could have involved in tutos and to make it an excellent tools or do some documentation of LDAP authentication ,
               
         Best of luck for your new software , I am checking the site now 
               Thanks 
                 Joseph John 

Sergey Korotkov <Ser...@ma...> wrote:
Hello list,

I am learned about TUTOS long time ago, and even trying to take part
in it's development.

		
---------------------------------
 ALL-NEW Yahoo! Messenger - all new features - even more fun!  

Hello list,
 
  I am learned about TUTOS long time ago, and even trying to take part
in it's development.
  However, even we have tried to use it several times in production (not
with nice play around)
we do not have success. Many reasons there: hard navigation, serious
resource requirements
(it just not work on cheap hosting),  bad notifications and so on. All
that things prevent us to
use it for longer that 3-4 weeks.
 In the same time, we consider that ideas of TUTOS is very good and
required for some groups 
like ours. Also, it is really nice that some development in branch 2.0
are done, however for me it
just cosmetic and usage of intermediate template engine does not change
current architecture
and not fixes current problems. It makes tutos more nice, and much more
resource dependant. 
 So, as the result we tried develop prototype of new, TUTOS like system
that claimed to solve all 
current issues. It also published under terms of GNU GPL.
http://www.pushok.com/soft_sema.php
 
Any comments are welcome.