Re: [Qscada-developers] R: Document templates

[Jovan K. <cho...@gm...>]

Hi,

I'm really late with this reply, but better ever then never :)

On 12/13/06, wireless <wir...@ta...> wrote:
> Some mechanism to archive the document before the given revision
> are made, should be simple to establish.

We don't have to care much about that. We will use some versoning sistem,
I prefer SVN, which will take care about that. That way we can maintain our
code easy without getting our hands dirty. Different file versions, backups,
restoring files it's all there.

I don't have much to say about the coding style. I'm completely flexible,
so whatever we make as a standard I will obey.
I like the rules that are shown in the document sent by Paolo
and I program with some simmilar rules.
I agree with Ian about the underscores, I don't like them too.
The coding style can be area specific but we should avoid to many
specific areas.



 > Documents:
I agree that document templates can be tricky, but if we all agree
to use this program with that font, or if we create so,e template
there shouldn't be any problems.

>Alternatively, I can just submit content in some agreeable form
>and somebody can put the content into a template form?

This can be one good solution, but the drawback is that someone
will have to do the DTP fo the others. As the projects grows, sooner
or later we'll have get a Documentation guy/team, so this would be
a logical solution.

At the end, I would share some book links with you
(they are pairs name- download location):

"Practical Process Control for Engineers and Technicians" by Wolfgang Altmann
http://rapidshare.com/files/2333374/Newnes.Practical.Process.Control.for.Engineers.and.Technicians.eBook-TLFeBOOK.rar

"Securing SCADA Systems" by Ronald L. Krutz
http://rapidshare.com/files/5092980/Wiley.Securing.SCADA.Systems.Nov.2005.eBook-DDU.pdf

"Practical Data Acquisition for Instrumentation and Control Systems"
http://rapidshare.com/files/7680226/e0750657960.pdf



Take care, Jovan