When developing a cross-platform application, the tools (or development library) you use often force you into a lowest-common-denominator approach. To avoid over-complexity, the tools tend to offer things only that all the target platforms can support. And since the different platforms rarely do all the menus, and the various widgets and UI components the same way, it ends up getting pretty ugly.
It's often pretty obvious when you're using an application that was written using cross-platform tools like wxWindows/etc.
So Creamware chose to use the cross-platform tools in a different way - rather than trying to use the abstractions for the various UI widgets, etc, they just use the low-level graphics support, and draw all their own widgets/menus/etc.
I agree, from the user's POV, this can be frustrating sometimes, as it doesn't conform to the platform user interface standards. But from CW's POV, it obviously makes their maintenance easier, as they don't have to maintain compatibility or follow trends in the platform UI standards.
So, as a user, I totally agree with the original post here- I'd like it if Scope was more consistent with all my other apps. But, as a software developer, I can understand why CW did it this way...
Cheers,
-John
Why doesn't CW follow the rules...
-
John Cooper
- Moderator
- Posts: 1182
- Joined: Thu Mar 22, 2001 4:00 pm
- Location: Planet Z
- Contact:
-
hubird
