web-erp-developers — Discussion on development of webERP

Re: [Web-erp-developers] Help

[Danie B. <br...@na...>]

Hi Phil,

Just Synced the CVS yesterday  and as such has only noticed the new help
system but has not yet gone through it.

In regards to the Wiki stuff it all you are storing in the database is
text it can be implemented at a later stage, Wiki's just takes plain
text with some formating rules and make it HTML
for instance :

 * This would be a bullet list
    * This would be a hanging bullet
 * This is not a hanging bullet.

Tables are generally written in this way :
|Head Col1|Head Col2|Head Col3|
|X1Y1|X2Y1|X3Y1|
|X1-2Y2|X3Y2|

For now I think we can implement the wiki latter.

Kind Regards
Danie Brink

On Wed, 2004-08-11 at 03:10, Daintrees wrote:

>  
> Danie,
>  
> Are you clear on the new context sensitive help we have in the system
> now as of 2.9. Its all db driven. based on text/html help records
> allocated to a specific pageid. 
>  
> I'm a little scared you might be developing on scripts that are old -
> its a pig to figure out for me he said selfishly! Tell me you update
> your CVS daily.
>  
> I'm very green/ignorant on XML Wiki Latex. I think what we have with
> the help system I developed is a kind of Wiki?? where anyone can add
> there own 2c. with the text records held in the db.
>  
> Phil
> 
>         ----- Original Message ----- 
>         From: Danie Brink
>         To: Phil Daintree
>         Sent: Wednesday, August 11, 2004 12:03 PM
>         Subject: Re: [Web-erp-developers] Help
>         
>         Hi Steve
>         
>         No I'm suggesting we write it in some combination of XML/ Wiki
>         markup that can easily be converted to either HTML or Latex or
>         whatever just using a tool. For instance I use a simple php
>         wiki on my website which saves me from checking all the HTML
>         but there should be no difficulty in taking those wiki pages
>         (manual) and converting them to latex to create a professional
>         looking manual, also it would then be fairly easy to maintain
>         the manual in plain text. see phpWiki -
>         http://sourceforge.net/projects/phpwiki/ I am fairly sure that
>         it would require less work to convert the manual to plain text
>         and to maintain it in that form. To generate Latex or should
>         be fairly simple it would just require the wiki to generate
>         Latex rather than html and passing that through a Latex parser
>         using popen with say pdflatex would generate a pdf document
>         etc.
>         
>         An additional benefit is that the client/customer/user could
>         add his own noted to the help as he require. These could then
>         be passed back to us in the form of a contribution, and as it
>         is text even the client/customer/user will be able to work on
>         the betterment of the manuals without having to know html.
>         
>         Kind Regards
>         Danie Brink
>         
>         On Tue, 2004-08-10 at 22:11, skaill wrote: 
>         
>         >  
>         > I think I'm a bit confused.  I think it will be clearer when
>         > I get the example.  It sounds like you're suggesting the
>         > manual would be best written in Latex (whatever that is) and
>         > then Latex will be easily able to parse the manual into
>         > those sections.  Am I understanding?
>         >  
>         > Steve
>         > 
>         >         ----- Original Message ----- 
>         >         From: Danie Brink
>         >         To: Phil Daintree
>         >         Sent: Tuesday, August 10, 2004 1:01 PM
>         >         Subject: Re: [Web-erp-developers] Help
>         >         
>         >         Hi Steve ,
>         >         
>         >         I have gained some experience recently with Latex
>         >         writing my reporting framework, and I know already
>         >         that it is hard to do and keep maintained, however,
>         >         there is converters which will convert latex to
>         >         HTML, pdf and other formats as well. It will also
>         >         look a lot more professional.
>         >         
>         >         I have included an example of what Latex can do in
>         >         one of my reports generated through my report system
>         >         in PDF format. 
>         >         
>         >         I am prepared to convert the manual as I have to do
>         >         it any way. I could do it in the next few days if
>         >         you want me to. I will just have to put the tax
>         >         system on hold for those few days.
>         >         
>         >         Just some thoughts. 
>         >         
>         >         P.S.  Latex Parsers/Converters is also available for
>         >         both windows and UNIX.
>         >         
>         >         Kind Regards
>         >         Danie Brink
>         >         
>         >         On Tue, 2004-08-10 at 14:50, skaill wrote:  
>         >         
>         >         > I've been thinking about the best way to not only
>         >         > get the manual into the online help for
>         >         > various scripts but also how to best maintain it
>         >         > in the future as the system evolves.  I'm thinking
>         >         > the best way would be to convert the manual to
>         >         > html since the online help needs to be formatted
>         >         > in html also.
>         >         >  
>         >         > Unfortunately if I try saving the manual to html
>         >         > in Word the document saved ends up xml plus it has
>         >         > all kinds of css.  None of this is needed.  From
>         >         > what I see only fonts (size mainly), bold,
>         >         > underline, returns, lists and tables are needed
>         >         > for the entire manual so a help css is overkill.
>         >         >  
>         >         > Now, I can sit and copy/format those 70 pages of
>         >         > manual into html manually and don't mind doing it
>         >         > but at the end I need to know that we can stick to
>         >         > the html version and not the .doc version of the
>         >         > manual.  Keeping up two versions as well as the
>         >         > online will be too much and the html version, I
>         >         > believe, is the one that makes sense.
>         >         >  
>         >         > Once I have the entire manual manually converted
>         >         > to html then copy and pasting to the online help
>         >         > will be simple.  It will continue to be much
>         >         > simpler in the future as well when the manual ends
>         >         > up being modified.
>         >         >  
>         >         > Note that going with html means we can also
>         >         > readily supply another link called something like
>         >         > Online Manual that will display the entire manual.
>         >         >  
>         >         > Any comments/suggestions from anyone?  Phil,
>         >         > please let me know if this is a good way to
>         >         > proceed.
>         >         >  
>         >         > Steve   

Re: [Web-erp-developers] Help

[skaill <sk...@ro...>]

I understand except for the following...

Are you saying page the html file based on section for the online help?

I'm not sure that you can effectively combine a linear organization from =
online.  For instance, there could be certain parts of the manual that =
will be suited to 2 or more sections and some may be suited to none.  It =
is an idea but I think we need it expanded.

I think it may work better the other way.  In other words, have a manual =
and then specify which sections each part belongs in.

Steve
  ----- Original Message -----=20
  From: Daintrees=20
  To: web...@li...=20
  Sent: Tuesday, August 10, 2004 9:02 PM
  Subject: Re: [Web-erp-developers] Help


  Maybe we could look at this from another angle. What about this ....

  The existing manual converted to html - I will do this tonight.
  Steve cut an paste the html into appropriate help pages.

  Perhaps we classify paged as belonging to certain modules and perhaps =
an order for the help page in the manual, then all future manuals could =
be created by a query to return the help stored in the db - slam dunk =
into a text/html file one big manual all linked based on our data in the =
db about pages and where they belong. The help in the db is thus the one =
source of information about webERP.

  Any thoughts guys?

  Phil


    ----- Original Message -----=20
    From: Danie Brink=20
    To: Phil Daintree=20
    Sent: Wednesday, August 11, 2004 12:03 PM
    Subject: Re: [Web-erp-developers] Help


    Hi Steve

    No I'm suggesting we write it in some combination of XML/ Wiki =
markup that can easily be converted to either HTML or Latex or whatever =
just using a tool. For instance I use a simple php wiki on my website =
which saves me from checking all the HTML but there should be no =
difficulty in taking those wiki pages (manual) and converting them to =
latex to create a professional looking manual, also it would then be =
fairly easy to maintain the manual in plain text. see phpWiki - =
http://sourceforge.net/projects/phpwiki/ I am fairly sure that it would =
require less work to convert the manual to plain text and to maintain it =
in that form. To generate Latex or should be fairly simple it would just =
require the wiki to generate Latex rather than html and passing that =
through a Latex parser using popen with say pdflatex would generate a =
pdf document etc.

    An additional benefit is that the client/customer/user could add his =
own noted to the help as he require. These could then be passed back to =
us in the form of a contribution, and as it is text even the =
client/customer/user will be able to work on the betterment of the =
manuals without having to know html.

    Kind Regards
    Danie Brink

    On Tue, 2004-08-10 at 22:11, skaill wrote:=20
      =EF=BB=BF=20
      I think I'm a bit confused.  I think it will be clearer when I get =
the example.  It sounds like you're suggesting the manual would be best =
written in Latex (whatever that is) and then Latex will be easily able =
to parse the manual into those sections.  Am I understanding?
      =20
      Steve=20
        ----- Original Message -----=20
        From: Danie Brink
        To: Phil Daintree
        Sent: Tuesday, August 10, 2004 1:01 PM
        Subject: Re: [Web-erp-developers] Help

        Hi Steve ,

        I have gained some experience recently with Latex writing my =
reporting framework, and I know already that it is hard to do and keep =
maintained, however, there is converters which will convert latex to =
HTML, pdf and other formats as well. It will also look a lot more =
professional.

        I have included an example of what Latex can do in one of my =
reports generated through my report system in PDF format.=20

        I am prepared to convert the manual as I have to do it any way. =
I could do it in the next few days if you want me to. I will just have =
to put the tax system on hold for those few days.

        Just some thoughts.=20

        P.S.  Latex Parsers/Converters is also available for both =
windows and UNIX.

        Kind Regards
        Danie Brink

        On Tue, 2004-08-10 at 14:50, skaill wrote:=20
          I've been thinking about the best way to not only get the =
manual into the online help for various scripts but also how to best =
maintain it in the future as the system evolves.  I'm thinking the best =
way would be to convert the manual to html since the online help needs =
to be formatted in html also.
          =20
          Unfortunately if I try saving the manual to html in Word the =
document saved ends up xml plus it has all kinds of css.  None of this =
is needed.  From what I see only fonts (size mainly), bold, underline, =
returns, lists and tables are needed for the entire manual so a help css =
is overkill.
          =20
          Now, I can sit and copy/format those 70 pages of manual into =
html manually and don't mind doing it but at the end I need to know that =
we can stick to the html version and not the .doc version of the manual. =
 Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.
          =20
          Once I have the entire manual manually converted to html then =
copy and pasting to the online help will be simple.  It will continue to =
be much simpler in the future as well when the manual ends up being =
modified.
          =20
          Note that going with html means we can also readily supply =
another link called something like Online Manual that will display the =
entire manual.
          =20
          Any comments/suggestions from anyone?  Phil, please let me =
know if this is a good way to proceed.
          =20
          Steve   

Re: [Web-erp-developers] Help

[Daintrees <p.d...@pa...>]

Danie,

Are you clear on the new context sensitive help we have in the system =
now as of 2.9. Its all db driven. based on text/html help records =
allocated to a specific pageid.=20

I'm a little scared you might be developing on scripts that are old - =
its a pig to figure out for me he said selfishly! Tell me you update =
your CVS daily.

I'm very green/ignorant on XML Wiki Latex. I think what we have with the =
help system I developed is a kind of Wiki?? where anyone can add there =
own 2c. with the text records held in the db.

Phil
  ----- Original Message -----=20
  From: Danie Brink=20
  To: Phil Daintree=20
  Sent: Wednesday, August 11, 2004 12:03 PM
  Subject: Re: [Web-erp-developers] Help


  Hi Steve

  No I'm suggesting we write it in some combination of XML/ Wiki markup =
that can easily be converted to either HTML or Latex or whatever just =
using a tool. For instance I use a simple php wiki on my website which =
saves me from checking all the HTML but there should be no difficulty in =
taking those wiki pages (manual) and converting them to latex to create =
a professional looking manual, also it would then be fairly easy to =
maintain the manual in plain text. see phpWiki - =
http://sourceforge.net/projects/phpwiki/ I am fairly sure that it would =
require less work to convert the manual to plain text and to maintain it =
in that form. To generate Latex or should be fairly simple it would just =
require the wiki to generate Latex rather than html and passing that =
through a Latex parser using popen with say pdflatex would generate a =
pdf document etc.

  An additional benefit is that the client/customer/user could add his =
own noted to the help as he require. These could then be passed back to =
us in the form of a contribution, and as it is text even the =
client/customer/user will be able to work on the betterment of the =
manuals without having to know html.

  Kind Regards
  Danie Brink

  On Tue, 2004-08-10 at 22:11, skaill wrote:=20
    =EF=BB=BF=20
    I think I'm a bit confused.  I think it will be clearer when I get =
the example.  It sounds like you're suggesting the manual would be best =
written in Latex (whatever that is) and then Latex will be easily able =
to parse the manual into those sections.  Am I understanding?
    =20
    Steve=20
      ----- Original Message -----=20
      From: Danie Brink
      To: Phil Daintree
      Sent: Tuesday, August 10, 2004 1:01 PM
      Subject: Re: [Web-erp-developers] Help

      Hi Steve ,

      I have gained some experience recently with Latex writing my =
reporting framework, and I know already that it is hard to do and keep =
maintained, however, there is converters which will convert latex to =
HTML, pdf and other formats as well. It will also look a lot more =
professional.

      I have included an example of what Latex can do in one of my =
reports generated through my report system in PDF format.=20

      I am prepared to convert the manual as I have to do it any way. I =
could do it in the next few days if you want me to. I will just have to =
put the tax system on hold for those few days.

      Just some thoughts.=20

      P.S.  Latex Parsers/Converters is also available for both windows =
and UNIX.

      Kind Regards
      Danie Brink

      On Tue, 2004-08-10 at 14:50, skaill wrote:=20
        I've been thinking about the best way to not only get the manual =
into the online help for various scripts but also how to best maintain =
it in the future as the system evolves.  I'm thinking the best way would =
be to convert the manual to html since the online help needs to be =
formatted in html also.
        =20
        Unfortunately if I try saving the manual to html in Word the =
document saved ends up xml plus it has all kinds of css.  None of this =
is needed.  From what I see only fonts (size mainly), bold, underline, =
returns, lists and tables are needed for the entire manual so a help css =
is overkill.
        =20
        Now, I can sit and copy/format those 70 pages of manual into =
html manually and don't mind doing it but at the end I need to know that =
we can stick to the html version and not the .doc version of the manual. =
 Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.
        =20
        Once I have the entire manual manually converted to html then =
copy and pasting to the online help will be simple.  It will continue to =
be much simpler in the future as well when the manual ends up being =
modified.
        =20
        Note that going with html means we can also readily supply =
another link called something like Online Manual that will display the =
entire manual.
        =20
        Any comments/suggestions from anyone?  Phil, please let me know =
if this is a good way to proceed.
        =20
        Steve   

Re: [Web-erp-developers] Help

[Daintrees <p.d...@pa...>]

Maybe we could look at this from another angle. What about this ....

The existing manual converted to html - I will do this tonight.
Steve cut an paste the html into appropriate help pages.

Perhaps we classify paged as belonging to certain modules and perhaps an =
order for the help page in the manual, then all future manuals could be =
created by a query to return the help stored in the db - slam dunk into =
a text/html file one big manual all linked based on our data in the db =
about pages and where they belong. The help in the db is thus the one =
source of information about webERP.

Any thoughts guys?

Phil


  ----- Original Message -----=20
  From: Danie Brink=20
  To: Phil Daintree=20
  Sent: Wednesday, August 11, 2004 12:03 PM
  Subject: Re: [Web-erp-developers] Help


  Hi Steve

  No I'm suggesting we write it in some combination of XML/ Wiki markup =
that can easily be converted to either HTML or Latex or whatever just =
using a tool. For instance I use a simple php wiki on my website which =
saves me from checking all the HTML but there should be no difficulty in =
taking those wiki pages (manual) and converting them to latex to create =
a professional looking manual, also it would then be fairly easy to =
maintain the manual in plain text. see phpWiki - =
http://sourceforge.net/projects/phpwiki/ I am fairly sure that it would =
require less work to convert the manual to plain text and to maintain it =
in that form. To generate Latex or should be fairly simple it would just =
require the wiki to generate Latex rather than html and passing that =
through a Latex parser using popen with say pdflatex would generate a =
pdf document etc.

  An additional benefit is that the client/customer/user could add his =
own noted to the help as he require. These could then be passed back to =
us in the form of a contribution, and as it is text even the =
client/customer/user will be able to work on the betterment of the =
manuals without having to know html.

  Kind Regards
  Danie Brink

  On Tue, 2004-08-10 at 22:11, skaill wrote:=20
    =EF=BB=BF=20
    I think I'm a bit confused.  I think it will be clearer when I get =
the example.  It sounds like you're suggesting the manual would be best =
written in Latex (whatever that is) and then Latex will be easily able =
to parse the manual into those sections.  Am I understanding?
    =20
    Steve=20
      ----- Original Message -----=20
      From: Danie Brink
      To: Phil Daintree
      Sent: Tuesday, August 10, 2004 1:01 PM
      Subject: Re: [Web-erp-developers] Help

      Hi Steve ,

      I have gained some experience recently with Latex writing my =
reporting framework, and I know already that it is hard to do and keep =
maintained, however, there is converters which will convert latex to =
HTML, pdf and other formats as well. It will also look a lot more =
professional.

      I have included an example of what Latex can do in one of my =
reports generated through my report system in PDF format.=20

      I am prepared to convert the manual as I have to do it any way. I =
could do it in the next few days if you want me to. I will just have to =
put the tax system on hold for those few days.

      Just some thoughts.=20

      P.S.  Latex Parsers/Converters is also available for both windows =
and UNIX.

      Kind Regards
      Danie Brink

      On Tue, 2004-08-10 at 14:50, skaill wrote:=20
        I've been thinking about the best way to not only get the manual =
into the online help for various scripts but also how to best maintain =
it in the future as the system evolves.  I'm thinking the best way would =
be to convert the manual to html since the online help needs to be =
formatted in html also.
        =20
        Unfortunately if I try saving the manual to html in Word the =
document saved ends up xml plus it has all kinds of css.  None of this =
is needed.  From what I see only fonts (size mainly), bold, underline, =
returns, lists and tables are needed for the entire manual so a help css =
is overkill.
        =20
        Now, I can sit and copy/format those 70 pages of manual into =
html manually and don't mind doing it but at the end I need to know that =
we can stick to the html version and not the .doc version of the manual. =
 Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.
        =20
        Once I have the entire manual manually converted to html then =
copy and pasting to the online help will be simple.  It will continue to =
be much simpler in the future as well when the manual ends up being =
modified.
        =20
        Note that going with html means we can also readily supply =
another link called something like Online Manual that will display the =
entire manual.
        =20
        Any comments/suggestions from anyone?  Phil, please let me know =
if this is a good way to proceed.
        =20
        Steve   

Re: [Web-erp-developers] Help

[Danie B. <br...@na...>]

Hi Steve

No I'm suggesting we write it in some combination of XML/ Wiki markup
that can easily be converted to either HTML or Latex or whatever just
using a tool. For instance I use a simple php wiki on my website which
saves me from checking all the HTML but there should be no difficulty in
taking those wiki pages (manual) and converting them to latex to create
a professional looking manual, also it would then be fairly easy to
maintain the manual in plain text. see phpWiki -
http://sourceforge.net/projects/phpwiki/ I am fairly sure that it would
require less work to convert the manual to plain text and to maintain it
in that form. To generate Latex or should be fairly simple it would just
require the wiki to generate Latex rather than html and passing that
through a Latex parser using popen with say pdflatex would generate a
pdf document etc.

An additional benefit is that the client/customer/user could add his own
noted to the help as he require. These could then be passed back to us
in the form of a contribution, and as it is text even the
client/customer/user will be able to work on the betterment of the
manuals without having to know html.

Kind Regards
Danie Brink

On Tue, 2004-08-10 at 22:11, skaill wrote:

>  
> I think I'm a bit confused.  I think it will be clearer when I get the
> example.  It sounds like you're suggesting the manual would be best
> written in Latex (whatever that is) and then Latex will be easily able
> to parse the manual into those sections.  Am I understanding?
>  
> Steve
> 
>         ----- Original Message ----- 
>         From: Danie Brink
>         To: Phil Daintree
>         Sent: Tuesday, August 10, 2004 1:01 PM
>         Subject: Re: [Web-erp-developers] Help
>         
>         Hi Steve ,
>         
>         I have gained some experience recently with Latex writing my
>         reporting framework, and I know already that it is hard to do
>         and keep maintained, however, there is converters which will
>         convert latex to HTML, pdf and other formats as well. It will
>         also look a lot more professional.
>         
>         I have included an example of what Latex can do in one of my
>         reports generated through my report system in PDF format. 
>         
>         I am prepared to convert the manual as I have to do it any
>         way. I could do it in the next few days if you want me to. I
>         will just have to put the tax system on hold for those few
>         days.
>         
>         Just some thoughts. 
>         
>         P.S.  Latex Parsers/Converters is also available for both
>         windows and UNIX.
>         
>         Kind Regards
>         Danie Brink
>         
>         On Tue, 2004-08-10 at 14:50, skaill wrote: 
>         
>         > I've been thinking about the best way to not only get
>         > the manual into the online help for various scripts but
>         > also how to best maintain it in the future as the system
>         > evolves.  I'm thinking the best way would be to convert the
>         > manual to html since the online help needs to be formatted
>         > in html also.
>         >  
>         > Unfortunately if I try saving the manual to html in Word the
>         > document saved ends up xml plus it has all kinds of css. 
>         > None of this is needed.  From what I see only fonts (size
>         > mainly), bold, underline, returns, lists and tables are
>         > needed for the entire manual so a help css is overkill.
>         >  
>         > Now, I can sit and copy/format those 70 pages of manual into
>         > html manually and don't mind doing it but at the end I need
>         > to know that we can stick to the html version and not the
>         > .doc version of the manual.  Keeping up two versions as well
>         > as the online will be too much and the html version, I
>         > believe, is the one that makes sense.
>         >  
>         > Once I have the entire manual manually converted to html
>         > then copy and pasting to the online help will be simple.  It
>         > will continue to be much simpler in the future as well when
>         > the manual ends up being modified.
>         >  
>         > Note that going with html means we can also readily supply
>         > another link called something like Online Manual that will
>         > display the entire manual.
>         >  
>         > Any comments/suggestions from anyone?  Phil, please let me
>         > know if this is a good way to proceed.
>         >  
>         > Steve   

Re: [Web-erp-developers] Help

[skaill <sk...@ro...>]

Thanks for the suggestions and information.=20

For Latex, if I understand correctly a person would need to work with a =
tool that supported the Latex format.  Doing this could start to exclude =
people from contributing to help.  As well, I think I understand that =
Latex format can be converted to html but I'm not sure the conversion =
would be any cleaner than converting from word to html.  Even if it was, =
we would have to make the decision to use a process of modifying in =
Latex and then going through a larger process of conversion then =
splitting into sections of online help.

As far as xml, if you know it then maybe a solution involving xml makes =
sense.  A solution would make sense if and only if it worked in most of =
the browsers as well.  For everyone else, there would need to be an =
abstraction through a tool such as a word processor in order to work =
with the xml document successfully.  Splitting into sections of online =
help would be difficult for anyone not understanding xml unless an =
automatic process was created.

For these reasons I would suggest that everyone who will be working on =
webERP will have html knowledge.  A solution that will work fairly =
smoothly is having the manual in html and splitting it into the various =
sections of online help.  Possibly that html could contain "tags" such =
as=20
<!-- SelectOrderItems -->=20
that would help manually, and even possibly automatically with a small =
utility, to split the help into sections of online help.

Keeping the manual in html format makes it quickly modifiable by the =
most people, makes it readily displayable online with nothing external =
such as a converter or pdf, and considering the relatively simple amount =
of formatting needed, it makes the document easiest to split into =
sections for online help.

Either:

1) Someone needs to suggest and probably take upon themselves doing the =
conversion of the manual as well as working out the processes for =
splitting it easily into sections for online help.  Possibly I could be =
involved.

or=20

2) I will offer to change the manual into html then split it up into the =
sections of online help as well as "tagging" the various sections using =
the comment method explained above.

Keeping to the principles of webERP of not introducing new technologies =
and keeping it as simple as possible for all to contribute, based on =
what I know, the html solution is what I am suggesting.  Keep in mind =
that later possibly a more elaborate solution could be undertaken and =
the html solution would be a step toward that solution anyway.


Steve

  ----- Original Message -----=20
  From: Danie Brink=20
  To: Phil Daintree=20
  Sent: Tuesday, August 10, 2004 1:01 PM
  Subject: Re: [Web-erp-developers] Help


  Hi Steve ,

  I have gained some experience recently with Latex writing my reporting =
framework, and I know already that it is hard to do and keep maintained, =
however, there is converters which will convert latex to HTML, pdf and =
other formats as well. It will also look a lot more professional.

  I have included an example of what Latex can do in one of my reports =
generated through my report system in PDF format.=20

  I am prepared to convert the manual as I have to do it any way. I =
could do it in the next few days if you want me to. I will just have to =
put the tax system on hold for those few days.

  Just some thoughts.=20

  P.S.  Latex Parsers/Converters is also available for both windows and =
UNIX.

  Kind Regards
  Danie Brink

  On Tue, 2004-08-10 at 14:50, skaill wrote:=20
    I've been thinking about the best way to not only get the manual =
into the online help for various scripts but also how to best maintain =
it in the future as the system evolves.  I'm thinking the best way would =
be to convert the manual to html since the online help needs to be =
formatted in html also.
    =20
    Unfortunately if I try saving the manual to html in Word the =
document saved ends up xml plus it has all kinds of css.  None of this =
is needed.  From what I see only fonts (size mainly), bold, underline, =
returns, lists and tables are needed for the entire manual so a help css =
is overkill.
    =20
    Now, I can sit and copy/format those 70 pages of manual into html =
manually and don't mind doing it but at the end I need to know that we =
can stick to the html version and not the .doc version of the manual.  =
Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.
    =20
    Once I have the entire manual manually converted to html then copy =
and pasting to the online help will be simple.  It will continue to be =
much simpler in the future as well when the manual ends up being =
modified.
    =20
    Note that going with html means we can also readily supply another =
link called something like Online Manual that will display the entire =
manual.
    =20
    Any comments/suggestions from anyone?  Phil, please let me know if =
this is a good way to proceed.
    =20
    Steve   

Re: Fw: [Web-erp-developers] Serialization and BOM

[Peter <use...@gm...>]

Chris,

What is the status on your RMA system? Is there any way that I could
obtain a snapshot of your code or assist you in development?

Thanks!

~Peter

On Fri, 6 Aug 2004 15:00:53 -0400, skaill <sk...@ro...> wrote:
> A clarification.  I didn't mean to be saying that web-erp follows all of
> PEAR.  I was only referring to the coding standards section within PEAR.
> 
> Steve
> 
> 
> 
> ----- Original Message -----
> From: "skaill" <sk...@ro...>
> To: <web...@li...>
> Sent: Thursday, August 05, 2004 2:15 PM
> Subject: Re: [Web-erp-developers] Serialization and BOM
> 
> > I think Phil mentioned PEAR which can be found here
> > http://pear.php.net/manual/en/standards.php
> > It is a short and easy read.  Basically it's what they teach in school or
> > you've seen in lots of good programs.  Chances are you're doing already.
> >
> > Steve
> >
> > ----- Original Message -----
> > From: "Danie Brink" <br...@na...>
> > To: <web...@li...>
> > Sent: Wednesday, August 04, 2004 7:07 PM
> > Subject: Re: [Web-erp-developers] Serialization and BOM
> >
> >
> > > Hi Peter
> > >
> > > I don't know if any of the other guys are awake right now, so I will try
> > to
> > > answer some of your questions.
> > >
> > > Serialization has been build into the stock to some extend Phil and
> Jessie
> > > worked on this, so they will probably fill you in on serialization.
> > >
> > > BOMS already have multilevel support in that a manufactured item with
> its
> > own
> > > BOM may be used within another BOM. There is however no single interface
> > to
> > > edit a tree like structure.
> > >
> > > Reporting of the BOM Tree are also lacking although with a bit of work
> it
> > is
> > > possible to build such a report.
> > >
> > > Like all of us go ahead, look through the code and if you feel up to it
> go
> > ahead
> > > and try. If you would like to run it past the the list do so. Phil is
> > fearly
> > > strict on the source code structure ( not overly so, but he has a point)
> > on the
> > > way he would like the code. Have a look at the current code you will see
> > he
> > > likes to keep every file as self contained as possible.
> > > He or someone else will probably mention it again soon. :)
> > >
> > > Someone mentioned a while back where we could find the standard Phil
> would
> > like
> > > us to use, If someone could tell us again. Also mabe Phil could put it
> on
> > the
> > > Source Forge Site as well under some FAQ. Just a thought. *wink-wink*
> > >
> > > There is also some work under way on work orders and costing by me and
> my
> > guys,
> > > And we are also doing some work on the taxes and manuals. We will
> > contribute it
> > > back and Phil will decide what he want's to include. It's his baby and
> he
> > did a
> > > good job so far.
> > >
> > > Kind Regards
> > > Danie Brink
> > >
> > > Quoting Peter <use...@gm...>:
> > >
> > > > I've shown Web-ERP to my manager and he was very impressed. It far
> > > > surpasses any open source ERP software we have used.
> > > >
> > > > Among a couple of small features, some requirements he had:
> > > >
> > > > * The support of serialized stock
> > > > * BOM reporting
> > > > * Milti - level BOM
> > > >
> > > > Has development started on these features? If so, can I help? If
> > > > development has not started, a co-worker and I can start developing
> > > > these.
> > > >
> > > > I have programmed some in PHP and MySQL and I have done a lot of
> > > > programming in other languages including C++ so I understand the OOP
> > > > mentality.
> > > >
> > > > ~Peter
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.Net email is sponsored by OSTG. Have you noticed the changes
> on
> > > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > > > one more big change to announce. We are now OSTG- Open Source
> Technology
> > > > Group. Come see the changes on the new OSTG site. www.ostg.com
> > > > _______________________________________________
> > > > Web-erp-developers mailing list
> > > > Web...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
> > > >
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > > one more big change to announce. We are now OSTG- Open Source Technology
> > > Group. Come see the changes on the new OSTG site. www.ostg.com
> > > _______________________________________________
> > > Web-erp-developers mailing list
> > > Web...@li...
> > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
> >
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>

Re: [Web-erp-developers] Help

[skaill <sk...@ro...>]

I think I'm a bit confused.  I think it will be clearer when I get the =
example.  It sounds like you're suggesting the manual would be best =
written in Latex (whatever that is) and then Latex will be easily able =
to parse the manual into those sections.  Am I understanding?

Steve
  ----- Original Message -----=20
  From: Danie Brink=20
  To: Phil Daintree=20
  Sent: Tuesday, August 10, 2004 1:01 PM
  Subject: Re: [Web-erp-developers] Help


  Hi Steve ,

  I have gained some experience recently with Latex writing my reporting =
framework, and I know already that it is hard to do and keep maintained, =
however, there is converters which will convert latex to HTML, pdf and =
other formats as well. It will also look a lot more professional.

  I have included an example of what Latex can do in one of my reports =
generated through my report system in PDF format.=20

  I am prepared to convert the manual as I have to do it any way. I =
could do it in the next few days if you want me to. I will just have to =
put the tax system on hold for those few days.

  Just some thoughts.=20

  P.S.  Latex Parsers/Converters is also available for both windows and =
UNIX.

  Kind Regards
  Danie Brink

  On Tue, 2004-08-10 at 14:50, skaill wrote:=20
    I've been thinking about the best way to not only get the manual =
into the online help for various scripts but also how to best maintain =
it in the future as the system evolves.  I'm thinking the best way would =
be to convert the manual to html since the online help needs to be =
formatted in html also.
    =20
    Unfortunately if I try saving the manual to html in Word the =
document saved ends up xml plus it has all kinds of css.  None of this =
is needed.  From what I see only fonts (size mainly), bold, underline, =
returns, lists and tables are needed for the entire manual so a help css =
is overkill.
    =20
    Now, I can sit and copy/format those 70 pages of manual into html =
manually and don't mind doing it but at the end I need to know that we =
can stick to the html version and not the .doc version of the manual.  =
Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.
    =20
    Once I have the entire manual manually converted to html then copy =
and pasting to the online help will be simple.  It will continue to be =
much simpler in the future as well when the manual ends up being =
modified.
    =20
    Note that going with html means we can also readily supply another =
link called something like Online Manual that will display the entire =
manual.
    =20
    Any comments/suggestions from anyone?  Phil, please let me know if =
this is a good way to proceed.
    =20
    Steve   

Re: [Web-erp-developers] Help

[skaill <sk...@ro...>]

Thanks Phil.  I guess my last email can be disregarded ;)

Steve
  ----- Original Message -----=20
  From: Daintrees=20
  To: web...@li...=20
  Sent: Tuesday, August 10, 2004 3:33 PM
  Subject: Re: [Web-erp-developers] Help


  I use open office - will produce a html version and pop it on =
sourceforge.

  Phil
    ----- Original Message -----=20
    From: skaill=20
    To: web...@li...=20
    Sent: Wednesday, August 11, 2004 12:50 AM
    Subject: [Web-erp-developers] Help


    I've been thinking about the best way to not only get the manual =
into the online help for various scripts but also how to best maintain =
it in the future as the system evolves.  I'm thinking the best way would =
be to convert the manual to html since the online help needs to be =
formatted in html also.

    Unfortunately if I try saving the manual to html in Word the =
document saved ends up xml plus it has all kinds of css.  None of this =
is needed.  From what I see only fonts (size mainly), bold, underline, =
returns, lists and tables are needed for the entire manual so a help css =
is overkill.

    Now, I can sit and copy/format those 70 pages of manual into html =
manually and don't mind doing it but at the end I need to know that we =
can stick to the html version and not the .doc version of the manual.  =
Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.

    Once I have the entire manual manually converted to html then copy =
and pasting to the online help will be simple.  It will continue to be =
much simpler in the future as well when the manual ends up being =
modified.

    Note that going with html means we can also readily supply another =
link called something like Online Manual that will display the entire =
manual.

    Any comments/suggestions from anyone?  Phil, please let me know if =
this is a good way to proceed.

    Steve  

Re: [Web-erp-developers] Help

[skaill <sk...@ro...>]

If someone has Open Office installed I'd appreciate if they could try it.  I
know Word does too much with it to be bothered.  Better to do manually at
that point!

Steve

----- Original Message ----- 
From: "Olwen Williams" <ol...@ha...>
To: <web...@li...>
Sent: Tuesday, August 10, 2004 12:53 PM
Subject: Re: [Web-erp-developers] Help


> Have you considered trying to save it with Open Office.  It may do a
> better job of saving a clean copy (I haven't looked at this myself)
>
>
> skaill wrote:
> > I've been thinking about the best way to not only get the manual into
> > the online help for various scripts but also how to best maintain it in
> > the future as the system evolves.  I'm thinking the best way would be to
> > convert the manual to html since the online help needs to be formatted
> > in html also.
> >
> > Unfortunately if I try saving the manual to html in Word the document
> > saved ends up xml plus it has all kinds of css.  None of this is
> > needed.  From what I see only fonts (size mainly), bold, underline,
> > returns, lists and tables are needed for the entire manual so a help css
> > is overkill.
> >
> > Now, I can sit and copy/format those 70 pages of manual into html
> > manually and don't mind doing it but at the end I need to know that we
> > can stick to the html version and not the .doc version of the manual.
> > Keeping up two versions as well as the online will be too much and the
> > html version, I believe, is the one that makes sense.
> >
> > Once I have the entire manual manually converted to html then copy and
> > pasting to the online help will be simple.  It will continue to be much
> > simpler in the future as well when the manual ends up being modified.
> >
> > Note that going with html means we can also readily supply another link
> > called something like Online Manual that will display the entire manual.
> >
> > Any comments/suggestions from anyone?  Phil, please let me know if this
> > is a good way to proceed.
> >
> > Steve
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [Web-erp-developers] Help

[Daintrees <p.d...@pa...>]

I use open office - will produce a html version and pop it on =
sourceforge.

Phil
  ----- Original Message -----=20
  From: skaill=20
  To: web...@li...=20
  Sent: Wednesday, August 11, 2004 12:50 AM
  Subject: [Web-erp-developers] Help


  I've been thinking about the best way to not only get the manual into =
the online help for various scripts but also how to best maintain it in =
the future as the system evolves.  I'm thinking the best way would be to =
convert the manual to html since the online help needs to be formatted =
in html also.

  Unfortunately if I try saving the manual to html in Word the document =
saved ends up xml plus it has all kinds of css.  None of this is needed. =
 From what I see only fonts (size mainly), bold, underline, returns, =
lists and tables are needed for the entire manual so a help css is =
overkill.

  Now, I can sit and copy/format those 70 pages of manual into html =
manually and don't mind doing it but at the end I need to know that we =
can stick to the html version and not the .doc version of the manual.  =
Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.

  Once I have the entire manual manually converted to html then copy and =
pasting to the online help will be simple.  It will continue to be much =
simpler in the future as well when the manual ends up being modified.

  Note that going with html means we can also readily supply another =
link called something like Online Manual that will display the entire =
manual.

  Any comments/suggestions from anyone?  Phil, please let me know if =
this is a good way to proceed.

  Steve  

Re: [Web-erp-developers] Help

[Danie B. <br...@na...>]

Hi Steve, 

I have posted a mail with some examples in reply to what is being
discussed here however it is being held back by the "moderator" 40k
limit, It is two small PDFs.

Kind Regards
Danie Brink.


On Tue, 2004-08-10 at 14:50, skaill wrote:

> I've been thinking about the best way to not only get the manual into
> the online help for various scripts but also how to best maintain it
> in the future as the system evolves.  I'm thinking the best way would
> be to convert the manual to html since the online help needs to be
> formatted in html also.
>  
> Unfortunately if I try saving the manual to html in Word the document
> saved ends up xml plus it has all kinds of css.  None of this is
> needed.  From what I see only fonts (size mainly), bold, underline,
> returns, lists and tables are needed for the entire manual so a help
> css is overkill.
>  
> Now, I can sit and copy/format those 70 pages of manual into html
> manually and don't mind doing it but at the end I need to know that we
> can stick to the html version and not the .doc version of the manual. 
> Keeping up two versions as well as the online will be too much and the
> html version, I believe, is the one that makes sense.
>  
> Once I have the entire manual manually converted to html then copy and
> pasting to the online help will be simple.  It will continue to be
> much simpler in the future as well when the manual ends up being
> modified.
>  
> Note that going with html means we can also readily supply another
> link called something like Online Manual that will display the entire
> manual.
>  
> Any comments/suggestions from anyone?  Phil, please let me know if
> this is a good way to proceed.
>  
> Steve  

Re: [Web-erp-developers] Help

[Olwen W. <ol...@ha...>]

Have you considered trying to save it with Open Office.  It may do a 
better job of saving a clean copy (I haven't looked at this myself)


skaill wrote:
> I've been thinking about the best way to not only get the manual into 
> the online help for various scripts but also how to best maintain it in 
> the future as the system evolves.  I'm thinking the best way would be to 
> convert the manual to html since the online help needs to be formatted 
> in html also.
>  
> Unfortunately if I try saving the manual to html in Word the document 
> saved ends up xml plus it has all kinds of css.  None of this is 
> needed.  From what I see only fonts (size mainly), bold, underline, 
> returns, lists and tables are needed for the entire manual so a help css 
> is overkill.
>  
> Now, I can sit and copy/format those 70 pages of manual into html 
> manually and don't mind doing it but at the end I need to know that we 
> can stick to the html version and not the .doc version of the manual.  
> Keeping up two versions as well as the online will be too much and the 
> html version, I believe, is the one that makes sense.
>  
> Once I have the entire manual manually converted to html then copy and 
> pasting to the online help will be simple.  It will continue to be much 
> simpler in the future as well when the manual ends up being modified.
>  
> Note that going with html means we can also readily supply another link 
> called something like Online Manual that will display the entire manual.
>  
> Any comments/suggestions from anyone?  Phil, please let me know if this 
> is a good way to proceed.
>  
> Steve  

[Web-erp-developers] Help

[skaill <sk...@ro...>]

I've been thinking about the best way to not only get the manual into =
the online help for various scripts but also how to best maintain it in =
the future as the system evolves.  I'm thinking the best way would be to =
convert the manual to html since the online help needs to be formatted =
in html also.

Unfortunately if I try saving the manual to html in Word the document =
saved ends up xml plus it has all kinds of css.  None of this is needed. =
 From what I see only fonts (size mainly), bold, underline, returns, =
lists and tables are needed for the entire manual so a help css is =
overkill.

Now, I can sit and copy/format those 70 pages of manual into html =
manually and don't mind doing it but at the end I need to know that we =
can stick to the html version and not the .doc version of the manual.  =
Keeping up two versions as well as the online will be too much and the =
html version, I believe, is the one that makes sense.

Once I have the entire manual manually converted to html then copy and =
pasting to the online help will be simple.  It will continue to be much =
simpler in the future as well when the manual ends up being modified.

Note that going with html means we can also readily supply another link =
called something like Online Manual that will display the entire manual.

Any comments/suggestions from anyone?  Phil, please let me know if this =
is a good way to proceed.

Steve  

Re: [Web-erp-developers] Updates to CVS

[Daintrees <p.d...@pa...>]

That would be fantastic!

You could produce an sql dump of the help table - using mysqldump from a dos
prompt or phpmyadmin. Email me the resultant file and we're away.

Phil


----- Original Message ----- 
From: "skaill" <sk...@ro...>
To: <web...@li...>
Sent: Tuesday, August 10, 2004 8:46 PM
Subject: Re: [Web-erp-developers] Updates to CVS


> If I was to go through the manual Phil, clip sections out and put into the
> various help areas what would be the best way to get it to you.  This
> assumes you think it's a good idea to do that.  I think emailing each as
it
> does automatically with config flag on would be tedious for you.  Would
some
> way such as somehow transferring the help table after I have filled it be
a
> better idea?
>
> Steve
>
> ----- Original Message ----- 
> From: "Phil Daintree" <p.d...@pa...>
> To: <web...@li...>
> Sent: Tuesday, August 10, 2004 3:28 AM
> Subject: Re: [Web-erp-developers] Updates to CVS
>
>
> > Whoops - thanks Steve, fixed now.
> > Also changed the help for the main menu page re the short cut keys - but
> > not updated CVS with the new help data - only the scripts.
> > There is no help data other than the main menu page help!!
> >
> >
> > Phil
> >
> >
> > On Tue, 2004-08-10 at 08:52, skaill wrote:
> > > There's an incorrect line in index.php that is
> > >
> > >      <td class="menu_group_headers">  !-- AR option Headings -->
> > >
> > > I think it probably happened when my code got combined with the base.
> > >
> > > Looks to me like maybe you didn't like the N/A in a section that has
no
> > > options.  If this is the case you may want to put a &nbsp; in to
display
> the
> > > white box unless you meant for it to not exist at all.
> > >
> > > Might want to put into the initial help screen about hot keys being
Alt
> +
> > > character.  For IE press return afterward.  Up to you...
> > >
> > > Steve
> > >
> >
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> > _______________________________________________
> > Web-erp-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>

Re: [Web-erp-developers] Updates to CVS

[skaill <sk...@ro...>]

Phil, I just noticed I missed resizing ap, ar and company pngs.  I have sent
to your sourceforge email.

Steve

----- Original Message ----- 
From: "Phil Daintree" <p.d...@pa...>
To: <web...@li...>
Sent: Tuesday, August 10, 2004 3:28 AM
Subject: Re: [Web-erp-developers] Updates to CVS


> Whoops - thanks Steve, fixed now.
> Also changed the help for the main menu page re the short cut keys - but
> not updated CVS with the new help data - only the scripts.
> There is no help data other than the main menu page help!!
>
>
> Phil
>
>
> On Tue, 2004-08-10 at 08:52, skaill wrote:
> > There's an incorrect line in index.php that is
> >
> >      <td class="menu_group_headers">  !-- AR option Headings -->
> >
> > I think it probably happened when my code got combined with the base.
> >
> > Looks to me like maybe you didn't like the N/A in a section that has no
> > options.  If this is the case you may want to put a &nbsp; in to display
the
> > white box unless you meant for it to not exist at all.
> >
> > Might want to put into the initial help screen about hot keys being Alt
+
> > character.  For IE press return afterward.  Up to you...
> >
> > Steve
> >
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [Web-erp-developers] Updates to CVS

[skaill <sk...@ro...>]

If I was to go through the manual Phil, clip sections out and put into the
various help areas what would be the best way to get it to you.  This
assumes you think it's a good idea to do that.  I think emailing each as it
does automatically with config flag on would be tedious for you.  Would some
way such as somehow transferring the help table after I have filled it be a
better idea?

Steve

----- Original Message ----- 
From: "Phil Daintree" <p.d...@pa...>
To: <web...@li...>
Sent: Tuesday, August 10, 2004 3:28 AM
Subject: Re: [Web-erp-developers] Updates to CVS


> Whoops - thanks Steve, fixed now.
> Also changed the help for the main menu page re the short cut keys - but
> not updated CVS with the new help data - only the scripts.
> There is no help data other than the main menu page help!!
>
>
> Phil
>
>
> On Tue, 2004-08-10 at 08:52, skaill wrote:
> > There's an incorrect line in index.php that is
> >
> >      <td class="menu_group_headers">  !-- AR option Headings -->
> >
> > I think it probably happened when my code got combined with the base.
> >
> > Looks to me like maybe you didn't like the N/A in a section that has no
> > options.  If this is the case you may want to put a &nbsp; in to display
the
> > white box unless you meant for it to not exist at all.
> >
> > Might want to put into the initial help screen about hot keys being Alt
+
> > character.  For IE press return afterward.  Up to you...
> >
> > Steve
> >
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [Web-erp-developers] Updates to CVS

[Phil D. <p.d...@pa...>]

Whoops - thanks Steve, fixed now.
Also changed the help for the main menu page re the short cut keys - but
not updated CVS with the new help data - only the scripts.
There is no help data other than the main menu page help!!


Phil


On Tue, 2004-08-10 at 08:52, skaill wrote:
> There's an incorrect line in index.php that is
> 
>      <td class="menu_group_headers">  !-- AR option Headings -->
> 
> I think it probably happened when my code got combined with the base.
> 
> Looks to me like maybe you didn't like the N/A in a section that has no
> options.  If this is the case you may want to put a &nbsp; in to display the
> white box unless you meant for it to not exist at all.
> 
> Might want to put into the initial help screen about hot keys being Alt +
> character.  For IE press return afterward.  Up to you...
> 
> Steve
> 

Re: [Web-erp-developers] Updates to CVS

[skaill <sk...@ro...>]

There's an incorrect line in index.php that is

     <td class="menu_group_headers">  !-- AR option Headings -->

I think it probably happened when my code got combined with the base.

Looks to me like maybe you didn't like the N/A in a section that has no
options.  If this is the case you may want to put a &nbsp; in to display the
white box unless you meant for it to not exist at all.

Might want to put into the initial help screen about hot keys being Alt +
character.  For IE press return afterward.  Up to you...

Steve

----- Original Message ----- 
From: "Daintrees" <p.d...@pa...>
To: <web...@li...>
Sent: Monday, August 09, 2004 4:06 PM
Subject: Re: [Web-erp-developers] Updates to CVS


> I included 99% of your stuff Steve. Update your CVS and have a look. I
left
> the logout on the quick menu. I did also lose the Main tab and retained
the
> existing order of the module links:
>
> Sales Orders always come first or there is no business.
> Accounts receivable is next because it is customer related and customers
are
> kings and queens.
> G/L and Setup are far right because these are lesser used only by the bean
> counters/sys admins
> AP and Purchasing are required to get stuff for customers so they're next.
>
> there is a little logic to the madness regarding the order of the links.
>
> the user is straight into the system - into Sales Orders in case we need
to
> service a customer quickly. The welcome message is gone I felt that this
> could get tiresome for regular users who just want to get on with it.
>
> I made a few breif comments in the change.log on your behalf. I think I
> called the changes "Extreme makeover MkII"
>
> Phil
>
> ----- Original Message ----- 
> From: "skaill" <sk...@ro...>
> To: <web...@li...>
> Sent: Tuesday, August 10, 2004 2:45 AM
> Subject: Re: [Web-erp-developers] Updates to CVS
>
>
> > I should explain what I did.  There are some physical changes to the
> > interface of which many are small such as the hot keys.  The css's have
> been
> > cleaned up and modified appropriately for those physical changes. .Also,
> > professional has been changed to "enhance" it's style.  When I think
about
> > it now though, I could have introduced a new style and left
professional.
> > That might be something to consider.  Here is a list of specific
changes:
> >
> > 1) Color use changes such as the left side of top header being colored
> > instead of white with the curve separating.
> >
> > 2) Hot keys for the quick menu functions such as Select Customer.  Use
ALT
> +
> > character for the hot keys.  In IE you must press enter after doing the
> hot
> > key.  Unfortunately, the hot keys are not supported in some browsers
even
> > though they are part of the html 4 specification.  All browsers but one
> that
> > we tested were able to do the hot keys.  Hopefully hot keys can be
> extended
> > to other options in the future.  Fast hot key access is something that
> many
> > of the commercial accounting softwares have and has no known negative
side
> > other than not working on the odd browser.
> >
> > 3) The most noticeable change is that the sections are across the page
> > instead of downward.  Reasons for this have mostly to do with user
> > friendliness including the consistency of the sections being in the same
> > place for all modules.  Also, the area downward that is taken up is only
> the
> > number of options in the longest section within that module instead of
> > adding the length of all the module's sections so there is now more room
> for
> > more options without the pages getting long.
> >
> > 4) The graphics have been shrunk down to make them more professional
> > looking...IMO anyway.
> >
> > 5) Modules that a user does mot have access to will appear in grey as a
> > clear indication of not being accessible.  Hopefully this approach can
be
> > extended to the options within the sections.  Just didn't do that part
at
> > this stage.
> >
> > 6) Logout has been moved down to the "main" menu as opposed to the quick
> > menu.  In my mind I see the quick menu as a toolbar for fast access
> really.
> > Hopefully the Main option on the "main" menu has been taken out.  I
meant
> to
> > and if not, it should be.
> >
> > 7) Now, when the user enters the system they are shown a welcome screen
as
> > opposed to being thrown into the first module they have access.  In this
> way
> > there can be an identification of the program as well as a short
> > description/introduction.  For instance, it would probably be a good
idea
> to
> > point out the help button up top and how it will give context sensitive
> > help.
> >
> > This assumes Phil kept all of my changes though, so possibly it has
ended
> up
> > a bit different which should and will happen.  Phil knows more about the
> > system and all that use it.
> >
> > All comments good and bad are welcome.  We are all trying to make webERP
> > better.  With interfaces though many will have the first reaction of not
> > liking anything new.  Please try it out for long enough before making
any
> > decisions.
> >
> > Is there anywhere else I should post these changes, Phil?
> >
> > Steve
> >
> > ----- Original Message ----- 
> > From: "Phil Daintree" <p.d...@pa...>
> > To: <web...@li...>
> > Sent: Monday, August 09, 2004 6:02 AM
> > Subject: [Web-erp-developers] Updates to CVS
> >
> >
> > > I uploaded Steve's modifications to the main menu (index.php and
> > > includes/header.inc) I think it looks better but an accountants
> > > impression of what looks good may not be worth much. Steve likes it
too!
> > >
> > > Phil
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by OSTG. Have you noticed the changes
on
> > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > > one more big change to announce. We are now OSTG- Open Source
Technology
> > > Group. Come see the changes on the new OSTG site. www.ostg.com
> > > _______________________________________________
> > > Web-erp-developers mailing list
> > > Web...@li...
> > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > one more big change to announce. We are now OSTG- Open Source Technology
> > Group. Come see the changes on the new OSTG site. www.ostg.com
> > _______________________________________________
> > Web-erp-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
> >
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [Web-erp-developers] Updates to CVS

[skaill <sk...@ro...>]

Great.  I can see your rationality for that order, even though the logic
wasn't immediately obvious to me ;)

Steve

----- Original Message ----- 
From: "Daintrees" <p.d...@pa...>
To: <web...@li...>
Sent: Monday, August 09, 2004 4:06 PM
Subject: Re: [Web-erp-developers] Updates to CVS


> I included 99% of your stuff Steve. Update your CVS and have a look. I
left
> the logout on the quick menu. I did also lose the Main tab and retained
the
> existing order of the module links:
>
> Sales Orders always come first or there is no business.
> Accounts receivable is next because it is customer related and customers
are
> kings and queens.
> G/L and Setup are far right because these are lesser used only by the bean
> counters/sys admins
> AP and Purchasing are required to get stuff for customers so they're next.
>
> there is a little logic to the madness regarding the order of the links.
>
> the user is straight into the system - into Sales Orders in case we need
to
> service a customer quickly. The welcome message is gone I felt that this
> could get tiresome for regular users who just want to get on with it.
>
> I made a few breif comments in the change.log on your behalf. I think I
> called the changes "Extreme makeover MkII"
>
> Phil
>
> ----- Original Message ----- 
> From: "skaill" <sk...@ro...>
> To: <web...@li...>
> Sent: Tuesday, August 10, 2004 2:45 AM
> Subject: Re: [Web-erp-developers] Updates to CVS
>
>
> > I should explain what I did.  There are some physical changes to the
> > interface of which many are small such as the hot keys.  The css's have
> been
> > cleaned up and modified appropriately for those physical changes. .Also,
> > professional has been changed to "enhance" it's style.  When I think
about
> > it now though, I could have introduced a new style and left
professional.
> > That might be something to consider.  Here is a list of specific
changes:
> >
> > 1) Color use changes such as the left side of top header being colored
> > instead of white with the curve separating.
> >
> > 2) Hot keys for the quick menu functions such as Select Customer.  Use
ALT
> +
> > character for the hot keys.  In IE you must press enter after doing the
> hot
> > key.  Unfortunately, the hot keys are not supported in some browsers
even
> > though they are part of the html 4 specification.  All browsers but one
> that
> > we tested were able to do the hot keys.  Hopefully hot keys can be
> extended
> > to other options in the future.  Fast hot key access is something that
> many
> > of the commercial accounting softwares have and has no known negative
side
> > other than not working on the odd browser.
> >
> > 3) The most noticeable change is that the sections are across the page
> > instead of downward.  Reasons for this have mostly to do with user
> > friendliness including the consistency of the sections being in the same
> > place for all modules.  Also, the area downward that is taken up is only
> the
> > number of options in the longest section within that module instead of
> > adding the length of all the module's sections so there is now more room
> for
> > more options without the pages getting long.
> >
> > 4) The graphics have been shrunk down to make them more professional
> > looking...IMO anyway.
> >
> > 5) Modules that a user does mot have access to will appear in grey as a
> > clear indication of not being accessible.  Hopefully this approach can
be
> > extended to the options within the sections.  Just didn't do that part
at
> > this stage.
> >
> > 6) Logout has been moved down to the "main" menu as opposed to the quick
> > menu.  In my mind I see the quick menu as a toolbar for fast access
> really.
> > Hopefully the Main option on the "main" menu has been taken out.  I
meant
> to
> > and if not, it should be.
> >
> > 7) Now, when the user enters the system they are shown a welcome screen
as
> > opposed to being thrown into the first module they have access.  In this
> way
> > there can be an identification of the program as well as a short
> > description/introduction.  For instance, it would probably be a good
idea
> to
> > point out the help button up top and how it will give context sensitive
> > help.
> >
> > This assumes Phil kept all of my changes though, so possibly it has
ended
> up
> > a bit different which should and will happen.  Phil knows more about the
> > system and all that use it.
> >
> > All comments good and bad are welcome.  We are all trying to make webERP
> > better.  With interfaces though many will have the first reaction of not
> > liking anything new.  Please try it out for long enough before making
any
> > decisions.
> >
> > Is there anywhere else I should post these changes, Phil?
> >
> > Steve
> >
> > ----- Original Message ----- 
> > From: "Phil Daintree" <p.d...@pa...>
> > To: <web...@li...>
> > Sent: Monday, August 09, 2004 6:02 AM
> > Subject: [Web-erp-developers] Updates to CVS
> >
> >
> > > I uploaded Steve's modifications to the main menu (index.php and
> > > includes/header.inc) I think it looks better but an accountants
> > > impression of what looks good may not be worth much. Steve likes it
too!
> > >
> > > Phil
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by OSTG. Have you noticed the changes
on
> > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > > one more big change to announce. We are now OSTG- Open Source
Technology
> > > Group. Come see the changes on the new OSTG site. www.ostg.com
> > > _______________________________________________
> > > Web-erp-developers mailing list
> > > Web...@li...
> > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > one more big change to announce. We are now OSTG- Open Source Technology
> > Group. Come see the changes on the new OSTG site. www.ostg.com
> > _______________________________________________
> > Web-erp-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
> >
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [Web-erp-developers] PDFCustomerList.php

[Daintrees <p.d...@pa...>]

Thanks Olwen/Chris.

Phil
----- Original Message ----- 
From: "Olwen Williams" <ol...@ha...>
To: <web...@li...>
Sent: Tuesday, August 10, 2004 12:25 AM
Subject: Re: [Web-erp-developers] PDFCustomerList.php


> The ` at the start of line 316
> ` } /*end if $PrintThisCustomer == true */
>
> Then it timed out for me, and when I resticted the size of the Select
> didn't seem to have a papersize set,
>
>
> Phil Daintree wrote:
> > Team,
> >
> > I am stuck on a script PDFCustomerList.php it goes with
> > includes/PDFCustomerListPageHeader.inc to produce a report of customer
> > address, branch delivery addresses etc by Sales Territory and
> > Salespeson.
> >
> > I have puzzled for too long on some obscure syntax error and wondered if
> > anyone else can figure it out - it going to be something simple and I'll
> > be embarassed but hey!
> >
> > Thanks
> >
> > Phil
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>

Re: [Web-erp-developers] Updates to CVS

[Daintrees <p.d...@pa...>]

I included 99% of your stuff Steve. Update your CVS and have a look. I left
the logout on the quick menu. I did also lose the Main tab and retained the
existing order of the module links:

Sales Orders always come first or there is no business.
Accounts receivable is next because it is customer related and customers are
kings and queens.
G/L and Setup are far right because these are lesser used only by the bean
counters/sys admins
AP and Purchasing are required to get stuff for customers so they're next.

there is a little logic to the madness regarding the order of the links.

the user is straight into the system - into Sales Orders in case we need to
service a customer quickly. The welcome message is gone I felt that this
could get tiresome for regular users who just want to get on with it.

I made a few breif comments in the change.log on your behalf. I think I
called the changes "Extreme makeover MkII"

Phil

----- Original Message ----- 
From: "skaill" <sk...@ro...>
To: <web...@li...>
Sent: Tuesday, August 10, 2004 2:45 AM
Subject: Re: [Web-erp-developers] Updates to CVS


> I should explain what I did.  There are some physical changes to the
> interface of which many are small such as the hot keys.  The css's have
been
> cleaned up and modified appropriately for those physical changes. .Also,
> professional has been changed to "enhance" it's style.  When I think about
> it now though, I could have introduced a new style and left professional.
> That might be something to consider.  Here is a list of specific changes:
>
> 1) Color use changes such as the left side of top header being colored
> instead of white with the curve separating.
>
> 2) Hot keys for the quick menu functions such as Select Customer.  Use ALT
+
> character for the hot keys.  In IE you must press enter after doing the
hot
> key.  Unfortunately, the hot keys are not supported in some browsers even
> though they are part of the html 4 specification.  All browsers but one
that
> we tested were able to do the hot keys.  Hopefully hot keys can be
extended
> to other options in the future.  Fast hot key access is something that
many
> of the commercial accounting softwares have and has no known negative side
> other than not working on the odd browser.
>
> 3) The most noticeable change is that the sections are across the page
> instead of downward.  Reasons for this have mostly to do with user
> friendliness including the consistency of the sections being in the same
> place for all modules.  Also, the area downward that is taken up is only
the
> number of options in the longest section within that module instead of
> adding the length of all the module's sections so there is now more room
for
> more options without the pages getting long.
>
> 4) The graphics have been shrunk down to make them more professional
> looking...IMO anyway.
>
> 5) Modules that a user does mot have access to will appear in grey as a
> clear indication of not being accessible.  Hopefully this approach can be
> extended to the options within the sections.  Just didn't do that part at
> this stage.
>
> 6) Logout has been moved down to the "main" menu as opposed to the quick
> menu.  In my mind I see the quick menu as a toolbar for fast access
really.
> Hopefully the Main option on the "main" menu has been taken out.  I meant
to
> and if not, it should be.
>
> 7) Now, when the user enters the system they are shown a welcome screen as
> opposed to being thrown into the first module they have access.  In this
way
> there can be an identification of the program as well as a short
> description/introduction.  For instance, it would probably be a good idea
to
> point out the help button up top and how it will give context sensitive
> help.
>
> This assumes Phil kept all of my changes though, so possibly it has ended
up
> a bit different which should and will happen.  Phil knows more about the
> system and all that use it.
>
> All comments good and bad are welcome.  We are all trying to make webERP
> better.  With interfaces though many will have the first reaction of not
> liking anything new.  Please try it out for long enough before making any
> decisions.
>
> Is there anywhere else I should post these changes, Phil?
>
> Steve
>
> ----- Original Message ----- 
> From: "Phil Daintree" <p.d...@pa...>
> To: <web...@li...>
> Sent: Monday, August 09, 2004 6:02 AM
> Subject: [Web-erp-developers] Updates to CVS
>
>
> > I uploaded Steve's modifications to the main menu (index.php and
> > includes/header.inc) I think it looks better but an accountants
> > impression of what looks good may not be worth much. Steve likes it too!
> >
> > Phil
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > one more big change to announce. We are now OSTG- Open Source Technology
> > Group. Come see the changes on the new OSTG site. www.ostg.com
> > _______________________________________________
> > Web-erp-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>

Re: [Web-erp-developers] Updates to CVS

[skaill <sk...@ro...>]

I should explain what I did.  There are some physical changes to the
interface of which many are small such as the hot keys.  The css's have been
cleaned up and modified appropriately for those physical changes. .Also,
professional has been changed to "enhance" it's style.  When I think about
it now though, I could have introduced a new style and left professional.
That might be something to consider.  Here is a list of specific changes:

1) Color use changes such as the left side of top header being colored
instead of white with the curve separating.

2) Hot keys for the quick menu functions such as Select Customer.  Use ALT +
character for the hot keys.  In IE you must press enter after doing the hot
key.  Unfortunately, the hot keys are not supported in some browsers even
though they are part of the html 4 specification.  All browsers but one that
we tested were able to do the hot keys.  Hopefully hot keys can be extended
to other options in the future.  Fast hot key access is something that many
of the commercial accounting softwares have and has no known negative side
other than not working on the odd browser.

3) The most noticeable change is that the sections are across the page
instead of downward.  Reasons for this have mostly to do with user
friendliness including the consistency of the sections being in the same
place for all modules.  Also, the area downward that is taken up is only the
number of options in the longest section within that module instead of
adding the length of all the module's sections so there is now more room for
more options without the pages getting long.

4) The graphics have been shrunk down to make them more professional
looking...IMO anyway.

5) Modules that a user does mot have access to will appear in grey as a
clear indication of not being accessible.  Hopefully this approach can be
extended to the options within the sections.  Just didn't do that part at
this stage.

6) Logout has been moved down to the "main" menu as opposed to the quick
menu.  In my mind I see the quick menu as a toolbar for fast access really.
Hopefully the Main option on the "main" menu has been taken out.  I meant to
and if not, it should be.

7) Now, when the user enters the system they are shown a welcome screen as
opposed to being thrown into the first module they have access.  In this way
there can be an identification of the program as well as a short
description/introduction.  For instance, it would probably be a good idea to
point out the help button up top and how it will give context sensitive
help.

This assumes Phil kept all of my changes though, so possibly it has ended up
a bit different which should and will happen.  Phil knows more about the
system and all that use it.

All comments good and bad are welcome.  We are all trying to make webERP
better.  With interfaces though many will have the first reaction of not
liking anything new.  Please try it out for long enough before making any
decisions.

Is there anywhere else I should post these changes, Phil?

Steve

----- Original Message ----- 
From: "Phil Daintree" <p.d...@pa...>
To: <web...@li...>
Sent: Monday, August 09, 2004 6:02 AM
Subject: [Web-erp-developers] Updates to CVS


> I uploaded Steve's modifications to the main menu (index.php and
> includes/header.inc) I think it looks better but an accountants
> impression of what looks good may not be worth much. Steve likes it too!
>
> Phil
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers

RE: [Web-erp-developers] PDFCustomerList.php

[Chris B. <cb...@en...>]

I took out the ' on 316 and it worked great for me.

Chris


-----Original Message-----
From: web...@li...
[mailto:web...@li...] On Behalf Of
Olwen Williams
Sent: Monday, August 09, 2004 7:25 AM
To: web...@li...
Subject: Re: [Web-erp-developers] PDFCustomerList.php

The ` at the start of line 316
`		} /*end if $PrintThisCustomer == true */

Then it timed out for me, and when I resticted the size of the Select 
didn't seem to have a papersize set,


Phil Daintree wrote:
> Team,
> 
> I am stuck on a script PDFCustomerList.php it goes with
> includes/PDFCustomerListPageHeader.inc to produce a report of customer
> address, branch delivery addresses etc by Sales Territory and
> Salespeson.
> 
> I have puzzled for too long on some obscure syntax error and wondered
if
> anyone else can figure it out - it going to be something simple and
I'll
> be embarassed but hey!
> 
> Thanks
> 
> Phil
> 


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Web-erp-developers mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [Web-erp-developers] PDFCustomerList.php

[Olwen W. <ol...@ha...>]

The ` at the start of line 316
`		} /*end if $PrintThisCustomer == true */

Then it timed out for me, and when I resticted the size of the Select 
didn't seem to have a papersize set,


Phil Daintree wrote:
> Team,
> 
> I am stuck on a script PDFCustomerList.php it goes with
> includes/PDFCustomerListPageHeader.inc to produce a report of customer
> address, branch delivery addresses etc by Sales Territory and
> Salespeson.
> 
> I have puzzled for too long on some obscure syntax error and wondered if
> anyone else can figure it out - it going to be something simple and I'll
> be embarassed but hey!
> 
> Thanks
> 
> Phil
>