Participated first Mozilla Meetup. It was held in Tokyo, Japan, at Ben’s Cafe (nice cafe! I like this place!), on the day just a year passed from Mozilla 1.0 release.
Attendees: Erwan, Gashu, Fakhar, kazhik, Ryuzi Kambe, yukichi
Below are the things we talked about, which I can remember:
- XUL is a simple programming language. It potentially gives more oppotunity of creating software to people who usually do not code.
- Its limitation depends on JavaScript. Due to JavaScript is a script language, does not have rich libraries, so it’s not that much powerful like Perl or Ruby.
- Translation interface of rikai.com, which uses Perl, is interesting.
- Nowadays, useful references of XUL, e.g. XUL Tutorials in XUL Planet are available, so It is not hard to understand what the XUL is, but following up version incompatibility is hard thing, and it can prevent continuous development for third party software.
- Erwan is considering MOJI code transplantation from Seamonkey to Mozilla Firebird.
- Gashu has started updating Lo-Fi theme for Mozilla Firebird 0.6 in slow pace. It will be out without some toolbar icons for first release.
- Mozilla 1.0 used to be expected that Mozilla’s API would be fixed till 2.0, but it is still changing.
- To start XUL programing, creating extentions for Mozilla is best way to learn.
- Komodo IDE uses whole Mozilla 0.9.5 as its XUL rumtime environment.
- Composer++ rocks as a standalone XUL product.
- Is GRE + XUL Toolkit XRE?
- AOL and Microsoft thing might effect hardware/network resource of mozilla.org. Now it seems to be in AOL network but it might be going to move to other place with less bandwidth. If situation goes like that, every regional community site should recommend using mirrors.
- Potentially, P2P file sharing will help some.
- It is a good idea to imprement XHTML Ruby support to Wazilla, and the patch is already available.
- Wazilla‘s purpose is gathering feedback for patches so imprementing XHTML Ruby support to improve usability is out of focus.
- i18n patches proposed from Bugzilla-jp to bmo are often ignored.
- It maybe because there are few resource for qualifying i18n patch.
- Using UTF-8 as software charset can widen range of usability of software itself. Especially Japanese codeset, it has three – SHIFT-JIS, EUC-JP and ISO-2022-JP – it’s too much.
- Some people bothering UTF-8. It is said that some people are feeling cultural violation to UTF-8.
- English to Japanese translation resource of Mozilla is great.
- Japanese to English translation resource is very few. That is one of the big problem of Opensource software (in every project).
- Why here’s no girl? This is a critical problem. How can we make girls like Mozilla?
- Change Lizard to something pretty like Hello Kitty, or make Ayumi Hamasaki say she likes to use Mozilla.
- yukichi has succeeded three girls to use Mozilla. More expected.
- Ryuzi Kambe likes to collect image files (of blue oceans).
- The Soft Revolution is cool.
Leave a Reply