Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » Mac OS » Porting (Mac OS X) and "reference application" idea
Re: Porting (Mac OS X) and "reference application" idea [message #33147 is a reply to message #33142] Mon, 11 July 2011 09:34 Go to previous messageGo to previous message
kohait00 is currently offline  kohait00
Messages: 939
Registered: July 2009
Location: Germany
Experienced Contributor
thanks for providing some insight..

the level of porting upp would be 'native', grabbing a spot of screen or a main window, and beeing able to draw on it. this can start off with the X11 based theIDE port, but it should end with a full rainbow complaint (see uppsrc/rainbow) port of the underlying structure. everything in between is sort of implementation detail Smile

concerning the widgets: upp has its own set of wifgets, so we don't need to mess around with the macos stuff at all, this is also the beauty of crossplatform.. an almost-macosx style of the upp widgets can be obtained with the skinning mechanism in upp. you already are able to have macos style in upp apps in windows..

so the basic thing is:

* implement the SystemDraw interface, which redirects the corresponding drawing operations (like DrawRect, DrawLine) to the native drawing contexts of macos.

* implement the mouse processing to translate the received mouse handling from macos to upp and have upp process it.

* implement the keyboard processing, translate the received key actions from macos to upp and have upp process it.

* when this quite works, stuff like copy/paste, drag/drop etc. can be handled (with macos means).

i'm novice in mac stuff (actually have done nothing with it, besides some research in the web for quartz port). but i will try to help. since MACOSX port of UPP would be a MAJOR boost for upp, and our company would HIGHLY apriciate, we have audio controlling software coded in upp, customers have windows, linux, AND ofcorse macos, and need to run it in simulaters. i'm a bit into the porting stuff (not too much though), porting to linux native framebuffer and SDL. so the process is comparable. but it this case, you have main windows of macos (which should map to TopWindow), and i have a single sheer of buffer Smile which is esier..
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon6.gif
Read Message
Read Message
Read Message
Read Message
Read Message icon5.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: possibly working theide on Mac OS X using tiny mods to UNIX dist
Next Topic: Mac OS X backend development process
Goto Forum:
  


Current Time: Wed May 08 06:13:28 CEST 2024

Total time taken to generate the page: 0.01481 seconds