grouptime-developers — Information, announcements etc. meant for the grouptime team members.

[Grouptime-developers] $B=PMh$A$c$C$?$N(B

[<in...@qs...>]

     $B!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y(B
     $B!y!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!z(B
     $B!z!!!!L5NA$N=P2q$$7O$,=PMh$A$c$C$?$N!!!y(B
     $B!y!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!z(B
     $B!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z(B



     $B!!A4$/$NL5NA$J$N$GEPO?$7$F$h!<(B
$B!!(B     http://www.ya2dic.com?num=2001
$B!!(B   $B$_$s$J$GEPO?$7$J$$$H3Z$7$a$J$$$h!<(B

          $B!&%(%s%H%j!<EPO?!!(BFREE$B!*(B
          $B!&%W%m%U1\Mw!!(BFREE$B!*(B
          $B!&%a!<%kAw<u?.!!(BFREE$B!*(B
          $B!&<L%a1\Mw!&7G:\!!(BFREE$B!*(B


$B!!(B     http://www.ya2dic.com?num=2001
  $B%(%C%A$J;R!!%m%j$J;R!!G($l$F$k;R!!A40w=89g!*(B



$B"(;HMQ$7$F$$$k$&$A$K2]6bH/@8$J$s$F$3$H$O$"$j$^$;$s!*(B
$B!!$:$C$HL5NA$G$4MxMQ$K$J$l$^$9!*(B

[Grouptime-developers] Long time no see

[Jan U. <sa...@ko...>]

Hi!
 
I'm happy to announce that i'm graduated Tallinn Techincal University
and now
i've got a little bit more time for group.time 2k2.
So! As i haven't heard much about you guys, lets keep doing this thing.
As i remember
correctly, Lucas promised to write some preliminary docs. How about it
lucas...
Of course, there is much my fault, that i've not been very active for
past two month
and i promise to fix that...
 
I think we sould get together and be a little bit more active (i mean
myself, sorry guys).
So, do you have any ideas, when???
 
PS! Merry forthcoming christmas and happy new year to everybody
 
With regards,
Jan Urva aka Sau
 

[Grouptime-developers] Textos...

[<au...@im...>]

Não deve ser nada de novo pra vcs, mas eu tava querendo saber mais
e tal... tá ai:

---------------------------------------------------------------------

 O que é Groupware?
 http://www.grupoelogica.com.br/suporte/terminologia/groupware.html

   Groupware é a palavra da língua inglesa que designa as ferramentas
 computacionais existentes para facilitar a comunicação, colaboração
 e coordenação de ações de diversas pessoas. Trata-se de uma série
 de ferramentas que permitem que pessoas trabalhem melhor juntas, o
 que facilita a integração, possibilita mais criatividade e inovação
 dentro da empresa, além de também permitir que respostas sejam
 encontradas mais rapidamente.

   Tipicamente, as ferramentas de groupware representam uma evolução
 das antigas ferramentas de workgroup, sendo estas caracterizadas por
 trazerem maior produtividade para cada pessoa isoladamente. Assim, se
 anteriormente as pessoas usavam ferramentas de agenda isoladamente,
 a partir da evolução para o groupware, a ferramenta de agenda passa a
 ser colaborativa; através da rede, todos podem ver as agendas dos
 demais e até mesmo agendar reuniões. 

   Outro termo muito usado quando se fala em groupware é "workflow",
 que diz respeito a groupware pois diversas ferramentas de groupware
 o implementam. Os chamados workflows ou fluxo de trabalho, também
 são formas de integrar pessoas, mas de uma maneira mais rigorosa,
 através de um fluxo de trabalho (por exemplo, um ciclo de aprovação
 no caso de um sistema de compras) bem definido.

---------------------------------------------------------------------

 Fluxo de Trabalho
 http://www.iis.com.br/~mlreis/fluxo.htm


   Ferramenta chave na automação de processos,substitui o tramite
 de documentos de papel. 

   Uma ferramenta de fluxo de documentos ou "workflow" é a de maior
 complexidade quanto à interface com o usuário. Ela possui funções de
 implementação de tomada de decisão, de desvio de processo, de
 atividades correlatas. 

   Como as atividades de trâmite de documentos variam muito de empresa
 para empresa e mesmo de setor para setor, os produtos oferecidos no
 mercado rumaram para a especialização ou para um excesso de generalização.

   Na hora da escolha da ferramenta, uma idéia deve estar sempre em mente:
 a transição do processo em papel para o processo totalmente informatizado
 é especialmente difícil para os funcionários e por isso a interface deve
 ser a mais amigável possível.


               Classificação de Ferramentas de Workflow

----------+-------------------+-------------------+---------------------
   Tipo   |Nível de utilização|Nível de atividades| Ferramenta auxiliar
          |  de documentos    |     externas      |
----------+-------------------+-------------------+---------------------
Produção  |       Alto        |       Baixo       |Armazenamento óptico
----------+-------------------+-------------------+---------------------
Administ. |       Alto        |       Alto        |Decisões, Regras de
          |                   |                   |Desvio, Grupos de
          |                   |                   |Trabalho e Gerenciamento
          |                   |                   |de documentos
----------+-------------------+-------------------+---------------------
Ad-hoc    |       Baixo       |       Baixo       |Groupware computing e
          |                   |                   |Correio eletrônico 
----------+-------------------+-------------------+---------------------
Colaborat.|       Baixo       |       Alto        |Gerenciamento de
          |                   |                   |documentos, Gerenciador
          |                   |                   |de tarefas, Gerenciador
          |                   |                   |de formulários
----------+-------------------+-------------------+---------------------

---------------------------------------------------------------------

Esse PDF parece ser bem explicativo:  (sobre Workflow)
http://www.fccn.pt/crc2001/pdf/posters/crc2001_p04_a28vf.pdf

---------------------------------------------------------------------

Aurium - com fome...
 
 
========================================================
  ,           ,
 /             \  Aurélio A. Heckert  [ GNU/Linux!!! ]
((__-^^-,-^^-__))    
 `-_---' `---_-'  Colegiado e Cultura - DACOMP
  `--|o` 'o|--'   Projeto Novas Lentes Para a História
     \  `  /      Integr. GAVRI-IM [Grupo Voluntário]
      ): :(       Integr. Prometeu [Neurônios->Sinapses]
      :o_o:       Compilador: http://www.freepascal.org
       "-"    
--------------------------------------------------------
  Entre para a lista de Pascal da UFBA    :   :   :   :
  Envie um e-mail para:                   :   :   :   :
  pas...@ya...    :   :   :   :
========================================================

"Se conhecimento é poder, que país governado por industriais
dará a verdadeira educação?. Cuidado com o feedback da miséria!"
  Tet Ramon

RE: [Grouptime-developers] Where are you guys!

[Cosimo V. <co...@da...>]

Hi all,
i'm still here but as my adsl connection home has expired
and for some reason i forgot it and they forgot to remind
it to me, i've to wait some days (perhaps 15) before it
will be newly activated.

So I can be online  only at work and it's not so easy to
discuss in IRC while at work..i hope you understand. :)

IMHO, discussing via email can be a right way to communicate,
it will take some more time than IRC, but being asyncronous
and living us in so different zones, i think it will be
the useful one.

Cosimo.

Il mar, 2002-10-01 alle 11:53, Jan Urva ha scritto:
> Hi,
>  
> > Sorry, tired with regular work, exciting about ming, bla... bla... 
> > that's make me forget this project for a while :) But, I'm still 
> > interest and still in. So, maybe we can help lucas about the doc and 
> > finish it, help vaga about template and we are ready to code. Let 
> > discuss it with this list. How about that?
> 
> Yes, thats nice, that you're still in :) In understand completely that
> from time to time we all have other things to take care of and that they
> are more important than gt. Don't worry, i've got quite busy myself.
> 
> About helping the vaga and lucas in qood thought, but we can't help them
> when no-one of them is in the IRC, we can't discuss these thing over
> e-mail,
> this is not very convinient. And also, for helping them, we need to know
> how
> far are they and what each partie must do. For now i know, that Lucas
> (and
> maybe one his friend also) making this core doc and hopefully we all can
> see
> the first draft, then we have good ground to move on. And Vaga promised
> to 
> improve a little bit of his templates system, so for now i'm waiting for
> them
> to send me (us) information on their progress.
> 
> Anyway, i'll try to be in the IRC as much as i can, so it's big
> possibility that
> you can find me there. 
> 
> One bad thing is that you're in Indonesia and Lucas is in Brazil, that
> makes the
> time difference almost 12 hrs, and Vaga, Andrey and me are in the middle
> of you 
> guys :) So it's very hard to find a proper meeting time, that all the
> parties can
> be there. I think we must find out some kind of compromise how to make
> these 
> meetings. But that's my work, so i'll try to think the best way for
> everybody.
> 
> With regards,
>      Jan aka Sau
> 
> > 
> > Regards
> > alfansa
> > 
> > 
> > 
> > Jan Urva wrote:
> > > Hi!
> > >  
> > > It has been for a while now when i last heard of you guys. The only 
> > > replay i got for previous letter was from Andrey Hristov. 
> > Lucas, Vaga, 
> > > Alfansa, where are you guys. Are you bored of this project 
> > already? If 
> > > so then pleas tell me so, no hard feelings will be held :). Or is 
> > > there some kind of other thing that don't work!? For the
> > > sake of the project just need to know who is in the project. 
> > >  
> > > With regards,
> > > Jan Urva
> > > Senior Development Specialist
> > > Realtime Ltd.
> > > GSM: +(372) 56 657 936
> > > Tel: +(372) 6 999 687
> > > E-Mail: ja...@re...
> > > ------------------------------------------------
> > > Why be difficult, when with just a little more effor, you can be 
> > > impossible!?
> > >  
> > > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by: DEDICATED SERVERS only 
> > $89! Linux or FreeBSD, FREE setup, FAST network. Get your own server 
> > today at http://www.ServePath.com/indexfm.htm
> > _______________________________________________
> > Grouptime-developers mailing list 
> > Gro...@li...
> > https://lists.sourceforge.net/lists/listinfo/grouptime-developers
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: DEDICATED SERVERS only $89!
> Linux or FreeBSD, FREE setup, FAST network. Get your own server 
> today at http://www.ServePath.com/indexfm.htm
> _______________________________________________
> Grouptime-developers mailing list
> Gro...@li...
> https://lists.sourceforge.net/lists/listinfo/grouptime-developers
> 

RE: [Grouptime-developers] Where are you guys!

[Jan U. <sa...@ko...>]

Hi,
 
> Sorry, tired with regular work, exciting about ming, bla... bla... 
> that's make me forget this project for a while :) But, I'm still 
> interest and still in. So, maybe we can help lucas about the doc and 
> finish it, help vaga about template and we are ready to code. Let 
> discuss it with this list. How about that?

Yes, thats nice, that you're still in :) In understand completely that
from time to time we all have other things to take care of and that they
are more important than gt. Don't worry, i've got quite busy myself.

About helping the vaga and lucas in qood thought, but we can't help them
when no-one of them is in the IRC, we can't discuss these thing over
e-mail,
this is not very convinient. And also, for helping them, we need to know
how
far are they and what each partie must do. For now i know, that Lucas
(and
maybe one his friend also) making this core doc and hopefully we all can
see
the first draft, then we have good ground to move on. And Vaga promised
to 
improve a little bit of his templates system, so for now i'm waiting for
them
to send me (us) information on their progress.

Anyway, i'll try to be in the IRC as much as i can, so it's big
possibility that
you can find me there. 

One bad thing is that you're in Indonesia and Lucas is in Brazil, that
makes the
time difference almost 12 hrs, and Vaga, Andrey and me are in the middle
of you 
guys :) So it's very hard to find a proper meeting time, that all the
parties can
be there. I think we must find out some kind of compromise how to make
these 
meetings. But that's my work, so i'll try to think the best way for
everybody.

With regards,
     Jan aka Sau

> 
> Regards
> alfansa
> 
> 
> 
> Jan Urva wrote:
> > Hi!
> >  
> > It has been for a while now when i last heard of you guys. The only 
> > replay i got for previous letter was from Andrey Hristov. 
> Lucas, Vaga, 
> > Alfansa, where are you guys. Are you bored of this project 
> already? If 
> > so then pleas tell me so, no hard feelings will be held :). Or is 
> > there some kind of other thing that don't work!? For the
> > sake of the project just need to know who is in the project. 
> >  
> > With regards,
> > Jan Urva
> > Senior Development Specialist
> > Realtime Ltd.
> > GSM: +(372) 56 657 936
> > Tel: +(372) 6 999 687
> > E-Mail: ja...@re...
> > ------------------------------------------------
> > Why be difficult, when with just a little more effor, you can be 
> > impossible!?
> >  
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: DEDICATED SERVERS only 
> $89! Linux or FreeBSD, FREE setup, FAST network. Get your own server 
> today at http://www.ServePath.com/indexfm.htm
> _______________________________________________
> Grouptime-developers mailing list 
> Gro...@li...
> https://lists.sourceforge.net/lists/listinfo/grouptime-developers
> 

Re: [Grouptime-developers] Where are you guys!

[Hansen <az...@ma...>]

Hi...,

Sorry, tired with regular work, exciting about ming, bla... bla... 
that's make me forget this project for a while :) But, I'm still 
interest and still in. So, maybe we can help lucas about the doc and 
finish it, help vaga about template and we are ready to code. Let 
discuss it with this list. How about that?

Regards
alfansa



Jan Urva wrote:
> Hi!
>  
> It has been for a while now when i last heard of you guys. The only
> replay i got for previous letter was from
> Andrey Hristov. Lucas, Vaga, Alfansa, where are you guys. Are you bored
> of this project already? If so then
> pleas tell me so, no hard feelings will be held :). Or is there some
> kind of other thing that don't work!? For the
> sake of the project just need to know who is in the project. 
>  
> With regards,
> Jan Urva
> Senior Development Specialist
> Realtime Ltd.
> GSM: +(372) 56 657 936
> Tel: +(372) 6 999 687
> E-Mail: ja...@re...
> ------------------------------------------------
> Why be difficult, when with just a little more effor, you can be
> impossible!? 
>  
> 

RE: [Grouptime-developers] Where are you guys!

[Lucas R. <lu...@uf...>]

Aurelio Heckert studies at the same University than me. It was me that
suggested him to participate. Hes a great programmer. :-)

Well, whn i said "docs patterns" i meant the formatting rules, sections,
to describe our software. For example, i need to describe the Database
Abstraction Component (DAC). There some classes in it. How we will
describe them? Exposing some examples, describing each class method, etc
etc.

now, do u know what i mean?

peace!

--lucasr

Em Seg, 2002-09-30 =E0s 10:20, Jan Urva escreveu:
> >We need to decide about a docs pattern
> What do you mean by that? Can you explain, then we can discuss this.
>=20
> With regards,
>     Jan
>=20
> PS! Do you know someone Aur=E9lio A Heckert? He's from Brazil also?
>=20
>=20
>=20
> > -----Original Message-----
> > From: gro...@li...=20
> > [mailto:gro...@li...] On=20
> > Behalf Of Lucas Rocha
> > Sent: 30. september 2002. a. 15:38
> > To: Grouptime
> > Subject: Re: [Grouptime-developers] Where are you guys!
> >=20
> >=20
> > Hi all! Sorry!
> >=20
> > i am just too busy cos of my work stuff!
> > In fact, i am getting some free time this week. I have=20
> > finished a basic genereric db component. I need to finish the docs!
> >=20
> > We need to decide about a docs pattern. How do we do this? I=20
> > need this defined to finish the docs...
> >=20
> > peace! I am IN the project! :-)
> >=20
> > --lucasr
> >=20
> > Em Seg, 2002-09-30 =E0s 09:04, Jan Urva escreveu:
> > > Hi!
> > > =20
> > > It has been for a while now when i last heard of you guys. The only=20
> > > replay i got for previous letter was from Andrey Hristov.=20
> > Lucas, Vaga,=20
> > > Alfansa, where are you guys. Are you bored of this project=20
> > already? If=20
> > > so then pleas tell me so, no hard feelings will be held :). Or is=20
> > > there some kind of other thing that don't work!? For the
> > > sake of the project just need to know who is in the project.=20
> > > =20
> > > With regards,
> > > Jan Urva
> > > Senior Development Specialist
> > > Realtime Ltd.
> > > GSM: +(372) 56 657 936
> > > Tel: +(372) 6 999 687
> > > E-Mail: ja...@re...
> > > ------------------------------------------------
> > > Why be difficult, when with just a little more effor, you can be=20
> > > impossible!?
> > > =20
> >=20
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf=20
> > _______________________________________________
> > Grouptime-developers mailing list=20
> > Gro...@li...
> > https://lists.sourceforge.net/lists/listinfo/grouptime-developers
> >=20

Re: [Grouptime-developers] Where are you guys!

[Lucas R. <lu...@uf...>]

Hi all! Sorry!

i am just too busy cos of my work stuff!
In fact, i am getting some free time this week. I have finished a basic
genereric db component. I need to finish the docs!

We need to decide about a docs pattern. How do we do this? I need this
defined to finish the docs...

peace! I am IN the project! :-)

--lucasr

Em Seg, 2002-09-30 =E0s 09:04, Jan Urva escreveu:
> Hi!
> =20
> It has been for a while now when i last heard of you guys. The only
> replay i got for previous letter was from
> Andrey Hristov. Lucas, Vaga, Alfansa, where are you guys. Are you bored
> of this project already? If so then
> pleas tell me so, no hard feelings will be held :). Or is there some
> kind of other thing that don't work!? For the
> sake of the project just need to know who is in the project.=20
> =20
> With regards,
> Jan Urva
> Senior Development Specialist
> Realtime Ltd.
> GSM: +(372) 56 657 936
> Tel: +(372) 6 999 687
> E-Mail: ja...@re...
> ------------------------------------------------
> Why be difficult, when with just a little more effor, you can be
> impossible!?=20
> =20

[Grouptime-developers] Where are you guys!

[Jan U. <sa...@ko...>]

Hi!
 
It has been for a while now when i last heard of you guys. The only
replay i got for previous letter was from
Andrey Hristov. Lucas, Vaga, Alfansa, where are you guys. Are you bored
of this project already? If so then
pleas tell me so, no hard feelings will be held :). Or is there some
kind of other thing that don't work!? For the
sake of the project just need to know who is in the project. 
 
With regards,
Jan Urva
Senior Development Specialist
Realtime Ltd.
GSM: +(372) 56 657 936
Tel: +(372) 6 999 687
E-Mail: ja...@re...
------------------------------------------------
Why be difficult, when with just a little more effor, you can be
impossible!? 
 

Re: [Grouptime-developers] Questions

[Andrey H. <and...@ma...>]

> -- Suggestion when is the best time for each one of you to meet next
> time?
>
I prefer meeting hours in the afternoon (GMT+2). 6am is quite early for me
because
I work till midnight and I am getting from bed in 6am GMT. Coming to work
30-60 minutes later.


Regards,
Andrey

[Grouptime-developers] Questions

[Jan U. <ja...@ko...>]

Hi!

Sorry, haven't got much time to deal with the project for a while now
but I'm trying to fix that problem :)

Anyway I have following suggestions/comments/questions:
-- please, can you be more active in IRC, we can't get any progress
without
communication.
-- Vaga: when can we see this templates system?
-- Lucas: when can we see this core documentation draft?
-- Can you have some comments about second meeting protocol?
-- Suggestion when is the best time for each one of you to meet next
time?

With regards,
       Sau

[Grouptime-developers] 2nd group.time meeting summary.

[Jan U. <ja...@ko...>]

Hi!

Ok, I've got some time now, and I wroted short summary of discussed 
in the 2nd meeting. Sorry it took so long, but I've been so busy lately.
Here it is:

http://grouptime.sourceforge.net/?main=12&task=view_topic&topic_id=30&fo
rum_id=13

Waiting feedback (in IRC preferrably).

PS! Lucas: How's the Core Doc is going
PS! Vaga: Yes, we use TAB's for identation, sorry, there was a little
mistake
in standard. I'll try to fix as soon as I can.

         Jan Urva

[Grouptime-developers] coding standards

[Cosimo V. <co...@da...>]

I'm going to rewrite template class code according to
our coding standards and to set tmpl tag to be more
php-style ({} instead of <>).

Reading the coding standard i found that this sentence:

indentation should be used four (4) whitespaces or TAB=92s that act like
four (4) whitespaces.

is the worst we can do.
We have to choose between spaces and tabs.

A tab is A CHAR (just one) that your application (it
can be your editor) *translates* it to a numbers of
pseudo-spaces. But it is only a char.
If I set my editor, to translate tabs to 2 spaces
(or eight) it's just what I see. Anyone else will see
it with its own preferences.

If we combine spaces and tabs we will have something
unreadable.

In my opinion tabs are better because anyone can choose
its own indentation and anyone will see that file the
way he preferes.
But if (for some reason) we choose "spaces" and not tabs,
it's ok, but only spaces in that case, not tabs.

Cosimo.

[Grouptime-developers] fundamental ideas [grouptime core]

[<lu...@uf...>]

Hi all! In peace?

I have some ideas about fundamental features of our core.
These are, as i see, the must-have features of this part of the 
project. I sorted this features by modules, they are:

::DB
  - Database independent
  - Configuration should be source independent, i mean, it should 
    be possible to load configuration vars from xml, text files,
    ldap, etc.
  - Must be all Object Oriented
  - It should be easy to port this database abstration to new database systems
    by just extending a set of basic classes (interfaces or abstract)

::Template System
  - Must be all Object Oriented
  - It should be easy to define new template structures (very extensible)
  - It should be very reliable and fast
  - it should support basic control structures like if, else, nested loops, etc

::User Management
  - Authentication
    + The login/password and group definition source must be transparent, 
      I mean, when writing scripts, it doesn't matter if the login/password 
      pairs and groups are being validated against a text file, xml, database
      or ldap server.
    + This authentication component will consist in these classes and some more:
      - User  - represents users :-P
      - Group - represents groups which contains other groups and users
    + It should be easy to extend these classes to support other kind of sources
  - Autorization
    + I should be able to map resources to user groups 
    + It should be easy to apply autorization setting to class methods
::Session Management
  - It should have all basic tasks for session:
    + Create session
    + destroy session
    + register new session vars
    + unregister new session vars

Probably you have percept that all modules hould have some kind of 
independence about the kind source from where they get configuration 
settings. I think we could develop a simple component that would be able to 
retrieve settings from diferent formats. For example, suppose that i need to 
load conf parameters to create a new database connection. I need to retrieve 
values like database name, host, username and password. This component could
load this from a xml, textfile, of ldap, using the same class interface. 
What do you think? This maybe sounds a litle bit complicated but it's not! :-)

Another feature that i think we should really rely on: all configuration files
must be in xml format. This is good for portability, interoperability with other
systems, and this is a very consisent format to describe data. I'd like to know
what do you think about this?

Please, suggest more things about these first ideas!

This is all for now.

peace!

--lucasr

-------------------------------------------------
This mail sent through IMP: http://www.webmail.ufba.br

[Grouptime-developers] Meeting, Friday 13th, 6am (GMT 0)

[Jan U. <sa...@kr...>]

Hi!

So, our second meeting will be held in mircx.com server,
#grouptime channel in friday 13th, 6am (GMT 0).

Also, one of the topics is when is the right time for
meetings, as most of us can be there.

Be there!
   Jan

Re: [Grouptime-developers] final comments

[Jan U. <sa...@kr...>]

Hi!

On 10 Sep 2002, Cosimo Vagarini wrote:

> Hi all,
> sorry not being here in this days but i wasn't home neither
> in office.
Don't worry, we all have our personal life aswell :) @ least most
of us :)

> I agreee with your "last" version.
>
> Are we sure we don't want to set some standard about variables
> names?
> I'm thinking not only to php variables but also (as in the
> "really final Luca's comments") to GET and POST variables.

If i remember correctly, there is standard about var names:
all the variable names must begin with lowercased word and if
there's another word(s), they must have the first letter capitalized:
$myVar;
$myNewVar;
$_GET['myVar'];
$_GET[$myVar];

> About on-line meeting, isn't there (during a week) an hour
> (a couple of hours) when we all are plugged?
for me, i'm practically all day 9:00am-12:00pm (GMT +3) in IRC,
therefore join me. i must say, that we should start using the irc
as our basic communication tool, meanign more people in online.

PS! Probably soon i'll move the #grouptime channel form mircx.com to
openporjects.net server. When i do, i inform you aswell :)

> I repeat my on-line status:
> 6.00AM -> 00:00AM (GMT 0) (during daytime I'm working but
> I can "steal" a bit of my time).
Fine, then at least this meating will be starting @ 6am GMT 0,
also, in this meeting we should discuss, when is the right time
to for meetings, so the most of us will be there.

Jan

>
> Cosimo.
>
>
>
>
>
> Il lun, 2002-09-09 alle 17:19, Lucas Rocha ha scritto:
> > Hi all! Here are my final comments about the coding standards.
> >
> > -------------
> >
> > In section 2.1 at the include/require/require_once/include_once explanation topic at line 2
> > it should be:
> > "When unconditional includings are needed, require_once() should be used.
> > When conditional includings are needed, then include_once() should be used."
> >
> > Instead of:
> >
> > "When the unconditional including needed, the require_once() should be used,
> > when the conditional including needed, then include_once() should be used."
> >
> > -------------
> >
> > Still at section 2.1 at the html explanation topic last line. It should be:
> > "For designing the templates, CSS should be used:"
> >
> > Instead of:
> >
> > "For designing the template the CSS should be used:"
> >
> > -------------
> >
> > Section 2.1 (yet!) at simple boolean expression topic. Is should be:
> > "ternary operator can be used for simple boolean expressions as following, but when the
> > expression is more complicated, all the other necessary standards should be used:"
> >
> > Instead of:
> >
> > "simple boolean expressions can be written as following, but when the
> > expression is complicated all the other necessary standards should be used: "
> >
> > -------------
> >
> > Section 2.2 the inicial text:
> > "In order to understand quickly the content of the directory structure, what some file
> >  might contain, we've made a simple file naming standard."
> >
> > Instead of:
> >
> > "In order to understand quickly when looking the directory structure, what some file
> > might contain, we've made a little file naming standard."
> >
> > -------------
> >
> > Section 2.3, class names:
> > "class names should match its file name without the '.class.php' sufix."
> >
> > Instead of:
> >
> > "class names should match it's file-based name without '_': MyClass.php."
> >
> > -------------
> >
> > Section 2.4 first topic should be:
> > "all the files, functions, classes and their methods should be commented so properly that
> >  even the developers, who are not familiar to the code, can easily understand and contribute."
> >
> > Instead of:
> >
> > "all the files, functions, classes and their methods should be commented so properly that
> > even the developers, who is not familiar the code, can easily understand and make a contribution."
> >
> > --------------
> >
> > Some "really" final comments: :-)
> > - Theres nothing about how to name variables that are passed via POST or GET. Do you think this important?
> > - I think we could add a last section that would give some practical information about who he/she can contact
> > to get more information.
> > - I think the docs should be distributed in pdf format because its pratical for printing and reading. The formats
> > could be rtf, pdf, html e txt. What do you think? The format conversions are very simples in this case.
> >
> > Thats all!
> >
> > p eace
> >
> > --lucasr
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: OSDN - Tired of that same old
> > cell phone?  Get a new here for FREE!
> > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > _______________________________________________
> > Grouptime-developers mailing list
> > Gro...@li...
> > https://lists.sourceforge.net/lists/listinfo/grouptime-developers
> >
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Grouptime-developers mailing list
> Gro...@li...
> https://lists.sourceforge.net/lists/listinfo/grouptime-developers
>

Re: [Grouptime-developers] final comments

[Cosimo V. <co...@da...>]

Hi all,
sorry not being here in this days but i wasn't home neither
in office.

I agreee with your "last" version.

Are we sure we don't want to set some standard about variables
names? 
I'm thinking not only to php variables but also (as in the
"really final Luca's comments") to GET and POST variables.

About on-line meeting, isn't there (during a week) an hour
(a couple of hours) when we all are plugged?

I repeat my on-line status:
6.00AM -> 00:00AM (GMT 0) (during daytime I'm working but
I can "steal" a bit of my time).

Cosimo.





Il lun, 2002-09-09 alle 17:19, Lucas Rocha ha scritto:
> Hi all! Here are my final comments about the coding standards.
> 
> -------------
> 
> In section 2.1 at the include/require/require_once/include_once explanation topic at line 2
> it should be: 
> "When unconditional includings are needed, require_once() should be used. 
> When conditional includings are needed, then include_once() should be used."
> 
> Instead of:
> 
> "When the unconditional including needed, the require_once() should be used, 
> when the conditional including needed, then include_once() should be used."
> 
> -------------
> 
> Still at section 2.1 at the html explanation topic last line. It should be: 
> "For designing the templates, CSS should be used:"
> 
> Instead of:
> 
> "For designing the template the CSS should be used:"
> 
> -------------
> 
> Section 2.1 (yet!) at simple boolean expression topic. Is should be:
> "ternary operator can be used for simple boolean expressions as following, but when the 
> expression is more complicated, all the other necessary standards should be used:"
> 
> Instead of:
> 
> "simple boolean expressions can be written as following, but when the 
> expression is complicated all the other necessary standards should be used: "
> 
> -------------
> 
> Section 2.2 the inicial text:
> "In order to understand quickly the content of the directory structure, what some file
>  might contain, we've made a simple file naming standard."
> 
> Instead of: 
> 
> "In order to understand quickly when looking the directory structure, what some file 
> might contain, we've made a little file naming standard."
> 
> -------------
> 
> Section 2.3, class names:
> "class names should match its file name without the '.class.php' sufix."
> 
> Instead of:
> 
> "class names should match it's file-based name without '_': MyClass.php."
> 
> -------------
> 
> Section 2.4 first topic should be:
> "all the files, functions, classes and their methods should be commented so properly that
>  even the developers, who are not familiar to the code, can easily understand and contribute."
> 
> Instead of:
> 
> "all the files, functions, classes and their methods should be commented so properly that 
> even the developers, who is not familiar the code, can easily understand and make a contribution."
> 
> --------------
> 
> Some "really" final comments: :-)
> - Theres nothing about how to name variables that are passed via POST or GET. Do you think this important?
> - I think we could add a last section that would give some practical information about who he/she can contact
> to get more information.
> - I think the docs should be distributed in pdf format because its pratical for printing and reading. The formats
> could be rtf, pdf, html e txt. What do you think? The format conversions are very simples in this case.
> 
> Thats all!
> 
> p eace
> 
> --lucasr
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Grouptime-developers mailing list
> Gro...@li...
> https://lists.sourceforge.net/lists/listinfo/grouptime-developers
> 

Re: [Grouptime-developers] News!

[Andrey H. <and...@ma...>]

 I cannot be here at this time. Why am and not pm.

Andrey
 
----- Original Message ----- 
From: "Jan Urva" <sa...@kr...>
To: <gro...@li...>
Sent: Monday, September 09, 2002 10:53 PM
Subject: [Grouptime-developers] News!


> I'm happy to announce as i didn't received any constructive
> feedback anymore, that the coding standard goes to final. Don't
> worry, if you have smht in your mind and you don't find it
> in the current standard. We're only in the beginning, so,
> we can review this sometime..
> 
> Therefore, we have to make now the core documentation ready to
> start programming. Therefore i think we should meet, is it ok,
> when  we hold the meeting in our usual IRC @ friday, 13th,
> 6:00am GMT 0 (i know, lucas it's quite late for you, can you
> handle that).
> 
> With regards,
>      Jan Urva aka Sau
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Grouptime-developers mailing list
> Gro...@li...
> https://lists.sourceforge.net/lists/listinfo/grouptime-developers

[Grouptime-developers] News!

[Jan U. <sa...@kr...>]

I'm happy to announce as i didn't received any constructive
feedback anymore, that the coding standard goes to final. Don't
worry, if you have smht in your mind and you don't find it
in the current standard. We're only in the beginning, so,
we can review this sometime..

Therefore, we have to make now the core documentation ready to
start programming. Therefore i think we should meet, is it ok,
when  we hold the meeting in our usual IRC @ friday, 13th,
6:00am GMT 0 (i know, lucas it's quite late for you, can you
handle that).

With regards,
     Jan Urva aka Sau

[Grouptime-developers] final comments

[Lucas R. <lu...@uf...>]

Hi all! Here are my final comments about the coding standards.

-------------

In section 2.1 at the include/require/require_once/include_once explanation topic at line 2
it should be: 
"When unconditional includings are needed, require_once() should be used. 
When conditional includings are needed, then include_once() should be used."

Instead of:

"When the unconditional including needed, the require_once() should be used, 
when the conditional including needed, then include_once() should be used."

-------------

Still at section 2.1 at the html explanation topic last line. It should be: 
"For designing the templates, CSS should be used:"

Instead of:

"For designing the template the CSS should be used:"

-------------

Section 2.1 (yet!) at simple boolean expression topic. Is should be:
"ternary operator can be used for simple boolean expressions as following, but when the 
expression is more complicated, all the other necessary standards should be used:"

Instead of:

"simple boolean expressions can be written as following, but when the 
expression is complicated all the other necessary standards should be used: "

-------------

Section 2.2 the inicial text:
"In order to understand quickly the content of the directory structure, what some file
 might contain, we've made a simple file naming standard."

Instead of: 

"In order to understand quickly when looking the directory structure, what some file 
might contain, we've made a little file naming standard."

-------------

Section 2.3, class names:
"class names should match its file name without the '.class.php' sufix."

Instead of:

"class names should match it's file-based name without '_': MyClass.php."

-------------

Section 2.4 first topic should be:
"all the files, functions, classes and their methods should be commented so properly that
 even the developers, who are not familiar to the code, can easily understand and contribute."

Instead of:

"all the files, functions, classes and their methods should be commented so properly that 
even the developers, who is not familiar the code, can easily understand and make a contribution."

--------------

Some "really" final comments: :-)
- Theres nothing about how to name variables that are passed via POST or GET. Do you think this important?
- I think we could add a last section that would give some practical information about who he/she can contact
to get more information.
- I think the docs should be distributed in pdf format because its pratical for printing and reading. The formats
could be rtf, pdf, html e txt. What do you think? The format conversions are very simples in this case.

Thats all!

p eace

--lucasr

Re: [Grouptime-developers] Coding Standard - is it ready?

[Jan U. <sa...@kr...>]

On Mon, 9 Sep 2002, Andrey Hristov wrote:

> Comments follow.
>
> ----- Original Message -----
> From: "Jan Urva" <ja...@ko...>
> To: <gro...@li...>
> Sent: Monday, September 09, 2002 6:31 PM
> Subject: RE: [Grouptime-developers] Coding Standard - is it ready?
>
>
> > > what about my proposals
> > > 1) to have C as prefix in the class names.
> > no C prefix, there's no point
>
> ok
>
> >
> > > 2)to use PHPDoc compatible comments - for file and functions.
> > > Constants will self explain them.
> > Nope, we use comments as they are described in our standard
>
> My reason to mention phpdoc comments is that there is phpdoc script that
> automatically generates
> help by parsing the code. I've used it and I liked it. The generated output
> is in XML and HTML so
> it is easily browseable. The HTML version has similarities of the Java docs.
> So the API can be generated with no hardness and regularily updated on the
> Home Page.
> I think is better to write comments in other way and to have automatic
> documentation generation.
Let's leave it open for now, i don't know about that, i have to think it
through. We're starting our comments standard.

>
> > 3)I see that there is no
> > > proposal for variable names : $some_var or $someVar. I think
> > > the former is better because the second is the way the
> > > methods are named. So by using the former it will be easier
> > > to track errors for using an property instead of calling
> > > method. ($s->updateThing vs
> > > $s->updateThing() ).
> > variable names are also used as $someVar, $someOtherVar
>
> I think that is not the best way.  PHP is case sensitive for vars so
> lowecased vars with
> words separated by _ is better (imo = in my opinion).
i know, but i like the $someVar more (and lucas likes it), so, i think
we'll keep it for now at least.
>
> > > 4)Strict typing :
> > >  If one var is used as int it will be int to the end of the
> > > script. In conditions IMO it is better to use === and !== to
> > > check and type. Otherwise problems can be faced. Consider
> > > this : <?php $str_val = '0'; if ($str_val) echo "one"; else
> > > echo "two"; ?> This will output "two" no matter that
> > > strlen($str_val) is not 0. This is type juggling. So use ===
> > > to check. 5)Casting : I prefer this : $i_var =
> > > (int)$some_str_val;  Others are (string), (float)
> > I've told you, both can be used, it's not a matter of standard as I see
> > it.
>
> ok
>
> > > New ones :
> > > 1)POSIX regex(ereg_* ) or PCRE regex(preg_*)
> > I preffer ereg_*.
>
> I will stick to preg_* much faster.
Ok, let's use preg_ then, no point of arquing, i think. For me it's
no difference actually...

Jan
> Andrey
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Grouptime-developers mailing list
> Gro...@li...
> https://lists.sourceforge.net/lists/listinfo/grouptime-developers
>

Re: [Grouptime-developers] Coding Standard - is it ready?

[Andrey H. <and...@ma...>]

Comments follow.

----- Original Message -----
From: "Jan Urva" <ja...@ko...>
To: <gro...@li...>
Sent: Monday, September 09, 2002 6:31 PM
Subject: RE: [Grouptime-developers] Coding Standard - is it ready?


> > what about my proposals
> > 1) to have C as prefix in the class names.
> no C prefix, there's no point

ok

>
> > 2)to use PHPDoc compatible comments - for file and functions.
> > Constants will self explain them.
> Nope, we use comments as they are described in our standard

My reason to mention phpdoc comments is that there is phpdoc script that
automatically generates
help by parsing the code. I've used it and I liked it. The generated output
is in XML and HTML so
it is easily browseable. The HTML version has similarities of the Java docs.
So the API can be generated with no hardness and regularily updated on the
Home Page.
I think is better to write comments in other way and to have automatic
documentation generation.

> 3)I see that there is no
> > proposal for variable names : $some_var or $someVar. I think
> > the former is better because the second is the way the
> > methods are named. So by using the former it will be easier
> > to track errors for using an property instead of calling
> > method. ($s->updateThing vs
> > $s->updateThing() ).
> variable names are also used as $someVar, $someOtherVar

I think that is not the best way.  PHP is case sensitive for vars so
lowecased vars with
words separated by _ is better (imo = in my opinion).

> > 4)Strict typing :
> >  If one var is used as int it will be int to the end of the
> > script. In conditions IMO it is better to use === and !== to
> > check and type. Otherwise problems can be faced. Consider
> > this : <?php $str_val = '0'; if ($str_val) echo "one"; else
> > echo "two"; ?> This will output "two" no matter that
> > strlen($str_val) is not 0. This is type juggling. So use ===
> > to check. 5)Casting : I prefer this : $i_var =
> > (int)$some_str_val;  Others are (string), (float)
> I've told you, both can be used, it's not a matter of standard as I see
> it.

ok

> > New ones :
> > 1)POSIX regex(ereg_* ) or PCRE regex(preg_*)
> I preffer ereg_*.

I will stick to preg_* much faster.

Andrey

Re: [Grouptime-developers] Coding Standard - is it ready?

[Lucas R. <lu...@uf...>]

> > New ones :
> > 1)POSIX regex(ereg_* ) or PCRE regex(preg_*)
> I preffer ereg_*.

I prefer preg_* ones! Perl is cool! :-) There are more docs about perl compatible than the other!

:-)

--lucasr

RE: [Grouptime-developers] Coding Standard - is it ready?

[Jan U. <ja...@ko...>]

> what about my proposals
> 1) to have C as prefix in the class names.
no C prefix, there's no point

> 2)to use PHPDoc compatible comments - for file and functions. 
> Constants will self explain them.
Nope, we use comments as they are described in our standard

3)I see that there is no 
> proposal for variable names : $some_var or $someVar. I think 
> the former is better because the second is the way the 
> methods are named. So by using the former it will be easier 
> to track errors for using an property instead of calling 
> method. ($s->updateThing vs
> $s->updateThing() ).
variable names are also used as $someVar, $someOtherVar

> 4)Strict typing :
>  If one var is used as int it will be int to the end of the 
> script. In conditions IMO it is better to use === and !== to 
> check and type. Otherwise problems can be faced. Consider 
> this : <?php $str_val = '0'; if ($str_val) echo "one"; else 
> echo "two"; ?> This will output "two" no matter that 
> strlen($str_val) is not 0. This is type juggling. So use === 
> to check. 5)Casting : I prefer this : $i_var = 
> (int)$some_str_val;  Others are (string), (float)
I've told you, both can be used, it's not a matter of standard as I see 
it.


> New ones :
> 1)POSIX regex(ereg_* ) or PCRE regex(preg_*)
I preffer ereg_*.

Jan 

Re: [Grouptime-developers] Coding Standard - is it ready?

[Andrey H. <and...@ma...>]

    Hi,
what about my proposals
1) to have C as prefix in the class names.
2)to use PHPDoc compatible comments - for file and functions. Constants will
self explain them.
3)I see that there is no proposal for variable names : $some_var or
$someVar. I think the former is better because the second is the way the
methods are named. So by using the former it will be easier to track errors
for using an property instead of calling method. ($s->updateThing vs
$s->updateThing() ).
4)Strict typing :
 If one var is used as int it will be int to the end of the
script. In conditions IMO it is better to use === and !== to check and type.
Otherwise problems can be faced. Consider this :
<?php
$str_val = '0';
if ($str_val) echo "one"; else echo "two";
?>
This will output "two" no matter that strlen($str_val) is not 0. This is
type juggling. So use === to check.
5)Casting :
I prefer this : $i_var = (int)$some_str_val;  Others are (string), (float)

New ones :
1)POSIX regex(ereg_* ) or PCRE regex(preg_*)



----- Original Message -----
From: "Jan Urva" <ja...@ko...>
To: <gro...@li...>
Sent: Monday, September 09, 2002 6:08 PM
Subject: RE: [Grouptime-developers] Coding Standard - is it ready?


> Ok, changed some standards, some bugfixes, some additions.
>
> Is this acceptable for all:
> http://www.realtime.ee/~sau/coding_standards.zip
>
> If something doesn't like, let us know, and I'll fix it.
>
> If now feedback havent received by the end of today 09.09.2002, 10pm GMT
> 0, then I'll take that all agreed and I'll declare this doc for final.
>
> May the source be with you
>          Jan Urva
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Grouptime-developers mailing list
> Gro...@li...
> https://lists.sourceforge.net/lists/listinfo/grouptime-developers