=== sunshine_ [i=chatzill@nat/intel/x-1c59cb00c31833c7] has joined #ubuntu-mobile === Charliefjohnson [i=cfj@nat/intel/x-e53b68bda93d9cc5] has joined #ubuntu-mobile === alek_laptop_ [i=chatzill@nat/intel/x-fe79c58b0fbb32b7] has joined #ubuntu-mobile === bfiller [n=bfiller@pool-72-74-234-2.bstnma.fios.verizon.net] has joined #ubuntu-mobile === rustyl [n=rusty@c-76-27-226-169.hsd1.or.comcast.net] has joined #ubuntu-mobile === bfiller [n=bfiller@pool-72-74-234-2.bstnma.fios.verizon.net] has joined #ubuntu-mobile === Jack_ [i=chatzill@nat/intel/x-d3f8446b07898125] has joined #ubuntu-mobile === LordlLnux [n=lordlinu@adsl-225-233.tricom.net] has joined #ubuntu-mobile === LordlLnux [n=lordlinu@adsl-225-233.tricom.net] has left #ubuntu-mobile ["Leaving"] === horaceli [i=hli23@nat/intel/x-498e04c739942d18] has joined #ubuntu-mobile === matt_c [n=mcroydon@137.147.45.66.cm.sunflower.com] has joined #ubuntu-mobile === HappyCamp_laptop [n=chatzill@63.116.149.163] has joined #ubuntu-mobile === javamaniac [n=gerardo@pwnd.gerardo.com.ve] has joined #ubuntu-mobile === px [n=px@unaffiliated/px] has joined #ubuntu-mobile === matt_c [n=mcroydon@137.147.45.66.cm.sunflower.com] has joined #ubuntu-mobile === TheJoeDotCom [n=Joe@ip68-108-123-29.lv.lv.cox.net] has joined #ubuntu-mobile === Lure_ [n=lure@89-212-18-142.dynamic.dsl.t-2.net] has joined #ubuntu-mobile === bobux [i=bspencer@nat/intel/x-17427246ba5051c7] has joined #ubuntu-mobile === Peter_u3 [i=PeterZhu@nat/intel/x-af2a8fdbd907451a] has joined #ubuntu-mobile === horaceli [i=hli23@nat/intel/x-5db679058cf1dd46] has joined #ubuntu-mobile === DannyZ [i=chatzill@nat/intel/x-e85677ca70f3f102] has joined #ubuntu-mobile === Jack_ [i=chatzill@nat/intel/x-a6213e9241113329] has joined #ubuntu-mobile === cwong1 [i=chatzill@nat/intel/x-bc1dff8e6672a905] has joined #ubuntu-mobile === sabotage_afk [i=sabotage@nat/intel/x-977ff79d80ecbb26] has joined #ubuntu-mobile === guardian [n=Guardian@mar44-1-87-90-32-28.dsl.club-internet.fr] has joined #ubuntu-mobile === ketrox [n=ketrox@Xbc9a.x.pppool.de] has joined #ubuntu-mobile === jgm [n=jgm@host-87-74-179-156.bulldogdsl.com] has joined #ubuntu-mobile === asac_ [n=asac@debian/developer/asac] has joined #ubuntu-mobile === seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-mobile === root__ [n=ketrox@X8139.x.pppool.de] has joined #ubuntu-mobile === guardian_ [n=Guardian@mar44-1-87-90-32-28.dsl.club-internet.fr] has joined #ubuntu-mobile === kwwii_ [n=kwwii@khepri.openbios.org] has joined #ubuntu-mobile === Starting logfile irclogs/ubuntu-mobile.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #ubuntu-mobile === Topic for #ubuntu-mobile: http://wiki.ubuntu.com/MobileAndEmbedded | https://wiki.ubuntu.com/MobileAndEmbedded/FAQ === Topic (#ubuntu-mobile): set by mdz at Thu Aug 16 15:19:37 2007 [07:02] (bspencer_/#ubuntu-mobile) ok. I can chat about this offline [07:02] (rustyl_/#ubuntu-mobile) making each commit into a patch is not very useful [07:02] (rustyl_/#ubuntu-mobile) it would be eaiser to create one big patch and just split it up by hand [07:03] (Mithrandir/#ubuntu-mobile) bspencer_: unsure if we have answered your question well? [07:03] (rustyl_/#ubuntu-mobile) another option is to only check in patches into the debian/patches dir [07:04] rustyl_: yes, that sounds like what I'd like to do [07:04] I really despise keeping patches in revision control systems, but I know some people like it. [07:04] :) [07:04] the reality is that different projects deal with this in different ways [07:04] it is temporary and reminds us that these need to be removed soon [07:04] so it annoys us that they are there, and we ask about them all the time [07:04] and we know how our branch is different from upstream and can point to the changes at any time [07:05] the worse thing about this approach is when some of your developers don't understand the concept, and then go and directly edit the source files [07:06] rustyl_: Mithrandir I'll do what you suggest. if we don't want to draga round patch files, I'll keep track of the changes elsewhere and just commit to the trunk. [07:06] bspencer_: sounds good to me. [07:06] [TOPIC] App selection [07:06] New Topic: App selection [07:06] agoliveira: your item [07:06] Sure. === bspencer_ is now known as bspencer [07:07] We still have a few points we need to iron out regarding to applications. [07:07] For instance: RSS reader. Should we use a separate one or a browser or email plugin? [07:07] agoliveira: good Q [07:07] we will have online RSS readers [07:07] and there is even a menu item for it in the mozilla browser [07:08] but that means they have to open the browser to read it [07:08] I don't think we should start a discussion here as it would take forever so I suggest that you take a good hard look here https://wiki.ubuntu.com/MobileAndEmbedded/UserApplications and take this to the mailing list. [07:09] That's becasue RSS is just one point :) [07:09] agoliveira: ok. but a chat about it would be good (not now) [07:09] mailing list sometimes takes a long time to resolve for small points [07:09] We can make something specific, no problem. [07:09] agoliveira: which apps are the ones you are wondering about? [07:09] bspencer: Agree [07:10] A few point then... [07:10] - Remote desktop client. I can prepare rdesktop and vnc but a few questions we need to iron out like, should they have panning? Should they work fullscreen only? [07:10] - RSS reader - Needed to decide which one. [07:10] - Office document viewer - There's none we can use directly, we need to discuss if we are going to do something about it like the options I proposed on the doc or not. [07:10] - Games? Which ones exactly. [07:11] I have opinions about all those [07:11] which we can chat about after? [07:11] Cool :) And why they aren 't on the wiki page? ;) [07:11] Sure [07:11] unless Mithrandir is eager to chat now :) [07:11] after the meeting sounds like a plan to me. [07:12] we here in boston probably want a 30-minute break or so to catch lunch. [07:12] agoliveira: sorry about my not commenting on wiki. post the link here? [07:12] (after the meeting) [07:12] agoliveira: probably ready to eat too [07:12] bspencer: Sure https://wiki.ubuntu.com/MobileAndEmbedded/UserApplications [07:12] agoliveira: do you want to sync up in an hour ? [07:13] bspencer: No problem. [07:13] (around 11:30am PDT) ? [07:13] (10:15 am PDT now) [07:13] Deal [07:13] I have one agenda item about moblin.org vs ubuntu-mobile and patches and such, so let's do that, then end the meeting, unless anybody else has more stuff. [07:13] [TOPIC] moblin.org, ubuntu-mobile, patches and such. [07:13] New Topic: moblin.org, ubuntu-mobile, patches and such. [07:14] so, we're currently at a sprint where we ended up having a bunch of issues because hildon-desktop on moblin had added a plugin API which didn't exist in Ubuntu [07:14] it's quite crucial that we don't go about modifying upstream projects in a way that changes the public API. [07:15] that won't gain us friends, and we end up with crazy problems when mixing and matching seemingly-compatible components. [07:16] I'm taking this up here so everybody sees it, I think we've already talked through it and are in agreement to avoid doing it in the future. [07:16] Mithrandir: you want to make a note of that in the log? [07:16] [AGREED] don't change upstream APIs unless in coordination with upstream. [07:16] AGREED received: don't change upstream APIs unless in coordination with upstream. [07:16] is the issue that we changed the public API, or that there were changes on moblin that weren't found in UME and broke the build? [07:17] kind of both, I think [07:17] it broke at runtime, not at build. [07:17] because just not changing the public API won't help the build problem [07:17] the former is really the biggest problem, since the latter wouldn't have happened without the former. [07:18] it wasn't a build problem, it was a runtime problem where the "prev" button in the marquee would go down in flames with an unresolved symbol. [07:18] (there might have been other problems too, but in this case, that was the problem) [07:18] yeah. not good [07:18] if upstream has taken a patch to add an API, it's fine, even if it's not in a released version. [07:19] just so I'm clear, the moblin version of hildon-desktop is going away and it will only be hosted on launchpad. correct? [07:19] bfiller_: gone [07:19] there is no moblin version of hildon-desktop. [07:19] it's already gone. [07:20] thanks [07:20] hildon-desktop was only in moblin.org temporarily until we could get our patches upstream [07:20] bspencer: got it [07:20] but obviously we didn't get them there soon enough :) [07:20] anybody got any more agenda items, or can we adjourn? [07:21] adjourned, then. [07:21] #endmeeting [07:21] Meeting finished at 17:13. [07:21] woo [07:21] only 80 minutes or so. [07:21] lunch! [07:22] bspencer, rusty: want to talk about the flash stuff now? [07:22] I would if rustyl_ is still here [07:22] rustyl_, I have a question about SDIO [07:23] patm: what's the question? [07:23] i'm hear [07:23] we are having trouble with SD memory cards with the latest patches applied [07:23] our SDIO wifi card works but not SD cards [07:24] the mmc_core module seems to conflict [07:24] bfiller_, i'm reading the doc you sent out [07:24] bfiller_: I'm reading your doc [07:24] patm: how so? [07:25] ok, we can talk after you're done [07:25] bfiller_, have you seen how application starting works now? [07:25] the driver will not load unless we remove the mmc_core [07:25] patm: do you have both MMC and MSS installed at the same time? [07:25] rusty: yes I have. I realize it's slightly different [07:25] rusty: I did have a question about it though [07:26] bfiller_, i like the idea of not having flash hard coded with exec commands [07:26] patm: MSS is a replacement for the MMC stack that's in the kernel by default. it's an either or option [07:26] rusty: agree [07:26] ok [07:26] when we have just mss, sd cards do not work [07:26] rusty: looks like you are storing the index into the array in the flash movie [07:27] only problem we hit in our case is that the flash movie has hard coded apps [07:27] bfiller_, yeap.... then all the flash content needs to do is say 'start #3' [07:27] patm: our focus right now is NOT to on MSS -- we want to move to Pierre Ossman's new SDIO stack [07:27] bfiller_, all you need to do is remove the hard coded apps, and replace that with a set of desktop files that result in the same behavior [07:28] rob_moblin, RIght, I understand [07:28] rob_moblin, wondered if it was a known issue or something to do with our environment === mfrey [n=mfrey@fw.pepper.com] has joined #ubuntu-mobile [07:28] if the we don't use the addApp() to add the movie dynamcially to flash, how does the movie know what the corresponding index is? [07:29] bfiller_, the idea is that the flash content is adding the apps dynamically [07:30] patm: we've seen that some SD cards work and others don't [07:30] patm: we've also seen even with the MMC stack, some SD cards work and other don't [07:30] bfiller_, quick quesion... [07:30] rusty: I think that is a good idea. Just not exactly sure how to modify the customer's movie to do this. [07:30] rob_moblin, in that case let me do some further testing, thanx [07:31] bfiller_, are you guys stuck with a flash based UI... do you have the ability to choose a different technology? [07:31] rusty: for this particular customer, we're stuck with flash. They are insistent with using it [07:31] bfiller_, i am very conserned about battery usage [07:32] rusty: yes, we've raised that issue [07:32] patm: we were also thinking there might be a problem with the crown beach board w.r.t. to SD cards, but if you're seeing different results on your non-crown beach HW it could be a SW issue === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-mobile [07:32] bfiller_, unless we can somehow stop the flash content while it is not visible, then the adobe flash implementation will never let the cpu go idle for long enough to get any benifit from all the new cpu mobile technologies [07:33] rob_moblin, the customer reported this, but I have not tried recently, I will try their dev board now [07:33] rustyl_: we should get someone good at flash to push that theory [07:33] patm: ok [07:33] rusty: how do the desktop files in /usr/share/mobile-basic-flash/applications get installed there? [07:33] and make the most basic flash program and see if it isn't our flash [07:33] rustyl_: have you tried other flash programs that are static? [07:33] I was expecting the home plugin to read the desktop files out of /usr/share/applications [07:33] bfiller_, the idea is that an applicatino that wanted to be presented in the UI would add it's own desktop file to that location [07:34] bfiller_: we didn't want to change the default applications .desktop content. For example, we don't want to show Python, though there may be a .desktop file for it [07:34] in /usr/share/applications [07:34] rusty, bspencer: I understand [07:35] rustyl_, it needs to be a more standard folder not tied to the flash ui [07:35] I do think it would be nice to have it located in /etc/mobile-ui/applications (or a symlink or something) [07:35] and every UI would look there, regardless of whether it was written in flash or other === lenkawell [n=len@fw.pepper.com] has joined #ubuntu-mobile [07:35] but that's just brainstorming [07:35] bspencer, bfiller_ ...although, we could look for a new entry (like stuff under ['Hildon Home'] ) [07:35] right, I just installed some new apps that need to have their rules changed to work [07:36] maybe /usr/share/applications/mobile-ui [07:36] or mobile-home [07:36] rustyl_: so does the mobile-basic-flash deb package current install those dekstop files? [07:36] yes [07:37] the other problem we have is dictating order of the icons [07:37] we need to create an "application requirements list" [07:37] applications should include creation of this item. (yes, ordering is also an issue) [07:37] looks like you are using the numbered prefix for ordering [07:37] right now we just send down the array of apps as they desktop entries are found [07:38] btw, ordering may be changed by end user. Also, applications could be grouped into category. The design should accomodate these things. [07:38] right our customer has defined a grouping [07:38] bspencer: what are the number prefixes used for? [07:38] order [07:38] :-\ [07:39] that is the order they will be represented in the current UI, left-to-right [07:39] bspencer: that's what I thought [07:39] actually, it's the order of the index entryies, which the flash content translates into a left-to-right icon ordering [07:39] we could add a desktop entry for group [07:39] who can write up the requirements and a proposal? [07:40] rustyl_ and I will talk about it [07:40] and send out something [07:40] great [07:40] actually [07:40] or [07:40] i don't think that is the best way [07:40] since we have our existing flash content that works (for some degree of work)... [07:41] oh oh [07:41] what we need are requirements from other people trying to make the UI work for different flash content [07:41] like what is coming out here [07:41] I know our customer will require grouping of apps [07:41] can we list them here briefly (the ones we know) ? [07:41] so I think that is important [07:41] - req1) grouping [07:41] for example... what if you don't have a slider concept... how do you deal with that? [07:41] a non-flash home page? [07:42] - req2) ordering by customer [07:42] - req3) ordering by end-user [07:42] - req 4) non-flash UI home page accomodated [07:42] multiple themes? [07:42] rustyl_: yes, in that case the ordering can be ignored, but maybe grouping is used [07:42] rustyl_: (if there is no slider, for example) [07:43] patm: what do you mean? It should support theming? [07:43] rusty: back to the index thing. Could we use an invented applicationId as the key rather than an array index? [07:43] icon needs to play along with it [07:43] rusty: the appId could be stored in the desktop file [07:44] rusty: then the flash movie doesn't need to necessary support dynamically adding apps [07:44] patm: the location of the icons is another topic -- good point. Actually the theme will include: /usr/share/theme/ AND /usr/share/icons/ [07:45] bspencer, so the icons go to /usr/share/icons ? but they do not today? [07:45] patm: right [07:45] they do not today [07:45] (well, rustyl_ may have changed that) [07:45] nope [07:46] originally the icons were in /usr/share/mobile-basic-flash/icons [07:46] they should probably go in /usr/share/icons/ [07:46] kwwii: yes that is what I meant to say [07:46] sounds good [07:46] we just don't have a theme yet :) ( kwwii : btw, how does an application get the name of the current theme ? ) [07:47] via the environment [07:47] bspencer, rustyl_: be right back, have to run to caf. before it closes [07:47] rustyl_: from a matchbox-wm method ? [07:47] bfiller_: k [07:48] - req5) home UI uses current theme for icons and default background [07:49] - req6) user can change the default background using control-panel applet for configuring desktop (or a shortcut on the home screen UI which does the same) [07:49] i think i need to think on this a bit [07:49] bspencer: it is a system variable (probably) set in gtkrc [07:49] bspencer: once we have a test theme a lot of this will become much clearer I assume [07:50] I looked into using the theme-maker java app to create a theme but the template file is in a totally different order for that [07:50] so I gave up [07:50] kwwii: I was going to hack a little on hildon-theme-mobile-basic to add icons for a temporary thing, so we could pull them into the UI and get the UI home screen working right [07:51] bspencer: sounds good for the short-term [07:51] kwwii: yeah, still not a real theme [07:51] bspencer: I was going to update the pics for the top-bar as well...I'll probably be pinging you about that sometime soon [07:52] sounds good [07:52] bspencer: it seems that in the next few weeks we need to have something that looks halfway like we want it to show to people [07:52] I'm back [07:53] kwwii: agreed. === lenkawell [n=len@fw.pepper.com] has joined #ubuntu-mobile [07:54] bspencer, rustyl_: any comments about the events doc? === HappyCamp_laptop [n=chatzill@fw.pepper.com] has joined #ubuntu-mobile === smagoun [n=steve@scoville.pepper.com] has joined #ubuntu-mobile [07:55] bfiller_, so you have a set of predefined events [07:56] rustyl_: that's what we were thinking for this particular customer. Could be made more generic though. [07:56] bfiller_: how does the javascript send a dbus event? [07:57] bspencer: it doesn't [07:57] ok. I thought I was missing something [07:57] bspencer: home plugin gets a dbus event and calls a javascript function umeEvent() passing it the appropriate event [07:58] home plugin is what -- gtkmozembed ? [07:58] like now? [07:58] bspencer: yes [07:58] sorry -- I'm looking at ht epicture and trying to understand it [07:58] bspencer: the change would be the home plugin would listen for appropriate dbus signals and then forward to the flash movie [07:58] so do we need an xpcom interface for javascript--> C code --> dbus event ? [07:59] that is part of the gtkmozembed plugin ? [07:59] bspencer, what are you asking? [07:59] no need for a new xpcom interface [07:59] how does the flash send a dbus event [07:59] all the native work is done in our container [07:59] what are the steps [08:00] js just acts as a glue layer between the flash content and our container [08:00] bspencer: here is the flow 1) flash movie calls umeEnable() function which tells container to start listening for a predefined set of events 2) when container (plugin) gets events, it delivers them to flash movie via javascript call [08:01] ok. the container is the C code sending/receiving dbus events. So javascript is making an "exec" call ? [08:01] bspencer, if you look at the current code, you will see how we transfer data back and forth [08:01] flash movie can also ask for specific property via umeGetProperty() [08:01] look at the code? inconceivable. ok. === lenkawell [n=len@fw.pepper.com] has joined #ubuntu-mobile === Lure_ [n=lure@89-212-18-142.dynamic.dsl.t-2.net] has joined #ubuntu-mobile [08:02] bspencer: C code uses gtkmozembed to call a know javascript function in the flash_home.html page passing it the information about the event === smagoun_ [n=steve@fw.pepper.com] has joined #ubuntu-mobile === mawhalen_ [i=chatzill@nat/intel/x-f98df3f2babaa57e] has joined #ubuntu-mobile === mawhalen_ is now known as mawhalen === hfreanzr [n=hfreanzr@brx116.neoplus.adsl.tpnet.pl] has joined #ubuntu-mobile [08:12] bspencer, rustyl_: when I get more of the event interaction coded in the mobile-basic-flash-plugin I will send you diffs to take a look at [08:22] rustyl_: please don't use a different directory for the .desktop files, but rather use the OnlyShowIn/NotShowIn keys in the .desktop files already existing. [08:22] Mithrandir: sorry I missed the meeting earlier, were there any hot topics for me? [08:23] ToddBrandt_: we'd liked to have had a status update on the control panel applets, so if you'd want to post that to the list, that'd be good. [08:23] Mithrandir: will do [08:23] thanks [08:30] bspencer: I'm ready when you are. [08:32] agoliveira: hi [08:33] bspencer: Want to talk about the apps now or later? [08:33] now [08:33] Cool. [08:33] rss reader: [08:33] it would be nice to have a small one outside the browser [08:33] but I don't think it is a high priority [08:34] I think we could call it post-Oct [08:34] unless we know of one that just works [08:34] we'll have online readers [08:34] and usually rss-reader sends you to the browser when you lcick an item [08:35] I have the RSS reader as your second round of "must haves" do you want to change that? [08:35] agoliveira: one thing we could onsider is a category of applications "works on mobile, but not ported yet" [08:35] rss reader support is required, just not the external one, I would argue [08:36] Ok. [08:36] if the browser supports an rss reader plugin, that would be ok [08:36] (or similar functionality) [08:36] but reading your page, I see a couple of links [08:36] it would be cool to try those on the mobile device and see how usable they were [08:36] and keep them as "help needed" items if someone wanted to jump in [08:37] That's the point. So you suggest leave it up to the browser now and go for a dedicated reader laert? [08:37] later === sabotage is now known as sabotage_afk === captainigloo [n=silent@gar31-4-82-240-198-102.fbx.proxad.net] has joined #ubuntu-mobile [08:39] yeah [08:39] bspencer: where did you get the layout file to use with the slicer? [08:39] About the applications on the page, not all of them were tested on the device itself but all were on a chroot at least and worked to some useful level at least unless they had some major drawback like mobipocket. [08:40] Or the document viewer just because it does not exist in the way we want it. [08:40] right, ok. [08:40] what was the next app to chat about? [08:41] kwwii: again, sorry, but I never used the slicer :-\ [08:41] oh, right...I forgot [08:41] I just took the end-result theme/images directory and replaced them with my own [08:41] bspencer: hold on a second. I lost my notes :) [08:41] http://liferea.sourceforge.net/screenshot8.png looks very nice, I have to say [08:42] ( agoliveira ) [08:42] bspencer: Remote desktop client [08:42] aaright [08:42] bspencer: Yes, liferea is great but needs hiuldonization [08:42] ooops [08:42] agoliveira: sure, but the UI is simple [08:43] Indeed. [08:44] sorry, I'm in and out [08:44] ok. remote desktop [08:44] I played with vncviewer [08:44] matchbox keyboard didn't work with it [08:44] so that would have to be figured out. probably matthew allum has a fix we could use === guardian [n=Guardian@ANantes-252-1-80-60.w86-195.abo.wanadoo.fr] has joined #ubuntu-mobile [08:45] bspencer: There's 2 things to figure out: vnc and rdesktop. Both can be put to work without much haslle as I did it on N770. Just need to know if we are going do both, none and when :) [08:46] rdesktop is to windows? [08:46] looking up rdesktop ... [08:46] Yep [08:46] RDP client [08:46] ok. is it in-the-clear legal? [08:47] " rdesktop was initially written by Matthew Chapman based on various scarce documentation, wire sniffs, and trial-and-error " [08:47] makes me worried [08:47] (speaking with my Intel hat on, not the hacker hat) [08:47] I can't say. In Brazil it is :) [08:52] ok. let me look around. Ideally we focus on connecting to windows desktop first, if it is possible to get a legal-in-US solution [08:52] Sure. You would need to consult your shark^H^H^H^H^H^H legal tem, I guess [08:52] team [08:52] yeah, :) [08:52] or at least wikipedia :) [08:52] bspencer: the rdesktop protocol is specified in a pile of ISO standards. [08:52] Mithrandir: do you see any reason not to use it? [08:52] Mithrandir: Yes, but don't care about implement it. I won't work. [08:52] agoliveira: do you know if it connect to Windows Vista and XP ? [08:52] I see NT mentioned [08:52] NT terminal server is still used though I think. [08:52] bspencer: It's latest encarnation uses RDP 5 and some bits of 6 so, yes. [08:52] agoliveira: -EPARSE. [08:52] bspencer: no, I thinkit's completely fine. [08:52] agoliveira: let's do that [08:52] bspencer: Ok. rdesktop and/or vnc? [08:52] w00t...I got it to work :-) [08:52] agoliveira: does rdesktop require something to run on Windows? [08:52] if not, then it is better than making the user install vncserver on their windows box [08:52] (my mom couldn't do that easily) [08:52] If it's a rdp server capable version of windows, no. [08:52] you probably have to configure your windows system and it only works with XP full edition, not home edition [08:52] Exactly [08:53] mm... ok. Well... I don't know then [08:53] it seems like a "nice-to-have" application, but also cool [08:54] if it can never work on XP Home edition, then I'm not as excited about it. At least vnc could work on all systems [08:54] bspencer: We need a GUI to it as it is a command line application. We do have tsclient we can use as a base but needs hildonization. [08:54] rdekstop was a popular demo on Pepper Linux, despite the fact it requires XP Pro, etc [08:55] bspencer: It won't work with XP home, that's for sure. [08:55] For comparison, VNC was barely on the radar [08:55] agoliveira: ok. I'm not knowledgeable enough about rdesktop to compare it to vnc. I've only used vnc. [08:55] rdesktop's more convenient on thin pieces of string. [08:55] smagoun_: do you know if that is because of performance, usability, or just market presence? [08:55] Mithrandir: even compared to tightvnc ? [08:56] bspencer: I believe so. [08:56] bspencer: RDP is supported by MS so we can take some advantages, it's usually faster, one can redirect devices, have different users/sessions, while vnc is a screen grabber/controller only. [08:56] bspencer: Market presence; all the marketing types walking into the Pepper booth at CES and Digital Life knew Remote Desktop was a marketing catchphrase and most had never even heard of VNC. [08:56] That too. [08:56] Sciri: ha ha. funny world. vnc is nice for linux hackers [08:57] ok. agoliveira just do both :P [08:57] bspencer: Exactly. All the Linux geeks who came to see the Pad asked for VNC but they were the minority. === agoliveira grumbles something about big mounths... [08:57] bspencer: xrdp exists and works. [08:57] bspencer: I'm not sure why it was so popular, but I think people understand + are familiar with windows, so it's a way to tie the mobile device to their windows pc. [08:58] a guy here at work tried rdesktop and vnc and some others [08:58] there was a common issue with matchbox keyboard [08:59] although I think he said it worked with rdesktop, not vnc [08:59] When I was working in consulting, I had a costumer for whom I created a very small linux distro that in the end just started rdesktop fullscreen so he could connect to windows servers. [08:59] lol [08:59] bspencer: People also liked that there was nothing to install (on the windows side). FWIW rdesktop performance is fine, depending on the network connection. [08:59] bspencer: Yep. Being there, done that [08:59] ok. so what does it take to get rdesktop to work? [08:59] smagoun_: You should try rdp over nx. Goes rounds around rdp alone. [09:00] what is this "command-line interface" [09:00] bspencer: rdesktop is a command line tool. We need agui to make it palatable. [09:00] and you mentioned one [09:00] There's tsclient but needs hildonization. [09:00] is tsclient sexy? === bspencer goes to look for a screenshot [09:01] agoliveira: "good enough" > spending time on the problem :) [09:01] It's a ripoff of the windows rdp client almost :) [09:01] I have to check if there's nothign already done for maemo. [09:02] ok. so let's move on. [09:02] Cool. [09:02] (btw, vnc as-is works, just isn't hildonized, which is fine for linux hackers today) [09:03] Fine [09:03] Next: office document viewer. [09:03] oh, excpet for keyboard. I'll ping matchbox guys about keyboard. [09:03] Tight spot as there's none. [09:03] office document viewer ... [09:03] btw we tried the Adobe PDF plugin in the browser awhile back [09:03] it hung the browser and system [09:03] it is a little bit BIIIIG [09:04] For PDF is easy. [09:04] what document types to support? [09:04] ODP, DOC, PDF [09:04] The problem is the MS documents [09:04] MS Office, Im eman [09:04] mean [09:04] or.. what is the extension for the standard open document format? odf? [09:04] I don't see any easy alternative here [09:04] odf [09:04] ok, that's what I meant [09:05] odp is for presentations, I think [09:05] let's talk about usage models [09:05] how are people getting .doc's on their MIDs? [09:05] We could easily use abiword and gnumeric but they don't read MS docs as well as openoffice and there's nothing for powerpoint. [09:05] email or browser, probably [09:05] Yep [09:05] "easily" sounds a little optimistic [09:06] OO is out of the question [09:06] bspencer: They are already hildonized. [09:06] so what's the belly achin about [09:06] Need a bit polish but works. [09:06]