Okay, so what information do we need to include in the banner?  I
suggest we vote on each item, and then worry about how to word each
item and how to assemble all of the results.  I'll post suggestions,
and then I'll vote myself in a separate message.

* Type "notebook()" for the notebook interface.     (FWIW, I worry
that "GUI" isn't helpful; how many mathematicians and math students
understand what this means?  Yes, I know I said that we'd worry later
about how to word each item, but I couldn't stop myself from
commenting.)

* Type "help()" for help.  (Or whatever the command is.)

* Type "quit" to quit.

* Type "license()" for license information.   (With or without a
statement explicitly mentioning GPL.)

* Build info

* Very detailed build info

* Type "???" to print system information (OS, type of processor,
amount of RAM, etc.)

Anything else we might include?

A question: if you worry that the banner might get too long, is that
for your own use -- you might get sick of seeing 8 lines instead of 4
-- or do you think it damages the esthetics generally?  I think we
could pretty easily have an environment variable, SAGE_SHORT_BANNER
for example, which if set to "yes" would result in a shortened banner
being printed, in case it's the former problem.  (We already have
SAGE_BANNER, which if set to "no" omits the banner entirely.)

  John
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to