qt已经基本完整支持symbian了，但是即使是基于qt的开发仍然显得过重，在symbian上支持pyqt显然没有那么容易，pys601.9.7这个版本已经很久了，在ovi上已经放出了python for s60 2.0的版本，我还没有把它弄下来，这个还有点难度，我的手机上用不了ovi，我比较期待2.1的版本，它或许能带给我更多惊喜。
看看pys60 fans们说些什么：
I have been developing an electronic cash client for the mobile phone using pys60. Now, with android etc. coming up, and seeing no further development on the pys60 (1.9.7 has been around forever), is it still worth pursuing this platform as a python dev?
我一直在使用pys60开发电子交易客户端，现在android雄起，而pys60却一直卡着毫无进展（1.9.7一直挂在那里），这还是值得我们追求的python开发平台吗
hello joerg
more than a week ago i was also thinking the same thing
but believe me that we all will get some nice gifts shortly as far as development in PyS60 is considered.
so just saty tuned
Regards,
俺一周以前也在想这个问题，但是相信俺吧，pys60不久会给我们带来一个令人惊喜的礼物。稍息稍息。
This looks promising:
http://www.allaboutsymbian.com/news/…arts_to_be.php
Hi delehrm and gaba88,
thanks for the pointer and calming words. This starts to look exiting. I just hope its not a one time effort, but a (re)start of a continious development / publishing cycle.
Santa, please… ;-)
难道这是传说中的pys60 2.0，看起来有点望头。
Hmph,
Is pys60 dead? Ever since I realized listboxes don’t work (and won’t get fixed) in touch devices and performance keeps getting worse release after release, my efforts have gone to iPhone development.
…it’s a shame, but I got to write something! I’m addicted to writing software, even if it’s “just” freeware and even if I’m the only user (as now with my iPhone apps). Got to code, got to design apps, got to make things, got to release things! PyS60 was ideal for me, since it was so easy to use and so very powerful. Pure pleasure, regardless of unclear future, no built-in support in devices, some defects and limited UI components, difficulty of installation, without discussion connection to development team etc. Even regardless of hostility of Microsoft Vista!
If PyS60 version 2.0 gets released, will I come back? Of course! I’ll check how many of my released 25 apps work with it, check whether Listbox defect with touch devices has been fixed, check whether performance with sensor framework is more than 1 screen update per second.
If yes, I got some ideas for new apps. If not, then I’ll wait PyS60 2.1 for S60 5.0 Touch UI devices.
Waiting,
–jouni blaming Microsoft Vista for many Nokia development problems, using MacBook Pro nowadays
pys60死了吗，自从俺在触屏设备上实现列表框遭到严重挫折（他娘的居然不能固定）以及一次一次发布带来的性能恶化。俺只好将精力倾注于iphone开发了。
耻辱啊，我是该写点什么，俺沉迷于编写软件，即使只是免费的，甚至俺是软件的唯一用户（比如俺现在的iphone应用），无论是编码，设计，编译，发布，pys60都是我理想的选择，它易用而强大，这是快乐的选择，无论它是否前途不明。没有内建的设备支持。充满缺陷和限制的组件，安装困难，社区凋零，甚至是八杆子打不着的ms的敌视。
如果2.0发布，或许我会回来？当然我得检测以下我发布的25个app是否能在上面正常工作，检查该死的列表框在触屏上是否固定了，检测在每秒高于一次的刷新速度上传感器框架的性能。
如果是，那好极了，我又得到了一个新的应用开发思路。如果不是，那么我只好等s60 5.0 触屏设备 的2.1版本
期待中….
Perhaps you should give a try to N900 (Maemo 5)? I borrowed one from a friend of mine and it seems it is very promising device, at least for developers/hackers.
It has Python and Python’s Qt bindings available, OS supports touch UI, built-in sensors, no SymbianSigned hell, very little restrictions i.e. “root access” to the device’s resources etc.
或许可以试试maemo5。
阿门，祝福所有对python有爱的兄弟。
http://embed.e800.com.cn/articles/2007/43/1175589178483302456_1.html
今天询问了一家J2ME签名的代理商，对方说Sybian已经放弃支持第三方签名，也就是VeriSign和Thawte的签名在Sybian的手机上不支持了，Sybian将自己销售签名，不知道这是不是Sybian没落的前兆之一，连这点小钱也要自己赚了。
(0119) 之前的说明有误，是Sybian自己SDK开发的程序签名不再支持VeriSign，只能通过再签名或者购买另外一格签名（好像是SunGlobal），而且是按签名次数计算的（还必须1年内签完，奸商！），J2ME签名没有受影响。
public class TabMapsExample extends TabActivity { TabHost mTabHost; @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); Context ctx = this.getApplicationContext(); //tab 1 mTabHost = getTabHost(); TabSpec tabSpec1 = mTabHost.newTabSpec("tab_test1"); tabSpec1.setIndicator("Map1"); Intent i1 = new Intent(ctx, MapTabView.class); tabSpec1.setContent(i1); mTabHost.addTab(tabSpec1); //tab2 mTabHost = getTabHost(); TabSpec tabSpec2 = mTabHost.newTabSpec("tab_test1"); tabSpec2.setIndicator("Map2"); Intent i2 = new Intent(ctx, MapTabView.class); tabSpec2.setContent(i2); mTabHost.addTab(tabSpec2); //tab 3 mTabHost = getTabHost(); TabSpec tabSpec3 = mTabHost.newTabSpec("tab_test1"); tabSpec3.setIndicator("Map"); Intent i3 = new Intent(ctx, MapTabView.class); tabSpec3.setContent(i3); mTabHost.addTab(tabSpec3); } }
这是地图和tabHost的使用
<?xml version="1.0" encoding="utf-8"?> <RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android" android:id="@+id/maptablayout" android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="fill_parent"> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_height="fill_parent" android:layout_width="fill_parent" android:background="#000000" android:orientation="vertical"> <TextView xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="fill_parent" android:layout_height="50px" android:id="@+id/textview" /> <com.google.android.maps.MapView android:id="@+id/mapview" android:layout_width="fill_parent" android:layout_height="fill_parent" android:clickable="true" android:apiKey="" /> </LinearLayout> </RelativeLayout>
上面的红线是必须的 apiKey是每个人都有一个特定的值
mapView.getController().zoomIn();
mapView.getController().zoomOut();
mapView.getController().setZoom(...);
Intent intent = new Intent(this, MyMapActivity.class); //this is just one way of specifying it intent.putExtra(MyMapActivity.ZOOM_LEVEL_CONSTANT, 10); startActivity(intent);
在MyMapActivity onCreate(...)
Bundle retrievedData = this.getIntent().getExtras(); if (retrievedData != null) { int zoomLevel = retrievedData.getInt(ZOOM_LEVEL_CONSTANT); mapView.getController.setZoom(zoomLevel); }
有时候你可能用到
MapView mapView = (MapView) findViewById(R.id.mapview);
mapView.setBuiltInZoomControls(true);
MapController mapController = mapView.getController();
mapController.setZoom(10);
那么如何在mapActivity加入菜单呢
其实很简单 你只要继承activity就可以了
其他的不变和activity一样
http://developer.android.com/intl/fr/guide/topics/ui/menus.html