Re: GTK widgets in C# was: Re: WSJ
Alle mercoledì 28 novembre 2007, Scott Cytacki ha scritto: Torello Querci wrote: If you're interested in supporting Mono on the OLPC, I can create a wiki where I'll put the code I've already written, because at this time I'm working alone. I am interested in supporting Mono on the OLPC. One thing I've wanted to try is running all of Sugar with IronPython. This ought to give C#, Java (through IKVM), and any other mono language: http://www.mono-project.com/Languages full access to the Sugar widgets and APIs. I don't have time to try this now, but when I or someone else does, it would be helpful to know what is necessary to run Mono. Scott Hi Scott, unfortunately, there are a few problems running existing Python code with IronPython because the glue level between Python and C library is managed in a different way. Python requires a specific C library to handle native calls, while IronPython uses PInvoke to do this. I'm now trying to implement a class library to run any mono program on Sugar, but being compatible with Python class libraries is not a priority at this time. Best Regards, Torello Querci ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: GTK widgets in C# was: Re: WSJ
Alle giovedì 29 novembre 2007, Chad Z. Hower aka Kudzu ha scritto: Im already working on this. Im working on it in a way though to run more effficiently than running as a normal JIT and instead working on a compiler of IL that can use the mono libs. We already have quite a bit working. Sorry Chad, I don't understand what you're doing. Is it like the AOT (Ahead Of Time compiler)? If so, I know that this function works in the mono compiler. I never use it because, when you use the AOT option to compile a program, the metadata are stored the usual way, but the native code for all the functions is also included in the final binary, so the size grows. Ok, you can save the startup time the JIT compiler, but it is generally fast and called only once per each method, do I don't know how much performance improvement you get. Best Regards Torello Querci - Original Message - From: Scott Cytacki [EMAIL PROTECTED] To: Torello Querci [EMAIL PROTECTED] Cc: devel@lists.laptop.org Sent: Wednesday, November 28, 2007 10:33 PM Subject: Re: GTK widgets in C# was: Re: WSJ Torello Querci wrote: If you're interested in supporting Mono on the OLPC, I can create a wiki where I'll put the code I've already written, because at this time I'm working alone. I am interested in supporting Mono on the OLPC. One thing I've wanted to try is running all of Sugar with IronPython. This ought to give C#, Java (through IKVM), and any other mono language: http://www.mono-project.com/Languages full access to the Sugar widgets and APIs. I don't have time to try this now, but when I or someone else does, it would be helpful to know what is necessary to run Mono. Scott ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
change gettext language?
hey! i'm working on the imagequiz, and have the following issue: * strings in the activity are translated via gettext * the questions themself are translated inside the database (it grows by submitted content) if a user chooses another language, i'd need to change the language gettext is working with. how can i do that? thanks, chris ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Banner for Kathmandu game jam
Here is the banner Om created for our upcoming mini game jam http://nepal.ole.org/home/sites/default/files/game_jam_flex.jpg Om did a fantastic job w/ this banner. In a couple days or less I will post the new user interface he created for our learning activities. As I told Om, Luke, and Ram today, it is such a pleasure working w/ people more talented than myself. In other news, I spoke with several individuals very keenly interested in developing educational games and graphics. Let's see what works out. The best thing about OLE Nepal is working with an extremely talented group of people. And as a corrollary, it is a pleasure to work w/ the extremely talented people involved in OLPC. We are hoping to have one mini-game jam per month for the next 12 months or so, culminating in a large scale game jam within the next several months. Our goal is to create a community of individuals iteratively involved in creating new activities and improving existing ones. -- Bryan W. Berry External Relations Manager OLE Nepal, http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Banner for Kathmandu game jam
Here is the banner Om created for our upcoming mini game jam http://nepal.ole.org/home/sites/default/files/game_jam_flex.jpg Om did a fantastic job w/ this banner. In a couple days or less I will post the new user interface he created for our learning activities. As I told Om, Luke, and Ram today, it is such a pleasure working w/ people more talented than myself. In other news, I spoke with several individuals very keenly interested in developing educational games and graphics. Let's see what works out. The best thing about OLE Nepal is working with an extremely talented group of people. And as a corrollary, it is a pleasure to work w/ the extremely talented people involved in OLPC. We are hoping to have one mini-game jam per month for the next 12 months or so, culminating in a large scale game jam within the next several months. Our goal is to create a community of individuals iteratively involved in creating new activities and improving existing ones. -- Bryan W. Berry External Relations Manager OLE Nepal, http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Wiki down
On Dec 2, 2007 8:35 PM, Edward Cherlin [EMAIL PROTECTED] wrote: Does anybody know why the Wiki is malfunctioning? OLPC has a problem Fatal error: Call to a member function selectRow() on a non-object in /var/www/wiki.laptop.org/includes/User.php on line 752 I believe we were slashdotted (we were at least groklaw'ed) yesterday. I'll leave it for the actual sysadmins to describe how that caused us to fail and why it won't happen again. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Signed 648 (ship.2 release candidate)
Hello, I don't know the plan of any sort, but presumably there will be the users of XO through G1G1 in the US and Canada (and other places) very soon. Is there any a jabber server (say) for them, or a forum, mailing lists of sort that they are going to be directed? Would a developer with B4 be able to look at it or participate it and see how software working for them (and possibly trouble shoot)? -- Yoshiki At Sat, 1 Dec 2007 13:47:58 -0500, Kim Quirk wrote: [1.1 text/plain; ISO-8859-1 (7bit)] [1.2 text/html; ISO-8859-1 (7bit)] Yes! If you have a 'secure' machine running 649 (ship2 release) you will be able to open the browser; click on other on the left hand side, then on about your xo. This will bring you to a tour of the laptop. Scroll all the way to the bottom to find the link apply for a developer key. We just got the link in there at the last minute, so it might move to a more prominent position in the future. Regards, Kim On Dec 1, 2007 1:39 PM, Gerard J. Cerchio [EMAIL PROTECTED] wrote: Alexander M. Latham wrote: --- Yoshiki Ohshima wrote: Great! but sorry for my ignorance but what a signed copy means? Shall we test it on our (B4) laptops? Or it'll make it hard for future update? http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2/build648/devel_jffs2/ is the same thing but unsigned? -- Yoshiki --- end of quote --- Signed means that it will work on a write protected machine. If you're laptop is not write protected, the unsigned version will work exactly the same. - AlexL ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel Is it going to be possible to unlock a G1G1 for development? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project Hosting request
1. Project name : Boggle
2. Existing website, if any : http://rpiolpc.blogspot.com
3. One-line description : A Simple boggle game
4. Longer description : A simple boggle game to increase student word
: knowledge and spelling ability. Will have
ability to
: easily swap in new dictionaries with varying word
: difficulties and languages.
5. URLs of similar projects : N/A?
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 tamoneya Andrew Tamoney [EMAIL
PROTECTED]
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Notes/comments:
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Project Hosting request (Key attached)
Andrew Tamoney wrote:
1. Project name : Boggle
2. Existing website, if any : http://rpiolpc.blogspot.com
3. One-line description : A Simple boggle game
4. Longer description : A simple boggle game to increase student
word
: knowledge and spelling ability. Will
have ability to
: easily swap in new dictionaries with
varying word: difficulties and languages.
5. URLs of similar projects : N/A?
6. Committer list Please list the maintainer (lead developer) as the
first entry. Only list developers who need to be given accounts so
that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URL
E-mail
-
--
#1 tamoneyaAndrew Tamoneyattached
[EMAIL PROTECTED]
If any developers don't have their SSH2 keys on the web, please
attach them to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to
the project's git tree. This is the standard model that will be
familiar to CVS and Subversion users, and that tends to work
well for most projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look
at one
or more of these trees, and merge changes into the
maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on
code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit
directly, as might be the case with a discussion tree, or a tree
for an individual feature, you may send us such a request by e-mail,
and we will set up the tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume
of messages related to your project reaches some critical mass, we
can trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more
lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to
the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created
for commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers
unless there's a demonstrated need. If you have one, please explain
here, and
list the usernames of the committers above needing shell access.
11. Notes/comments:
BEGIN SSH2 PUBLIC KEY
Comment: rsa-key-20071204
B3NzaC1yc2EBJQAAAIEAiS9OBT8n9TxbPKhdfU3dxy5SA2yloPstxCO2
qSIN/zsXfSjGvW6ZMxtZdMoiL81mshfxfaM5vFwiuE1mCRtOQeKLmnlieTMg4+aw
X1Zp1mqdlZwBW6mpO/8SLME+BWKvMu2TTRwwcC7q3et/htcvc93CAlNI2+pOHqVC
XiuOnrU=
END SSH2 PUBLIC KEY
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: clean installation of 643.
The autoinstaller is not working properly. This is a known problem, but given that the preferred method of upgrade is now over the network, it has not been a priority. To install the firmware from a USB stick using OFW: flash path_to_file where path_to_file is usually something like u:q2d05.rom You can use: dir u: to list the contents of the USB stick. To install a build from a USB stick using OFW: copy-nand path_to_file This will overwrite all data on the laptop. Make sure to backup anything you want to keep! wad On Nov 28, 2007, at 12:31 PM, Yoshiki Ohshima wrote: Alex, In the future, if you're only updating the ofw, you should just get to the ok prompt and type: ok flash path_to_file Yes, I know that, but it is not a good way to check if there is a bug or not^^; Also, after the firmware is upgraded, it reboots the machine, which would then lead the machine into trying to do an upgrade instead of a clean install if you don't hold the square key. That is probably why it created a backup and tried to restore from it. This means there may be some issues with the auto-reinstallation process, which should be looked into. Yes, that explains. Thank you! -- Yoshiki ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Project Hosting request
Nice. The world's greatest word game. You might consider a handicap
system where players can be restricted from playing short or common
words.
And of course in digital boggle one isn't limiited to 6-sided cubes...
SJ
On Dec 4, 2007 12:31 AM, Andrew Tamoney [EMAIL PROTECTED] wrote:
1. Project name : Boggle
2. Existing website, if any : http://rpiolpc.blogspot.com
3. One-line description : A Simple boggle game
4. Longer description : A simple boggle game to increase student word
: knowledge and spelling ability. Will have
ability to
: easily swap in new dictionaries with varying
word
: difficulties and languages.
5. URLs of similar projects : N/A?
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
non-committer developers.
Username Full name SSH2 key URLE-mail
- --
#1 tamoneya Andrew Tamoney
[EMAIL PROTECTED]
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[X] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most
projects.
[ ] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
main tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a discussion tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named __
[X] No
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
later.
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to the list
we chose to create above
[ ] A separate mailing list, projectname-git, should be created for
commit
notifications
[X] No commit notifications, please
10. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
11. Notes/comments:
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
