Changes between Version 8 and Version 9 of NameSuggestions

Timestamp:

Aug 26, 2006, 2:30:03 PM (18 years ago)

Author:

cboos

Comment:

discuss pymarkup and improve the logos

NameSuggestions

@@ -23 +23 @@
 > hits so far...).
 
-In response to Christian Boos:
-> Response by [http://www.cmlenz.net/ Christopher Lenz]:
->> I'm not a fan of such prefixed names (!WinFoo, KFoo, GFoo, iFoo, etc).   
->> IMHO those fall in the "cheesy" category ;-) 
->> Exceptions are bindings or Python versions of some product, but   
->> otherwise I think it's rather ugly. 
-> Yes, ''pySomething'' usually stands for the Python bindings for that ''Something''.
-> In the context of Markup, it was more meant to be reminiscent of the `py:` prefix we use everywhere in our templates.
-> So maybe... py:markup? Additionally, this goes well with the encapsulation in <...> illustrated in the logo.
-
-See the comment I added at the top of the page about constraints on the project name. I actually like `py:markup`, but don't see how that would work as a name.
+Discussion:
+>>> I'm not a fan of such prefixed names (!WinFoo, KFoo, GFoo, iFoo, etc).   
+>>> IMHO those fall in the "cheesy" category ;-) 
+>>> Exceptions are bindings or Python versions of some product, but   
+>>> otherwise I think it's rather ugly. 
+>>> [[br]] - [http://www.cmlenz.net/ Christopher Lenz]
+>> Yes, ''pySomething'' usually stands for the Python bindings for that ''Something''.
+>> In the context of Markup, it was more meant to be reminiscent of the `py:` prefix we use everywhere in our templates.
+>> So maybe... py:markup? Additionally, this goes well with the encapsulation in <...> illustrated in the logo.
+>> [[br]] - cboos
+> See the comment I added at the top of the page about constraints on the project name. I actually like `py:markup`, but don't see how that would work as a name.
+> [[br]] - cmlenz
+Ok, then I stand for '''''pymarkup''''' for the project name ''and'' the package name; only the logo would be slightly different (''`<py:markup!>`'' but see below for a nicer rendering). Note that this slight difference already exists for the current logo/name (''`<markup/>`'' vs. Markup).
+[[br]] - cboos
 
 == “Markhor” ==
@@ -63 +66 @@
 > "python papyrus" turns up nothing relevant. So my suggestion
 > is - grab the name while you can :)
+> [[br]] ~talin
+... except for the fact that this name is not already used, what would be the connection?
+[[br]] - cboos
 
 ----
@@ -69 +75 @@
 I like the current logo, however I thought about a small twist that would make it look even better: use a "!" instead of "/". That makes it more "dynamic".
 
-HTML prototype: [[html(<em><span style="color: #888">&lt;</span>markup<span style="color: #b33">!</span><span style="color: #888">&gt;</span></em>)]]
+HTML prototype: [[html(<em style="font-family: impact; font-size: 24pt"><span style="color: #888">&lt;</span>markup<span style="color: #b33">!</span><span style="color: #888">&gt;</span></em>)]]
 
 The "!" could even be interpreted as: "yeah, the name is ''markup''! despite all what people are saying about its googlability and other neologisms..." ;)
 
-HTML prototype for py:markup: [[html(<em><span style="color: #888">&lt;</span><span style="color: #b33">py</span><span style="color: #888">:</span>markup<span style="color: #b33">!</span><span style="color: #888">&gt;</span></em>)]]
+HTML prototype for py:markup: [[html(<em style="font-family: impact; font-size: 24pt"><span style="color: #888">&lt;</span><span style="color: #b33">py</span><span style="color: #888">:</span>markup<span style="color: #b33">!</span><span style="color: #888">&gt;</span></em>)]]