Home  
Login
Username:

Password:

Remember me



Lost Password?

Register now!
Sections
Who's Online
27 user(s) are online (8 user(s) are browsing Forums)

Members: 0
Guests: 27

more...
Support us!
Recent OS4 Files
OS4Depot.net



« 1 2 (3)


Re: ReAction, what is missing to make it a good GUI?
Quite a regular
Joined:
2009/5/1 17:57
From Czech Republic
Posts: 831
@afxgroup

Sure but BOOPSI is not "real" OOP so just respecting the fundamentals, ie. manipulating objects via methods, is an improvement in my view.

   Report Go to top

Re: ReAction, what is missing to make it a good GUI?
Just popping in
Joined:
2008/3/1 9:53
Posts: 138
@trixie

Quote:

Tags should describe object properties, not invoke function calls - that's what methods are for. So the introduction of the child removing method was the right step, in line with OOP principles.


Uhm...

Quote:

if(LayoutBase->lib_Version>=53)
{
IIntuition->IDoMethod((Object *)mommy, LM_REMOVECHILD, inst->Win, ubrow->buttons[j], TAG_DONE);
}
else // Use fallback function. Note, this function may deadlock
{
IIntuition->RefreshSetGadgetAttrs(mommy, NULL, NULL, LAYOUT_RemoveChild, ubrow->buttons[j], TAG_DONE);
}


I believe LM is for LayoutMethod, so here is used a method which is called on object mommy and take a window and the object to remove (a button).

On MUI you does:

Quote:

DoMethod(group, MUIM_Group_InitChange);
DoMethod(group, OM_REMMEMBER, button);
DoMethod(group, MUIM_Group_ExitChange);


You tell to MUI you are doing a change(s) into a group and then you make your changes, in this case you remove a button from a group with BOOPSI method OM_REMMEMBER.

From programming POV is better the new LM_REMOVECHILD (from this little example code) because system takes care about the state of objects, while in MUI way user have to take care of state of object to change with IntiChange/ExitChange.

   Report Go to top

Re: ReAction, what is missing to make it a good GUI?
Just can't stay away
Joined:
2006/12/4 23:15
Posts: 1482
@afxgroup

Quote:

if you want real oop you should have:

mommy.RemoveChild(j)

this should be the right step...



That's no more or less OOP than the intuition call. But it is a more of a C++ thing, with the intuition call any language with a wrapper for IDomethod can make the call with needing updating (just some extra tags values might need adding)

   Report Go to top


« 1 2 (3)



[Advanced Search]


Powered by XOOPS 2.0 © 2001-2014 The XOOPS Project