I'm not sure if we are talking at cross purposes here, I seem to be missing something???
Usually you are the first to complain about big bloated apps - consider 2 dotnet2 based Thinapp packages - both having all dotnet2 related files and dependencies embedded = thats a big waste ...
I think we are talking about the various options that are currently available, not about necessarily making a clone of Thinapp, I think what we are talking about is basically conceptual i.e Thinapp, sandboxie SVS even snap shotting the registry/&files before & after etc are being discussed, the virtues the pro's & Cons evaluation so to speak.
Indeed, big bloated apps too many are not desirable, but others have a different perspective or may just want an ad hoc gizmo here and there, I suppose the point is furnishing choice. Some say that Thinapp portables do not mix favorably with PE environments but that is here-say unless someone would like to correct me?
In some respects it is difficult to advocate Thinapp Portables because my suspicion is that most will fall under the umbrella of warez, who can afford the price tag of progeys like Thinapp & yet produce supposed Freeware portable programs but if we produced something similar and it was freeware there would be no need to breach copyright & a freeware option would have the knock on effect of forcing the commercial variants in a downward direction! As it is there is no competition & I include cartel arrangements also between commercial companies, however I could be wrong as I very often am?
Question, are we (sometime) in the future going to write a portable software maker to serve the needs of Winbuilder i.e Job specific?
or is the portable program maker going to be for mainstream portables?
Does it need to serve both maybe, or do you create two different variants?
We have discussed a few of the current ways/methods that others commercial & otherwise which will have their own inherent Pro's & Cons
Are we going to exclude the idea that dotnet is taboo or design the development with all inclusive attributes in mind thus increasing choice! Don't Bloat but if you must its there - Philosophy?
I don't think (& correct me if I am wrong?) but "Thinapp" does not really care whether the progey is dotnet based or not, but the "Thinapp" way could be excluded by virtue of certain incompatibilities?
I suppose what it boils down to is what do you want it to do, what are your expectations & how do you realize those expectations within the resources that will be available, these are questions for a development team or individual. Under the umbrella of What have we got, what do we need & how do we achieve it, is within the criteria of planning &/or procurement! & the most important answer to come out of questions like this, "Is it feasible?"
I think we have to be realistic it is not going to be a push over unless as MedEvil states, "we are into toy manufacture" all the necessary disciplines (whatever they are need to be Jelled together) so that the eventual finished product will hopefully be a viable alternative to Thinapp Sandboxie SVS etc etc Dependant on which route you/we all eventually decide to take.
However it does not hurt to talk & discuss & do research IF that is the consensus & most people want to get on board & take the bull by the horns & "Go 4 IT"
Any other Business?
Regards & Respect,