Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #31121 > unrolled thread

flow charting or organizing tool

Back to article view | Back to comp.lang.javascript

Contents

  flow charting or organizing tool wmgill <webworker1950@gmail.com> - 2016-08-20 01:27 -0400
    Re: flow charting or organizing tool "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-08-20 09:35 +0200
      Re: flow charting or organizing tool wmgill <webworker1950@gmail.com> - 2016-08-22 14:24 -0400
        Re: flow charting or organizing tool "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-08-22 21:00 +0200

#31121 — flow charting or organizing tool

I am working on a small project that involves using JavaScript in the 
client, and php in the server. I need to organize what needs to be done 
and where it needs to be done to help me map things out before just 
jumping into the code. I have a couple flow charting programs, but they 
seem to be more of a distraction, than a help. I even tried my own mix 
of pseudo code & outlining, but that doesn't really help. Does anybody 
have any good suggestions for tools to help me organize and see what I 
need to do before I just code as I go?

It doesn't need to be fancy, but I should be able to add and remove 
blocks or elements without having to start all over every time.

[toc] | [next] | [standalone]

#31125

wmgill <webworker1950@gmail.com> wrote on 20 Aug 2016 in 
comp.lang.javascript:

> I am working on a small project that involves using JavaScript in the 
> client, and php in the server. I need to organize what needs to be done 
> and where it needs to be done to help me map things out before just 
> jumping into the code. I have a couple flow charting programs, but they 
> seem to be more of a distraction, than a help. I even tried my own mix 
> of pseudo code & outlining, but that doesn't really help. Does anybody 
> have any good suggestions for tools to help me organize and see what I 
> need to do before I just code as I go?

Think modular. Test modular.

Use your brain in that way. 
Sleep on it, older brains are more lucid after a good sleep.

Recognize if you have visual concepts of your programming, 
and only if so use paper and pencil.

> It doesn't need to be fancy, but I should be able to add and remove 
> blocks or elements without having to start all over every time.

Programme modular. 
Define the inputs and ouputs of your modules.
Build temporary container that test single modules.

And yes, indeed, getting grasp of what you really want your programme to do 
often comes up during this period, this feels like an autorelevation, and 
starting all over pays of.

However using older finished modules that fit the new concept does not 
always hurt.

==================

I, using serverside ASP, often [temporarily] put the modules in seperate 
files, using a skeleton final file with include statements. 

Testing a new module in-place only needs a renaming of the modules filename,
while saving older versions.

===================

Yes, I suppose you really asked for a programme to [help you] do your work,
may be they are out there, I only expect a decent code-colouring text/file-
editor with project-defining capabilities to help me. I use Editpad-pro.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#31140

On 8/20/2016 3:35 AM, Evertjan. wrote:
> wmgill <webworker1950@gmail.com> wrote on 20 Aug 2016 in
> comp.lang.javascript:
>
>> I am working on a small project that involves using JavaScript in the
>> client, and php in the server. I need to organize what needs to be done
>> and where it needs to be done to help me map things out before just
>> jumping into the code. I have a couple flow charting programs, but they
>> seem to be more of a distraction, than a help. I even tried my own mix
>> of pseudo code & outlining, but that doesn't really help. Does anybody
>> have any good suggestions for tools to help me organize and see what I
>> need to do before I just code as I go?
>
> Think modular. Test modular.
>
> Use your brain in that way.
> Sleep on it, older brains are more lucid after a good sleep.
>
> Recognize if you have visual concepts of your programming,
> and only if so use paper and pencil.
>
>> It doesn't need to be fancy, but I should be able to add and remove
>> blocks or elements without having to start all over every time.
>
> Programme modular.
> Define the inputs and ouputs of your modules.
> Build temporary container that test single modules.
>
> And yes, indeed, getting grasp of what you really want your programme to do
> often comes up during this period, this feels like an autorelevation, and
> starting all over pays of.
>
> However using older finished modules that fit the new concept does not
> always hurt.
>
> ==================
>
> I, using serverside ASP, often [temporarily] put the modules in seperate
> files, using a skeleton final file with include statements.
>
> Testing a new module in-place only needs a renaming of the modules filename,
> while saving older versions.
>
> ===================
>
> Yes, I suppose you really asked for a programme to [help you] do your work,
> may be they are out there, I only expect a decent code-colouring text/file-
> editor with project-defining capabilities to help me. I use Editpad-pro.
>

Forgive the unedited quote, but I couldn't determine where and what to 
reply to short of responding to everything as a whole.

Your suggestions are fine, and I already employ many of these techniques 
(modular code, code reuse, etc). However what I'm looking for is a tool 
to aid me in the macro view of things. As it is now I am using a large 
white board with post-it notes and diagrams to arrange all the pieces 
(modules, etc) and their flow/interaction on a macro view concept map. 
My older brain has learned that having a physical image in lieu of a 
mental map is much more reliable, and resilient.  Once this is done I 
have a better understanding of the inputs and outputs of each module. In 
the old days (long before Object Oriented Programing) I used to call 
this "black-boxing." I didn't need to know what went on inside each box, 
just what went in, and what came out. I could distribute the design of 
each box to a different team who did not need to know what any other 
team was doing. This technique isn't limited to coding, it also worked 
well with electronic and mechanical equipment design.

[toc] | [prev] | [next] | [standalone]

#31141

wmgill <webworker1950@gmail.com> wrote on 22 Aug 2016 in
comp.lang.javascript: 

> Your suggestions are fine, and I already employ many of these techniques
> (modular code, code reuse, etc). However what I'm looking for is a tool 
> to aid me in the macro view of things. 

Don't know about commercial packages.

====================

That's why I advised to have the executing page to be just a sum of the 
modules, at least during development. 

In ASP, also if the content only has html cum css and clientside js:

=== main.asp ============

<% ' this module inputs a.b.c %>
<% ' this module does ...  %>
<!-- #include virtual ="/detail/module1.asp"-->
<% ' this module returns f %>

<% ' this module has header html %>
<!-- #include virtual ="/detail/module2.asp"-->

<% ' this module has basic js datetime functions %>
<!-- #include virtual ="/detail/module3.asp"-->

===================

Then you are able to work on [=edit] each module seperately.

The saved result will both be available to main.asp,
and where necessary to a skeleton testing asp.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web