Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse-scripting-dev] RE : eScriptMonkey naming

Why not toth ? It refers to the ancient art of scripting in ancient Egypt.
De : eclipse-scripting-dev-bounces@xxxxxxxxxxx [eclipse-scripting-dev-bounces@xxxxxxxxxxx] de la part de Christian.Pontesegger@xxxxxxxxxxxx [Christian.Pontesegger@xxxxxxxxxxxx]
Date d'envoi : mercredi 11 septembre 2013 11:04
À : eclipse-scripting-dev@xxxxxxxxxxx
Objet : Re: [eclipse-scripting-dev] eScriptMonkey naming

The Name Script(My)Eclipse is nice, as it actually describes what we are doing.
Unfortuantely you may install scriptEclipse from eclipse marketplace already. So I guess we would need another name.
Before you ask: eclipseScript is also taken by other projects.

What about something more abstract: “Phoenix”
“… as EclipseMonkey rises like a phoenix from the ashes…”

Would give a nice logo…

I guess for the top level package name we have to ask someone at eclipse for clearance anyway.


From: eclipse-scripting-dev-bounces@xxxxxxxxxxx [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent: Wednesday, September 11, 2013 10:44 AM
To: Discussions about scripting Eclipse.
Subject: Re: [eclipse-scripting-dev] eScriptMonkey naming

I really like “ScriptMyEclipse” , it addresses all the criteria that I’ve mentioned in my previous E-Mail.

What about shortening it to just “ScriptEclipse” and package names org.eclipse.scripteclipse.*

Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6

From: eclipse-scripting-dev-bounces@xxxxxxxxxxx<mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx> [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria
Sent: Wednesday, September 11, 2013 10:40 AM
To: eclipse-scripting-dev@xxxxxxxxxxx<mailto:eclipse-scripting-dev@xxxxxxxxxxx>
Subject: Re: [eclipse-scripting-dev] eScriptMonkey naming

Although I'm not a contributor, I'd like to give my 2 cents.

* IMHO, acronyms are generally very bad at getting attention and understanding from people out of the community. EASE and DSEE don't mean much to anyone, it's impossible to guess what the project is about from this acronym, I've not tried Googling it but I'm pretty sure that those acronyms are already used in some other contexts (just like any acronym), and it is easy to mess up and switch letters without paying attention. Also "ease" is a very common word, so it will make googling very difficult.
* What is the issue with long packages name? Almost no-one ever types it as it is often generated.

EScriptMonkey is not that bad but suffers from the competition of the hundreds of other EScript projects existing.
I would go for something more explicit, such as ScriptMyEclipse, with the long scriptmyeclipse package name; it costs a few extra characters but it's explicit, easy to remember, not competing with other names, and you can even make typos in your Google researches it will find it.

Mickael Istria
Eclipse developer at JBoss, by Red Hat<>
My blog<> - My Tweets<>

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

Back to the top