Hi, the fact that you are using DI does not change your startup time. Your application will take approximately the same time to load if you does the injection by hand. Actually, I think you want to create your view only when you really need it instead of instantiating everything at startup. When using Gin, it is common to let the framework inject everything for you without considering what have to be instantiate and when. Keep in mind that Gin is just here to help you structuring your application. If you want to instantiate view not at startup time but while using application consider injecting Provider<T> instead of directly T. This way you have the ability to instantiate what you need when you need via those providers. It will be a little bit tricker, because you will have to manager when to instantiate your views but it's not a Gin matter
regards On Jul 9, 8:29 pm, mk <munna.kaka.ch...@gmail.com> wrote: > I used DI i.e. used @Inject to inject (Presenter, EventBus) in all of > Views. > > Now it seems that if I use DI than all views are generated at web app > intial start time in browser. Thus start time becomes slow. Am I > right? ( I think I heard something like this before also but just want > to validate). > > So if above is true than using @Inject is no good .. right? ( or where > can we use @Inject ). > > Can we use use @Inject to lazily create views instead of web app start > time? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
