RE: [maemo-developers] Maemo 2.0 API changes, signals andproperties (was: ANN: Eagle)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ext Shawn Gordon Sent: 19 April, 2006 19:15 To: maemo-developers@maemo.org Subject: Re: [maemo-developers] Maemo 2.0 API changes, signals andproperties (was: ANN: Eagle) I gotta say as a third party developer that the state of Maemo is rather frustrating, it seems like a far from done piece of work and a moving target. I've seen a lot of complaints on industry reviews of - First it is expected to be a moving target :) [improved features, bug fixes, runtime performance improvements etc ..] - Its strange to say Maemo ... far from done piece of work. What are your expectations??? IMHO Maemo 1.1 provides a solid start point. Its gives you capability to write, test, cross compile in a easy to use environment. Most of the developers have really appreciated the kind of plumbing less (if a word like that exist:) development environment. There are short commings, but I dont think developers with C/glib/gtk/sdl have any major issues. Community has been great at pro actively providing great support to who asked for it on developer mailing lists, and have produced so much sample code (sdl games, hildon apps, plugins etc), to make up for lot of still missing documentation. As for other things source code to almost everything is available (http://maemo.org/lxr/), browse it and you would know in most cases, what is going wrong. Most places, examples could be found together with source e.g http://maemo.org/lxr/source/maemo-examples/ I agree it all can be better organized (and we working on it), as for API breaks, Maemo almost all is built on top of open source projects (hildon/hildon desktop/haf included), so we just need to be able to deal with it (API changes, reasonable effort is made not too), important thing is we are able to communicate them early on (again a work item) the device as well to the stability and selection of software included on the device. What's happening at Nokia to help with this and remove the perception that the device is a beta unit? As with all devices, you get some good reviews, some ok, and some bad. What is important is we are commited to delivering good quality products for our focused target segment. Devesh thanks, shawn At 08:52 AM 4/19/2006, you wrote: On Tue, 2006-04-18 at 08:51 -0300, ext Gustavo Sverzut Barbieri wrote: Hello, Eagle (http://www.gustavobarbieri.com.br/eagle/) was ported to Maemo/Hildon (http://blog.gustavobarbieri.com.br/2006/04/eagle-in-maemo.html). In your blog you had mentioned this: However I opted to not port every component, like HildonColorButton or HildonNote because I think they're not well designed, they don't even provide signal changed, used by Eagle's DataWidget to persist data automatically. As API will change in Maemo 2.0, I won't bother with this until then. HildonColorButton and HildonNote APIs are not changing in any signifcant way, so don't let that stop you from including more widgets in the supported list. Hildon-related API changes are more or less limited to HildonApp and AppView and gtk_infoprint (and widgets no one was supposed to be using anyway) See http://maemo.org/maemowiki/HildonWidgets for a bit more details. HildonColorButton doesn't need a specific changed signal, it is already provided, though it's called notify::color and the callback signature is slightly strange (http://developer.gnome.org/doc/API/2.0/gobject/gobject-The-B ase-Object-Type.html#GObject-notify) (The older version of generated API documentation misses some crucial bits like signals and properties, the new API has slightly better generated documentation in https://stage.maemo.org/svn/maemo/projects/haf/doc/api/hildon-libs/HildonColorButton.html) It's a less known feature in GObjects that all properties have implicit changed signals associated with them. It has the benefit that you don't need multiple foo-changed, bar-changed, ... signals for complex objects. So the lack of extra signal is intentional and we plan to use the same design in new widgets as well, see HildonProgram for example. -- Tommi Komulainen[EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers Regards, Shawn Gordon President theKompany.com www.thekompany.com www.mindawn.com 949-713-3276 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Maemo 2.0 API changes, signals and properties
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ext Shawn Gordon Sent: 19 April, 2006 20:10 To: maemo-developers@maemo.org Subject: Re: [maemo-developers] Maemo 2.0 API changes, signals and properties At 10:03 AM 4/19/2006, Marius Vollmer wrote: ext Shawn Gordon [EMAIL PROTECTED] writes: What's happening at Nokia to help with this and remove the perception that the device is a beta unit? We are hanging around on mailing lists and browse blogs, waiting for someone to tell us what to do. ;-) I'm engaged in private conversations with 2 people at Nokia involved with the 770 about our issues and they agree with everything, but we're still waiting for something to happen. My concern is that these conversations have been going for 5 months now with no visible progress. There could be progress behind the scenes, but I'm not privvy to it, so I'm expressing my frustration here. The other frustration is that we have a number of applications on other devices that we'd port to the 770 except that Nokia has given the impression that these are coming any time now, so we haven't done it, but the apps haven't shown up either. I think the device is really nice, but maemo itself just seems far from complete and it gives the whole experience a beta feel. Not to It will really help me if you please send a list, where you think we need to improve (please dont say we need to move to QT :) e.g API (functionality) missing in Maemo which is there in Qtopia Devesh dredge up the whole decision of what to use on the device again, but Qtopia would have been a lot less of a hassle. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers Regards, Shawn Gordon President theKompany.com www.thekompany.com www.mindawn.com 949-713-3276 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Too busy to accept help? I'm not complaining
On ons, 2006-04-19 at 13:06 -0700, ext Shawn Gordon wrote: [snip] faster because it is done, has been used, refined, debugged and developed for for years, so other than device drivers in the kernel it wouldn't have taken hardly any time at all to get it up and running. cheaper - I'm assuming cheaper based on what I know of the licensing costs and the costs to hire a bunch of developers for years to develop and support the software. Nokia is not going to just rely on the open source community for something that they depend on, they will certainly have their own developers and these are going to be far more expensive than simply paying a small per unit license cost (I'm talking ones of dollars per unit). Just using plain Qtopia wouldn't have been an option, just as using plain GTK+ without Hildon wasn't an option; we had to use a UI that looks somewhat like Nokia's earlier products, without forking too wildly. So the work effort would've been the same either way; the difference being that Qtopia would've incurred the added penalties of a licensing cost, C++, and of course the extra legal issues surrounding the fact that Qtopia is GPL, not LGPL. The Nokia legal process is not a smoothly operating machine, it's more akin to the Spanish inquisition... [snip] The world is only black and white if you filter out the greys by deliberately ignoring to see some things and are not privy to other things. Regards: David ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Too busy to accept help? I'm not complaining
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ext Shawn Gordon Sent: 19 April, 2006 23:06 To: maemo-developers@maemo.org Subject: Re: [maemo-developers] Too busy to accept help? I'm not complaining At 12:23 PM 4/19/2006, Philippe De Swert wrote: Hello Shawn, On Wed, 2006-04-19 at 11:59 -0700, Shawn Gordon wrote: I've already got Nils slamming me privately because I dared to mention Qtopia, but let me provide some perspective as a company who was very successful with Qtopia and the Sharp Zaurus and what Sharp and Trolltech did both right and wrong that Nokia could learn from (I don't care if they use Qtopia at this stage, I just honestly think it would have been faster and cheaper than going the route they did, but I am not privy to the information that went in to making that decision). Why would Qtopia be faster and cheaper? faster because it is done, has been used, refined, debugged and developed for for years, so other than device drivers in the kernel it wouldn't have taken hardly any time at all to get it up and running. no offense, it always look simpler from the other side. Developing and bringing a product to market (in all my experience) is no simple task combine that with new challenges working with open source, and OS communities, new processes and at the same time building a truely open product. I am not saying we havnt and we will not make mistakes (maybe we will), but we are ready to listen and willing to learn. And as i see right now, I am ready to take small baby steps and disappoint few than going grand. There is a natural order of things, and lot what you suggested would/may happen but lets take patience as a virtue. As your rightly said, its about expectation management :) cheers Devesh cheaper - I'm assuming cheaper based on what I know of the licensing costs and the costs to hire a bunch of developers for years to develop and support the software. Nokia is not going to just rely on the open source community for something that they depend on, they will certainly have their own developers and these are going to be far more expensive than simply paying a small per unit license cost (I'm talking ones of dollars per unit). I am not trying to troll here but both have wide support in the Free Software community. (However in the embedded space GTK might have an edge. GPE is atm better supported and has more active developers than Opie for example. And I am not stating that because I happen to be involved with GPE, but because both Opie and GPe are involved with familiar we know about each other projects and we even co-operate on certain parts.) Keep in mind that Opie is simply a fork of the GPL version of Qtopia, so they get the advantage of all the things I spelled out above. Now by the time the Zaurus was commercially available, my company already had a dozen products running on it, maybe more, and there was a big and healthy open source movement that was also producing software, I don't remember how many apps, but it was a good amount and grew very rapidly. Well Nokia might not have had applictions readily available before the product was released. But I do remember porting an app in the maemo SDK before the device was actually available What was done right: 1.Sharp actually located about 50 companies and individual developers 2.They worked with Handango to create a web site where commercial and 3.Trolltech hired a liaison to work directly with the embedded community and keep the line of communication open. Ok. That indeed are valid points that could contribute to success with an open project. However *again* I see no reason why Qtopia would have been an advantage. In it's own right I believe the technical choice GTK vs QT(opia) has nothing to do with the success of these projects. As you point out political choices are much more important. Nokia has supported Gnome and has hired professional companies to support them as can be seen in Ari Jaaksi's presentation from Boston see (slide 7): http://www.kotiposti.net/jaaksi/ME9_LinuxWorld_2006_AriJaaksi_.pdf . So the one thing they really need to do is having somebody that can put time in co-ordinating the community and pass on all interesting developments to the people in Nokia who take the decisions. This last part has not yet been done. And if they manage to pick up the good things from the community it will become a killer product. So they definitely need to work on point 3. Apart from that the used toolkit point is completely moot. The 770 would probabely be as good/bad as it is now regardless of GTK or QT. I'm not espousing the benefits of one technology over another here, I'm simply making the point of how the business was and was not well handled in my opinion. Regards, Philippe -- |
RE: [maemo-developers] Too busy to accept help?]
Original Message Subject: [maemo-developers] Too busy to accept help? Date: Wed, 19 Apr 2006 13:14:13 +0200 From: ext Murray Cumming [EMAIL PROTECTED] To: maemo-developers@maemo.org The Maemo community is alive, but not thriving as much as it could. This is because the Nokia developers are so busy and are often unable to respond to the simplest of requests for changes or information, and often unable to even acknowledge that contributions have been accepted. I agree. but sometimes, I believe also community cannot be pushed too hard either, things just take time (simple example is if something itches, you step in to solve :) It's OK to be busy, so this isn't a personal attack on those developers. It's a suggestion for how to take the weight off them. I think Nokia needs to assign a dedicated community liaison, full time or part time, while still demanding that all developers are involved with the community as much as possible. This person would maintain the web site, and help the community to maintain it by extracting information from Nokia. This person would also do simple patch and bug triage and apply obvious changes without bothering the developers with trivial stuff. I rather turn this other way to identify clear problems today and expectations e.g (here is my list), feel free to add 1. Responsive discussion on mailing list (this should decrease, as Maemo matures, and more things get documented) - so patience advised [Thing community can do for us] : Create a Wiki page with concrete How-To's needed. Remember so many things are discussed on mailing dev list, which are asked again and again. Also it is easier to update things at one place, when things change 2. clear forums for feature/enhancements discussion 3. more transparency from Nokia about Maemo roadmap (with ability for community to be involved) 4. responsive bugzilla [this should now start to work :) 5. ability for community to be involved with bleeding edge Maemo, to contribue and experiment baby step [http://maemo.org/pipermail/maemo-developers/2006-April/003550.html] 6. ability for community to contribute and share Maemo applications 7. Clear process from each project (in Murrays case HAF) - how they accept contributions (e.g access rights, patches, feature enhancements) I still see a lot of value in Murrays proposal, and as Carlos pointed out :) there are hiring announcements :). Devesh It must be politically acceptable for this person to be under less pressure than a regular developer. If the community liaison ever has no problems to solve then that's good. If you need a more traditional job title, you could squeeze these responsibilities into Documentation or Q A. Nokia will get a lot of the advantages of open source if they don't do this, and the community will survive if they don't do this, but I think the extra salary would be a good investment to get even more valuable advantages. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Too busy to accept help? I'm not complaining
Weinehall David (Nokia-M/Tampere) wrote: [snip] Just using plain Qtopia wouldn't have been an option, just as using plain GTK+ without Hildon wasn't an option; we had to use a UI that looks somewhat like Nokia's earlier products, without forking too wildly. So the work effort would've been the same either way; the difference being that Qtopia would've incurred the added penalties of a licensing cost, C++, and of course the extra legal issues surrounding the fact that Qtopia is GPL, not LGPL. The Nokia legal Correction. Qtopia is dual licensed, commercial and GPL. GPL of course has no licensing cost. The only legal difference of GPL and LGPL is that GPL insures derived sources remain open. -- Lorn 'ljp' Potter Trolltech Qtopia Community Manager Opie Core Developer http://qtopia.net ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] MaemoDict deb file
Thanks Kasper!!This is a very usefull tool. I will send you my feedbackOn 4/19/06, Kasper Souren [EMAIL PROTECTED] wrote:I created a Debian package for MaemoDict. To use it you also need to put some dicts somewhere. You can install Debian's dict-* packages or manually put the .dict.dz and index files in /media/mmc1/MaemoDict or /home/user/MyDocs/.documents/MaemoDict The package: http://www.sia.huaral.org/download/maemodict-0.1.7.0.deb More information at http://www.industree.org/guaka/wiki/MaemoDict ___maemo-developers mailing listmaemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- Pedro A.Linux User: #199452 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Too busy to accept help? I'm not complaining
On 4/20/06, Lorn Potter [EMAIL PROTECTED] wrote: Weinehall David (Nokia-M/Tampere) wrote: [snip] Just using plain Qtopia wouldn't have been an option, just as using plain GTK+ without Hildon wasn't an option; we had to use a UI that looks somewhat like Nokia's earlier products, without forking too wildly. So the work effort would've been the same either way; the difference being that Qtopia would've incurred the added penalties of a licensing cost, C++, and of course the extra legal issues surrounding the fact that Qtopia is GPL, not LGPL. The Nokia legal Correction. Qtopia is dual licensed, commercial and GPL. GPL of course has no licensing cost. I remember seeing (but cannot confirm right now) a statement that some modules were not allowed to be used on GPL when I compiled the opensource version of Qtopia last night. So I guess to really have that edge whith all the readily available thingies that were mentioned one must pay the fee anyway? The only legal difference of GPL and LGPL is that GPL insures derived sources remain open. No. Sources will always remain open with LGPL too. It's the combining and linking with non-free (in fact, any) licensed work that LGPL allows (and GPL doesn't). -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Too busy to accept help? I'm not complaining
ext [EMAIL PROTECTED] [EMAIL PROTECTED] writes: And as i see right now, I am ready to take small baby steps [...] First baby-step for you, Devesh: use a real mail program and not one that corrupts your From: header... :-) (From what I have heard, these annoying [EMAIL PROTECTED] addresses are due to some Outlook or Exchange mis-feature that tries to clean outgoing mail addresses.) ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: [maemo-users] New Nokia 770 software image available
Will changelogs be provided later? (Not to threadjack this into the other conversation, but this is a great example of where nokia can better their interaction with the community in a fairly easy way. Even if some parts have to be left out or summarized as Browser stability, most of the changelogs should be safe enough.) On Thu, 20 Apr 2006, team maemo did have cause to say: Greetings! A new Nokia 770 software image -2005 Software Edition- is available from http://www.maemo.org/downloads/nokia_770?f=Nokia_770_SE2005_5_2006_13_7.bin The version is 5.2006.13-7. Changelogs are not available. Regards, maemo team ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users !DSPAM:4447894446765593019564! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] New Nokia 770 software image available
Greetings! A new Nokia 770 software image -2005 Software Edition- is available from http://www.maemo.org/downloads/nokia_770?f=Nokia_770_SE2005_5_2006_13_7.bin The version is 5.2006.13-7. Changelogs are not available. Regards, maemo team ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bug with GtkCellRendererToggle?
Hi, On Wed, 2006-04-19 at 22:00 -0300, Gustavo Sverzut Barbieri wrote: On 4/19/06, Jan Arne Petersen [EMAIL PROTECTED] wrote: Disable checkbox-mode: g_object_set(G_OBJECT(tree_view), allow-checkbox-mode, FALSE, NULL); No it doesn't help and I have an example code to demonstrate it, see attached file. It fixed the problem here. I tried it with the modified example (attached). From that code, Gaim and my library, it seems that _FIRST_ append'ed column that have a GtkCellRendererToogle fails, others works as expected. That is the maemo checkbox-mode: The first checkbox in a row is active if and only if the row is selected. Regards Jan Arne Petersen #!/usr/bin/env python2.4 import gtk import gobject app = gtk.Window() c1 = gtk.TreeViewColumn( text, gtk.CellRendererText(), text=0 ) c2 = gtk.TreeViewColumn( b1, gtk.CellRendererToggle(), active=1 ) c3 = gtk.TreeViewColumn( b2, gtk.CellRendererToggle(), active=2 ) c4 = gtk.TreeViewColumn( b3, gtk.CellRendererToggle(), active=1 ) # use 1 again! m = gtk.ListStore( gobject.TYPE_STRING, gobject.TYPE_BOOLEAN, gobject.TYPE_BOOLEAN ) m.append( [ 'True', True, True ] ) m.append( [ 'False', False, False ] ) t = gtk.TreeView( m ) t.set_property ( 'allow-checkbox-mode', False ) t.set_headers_visible( True ) t.append_column( c1 ) t.append_column( c2 ) t.append_column( c3 ) t.append_column( c4 ) app.add( t ) app.show_all() app.connect( delete-event, gtk.main_quit ) gtk.main() ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: Memory card corrupted or unformatted
Later I found the format thing in the File manager's menu. I didn't expect it to be there. I guess it'd be nice to also add it to the context menu of the memory card. Or simply ask the question Do you want to format the memory card now?, after the first time the device finds out the card is unformatted or corrupted. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] New Nokia 770 software image available
Disconnect wrote: Will changelogs be provided later? (Not to threadjack this into the other conversation, but this is a great example of where nokia can better their interaction with the community in a fairly easy way. Even if some parts have to be left out or summarized as Browser stability, most of the changelogs should be safe enough.) http://maemo.org/pipermail/maemo-developers/2006-April/003639.html Might be a fix for this problem? ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] New Nokia 770 software image available
On Thu, 20 Apr 2006, Siarhei Siamashka did have cause to say: Disconnect wrote: Will changelogs be provided later? (Not to threadjack this into the other conversation, but this is a great example of where nokia can better their interaction with the community in a fairly easy way. Even if some parts have to be left out or summarized as Browser stability, most of the changelogs should be safe enough.) http://maemo.org/pipermail/maemo-developers/2006-April/003639.html Might be a fix for this problem? Might be a whole lot of things... thats the point.. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] New Nokia 770 software image available
Early reports have found the following: 1. Opera Browser - can load large sites without using swap file workaround 2. PDF reader - faster in opening pdf files (e.g. 40 seconds to 3 seconds) 3. Sound prompt when inserting/removing into/from case - some have found this a bit annoying The discussion can be found here: http://www.internettablettalk.com/forums/showthread.php?t=1840 On Thu, 20 Apr 2006 18:22:52 +0200, Detlef Schmicker [EMAIL PROTECTED] wrote: On Thu, 20 Apr 2006, Siarhei Siamashka did have cause to say: It is not a fix for: [Bug 329] WIFI connection drops intermittently In case anybody hoped so. Detlef Schmicker Disconnect wrote: Will changelogs be provided later? (Not to threadjack this into the other conversation, but this is a great example of where nokia can better their interaction with the community in a fairly easy way. Even if some parts have to be left out or summarized as Browser stability, most of the changelogs should be safe enough.) http://maemo.org/pipermail/maemo-developers/2006-April/003639.html Might be a fix for this problem? Might be a whole lot of things... thats the point.. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- Detlef Schmicker [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] New Nokia 770 software image available
Sup, I just tried it, i have the newest OS and only x chat + x terminal installed. And i found that they have turned everything that logs anything off. There isn't any log files in /var/log/. So at least wtmp file growing has been handled. Cheers, Forge -- Siarhei Siamashka wrote: Disconnect wrote: Will changelogs be provided later? (Not to threadjack this into the other conversation, but this is a great example of where nokia can better their interaction with the community in a fairly easy way. Even if some parts have to be left out or summarized as Browser stability, most of the changelogs should be safe enough.) http://maemo.org/pipermail/maemo-developers/2006-April/003639.html Might be a fix for this problem? ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Too busy to accept help? I'm not complaining
Jussi Pakkanen wrote: --- Lorn Potter [EMAIL PROTECTED] wrote: Correction. Qtopia is dual licensed, commercial and GPL. GPL of course has no licensing cost. The only legal difference of GPL and LGPL is that GPL insures derived sources remain open. There is also the problem of free software that is GPL-incompatible (MAME etc). They can't link against GPL libraries, nor will anyone buy a commercial license for them. Which means you are pretty much screwed. No, this just means that MAME is screwed. MAME has it's own legal problems, so I really doubt any company would take the chance on delivering that on a device. -- Lorn 'ljp' Potter Trolltech Qtopia Community Manager Opie Core Developer http://qtopia.net ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] some packages
After finding out how to make packages I created some more today, forGNU Screen, bzip2 and ar (for making packages on the N770 itself)Available here: http://www.sia.huaral.org/download/Comments welcome... ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Too busy to accept help? I'm not complaining
On 4/20/06, Lorn Potter [EMAIL PROTECTED] wrote: Kalle Vahlman wrote: The only legal difference of GPL and LGPL is that GPL insures derived sources remain open. No. Sources will always remain open with LGPL too. It's the combining and linking with non-free (in fact, any) licensed work that LGPL allows (and GPL doesn't). Which means sources are not open (those that are non free that are allowed to link to LGPL), which was my point. Sources _derived_ from LGPL code will be, which was the fault in your statement. Sources _combined_ with LGPL need not be, naturally. -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
