Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 678711
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T01:10:47+00:00 2026-05-14T01:10:47+00:00

Ok, so is it better to create my own components (Either inherit them from

  • 0

Ok, so is it better to create my own components (Either inherit them from existing ones or creating them from scratch) or to use the ones that come by default?

I’m asking this under the umbrella of scalability, overhead and other factors that my contribute on each of the choices.

UPDATE: Sorry if I’m to vague. I don’t really know how to explain myself better. Isn’t it a good idea to inherit each default component? For example what if I’m to design a rather large application and for example i need to change the display format on a DateTimePicker. Wouldn’t it better to think ahead and inherit it and use the inherited component instead of the defaults?

But, wouldn’t it add a lot of overhead in small applications?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T01:10:48+00:00Added an answer on May 14, 2026 at 1:10 am

    This is a difficult question to answer, and may get closed as subjective. It depends on what you are doing, and whether the supportability of scaling it over an existing component is less than that of wrapping a whole new component (inherited or not) and all the entailing support work.

    For instance, suppose we have a textbox where we always want to have the text be green. We could just set the font property for the textbox and be done, that would be simple and straight forward, and not need a custom component. However, what if we wanted it to always be green, not be changeable and be enforced regardless of what might be put into the textbox? That would require more code and a certain amount of design work in the app, or we could create a custom component to do this work for us, and have it appear as a textbox to everyone who implements it. Simplifying the deployed code in essence (by hiding it inside the control) and making the overall design cleaner. If we only need this textbox in one place, it is probably overkill, however if this textbox is pivotal to our app it might be worth the time.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

When creating web parts for Sharepoint, is it better to create an actual web
When creating a 3D array in C#, which is a better way to create
I built a LAMP web application that let's users create their own profile page
Aside from the framework, is jQuery worth using rather than creating your own javascript?
I'm working with my ASP.NET development team to try and create better (i.e. cleaner)
Is it considered better practice and/or more efficient to create a 'reset' function for
Is it better(what is the best practice) to create methods with a long list
i am trying to create slider movement graphics. The code explain better this. using
Or better said: When to use array as a field data type in a
Everyone who's done any web application development in Scala knows that you can use

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.