18 | | Response by [http://www.cmlenz.net/ Christopher Lenz]: |
19 | | |
20 | | > I'm not a fan of such prefixed names (!WinFoo, KFoo, GFoo, iFoo, etc). |
21 | | > IMHO those fall in the "cheesy" category ;-) |
22 | | > Exceptions are bindings or Python versions of some product, but |
23 | | > otherwise I think it's rather ugly. |
| 18 | In response to: |
| 19 | >Response by [http://www.cmlenz.net/ Christopher Lenz]: |
| 20 | > |
| 21 | >> I'm not a fan of such prefixed names (!WinFoo, KFoo, GFoo, iFoo, etc). |
| 22 | >> IMHO those fall in the "cheesy" category ;-) |
| 23 | >> Exceptions are bindings or Python versions of some product, but |
| 24 | >> otherwise I think it's rather ugly. |
| 25 | Yes, ''pySomething'' usually stands for the Python bindings for that ''Something''. |
| 26 | In the context of Markup, it was more meant to be reminiscent of the `py:` prefix we use everywhere in our templates. |
| 27 | So maybe... py:markup? Additionally, this goes well with the encapsulation in <...> illustrated in the logo. |