h a l f b a k e r yApply directly to forehead.
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
Loading bars that are so complex that they
themselves require loading bars.
i.e. first loading bar is the standard
rectangle, it displays the status of the
second loading bar, say a fractal render. The
fractal loading bar displays the status of the
third loading bar, say a 3D render of
tree
beard from lord of the rings and so on ad
infinitum.
Please log in.
If you're not logged in,
you can see what this page
looks like, but you will
not be able to add anything.
Annotation:
|
| |
This has been unintentionally baked by a number of very poorly designed websites. |
|
| |
//a 3D render of tree beard// |
|
| |
Do the statues of the second loading bar live on your desk? |
|
| |
//The patterns of fractal breakdown could be recorded for later use e.g. run once during testing and the customer sees one uniform speed progress bar.// |
|
| |
This idea is for several loading bars that do not progress at uniform speed. |
|
| |
I agree, I probably jumped the 3D render a little quick. I didnt want to type out the hundreds of loading bars that could potentially fall in between. |
|
| |
I might be misusing 'recursive'. I'm talking about several independant loading bars, each taking different form, with bar x's loading status being displayed by bar(x-1) which is of a different and less complex form. Prior to bar(x-1)'s display its status was displayed by an even less complex bar(x-2). |
|
| |
i.e. useless application is opened: |
|
| |
bar 1 (a simple rectangle status bar) is displayed and quickly loads while the computer processes bar 2. |
|
| |
Bar 2 loads (a complex picture) while the computer processes bar 3. |
|
| |
Bar 3 loads (a realtime chaotic branching) while the computer processes bar 4... |
|
| |
I tend to loose votes after i explain myself, so if you change your vote, please tell me what you thought this was so i can learn from your interpretation. thanks. |
|
| |
I guess an easier way to put it is the computer renders increasingly complex images to use as the image background for the following loading bar. |
|
| |
Is iterative the word i'm looking for instead of recursive? |
|
| |
//i.e. useless application is opened// |
|
| |
Then compounded by endless useless loading bars. I'd rather waste my time on the halfbakery. [-] |
|
| |
Doesn't the placement in ":unwanted
feature" negate it being something you
don't want as a reason to bone? |
|
| |
I'd bone the category if I could. You said it yourself: "Another bad Idea" |
|
| |
Every time I look at this title I imagine looking in the back of a Mercedes Sprinter and seeing two 2" sprung loadbars mounted widthways, with smaller 1" loadbars mounted lengthways between the big ones. Between the 1" loadbars are 0.5" loadbars mounted widthways... |
|
| |