Remember me

Lost Password?

Register now!
Who's Online
72 user(s) are online (52 user(s) are browsing Forums)

Members: 0
Guests: 72

Support us!
Recent OS4 Files
Report message:*

Re: BOOPSI Menu Class: first update

Subject: Re: BOOPSI Menu Class: first update
by trixie on 2014/7/4 9:01:36


Thanks for your ideas! I'll explain in a bit more detail what I'm trying to do.

I'm designing the class in such a way that it provides a general description of a menu hierarchy, and a set of atributes and methods to manipulate it. The keyword here is general. Neither Intuition, nor Gadtools is involved in the class' inner workings. Only when there is a request to attach the menu object to a window will the class translate the object data into something that Intuition or Gadtools can use. This is to allow an easy rewrite should a new menu system ever be introduced: much of the class will remain the same, only the translation code will have to change.

If the object data gets happily translated into a field of NewMenus then I'll certainly want to use CreateMenus(), to save me trouble and to make the translation code as short/simple as possible. I'll only dive to Intuition's treacherous depths if there's no other way

Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project