UCOSP Spring 2012/Standups/16 Mar

Standup at 1pm EST alright you ready? i'll log it ok, then thanks who first? it's all you, man Haha okay, so I had a few things I looked into 1) people have been complaining that the app icon looks "really bad" on their phones I tried with heatherw to edit some of the images, but they still don't look the greatest I looped in Amgine on the emails but we might need to find yet another logo to use (instead of the red W on the tile) 2) I am aware that the wrong image is being used beside the search bar (currently is a black W on a brown tile). This can be changed as soon as we all know which icon/logo is going to be used there So those are two of the bugs I have assigned to me ok, sweet question about the icon: it seems like different parties are giving conflicting feedback - is that right? Yes haha nice It is also very much based on people's personal opinions, so not necessarily a "party" ok, I getcha. Okay and the last thing So the feature where you can use another app to open wiktionary is still working great, but patrick raised an issue where it acted a little "odd" So if a user tries to share a Wktionary page, then the phone will suggest sharing it to the Wiktionary app along with others, and if you choose Wiktionary then it would show a "page not found" message yeah - I think that might be what I'm working on yup - that's the one! oh really? I am as well Oh, ok well how's it going? Pretty good, but you might be able to help me with a judgement call question So basically the issue was that the "share page" feature exports the url and the app is supposed to be opened with a specific word to show, not a url so I have it now parsing the url to extract the word we want to show Note: this parsing only works for wiktionary urls and wikipedia urls (in case they are coming from the share page feature of the wikipedia app) Now it would be nice if we could share a page from wikipedia to wiktionary and have it open the proper page, but the issue is that a lot of wikipedia pages capitalize the subject, and wiktioniary is case sensitive so for example, if you share the "Trophy" page from wikipedia and open it in wiktionary, it won't find it because it is "trophy" in wiktionary We could cast to lower case, but for some words that will again cause problems, such as "Europe" So I am trying to figure out what the default behaviour should be. I tried looking for an easy way to see if a page exists (and thus we could try both options) but couldn't find one that's all I think we're looking at the problem differently... haha Well they might be slightly different, I know mine was just mentioned recently What was your issue? the way you see it, the problem is that when the user clicks Wiktionary from the list of apps, the sucker crashes they way I see it, Wiktionary shouldn't even be in the list in the first place Okay yeah, I had considered that option, but I think since we are using Android Intents and intent filters, we can't avoid being in the list Yeah, it's not easy, but I think it's possible Our app accepts any mime type that fits "text/*" I've been trying to build a custom dialog and pruning from the list of candidate activities based on their package name if the package name matches ours, we remove it from the list before displaying it to the user Oh really? Okay so if that works then it will fix the wiktionary -> wiktionary case, which would be great! Yeah, that's the plan And then we would still have the wikipedia -> wiktionary issue right? I haven't got it running yet, but I haven't given up either Sweet I'm finished with my updates if you want to go ahead with yours Well the Wikipedia -> Wiktionary issue might be trickier My update: I've been working on this issue haha Yeah, it sounds like a great plan. Keep me posted on it! IMO, thing about wiktionary <--> wikipedia sharing is that actually wikipedia shouldn't be a candidate activity for this intent I think it's meant for emails and text messages - so that people can open the link in the browser of their choice Sounds good. So I'll put my two Sounds good. So I'll put my two "workarounds" on the back burner for now, and if your component is implemented then we can just go ahead with that. :) ok - sounds good to me as well! anything else? That's all for me! I'll keep emailing and bugging people about icons! yeah man - keep it up! it sounds like a pretty tough, thankless job