Re: [Bashburn-info] All the sleeps are now removed.

[Steven W. O. <st...@sy...>]

On Sunday, Sep 28th 2008 at 02:50 -0000, quoth Nick Warne:

=>On Sat, 27 Sep 2008 23:21:02 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> wait_for_enter now waits for any keypress.
=>> message prints a message and calls wait_for_enter
=>> 
=>> It's getting cleaner.
=>> 
=>
=>This doesn't work (yet).
=>
=>It appears misc/commonfunctions.sh doesn't get sourced until AFTER the
=>function 'message' is called, when starting BB.
=>
=>Secondly, even if I source that file first, then option 8) 'check
=>paths' doesn't work right.  Nothing appears, but if you scroll up your
=>terminal you will see the output above the bashburn menu.
=>
=>Lastly, the new $VAR bb_hit_any_key_to_continue doesn't seem to get
=>assigned, so the 'wait_for_enter' prompts are empty like this

Ok, let's try again. :-(

I think I fixed it (let me know), but there's a problem brewing here that 
I think needs to be addressed sooner than later. That problem is src code 
structure. This whole thing feels to me like it's getting fragile. As I'm 
writing this I see a total of 10334 lines of src code. And all of that src 
code is broken up into seperate modules that have a sort of mishmashed 
logic to it all. I suspect that there was some sort of rhyme or reason to 
it all earlier in the game, but at this point it's starting to feel 
unwieldy. I need to throw out a couple of examples.

We have a directory called menu. (Almost) None of the files in that 
directory are in any way related to each other other than the fact that 
they call bbmenu in some way. Even before I wrote bbmenu it didn't matter; 
they still were not fundamentally related. There were a collection of 
modules that all produced different menus, but they still were not 
related.

Let's look at configuration. We have menus/configure.sh, 
func/configfunc.sh, misc/commands.idx, and the granddaddy of all garbage 
dumps, misc/commonfunctions.sh

Let's look at filename extensions. We have lang files sitting in lang 
directories. We have idx files and I don't even know what those mean.

Before I got into this, the big difference was that bb was cranking huge 
numbers of processes. But that characteristic is a runtime aspect. What 
I'm talking about here is src code respository shape.

And as a side note, one of the things that we're doing right is to always 
execute from an installed release. We no longer execute anything from a 
workspace. But, what we're not asking ourselves is whether the installed 
tree structure is something that is supposed to look like the repository 
structure.

End of long ramble. Please, thots anyone?

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net