color scheme for new logo and shinyStan GUI (a lighter topic)

[Jonah]

Does anyone know the colors (in hex or rgb) for the new logo art? Or has it been put up on GitHub yet? I was thinking I should incorporate the colors into the color scheme of the shinyStan GUI for the next release.

Jonah

[Bob Carpenter]

Looks like we're going Harvard-like instead of Columbia-like
or Xbox-like. The ones from the images Michael sent around
are:

Light crimson: RGB: 176, 12, 37 aka: b31028
Dark crimson: RGB: 87, 8, 20 aka: 570814

Those are going to be tough as they're both relatively dark.

- Bob

> On Mar 20, 2015, at 1:47 PM, Jonah <jga...@gmail.com> wrote:
>
> Does anyone know the colors (in hex or rgb) for the new logo art? Or has it been put up on GitHub yet? I was thinking I should incorporate the colors into the color scheme of the shinyStan GUI for the next release.
>
> Jonah
>

> --
> You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Jonah Sol Gabry]

Thanks Bob. I haven't seen the logo yet, but yeah those colors are a bit dark, even the light crimson. I'll play around a bit and see if I can come up with anything decent to do with them in shinyStan.

You received this message because you are subscribed to a topic in the Google Groups "stan development mailing list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/stan-dev/5DE0sQUYhO8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to stan-dev+u...@googlegroups.com.

[Michael Betancourt]

To be exact (straight from the SVG itself):

Light: b2001d

Dark: 590815

https://www.dropbox.com/s/o84jkq7glvjgmjd/shinystan_logo_name.png?dl=0

The crimson is meant to be a highlight — if you use white and light grey

for backgrounds then you should be able to come up with a snappy color

scheme.  When we officially drop the logo I’ll update the website as an

example.

[Bob Carpenter]

What do you mean by officially drop the logo? I think
we're ready as soon as you're done tweaking it.

I used the color probe tool in pixlr to read the colors
off the PNG, but either it's broken or the PNG you sent
has different colors than the SVG original. Weird. Did
you do soemthing like reduce the colors for the web or
something?

- Bob

[Michael Betancourt]

> What do you mean by officially drop the logo? I think
> we're ready as soon as you're done tweaking it.

I’m waiting for confirmation on the font and pulling the
logo out into a separate repo.

> I used the color probe tool in pixlr to read the colors
> off the PNG, but either it's broken or the PNG you sent
> has different colors than the SVG original. Weird. Did
> you do soemthing like reduce the colors for the web or
> something?

Just the default Inkscape export but there may be color
resolution options that I missed.

[Jonah]

Hi Michael,

The logo looks really good! One thing: we've been using shinyStan rather than ShinyStan. Is it possible to make the first 's' lowercase in the logo?

[Michael Betancourt]

That would be easy but it would clash with the other
interfaces that go full camel case. Do we want
shinyStan to follow the interface naming convention?

[Bob Carpenter]

Didn't you get my message on the font EULA? We're
good to go for using it in a logo --- what we can't do
is redistribute the entire font set as SVG or TT --- they
explicitly allow use in logos and other bitmapped graphics.
(Of course, we can develop the logos in SVG format.)

- Bob

[Michael Betancourt]

Sorry — I thought that was an ongoing conversation.

So given that Inkscape does not embed fonts are
we good to include both the svg and pngs?

[Bob Carpenter]

We already had the discussion about shinyStan (I objected
to naming it both after Stan and after shiny, but The Nominator
didn't want something obscure or cute [go figure --- he's the
one who gave us "Stan"], like say a riff on "coda" [pun intended]).

"Shiny" is capitalized on their own pages, so I'm not sure
why "shinyStan" was chosen.

I'm OK with changing it --- we've already confused the hell out
of people by calling the R interface "RStan" in print, but "rstan"
as a package and for the repo and capitalizing "STAN" in the first
logo.

As to camel case, a common convention is that classes
are uppercased and variables lowercased initially, so
that'd be "ShinyStan" for a class and "shinyStan" for a variable.

- Bob

[Bob Carpenter]

> On Mar 21, 2015, at 11:54 AM, Michael Betancourt <betan...@gmail.com> wrote:
>
> Sorry — I thought that was an ongoing conversation.
>
> So given that Inkscape does not embed fonts are
> we good to include both the svg and pngs?

Yes. Anything we distribute outside of the repo
will be either a PDF without embedded fonts (manual),
a PNG (for the web site), and print (t-shirt, etc.),
all of which are OK under the EULA.

We just can't distribute the whole font set as an SVG.
So just make sure we don't have an ABCDEFGHIJKLMNOPQRSTUVWXYZStan
distributed as an SVG.

Any use as a PDF without embedded fonts, a PNG, or print
is just fine.

- Bob

[Jonah Sol Gabry]

Naming things has never been my forte. 

If it's not a big deal then at this point I would prefer to keep the name shinyStan, although I'm not opposed to changing it if people feel very strongly about it. 

The naming convention for R packages that use Shiny (or add functionality to Shiny) is to use a name of the form shinyX (e.g. shinyAce, shinyBS, shinyIncubator, shinyFiles, shinyGridster, etc.). There are a few exceptions, but none of them use Shiny with a capitalized S. 

--
You received this message because you are subscribed to a topic in the Google Groups "stan development mailing list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/stan-dev/5DE0sQUYhO8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to stan-dev+u...@googlegroups.com.