Menu
▾
▴
web-erp-developers
|
From: skaill <sk...@ro...> - 2004-08-10 12:49:46
|
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 |
|
From: Olwen W. <ol...@ha...> - 2004-08-10 16:53:28
|
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 |
|
From: skaill <sk...@ro...> - 2004-08-10 20:04:40
|
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 |
|
From: Danie B. <br...@na...> - 2004-08-10 17:05:11
|
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 |
|
From: Daintrees <p.d...@pa...> - 2004-08-10 19:32:02
|
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 |
|
From: skaill <sk...@ro...> - 2004-08-10 20:11:21
|
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 |
|
From: Daintrees <p.d...@pa...> - 2004-08-11 01:09:13
|
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 |
|
From: Danie B. <br...@na...> - 2004-08-11 08:15:07
|
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
|
|
From: Phil D. <p.d...@pa...> - 2004-08-11 08:40:29
|
Phew! P > Just Synced the CVS yesterday |
|
From: Danie B. <br...@na...> - 2004-08-11 12:36:30
|
Hi Phil Please keep in mind we have been working on stuff external to what is happening now and we only required to update when major changes that affect the database is completed. I.E. we have Php and applications that are currently developed to add on not expand. We want to prove it first. However it hooks into the database. Also it took a while for me to get my affairs in order and get my new guys sorted so they understand what it is I want to do. Our primary focus at this stage is to find customers that want webERP. And then customize. We have a potential customer pool of about R300,000 / $50,000 but we are in a lot of discussions in regards to customization at this point, only one customer has signed a contract and we need to finalize discussions on that side. If we are successfully we will be able to fund webERP permanently in the future. Kind Regards Danie Brink On Wed, 2004-08-11 at 10:42, Phil Daintree wrote: > Phew! > > P > > > Just Synced the CVS yesterday > > > > ------------------------------------------------------- > 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 > |
|
From: Daintrees <p.d...@pa...> - 2004-08-11 20:04:01
|
This sounds great Danie. Certainly good to have you back in the loop! I think sales and marketing are much harder (and frustrating) than = development. Phil ----- Original Message -----=20 From: Danie Brink=20 To: Phil Daintree=20 Sent: Thursday, August 12, 2004 12:36 AM Subject: Re: [Web-erp-developers] Help Hi Phil Please keep in mind we have been working on stuff external to what is = happening now and we only required to update when major changes that = affect the database is completed. I.E. we have Php and applications that = are currently developed to add on not expand. We want to prove it first. = However it hooks into the database. Also it took a while for me to get my affairs in order and get my new = guys sorted so they understand what it is I want to do. Our primary = focus at this stage is to find customers that want webERP. And then = customize. We have a potential customer pool of about R300,000 / $50,000 = but we are in a lot of discussions in regards to customization at this = point, only one customer has signed a contract and we need to finalize = discussions on that side. If we are successfully we will be able to fund = webERP permanently in the future. Kind Regards Danie Brink On Wed, 2004-08-11 at 10:42, Phil Daintree wrote:=20 Phew! P > Just Synced the CVS yesterday=20 ------------------------------------------------------- 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X