>>Pyjamas to create real WebApps (I remember Ed being less than enthusiastic...) should be the first step IMHO - would be good demo/starting point >for all devices. If a customer DEMANDING native versions steps up, another port can be made - by that time the GUI classes must be in a similar >clean state as the DB classes - currently there is no way to even think of a port, as wx code is intermingled with pure python dabo GUI logic.
>
>>but that is only from the POV of an interested outsider taken a good look at the code...
>
>>regards
>
>>thomas
>
>I went to Python because it was very close to VFP. That said I don't like javascript (even using jQuery). So if I'm forced to use javascript then pyjamas looks much better. But the pyjamas project is still young and will need much more devel. With reference to your last statement I don't understand. All the UI code is separate from the biz (model) etc... ?????

class dButton(cm.dControlMixin, wx.Button):
	def __init__(self, parent, properties=None, attProperties=None, *args, **kwargs):
		self._baseClass = dButton
		preClass = wx.PreButton
		cm.dControlMixin.__init__(self, preClass, parent, properties, attProperties,  
				*args, **kwargs)


	def _initEvents(self):
		super(dButton, self)._initEvents()
		self.Bind(wx.EVT_BUTTON, self._onWxHit)
		
	
	def __onCancelButton(self, evt):
		# This callback exists for when the user presses ESC and this button
		# is the cancel button. Raise dEvents.Hit.
		self.raiseEvent(dEvents.Hit)

Here pure python code like def __onCancelButton(self, evt): IMHO should be separated from the pure toolkit-adapting code, either into a parentclass or another, "pure-python" mixin of common functionality for the button class to keep the code DRY. The event binding would remain in the toolkit-specific class, so that the event binding or mapping to constants would be coded according to the specific method names used in each toolkit.

>I, in fact was able to get QT to work as the UI for Dabo (just opened a form) by redirecting the UI call from wx to QT.
>

must be more similar than I thought...

>But like you, I would like to see other ports - mainly QT. If we had QT - today we would have native android, iphone, iPad, Andriod-pads. Yes both the android and iOS projects still need devel. time but they are coming along. Of course you don't need Dabo for QT they do have a model that works very well. pyside 1.0 was release this month and works. pySide is free and open source. The only question I have about QT is what is Nokia going to do with it in the future.

Yupp, and the things in store for HTML5 make it interesting as well - a browser based approach becomes more standard.

regards

thomas