Hi,
Thnx for the responds, but I think people are misunderstanding me. I
have read a lot of the blogs (including davids) about rails and I
understand his hesitation to resist the development of highlevel
components. I have learned a lot by making a component based framework,
it just doesn't work, components are not flexible enough and you should
make everything into a component. However, there are cases where you
just need to make a component to hide the complexity of implementation
(thats the case with for example fckeditor). It would just be annoying
to implement this for each and every application I make
To start with the pointers to Engines, those things just scare me : )
they are MUCH to powerful to be used for something like components. And
plugins are in some cases to weak to be used for components. I think the
perfect combination would be combining components and plugins (Ticket
#3357). This would allow for some (not to many) highlevel components
that can be pluged into rails without to much work.
However, I am not suggesting making the plugin architecture so complex
that one plugin would be dependent on a other and other complex blabla.
That would really make components and plugins much more complex (and
hard to manage). But there is need for some more power for creating
generic components. I agree that creating components like 'the perfect
authentication system' are thing that can't never be done. Components
will always service a certain group of people and won't be the solution
for everyone.
Still I think, it would be ideal to have the same plugin type of
behaviour applied to components...
Abdur-Rahman Advany
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core
