As far as I know a first discriminator should be reusability:
- components should focus on characteristics related to his own features and scope, in this way they can be reused in several contexts (different pages, embedded in other components...)
- pages are usually more specific in their function and less reusable


Kunal Ashar wrote:

Are there are guidelines or user experiences out there that help users decide 
when to use pages and when to use components?

In my project, I'm trying to find the right reason(s) for developers to develop 
a page instead of a component or vice versa, instead of arbitrarily selecting 
one or the other based on individual preferences.

One way to look at the problem is from a component and page initialization 
perspective. Does the order in which each is initialized/loaded affect the 
decision to use either? Or some definite combination of both?

What could be the other influencing/deciding factors?

Thanks in advance,
Kunal



-- Ivano Pagano

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to