wxFlatMenu & wxFlatMenuBar
in [wxWindows]
|
From: Robert Roebling on 16 Oct 2006 14:30 > For those of you are not visiting the wxForum at > http://wxforum.shadonet.com/ , I would like to announce that I am > currently developing an > alternative for the common wxMenuBar & wxMenu - wxFlatMenu & > wxFlatMenuBar Are these written completely in generic wxWidgets code? They surely look very nice (just as the wxFlatNotebook). I wonder how this could be made into a coherent thing. People are frequently asking about how to "customize" the look of wxWidgets apps and we are now getting more and more generic controls (wxComboCtrl, wxRichEditCtrl, wxVListBox, wxAUI in a sense) and we already have the wxUniversal "widget set". What we'd need is e.g. a wxFlatListBox which would use the same code for rendering a highlighted item as your wxFlatMenu code to make the two coherent. I'd think that other controls like the buttonXX and radioXXX classes are pretty easy to implement so in the end we only need to (and should) use the native text control and we'd have a fully themable app. Have you looked at writing a new theme for the wxUniversal widget set using the gradient code and mini-art you are using for your wxFlatControls? Robert --------------------------------------------------------------------- To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org
From: Eran Ifrah on 16 Oct 2006 14:27 Robert Roebling wrote: >> For those of you are not visiting the wxForum at >> http://wxforum.shadonet.com/ , I would like to announce that I am >> currently developing an >> alternative for the common wxMenuBar & wxMenu - wxFlatMenu & >> wxFlatMenuBar >> > > Are these written completely in generic wxWidgets code? > They surely look very nice (just as the wxFlatNotebook). > > I wonder how this could be made into a coherent thing. > People are frequently asking about how to "customize" > the look of wxWidgets apps and we are now getting more > and more generic controls (wxComboCtrl, wxRichEditCtrl, > wxVListBox, wxAUI in a sense) and we already have the > wxUniversal "widget set". What we'd need is e.g. a > wxFlatListBox which would use the same code for > rendering a highlighted item as your wxFlatMenu code > to make the two coherent. I'd think that other controls > like the buttonXX and radioXXX classes are pretty easy > to implement so in the end we only need to (and should) > use the native text control and we'd have a fully > themable app. > Have you looked at writing a new theme for the > wxUniversal widget set using the gradient code > and mini-art you are using for your wxFlatControls? > > Robert > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org > For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org > > > It is a generic code indeed, all drawings are done using the regular wxDC/wxMemoryDC family (except for the shadows for the menus). I think in time I will complete a full set of controls (buttons, check box, combo etc all from the "wxFlat" family) Eran --------------------------------------------------------------------- To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org
From: Vadim Zeitlin on 16 Oct 2006 22:53 On Mon, Oct 16, 2006 at 08:27:08PM +0200, Eran Ifrah wrote: > It is a generic code indeed, all drawings are done using the regular > wxDC/wxMemoryDC family (except for the shadows for the menus). Maybe it would make more sense to add some new methods to wxRenderer? > I think in time I will complete a full set of controls (buttons, check > box, combo etc all from the "wxFlat" family) But this is exactly the problem: how we're going to manage this? I.e. it's one thing to have one or two controls like this but if there are 20 of them it can become a nightmare if you decide to change something. Also, I think having a "flat" theme for wxUniv as mentioned by Robert would be a really great thing. Regards, VZ --------------------------------------------------------------------- To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org
From: Noel on 17 Oct 2006 03:03 Vadim Zeitlin wrote: > On Mon, Oct 16, 2006 at 08:27:08PM +0200, Eran Ifrah wrote: > > It is a generic code indeed, all drawings are done using the regular > > wxDC/wxMemoryDC family (except for the shadows for the menus). > > Maybe it would make more sense to add some new methods to wxRenderer? Eran wrote a renderer class and he decided towards a wxUniv renderer style method signatures. At least to draw a button. But AFAIK this renderer exists only in the wxUniv port. What should Eran do? He wants to see his flat menu on windows together with the native controls and on GTK together with GTK controls. I think you faced the same problem before and decided to create two different renders. One in the wxUniv port and another one in the other ports? If one wants to do this in a generic way (with a common renderer) doesn't that mean, we would need a common renderer across all the port? That sounds challenging. And with the ability to use native widgets too, wxWidgets would become a all-in-one device suitable for every purpose. But that is IMHO quite a long way to go. Or am I completely wrong? > > I think in time I will complete a full set of controls (buttons, check > > box, combo etc all from the "wxFlat" family) > > But this is exactly the problem: how we're going to manage this? I.e. it's > one thing to have one or two controls like this but if there are 20 of them > it can become a nightmare if you decide to change something. Well as long as this (really good looking and well designed) wxFlat things are in a separate library it is IMHO no problem to maintain. If one wants a flat menu, he simply links against this library and if one doesn't he uses the build in wxWidgets things (I could imagine macros to map from wxFlatMenu to wxMenu). That keeps things simple at the moment and enables Eran to develop quite quickly. My point: can we give advice or a kind of guideline for anybody who wants to reimplement a widget that already exists in wxWidgets? Are there plans or visions regarding the 'themeability' of the wxWidgets ports? > Also, I think having a "flat" theme for wxUniv as mentioned by Robert > would be a really great thing. Best regards, Noel
From: Julian Smart on 17 Oct 2006 05:27
Hi Eran, Vadim Zeitlin wrote: > On Mon, Oct 16, 2006 at 08:27:08PM +0200, Eran Ifrah wrote: > >> It is a generic code indeed, all drawings are done using the regular >> wxDC/wxMemoryDC family (except for the shadows for the menus). >> > > Maybe it would make more sense to add some new methods to wxRenderer? > > >> I think in time I will complete a full set of controls (buttons, check >> box, combo etc all from the "wxFlat" family) >> > > But this is exactly the problem: how we're going to manage this? I.e. it's > one thing to have one or two controls like this but if there are 20 of them > it can become a nightmare if you decide to change something. > > Also, I think having a "flat" theme for wxUniv as mentioned by Robert > would be a really great thing. > Yes, I really like the flat notebook and this latest menu look. Great work! If you were to centralize the code that draws the check marks etc., then it would certainly make it easier to integrate into wxRenderer or a theme later. Best regards, Julian --------------------------------------------------------------------- To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org |