Development

To: haiku-development haiku-development@xxxxxxxxxxxxx Sent: Mon, May 18, 2015 6:09 pm Subject: [haiku-development] Re: Who's working Haiku's on UI/UX? I want to share some ideas from the craziest UI windowing system I ever used. It was called NeWS and maybe some people heard of it. It ran on SunOS and was based on interpreted object oriented PostScript code. Any window could ...

From: Pete Goodeve pete.goodeve@xxxxxxxxxxxx To: haiku-development haiku-development@xxxxxxxxxxxxx Sent: Mon, May 18, 2015 6:09 pm Subject: [haiku-development] Re: Who's working Haiku's on UI/UX? a general comment, I suspect that UI Designers are apt to think that everyone uses an OS the same way -- and *all* OSs the same way. ...

[This thread has essentially self-destructed by now, but I'll reply anyway] On Mon, May 18, 2015 at 10:25:08AM +0400, fox noodles wrote: [in reply to me] [As a personal opinion, I'm not too impressed with a lot of the trendy UI stuff. Ubuntu has a lot of the fades, and so on, and is often frustratingly unusable. In particular the scrollbars are abysmal!] ...

Look versus feel: The look of the system is that it's out of the 90's (which it is) It may be an ugly interface by todays standard (lickable icons in mac), however even if you look at windows 10, you will still see elements this OS has, in their flat interface be it scrollbars that are gone or not, most of your ideas won't be able to be implemented until we have 2d acceleration (let alone 3d accelerated)... The feel of the system is that it's from today ...

support/Archivable.h calls <image.h>

This isn't found, since the directory it lives in isn't in the header path.

Should be <kernel/image.h>

This header is required fpor the definition of image_id in the following line:

BArchivable* instantiate_object(BMessage* from, image_id* id);

TeamSettingsWindow: - Split out functionality into separate views for images and exceptions, which in turn are held in dedicated tabs. TeamSettingsWindow: - Split out functionality into separate views for images and exceptions, which in turn are held in dedicated tabs.

262 MB

- Rename BreakConditionConfigWindow to TeamSettingsWindow, and move to own dedicated subfolder. Adjust callers accordingly. Preparation work for other changes to come. - Rename BreakConditionConfigWindow to TeamSettingsWindow, and move to own dedicated subfolder. Adjust callers accordingly. Preparation work for other changes to come.

263 MB

264 MB

ImageFunctionsView: - For function nodes, also display the start address of the function in question. Makes it somewhat more convenient to determine which function a function pointer actually refers to. ImageFunctionsView: - For function nodes, also display the start address of the function in question. Makes it somewhat more convenient to determine which function a function pointer actually refers to.

VariableTableModel: - When attempting to retrieve the type for a given node, ensure that it actually has a value node first. This might not necessarily be the case if no appropriate type handler was found. VariableTableModel: - When attempting to retrieve the type for a given node, ensure that it actually has a value node first. This might not necessarily be the case if no appropriate type handler was found.

AddressValueNode: - If the address node is pointing to a function, don't bother creating a child, as there isn't really any useful information that can be displayed for such a node besides its target address, which is already shown by the address node anyways. AddressValueNode: - If the address node is pointing to a function, don't bother creating a child, as there isn't really any useful information that can be displayed for such a node besides its target address, which is already shown by the address node anyways.

TeamDebugger: - Add signal events to debug event mask. Upon receipt of such an event, stop the target thread. WIP. TeamDebugger: - Add signal events to debug event mask. Upon receipt of such an event, stop the target thread. WIP.

DebugEvents: - Add definition for SignalReceivedEvent. DebuggerInterface: - Generate SignalReceivedEvent upon receipt of B_DEBUGGER_MESSAGE_SIGNAL_RECEIVED. DebugEvents: - Add definition for SignalReceivedEvent. DebuggerInterface: - Generate SignalReceivedEvent upon receipt of B_DEBUGGER_MESSAGE_SIGNAL_RECEIVED.

- Represents information about a signal being delivered to the team. - Represents information about a signal being delivered to the team.

262 MB

263 MB

264 MB