To Both  Harold Fuchs and NoOp;
         Thanks for the URL's.

Steve
===================================


NoOp wrote:
On 10/08/2008 03:34 PM, norseman wrote:
[I'll try to snip a little so as not to repeat Harold's full copy for a
one line response]
Yes I'm frustrated, but I'm not mad.  I like using OpenOffice. I just
wish those in it's driver seat could do something besides just code.
Without proper documentation a program is all but totally useless. You
know that as well as I.

Where is the real documentation? Is it just for the 'inside' crowd only?
Don't actually have any?  I can create it, but I have rules.

The web asks for help in all phases of OOo. Just exactly how does one code without knowing the purpose, name and syntax of each item in the library in use????

Steve
[EMAIL PROTECTED]

I recommend that you ask your python questions on the developers
list(s). See:
http://www.openoffice.org/mail_list.html
[EMAIL PROTECTED]

Also see:
http://projects.openoffice.org/index.html

As for the website questions/issues - same link as above:
Promotion
 Website
http://website.openoffice.org/
Although be advised that in the past when "users" ventured into trying
to assist/advise/complain about the website (most recent change and
accessability was a _big_ issue) that the folks there tend (IMO) to get
a little defensive, so word your issues carefully when expressing them
to the website folks :-)

...(snip)
To all who read this:

The web folks there and the web folks here are same in that respect. Negative anything and/or "How about if it was this..." are not appreciated by them (yours or mine), nope, not at all.

I think the educators can be blamed for the web folks attitudes. A brother of mine went back to finish his degree. He took a web design class. He showed me some of his assignments. My first question was "Where is your target concept outline? You know, your web page goals, its bounds, its purpose. In short, why is it to exist?" He gave me a dumbfound look. 'I dunno', he said. Turns out that most web classes, not just his, focus on line by line syntax with no thought to overall purpose.

Without a goal that specifies a dimension, purpose and a scope, building a proper foundation is pretty near impossible. Try putting the Empire State Building on a foundation built for a single story suburbia home. So when this house in suburbia needs to be moved downtown and made 20 floors tall things come apart. But they did spend lots of time on the syntax and the thought of scrapping all those hours and starting completely over generates the expected (and demonstrated) attitude.

For what it is worth, I think we all try to get away with 'fire for effect' and maybe correct up later, but only if we have to. :)

Something to try in building the foundation; Use the English Term Paper outline. When it reads correctly begin coding. It is super simple to (re)group things properly and to hand to someone and ask for what is left out. What should be removed? Does this belong here or there? ...

First question to ask when starting, "What am/are I/we going to achieve?" ('UH, I'm going to make a web page?' doesn't cut it.)

Second question and on:
What does it have to do?
What do I want it to do?
What do you want it to do?
What else can it do?
What else should be included?
In the wildest of dreams, what else could it do?

Then start the outline.  Group accordingly under main sections:
( Payroll, Collections, Personnel, Receivables, Payables, Vendors,...)
Under each main start the related subsets.
(for Personnel
( fica, futa, ss, federal, state, local?, adntl withholding1, rate, ...)
( for fica
( this fiscals' multiplier, this fiscals' max value (0=no-max))

Bookkeeping has been around since humans could count pebbles. Change the titles, the subtitles, whatever, but it's the same process. It assures you have considered all the pieces before you start. (Well, a big chunk of them anyway. :)

If you outgrow the original foundation, create an annex. Old Office here, cryogenics lab there, fusion reactor over yonder and so forth. Where you 'live' isn't important. A familiar and well built hearth is very warming to the repeat visitor.

Steve
[EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to