[V4RB] Valentina 2.0 installation

[Brendan Murphy]

Ruslan, you are making the some the same mistakes here that RS has
made in the past. They choose an implementation without regard to
how it impacts the customers since it serves their perspective.

WE NEED this component architecture to be an option! Having files
spread out all over the place is an invitation to a support
nightmare. End user's screw with their systems is a plain fact of
life. The more split up an application is, the more possible
points of failure you have. If a customer sees the component
folder one day and says, "What's this?" and decides to do some
creative deleting or updating, suddenly my application doesn't
work and I get a call. This cost me money!!!

If you don't do something to solve this problem, I will be a very
pissed off customer and I am sure there are a few others out there
who will feel the same way. I can't express what a negative
feeling in me this component architecture creates since you are
making unilateral design decision for my product. Bad idea. Very
bad idea!

I offer to you an idea for you to implement your component idea
and satisfy those who need an all in one plugin. Create a helper
application that will take the contents of the components folder
etc. and package them into one plugin. So when I download the V4RB
SDK, I will customize my components folder and then run the helper
application which will produce a V4RB plugin that I will use in
RB. This way I control what my end user sees and you get to have
your component architecture. Problem solved.