Ok. Suppose any of these methods foo(), bar() or goo() use some class variable, global variable or some variable defined in another class then how does it affect code splitting here?
On 2/23/11, Philippe Beaudoin <philippe.beaud...@gmail.com> wrote: > You are correct: the code you pasted has only one split point and (provided > they are not called from anywhere else), foo(), bar() and goo() sit behind > that split point -- it means they will only be loaded when onClick is > called. [That's what the sentence you highlighted in red means.] > > If you call, say, bar() from elsewhere then bar() will be in the leftover > fragment and will be loaded at app start. > > Cheers, > > Philippe > > -- > 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-toolkit@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. > > -- 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-toolkit@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.