Great comments. The suggestion was to faciliate Web2PY branding and to automagically link anything YadaYada2Py with Web2PY Of course there are no rules and that is how it should be....
Thanks for commenting. G On Jul 14, 9:41 pm, Yarko Tymciurak <[email protected]> wrote: > On Tue, Jul 14, 2009 at 7:08 PM, JohnMc <[email protected]> wrote: > > > It is kind of traditional in the Python community to name an > > application <something>py. I don't see anything wrong with the > > suggestion. But then I don't see anything wrong naming an application > > right.... it's just foobar2py is more suggestive (to me) of a python app > (and there's nothing wrong with that) than of a web2py app... > > which is why for registration system, I opted for web2<app_name> > > I suppose an idiom like web-<appname>2py would suggest the same for a > project name, but then within web2py there's no need for those kinds of > names. > > > -- > > > * Kittyhawk -- aviation application > > * Pompeii - volcanologist program > > * BroadSt - Finance program > > * Florence - banking application > > > etc. Making historical references to what the program does. > > > JohnMc > > > On Jul 14, 6:46 am, gluegl <[email protected]> wrote: > > > I have been thinking on what would enhance the mindshare of Web2Py and > > > help create "deep burned-in branding" > > > My thinking is to when any create HELPERs, APPLIANCES, ADD-ONs > > > Instead of crypted names such as T2, T3, KPAX ... opt in for something > > > that would automagically associated with Web2Py such as > > > > Jque2Py > > > Doj2Py > > > PyJam2Py > > > iPhon2Py --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
