On Fri, Sep 19, 2008 at 8:06 AM, Christopher Arndt <[EMAIL PROTECTED]> wrote:
>
> Ken Kuhlman schrieb:
>> On Thu, Sep 18, 2008 at 6:45 PM, Florent Aide <[EMAIL PROTECTED]> wrote:
>>> I created a ticket #1992 in our trac and begun work on it.
>>
>> My concern with the original wording here was that it sounded a little
>> bit defensive.  A quickstarted template isn't the right place for
>> that, since it's one of the first things a new TG customer sees.  We
>> should strive for warm, friendly, & engaging.
>> [...]
>> Regardless,
>> support timelines are a topic for blog posts & perhaps the main
>> webpage, but not a quickstart template.  I'd also prefer that we
>> didn't say 1.x in this context, but rather specify 1.0.x specifically.
>>   1.x will live on as long as people are interested in it, just like
>> any software project.   (Obviously I'm biased, but I think 1.5 opens
>> up a whole new world of possibilities for us.)
>
> I fully agree. Quickstart templates should show off the best of
> TurboGears (without being overly complicated and bloated) and give
> pointers where users can learn more, if they want to.


While we are on this topic..would we be interested in having a build in menu?
I have talked to a guy who created this menu:

http://www.cssplay.co.uk/menus/final_drop2.html

and if "his name is listed and shows a copyright notice" he would be
willing to release it under BSD license for turbogears use.

This was the only cascading menu I was able to find that works when
you move the menu around in places, and it works on all browsers.

A separate file I would assume. menu.css

Interested?

Thanks,
Lucas

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to