Google Translate was helpful, but still not perfect :P Assuming the translation is reliable, I agree; naming is important and the docs should be consistent...
> You use package to define a set of features, like a library of components and > cositas otras bad that can be "assembled" in one or more modules? > > I tend to call everything that is not Tapestry-out-of-the-box as a library. > :-) tapx is one, is another kit chenille, so it goes. If there are one or > more modules in that library, I think it is irrelevant in this context. I > associate the extension more distributed configuration and possibilities for > interference / overwrite the mechanisms of Tapestry (web), not to libraries. > Libraries use the (many) options for extensibility of Tapestry. > > But like you said, a rose would still smell like a rose if her name change. > But also by giving a counter-counter-point, the names of design patterns are > as important as the description of themselves, so the name makes a > difference. :-P (I'm learning to write crazy things, contradictory and > unconnected to the Galaxy Hitchhiker series ...) 2011/1/13 Matheus Eduardo Machado Moreira <[email protected]>: > Você usa package para definir um conjunto de funcionalidades, tipo uma > biblioteca de componentes e otras cositas más que podem ser "montadas" em um > ou mais módulos? > > Minha tendência é chamar tudo o que não é Tapestry-out-of-the-box como > biblioteca. :-) tapx é uma, chenille kit é outra, por aí vai. Se existem um > ou mais módulos naquela biblioteca, acho que é irrelevante nesse contexto. > Extensão eu associo mais à configuração distribuída e as possibilidades de > interferência/sobrescrita dos mecanismos do Tapestry (web), não a > bibliotecas. Bibliotecas usam as (muitas) opções de extensibilidade do > Tapestry. > > Mas, é como você disse, uma rosa não deixaria de cheirar como uma rosa se > seu nome mudasse. Também mas, dando um contra-contra-ponto, os nomes dos > design patterns são tão importantes quanto a descrição dos próprios, então o > nome faz diferença. :-P (Tô aprendendo a escrever coisas malucas, > contraditórias e sem nexo com a série Mochileiro da Galáxia...) > > Atenciosamente, > > Matheus Eduardo Machado Moreira > [email protected] > > Good cooking takes time. If you are made to wait, it is to serve you better, > and to please you. > Menu do Restaurant Antoine, New Orleans > > > > 2011/1/13 Thiago H. de Paula Figueiredo <[email protected]> >> >> On Thu, 13 Jan 2011 17:06:22 -0200, Josh Canfield <[email protected]> >> wrote: >> >>> Hmm... yeah, it's hard distinction, but aren't some "extensions" built >>> into more than one module? For instance, hibernate-core and >>> hibernate... a Module is distinctive thing in tapestry (AppModule, >>> TapestryModule) >> >> I'd say that: >> * Tapestry doesn't have plugins (at least nothing with this name) >> * 'extension' could be a good name, more easily understandable than >> 'module', which is mostly Tapestry-IoC vocabulary in this context. >> * Calling everything a package wouldn't be bad either. >> >> Roses would still smell the same even if they were called madeinusas, but >> people wouldn't know what's being talked about. :P >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, >> and instructor >> Owner, Ars Machina Tecnologia da Informação Ltda. >> http://www.arsmachina.com.br > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
