← Back to team overview

elementaryart team mailing list archive

[Bug 837813] [NEW] granite.appmenu should work the same as gtk.menu

 

Public bug reported:

I think it's not a good idea to use a menu as argument in the
constructor of appmenu, it should work exactly as gtk.menu I think, you
know, a constructor without arguments and an append() function.

Also I think all the default elements should be optionals. the
"translate" and the "report a problem" are not neccessary I think, these
options should be all contained in an "about elementary" app similar as
gnome does... its just an idea.... there's a lot of ways to do it.

** Affects: granite
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of
elementary desktop team, which is the registrant for Granite.
https://bugs.launchpad.net/bugs/837813

Title:
  granite.appmenu should work the same as gtk.menu

Status in Granite Framework:
  New

Bug description:
  I think it's not a good idea to use a menu as argument in the
  constructor of appmenu, it should work exactly as gtk.menu I think,
  you know, a constructor without arguments and an append() function.

  Also I think all the default elements should be optionals. the
  "translate" and the "report a problem" are not neccessary I think,
  these options should be all contained in an "about elementary" app
  similar as gnome does... its just an idea.... there's a lot of ways to
  do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/granite/+bug/837813/+subscriptions


Follow ups

References