Skip to main content

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

Another suggestion: s4?

---
Pierre


-----Original Message-----
From: eclipse-scripting-dev-bounces@xxxxxxxxxxx [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] On Behalf Of DAUSSY Arthur
Sent: Monday, September 23, 2013 12:25 PM
To: Discussions about scripting Eclipse.
Subject: Re: [eclipse-scripting-dev] eScriptMonkey naming

Hi,

 Although I really like the suggestion of Aaron I would suggest "ScriptEc" for Scripting Eclipse.

Regards,


Arthur Daussy
Atos
arthur.daussy@xxxxxxxx
+33 5 34 36 32 90





-----Message d'origine-----
De : eclipse-scripting-dev-bounces@xxxxxxxxxxx [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] De la part de Aaron Spear Envoyé : dimanche 22 septembre 2013 04:01 À : Discussions about scripting Eclipse.
Objet : Re: [eclipse-scripting-dev] eScriptMonkey naming

"Scriptonite" ? :-)

Aaron Spear

----- Original Message -----
> I still like "Scriptic" although I'm slightly concerned that one could 
> associate it with "Cryptic" which is exactly _not_ what we want to be .
>
> What about something like "Bach" , "Fuga" , "Symphony" , "Sinfonia" , 
> "Scriptony"
>
> Since we want the scripting to be able and automate all of Eclipse, 
> "orchestrating" the various plugins into something that works together 
> producing better workflows through automation ? Other names about 
> famous authors or musicians would also work of course.
>
> I think the project name is only relevant while Scripting is a 
> separate component, to be discovered and installed separately. It 
> should be easy to find, remember, and install. In case we should get 
> into the Platform at some point via e4, the project name wouldn't 
> really matter any more since then scripting is just "already there".
>
> Thanks,
> Martin
> --
> Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind 
> River direct +43.662.457915.85  fax +43.662.457915.6
>
>
> -----Original Message-----
> From: eclipse-scripting-dev-bounces@xxxxxxxxxxx
> [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] On Behalf Of 
> Oberhuber, Martin
> Sent: Wednesday, September 11, 2013 10:43 AM
> To: Discussions about scripting Eclipse.
> Subject: Re: [eclipse-scripting-dev] eScriptMonkey naming
>
> Hi all,
>
> I like "Scriptic" , although it doesn't have any connection to Eclipse 
> or what we're trying to achieve specifically with this project.
>
> What about "EasyScript" since one goal is appealing to end users and 
> make scripting for them very easy (regardless of scripting language) ?
> I think the "ease of use" was one of the design goals behind Monkey, 
> it strived to be as easy and widespread as Mozilla GreaseMonkey.
>
> Shortening EasyScript, we're back to "EScript" which could be taken 
> for "Eclipse Scripting" or "Easy Scripting".
>
> Are there any must-have criteria why we absolutely can't take "EScript" ?
> Perhaps we can remove any blockers here by some other means ?
>
> Thanks,
> Martin
> --
> Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind 
> River direct +43.662.457915.85  fax +43.662.457915.6
>
>
> -----Original Message-----
> From: eclipse-scripting-dev-bounces@xxxxxxxxxxx
> [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] On Behalf Of DAUSSY 
> Arthur
> Sent: Wednesday, September 11, 2013 10:25 AM
> To: Discussions about scripting Eclipse.
> Subject: Re: [eclipse-scripting-dev] eScriptMonkey naming
>
> Hi Christian,
>
>  I agree with you about the name. Something new would be better.
>  However I don't really like using acronyms for name. I find it hard 
> to  remember. I would prefer something like Scriptic or ScriptOn 
> (already
>  taken) that seems easier to remember.
>  I have thought about :
>         4Script (If we are host in E4)
>         Scriptic
>         Scripto
>
>
>  Regards,
>
>
> Arthur Daussy
> Atos
> arthur.daussy@xxxxxxxx
> +33 5 34 36 32 90
>
>
>
>
>
>
> -----Message d'origine-----
> De : eclipse-scripting-dev-bounces@xxxxxxxxxxx
> [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] De la part de 
> Christian.Pontesegger@xxxxxxxxxxxx
> Envoyé : mardi 10 septembre 2013 08:47 À :
> eclipse-scripting-dev@xxxxxxxxxxx Objet : [eclipse-scripting-dev] 
> eScriptMonkey naming
>
>
> Hi,
>
> as the new eScriptMonkey project is growing on GitHub, I'd like to 
> propose to find a nice new project name for it. While a eScriptMonkey 
> is fine as a working title I would prefer a new name for following reasons:
>
> * There already exists a project called scriptMonkey on github:
> https://github.com/siddii/scriptmonkey/
>
> * The name very similar to EclipseMonkey. While a "monkey" would be 
> great for icon design (which we will need in time) I think the name 
> would let users think, that this project is a simple revival of 
> EclipseMonkey. But it is far more than that. Actually the "monkey"
> part (loading scripts, having dynamic menus to organize them, the DOMs) is just one facet of the whole thing.
> Providing a simple module mechanism for users to contribute, shell 
> scripting, ev. Visual scripts are things beyond the focus of 
> EclipseMonkey (please correct me, if I'm wrong).
>
> * eScriptMonkey (to me) seems very long as a root package name
> (org.eclipse.escriptmonkey...)
>
>
> I am not very happy with eScript either as it sounds more like a new 
> scripting language than what it actually is: an interpreter framework.
>
> So I started thinking and found some candidates:
>
> DSEE: Dynamic Script Execution Environment (pronounce: [di: si:], like 
> the 2nd part of AC/DC)
> EASE:  Eclipse Advanced Scripting Environment
>
>
> Let me know what you think: do we need a better project name? Any 
> suggestions for a decent name?
>
> Best regards
> Christian
>
> _______________________________________________
> eclipse-scripting-dev mailing list
> eclipse-scripting-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev
> ________________________________
>
>
> Ce message et les pièces jointes sont confidentiels et réservés à 
> l'usage exclusif de ses destinataires. Il peut également être protégé 
> par le secret professionnel. Si vous recevez ce message par erreur, 
> merci d'en avertir immédiatement l'expéditeur et de le détruire.
> L'intégrité du message ne pouvant être assurée sur Internet, la 
> responsabilité du groupe Atos ne pourra être engagée quant au contenu 
> de ce message. Bien que les meilleurs efforts soient faits pour 
> maintenir cette transmission exempte de tout virus, l'expéditeur ne 
> donne aucune garantie à cet égard et sa responsabilité ne saurait être 
> engagée pour tout dommage résultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended 
> solely for the addressee; it may also be privileged. If you receive 
> this e-mail in error, please notify the sender immediately and destroy 
> it. As its integrity cannot be secured on the Internet, the Atos group 
> liability cannot be triggered for the message content. Although the 
> sender endeavors to maintain a computer virus-free network, the sender 
> does not warrant that this transmission is virus-free and will not be 
> liable for any damages resulting from any virus transmitted.
> _______________________________________________
> eclipse-scripting-dev mailing list
> eclipse-scripting-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev
> _______________________________________________
> eclipse-scripting-dev mailing list
> eclipse-scripting-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev
> _______________________________________________
> eclipse-scripting-dev mailing list
> eclipse-scripting-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev
>
_______________________________________________
eclipse-scripting-dev mailing list
eclipse-scripting-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev
________________________________


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
_______________________________________________
eclipse-scripting-dev mailing list
eclipse-scripting-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev

This mail has originated outside your organization, either from an external partner or the Global Internet.
Keep this in mind if you answer this message.



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