[johan_tre]

hello x3lectric,

I'm affraid you'll have to help me out a little, I'm just trying to understand.
Hope you're not pissed because I said it's hard to maintain?
It is only to help pointing difficulties and finding solutions for it.

@ johan_tre
Its not hard to maintain when the problems are solved annd it is all modular so each area says what it does...

what do you mean by that?
I hope you're not offended when I found it a hard-to-maintain script.
And I've done the effort of reading it, in order to solve the problem I had at the time.
Conclusion for me: It's far to long to be kept clear, all the dialog clutter doesn't do good to it, the mix between installation ways doing the same thing, the incorrect Alsa installation, the ever recurring ppa problems (you're not the only having these prob's, xbmscript has the same issue), it's all just confusing. All in one script.

Go back to the last problem: installation ends up in a ghost process.
now what? where is the problem? the wheel stops rolling. end users get no support.
You want (i guess) a solution, the users want it too.
I've also tried it, thing doesn't work.
And the problem remains.
Can you imagine what a non-developer sees opening that script?
His conclusion will be simple: it doesn't work. Period.
I believe that a split up of the script would make it easier to understand and to report problems on.
It would help less skilled people to add feedback in order to help developers better.
I'm not a scripting ninja, so I'm interested in anyone's feedback to understand this better.
For instance yours. I think you say that a splitup is not a good idea? (see below) I would like to understand why.
Maybe the merge of your, my and others knowledge can bring something better.
The only solution of bringing improvement is cooperating.

My idea is that it is not really easy to maintain, so I thought a split-up would be a good solution.
Like that, the parts of the script can kept stable, if they do not change.
Like that, the parts causing troubles could be adapted, and also easier to spot. And those are not the only advantages I think.

So in my search of solutions (here I got stuck unfortunately) I found OpenElec.tv that has a bit the problem of inflexibility due to hardware setups, BUT has the advantage of a all-in-one installation.
And that did rang a bell to me, since I've used XCI till I got stuck: XCI has the marvelous option to have an installation approach where you choose your drivers.
I find it really a good script. I honestly do.
You'll understand the irritation when installing Dharma and nvidia 256 (my previous setup) was also not installing properly anymore.
Then I'm out of options... I see people having the same problem, and there it ends if there comes no response of the forum.
So you start looking into the script. And looking into the script gives some info, but regarding the last problem, (the ghost process) there is not so much you can do but comparing the working and non-working version in order to see what has changed.
Guess what... not so much was changed. So what could be the problem then?? It's at THAT moment you decide to look for other options. Forced a little, because of the lack of knowledge and support.
I wanted a solution for my problem.

See what I mean?
Understand how I came to the ideas?
They are not meant to be offending. Only to help.

Nothing good comes of easy/lazy work.

Totally agree on that one!!

Openelec and the script cant be used together simply because openelec is not Debian based, I know I spoke to the dev many times.

Shit, how come?
Has OpenElec's distro no similar "dialog" package then?

yet your suggestion could probably make it simpler but I see now, it unlikely.

So split up is not a good idea, is that what you're saying?

Also the point of having a installer with menu parts all in one despite size is easier to maintain and easier for the end user to use.

The menu handler is not a good idea, is that what you're saying?
If it increases simplicity by splitting up in an flexible way, why not?
To me it seemed a good idea... (but maybe unfeasible?)

I wouldn't want to be hours running scripts when I can do it all in one hour.

Please explain? "hours running scripts". For which conditions you mean that?
A split up can't make that difference, can it?
When I speak about splitting up, I mean this in an dynamic way. So that the user can't see the difference between the old and the new script. The only difference would be simplicity when a problem occurs, and a cause of problem could easier be pointed.
One script can call another, no?
Having one script representing the main stream of dialogs etc, calling scripts doing the work is not such a bad idea, no?
Maybe I'm to progressive in my perception about the possibilities here?

Thx anyway man, rather you tell me that you not going to do it then to say yes and disapear like the rest of all the others, including the other co-founder.

You mean I'm chickening out or so?
I just want to put my effort the most effecient way
My attempt to find out the ghost process problem showed me how easily comes to a dead end. I wasn't the first reporting that problem.
And I've done the effort of cracking open the script without success.
For me, it's a way of contributing, by giving suggestions.
Maybe these ideas are stupid, not possible, or whatever.
But at least I offer them.
So I expect feedback. And maybe that feedback helps me finding a solution, and if so, you'll see a post of me for sure.
It's only in an effort to help mate.
Improvement can be made by working together.

The coming days I'll give it a try for a retest of the scripts latest version.
I'll post my findings if there is any change.
My installation test:
Karmic,
stable version xbmc +
nvidia drivers 256 (which worked in the past for me) +
external Alsa 1.0.23 installation (the xci version is not working correctly for some reason)

regards