[10:05:18] CONTENT MEETING ahoy [10:05:23] ahoy!! [10:05:55] anyone else around [10:06:22] rworth? nacin? scott_gonzalez ? [10:06:27] here [10:06:38] I'm here [10:06:44] hi agcolom! [10:06:48] not here - T minus 6 days to 3.5 [10:06:59] lurking [10:07:16] sooo [10:07:24] ok, nacin. you're off the hook. but I'm still waiting for my jsonp search update for api.jquery.com. :p [10:07:51] quick learn site update: we still haven't announced yet [10:08:00] going to do it tomorrow regardless of whatever [10:08:11] would like to get better tiered navigation in before then [10:08:31] but we got the live site up to 3.5 RC 1 so the chapter listing is displaying correctly [10:09:01] nice! [10:09:05] and we are also now properly displaying contributors in articles [10:09:15] using the git file history and the attribution flag in articles [10:10:07] which is a nice thing to be able to launch with [10:10:15] ajpiano: what's with the reference to /exercises/index.html and /exercises/js/blog.js in http://learn.jquery.com/effects/effects-exercises/ ? [10:10:39] kswedberg: that page is gone [10:10:56] throw a stage in front of there and you'll see [10:11:03] ah, ok! :) [10:11:51] outside of learn, we are trying to get new-css ready [10:12:21] so we can pull the trigger on that and get, among other things, api.jquery.com launched [10:12:28] yay! [10:12:30] yay [10:12:42] rworth has been making some progress but i don't know if we are going to be where we want to be on dec 1st [10:13:16] yesterday on dev leads i said i would attempt to jump into the breach next week if necessary but now i may be starting on a client project, so i'm unsure [10:13:24] yeah, I'm doing what I can, but I'm a couple days behind [10:13:29] i think we'll just have to evaluate on monday [10:13:33] my holiday travel was extended a tad [10:14:35] also, there is one high priority thing that needs to get done, which is re-writing the box on bugs.jquery.com [10:14:39] to reflect... the present [10:15:17] i'm going to take care of that today or tomorrow, unless DaveMethvin still feels like taking a shot at it [10:15:23] :p [10:15:36] wow, i am JUST doing that ajpiano [10:15:39] as we speak [10:15:41] DaveMethvin: awesome [10:15:45] let me press submit [10:15:46] lemme know when it's updated [10:15:50] awesome [10:16:41] http://bugs.jquery.com/newticket stilll needs work but at least it's visible on screen; I need to find out how to avoid it focusing the first form element [10:17:09] $("*").on("focus").blur() ;) [10:17:19] the window still will be scrolled :p [10:17:23] DaveMethvin: main thing to add would be [10:17:31] for bugs with the the jQuery Website [10:17:41] i don't think the wiki site lets me add script [10:17:56] but let me stop hijacking this meeting, ping me after :D [10:18:02] ok [10:18:12] well there's my thought anyway :p [10:18:59] ajpiano: is there a guide for giving proper attribution on the learn site? [10:19:29] like if the article was originally published on someone else's blog? [10:19:35] it's in the style guide [10:19:43] awesome. thx! [10:19:53] if it was initially published by someone else, you put source and attribution [10:20:03] and that gets pushed to the top of the list [10:20:13] i'm not *linking* to the old resource though, except for jquery fundamentals [10:20:29] ok. [10:20:44] ajpiano: your changes in web-base-template need to be brought in I think (I'm still seeing that FF problem) [10:20:47] seems weird to link to a similar outdated version of an article you're already on [10:20:55] agcolom: yeah we haven't updated live in a few days [10:21:15] rworth: what do you think of the aesthetics of the contributors block right now [10:21:27] it is neither the best nor is it the worst [10:22:16] yeah, it looks ok [10:22:28] can we link to people's github accounts? [10:22:54] i don't think we have their github usernames [10:23:06] i mean, i know we don't [10:24:02] so for now i think the answer is no [10:24:11] oh that's right, we only get name and email [10:24:15] ok, it's fine yeah [10:25:45] i think that's all i have for learn... it's a work in progress, we have to take the veil off sometime :) [10:26:35] should jQuery Fundamentals have the jQuery logo? [10:26:44] i asked rebecca yesterday [10:26:45] that was my only concern when I first saw the box [10:26:53] it never had a logo [10:26:57] so i wasn't sure what to use [10:27:01] she said jq logo was fine w/ her [10:27:09] that's what i had been using months ago [10:27:09] seems… weird [10:27:13] not sure what else to use [10:27:16] right [10:27:33] I guess I could go either way [10:27:40] just wanted to see where there origins of it were [10:28:06] it's hardcoded https://github.com/jquery/learn.jquery.com/blob/master/grunt.js#L133-L134 [10:28:13] so if we wantt to use something else we can [10:28:24] right. I mean origins like why and when and how we decided on it, or if it had it before [10:28:28] yup [10:28:53] rworth: cause it wasn't *only* rebecca who worked on jqf [10:29:00] and since it doesn't have a logo of its own [10:29:02] caus if it had had it before (or even now) it would be a trademark violation [10:29:07] there isn't really a good answer as to what to show [10:29:38] of course it's not a violation if we approve it [10:29:44] "jquery fundamentals" doesn't have a jquery logo in it at all [10:29:50] right [10:29:51] we're just shoing a jquery logo next to it [10:29:52] on our site [10:29:56] that's why it seems weird [10:29:59] yeah, I understand [10:30:04] do you have any other ideas [10:30:19] we could not show an image at all [10:30:20] A picture of David Mark? [10:30:45] a book icon? [10:31:17] that is clever [10:31:29] would work [10:32:02] though i don't think we should chase our own tail around too much in terms of attempting to figure out whether we're violating our own copyright by putting our own logo next to the title of a legacy content that was itself donated to us [10:32:09] jussayin [10:32:32] well, it was donated to us but not assigned to us [10:32:45] not trying to minimize the contribution [10:32:51] i realise that [10:32:58] but we're going to iron out the technical side of it [10:32:59] but the donation wasn't more than what's allowed by the original license [10:33:02] yup [10:33:56] so let's decide on that finally after we talk to rebeca bout it [10:33:59] book icon is fine with me [10:34:28] let's just stick a book icon there in the meantime, the swoops on their own just worry me in terms of our coming trademark use guidelines [10:34:52] i think we should probably find someone else to target with those guidelines besdies us [10:34:57] again, we can do what we don't allow others to do, but we should take care in that [10:35:10] yep [10:35:36] alright [10:35:37] moving on [10:35:46] anyone got anything they want to bring up from API docs etc [10:36:13] nothin here [10:36:15] all fine on my side... [10:36:44] I just want to make sure that rworth is moving the common API stylings to the correct location when doing the new-css migration. [10:37:01] Since master has common styles either duplicated across themes or only implemented in api.jqueryui.com. [10:37:19] actually I wanted to discuss this (or something like it) [10:37:24] oh yes... [10:37:27] we currently have 2 stylesheets per site [10:37:30] base.css for all sites [10:37:43] that's shared [10:37:50] i will be back in 3 mins, contine w/o me obvi [10:37:51] and a sep. style.css per site/theme [10:38:26] for something like API where 3-5 sites will use the same style(s), should we just put that in base, in an API section? [10:38:35] caus adding a 3rd sheet seems a bit much [10:39:12] Moving them to base seems fine, we can always get them into a 3rd file that goes away with a build process later. [10:39:17] ideally we'd concat the stylesheets [10:39:22] ok [10:39:48] we'll do that for now. when base gets too big we'll come up with some other solution like that. That's what I was thinking [10:39:49] thanks [10:39:58] so, yeah, I'll consolidate all the api styles into base [10:39:59] +1 [10:40:56] thanks! [10:42:01] imagine if there was some kind of crazy "css preprocessor" that would allow for this type of style sharing [10:42:02] :p [10:42:37] :D [10:42:38] well, now that i've trolled my own meeting... i think we can wrap up [10:42:54] the important part is we're gonna get 1.8 on jquery.com [10:43:08] everything else is small potatoes compared to that [10:43:49] alright, see everyone in #jquery-content [10:44:14] gonna leave the chan open for now as mobile is starting in 15 minutes anyway [10:44:21] it's all yours toddmparker :) [10:44:22] bye [11:03:43] Hi all [11:03:49] Hello [11:03:57] The jQuery Mobile team meeting is starting up [11:04:02] chime in if you're here [11:04:08] (hey RWhitbeck) [11:04:11] hey [11:04:22] Hi [11:04:23] agenda here: https://docs.google.com/document/d/1lhOuwXgrFqfrc2SrHvfv9KcyGX69rkNnxLz0wVoJENU/edit# [11:04:26] hi! [11:04:35] hi agcolom, arschmitz, jlembeck [11:05:04] guess we need johnbender, _|Nix|_ and uGoMobi [11:05:06] and JasonDScott__ [11:05:17] I am here [11:05:29] bingo [11:06:01] JasonDScott__ is in Bangkok I think for BBJam asia [11:06:07] ah, ok [11:06:47] Sounds like that would hurt … badum ching [11:06:59] hehe [11:07:14] ZING RWhitbeck! [11:07:16] :) :) [11:07:19] ok, we can start. maybe _|Nix|_ will hop on in a bit [11:07:25] my update is quick [11:07:39] Good progress on 1.3: 14 open issues / 36 closed - https://github.com/jquery/jquery-mobile/issues?direction=desc&milestone=19&sort=updated&state=open [11:07:39] Sliding panel widget work underway in a branch, will need docs and demos soon [11:07:48] <_|Nix|_> Hey! [11:07:49] ^ Jeff can talk about panels in a bit [11:07:53] hey _|Nix|_ ! [11:08:09] I will focus on release notes for 1.1.2 and 1.2.1 this week so we can get those released [11:08:20] jlembeck has a script I can use for that [11:08:34] Next: new demos site to compliment new API site [11:08:48] yes! [11:08:53] Collecting a rough set of demo pages here - http://jquerymobile.com/test/docs/demos/ [11:09:29] Hoping we're on track for a beta of 1.3 by the end of the year. Seems reasonable. [11:09:40] awesome. [11:09:55] 1.4 is looking like it will be heavy on re-factoring for speed, consistency and performance [11:10:09] provided John "Douchebag" Bender doesn't hold things up [11:10:22] yeah, DB [11:10:40] don't derail this train [11:10:46] :p [11:10:53] I'm tryin not to I promise [11:10:58] that's why it's taking so long [11:11:03] The Kinks [11:11:06] speaking of johnbender - wanna give us an update on your nav work? [11:11:08] yes [11:11:10] toddmparker_ will we be focusing more on using jQM with RWD techniques in 1.3 or 1.4? I can't remember what you said. How are we going to do that? Tutorials? [11:11:11] 3 yests left [11:11:13] tests [11:11:17] for the whole sweet [11:11:25] suite [11:11:27] good lord [11:11:30] heh [11:11:41] but things are looking good [11:11:58] once I get it merged there's some refactoring of my refactoring to do :x [11:12:03] but not much [11:12:19] cool [11:12:21] been working on internal stuff alot recently [11:12:27] so that's why it's not merged already [11:12:28] :( [11:12:34] internal = adobe? [11:12:49] yessir [11:12:52] Vagrant stuff [11:13:08] which I'm the authority on for god knows what reason :) [11:13:25] <_|Nix|_> johnbender: You're the vagrant authority? :) [11:13:34] haha [11:13:40] indeed! [11:14:26] probably a reason or two behind that. [11:14:49] sounds like vagrant is going to be able to move forward even faster now [11:15:01] yah super excited for Mitch [11:15:13] he's work insanely hard on that project [11:15:17] *worked [11:15:19] yeah, great news [11:15:22] i bet [11:16:02] johnbender: is there a quick way to summarize what part sof you nav you're working on for 1.3? [11:16:11] yes [11:16:17] do you want me to write something up? [11:16:18] I have seen a few Q"s about that [11:16:20] I'v got my writing hat on [11:16:30] sure, probably too hard to wing it here [11:16:37] * johnbender thinks his typing hat must have fallen off though [11:16:41] be helpful for the blog post too [11:16:50] toddmparker__: kk, I'll do a paragraph [11:16:54] <_|Nix|_> johnbender: So, you're gonna use pen and paper? [11:16:56] cool [11:17:07] _|Nix|_: I'm no hipster ?:) [11:17:22] for example, will the separation of nav into more of a standard plugin out of the core stuff be for 1.4? [11:17:42] or the start of that process anyway [11:18:11] johnbender ^ [11:18:51] toddmparker__: it can start now [11:18:52] at 1.3 [11:18:55] cool [11:18:57] if we're comfortable with the api shape [11:19:00] that was my goal [11:19:05] and part of why it was so hard [11:19:15] value for the user + value for the project [11:19:15] it'll probably be a multi-part thing. groundwork now, more in 1.4 [11:19:20] right. [11:19:26] yes, it's a start [11:19:32] and a good one I think [11:19:38] nice [11:19:42] thanks johnbender [11:19:51] RWhitbeck re: RWD [11:20:06] 1.3 will be chock full of RWD stuff [11:20:16] RWD intro started (very basic): http://jquerymobile.com/test/docs/demos/grids/rwd-basics.html [11:20:16] Responsive grids w/default breakpoint: http://jquerymobile.com/test/docs/demos/grids/grid-stack.html [11:20:16] Responsive tables: http://jquerymobile.com/test/docs/tables/index.html [11:21:08] the panels will also have a responsive element where we could have a demo showing how we could display a panel and hide the open/close button above a certain width [11:21:15] awesome. I'd love to know how I can help preach the good word on RWD. Let me know how I can help [11:21:41] i need to flesh out the into with best practices [11:21:59] that could be moved over to the learn site if we think that will be more visible [11:22:19] we're going to be building more responsive demos too [11:23:12] widgets like tables and grids will have a single, optional preset breakpoint people can opt into via a class and we'll use demos and docs to teach people how to customize for their needs [11:23:52] scroll to the bottom here to see a bunch of more customized RWD table demos - http://jquerymobile.com/test/docs/demos/ [11:24:11] each have a style block so you can see how we customzed [11:24:30] i'd like to coordinate w/you on this more though. [11:24:40] RWhitbeck: want to go next? [11:25:19] Sure [11:25:56] I've been heading up a community effort to write a book for O'Reilly called the jQuery Mobile Cookbook. More info here http://jquerymobilecookbook.com [11:26:59] Have good momentum now. HAve a few dozen authors that have contributed and looking for more. Hoping to have this published first half of next year ideally [11:27:31] I am also working on putting together some jQuery Mobile talks that I can submit to conferences so that I can work on preaching jQuery Mobile's good word. [11:27:34] been seeing a lot of commits to the cookbook [11:28:01] roughly how far along is it? [11:28:03] yeah it's been great [11:28:17] about 40-50% [11:28:35] here is my presentation slides from jQuery Asia https://speakerdeck.com/rwhitbeck/in-depth-look-at-jquery-mobile [11:28:43] ok, great. momentum is back [11:29:13] woudl you be interested in helping with mobile support on the #jquery channel [11:29:29] had a interesting question come from that. How are we going to handle tablets that are 10" or greater. I suggested that we'd be talking about RWD techniques but wasn't sure if we had an official answer. [11:29:30] or forums? [11:29:47] you guys and your keynote slides [11:29:52] sure I can jump in there. [11:29:54] yeah, all the widgets are 100% flexible [11:29:54] my next preso is going to be pretty [11:29:56] I swear [11:30:05] and we're building some RWD stuff in, like for tables [11:30:27] RWhitbeck: there is no real size restrictions currently [11:30:40] to support a broad range of devices, people really need to write some media queries that make sense for their design and content [11:30:53] we'll help with docs and demos to show the way [11:31:02] ok so I was on par with my answer [11:31:07] right now, things will stretch out to 100% [11:31:10] yeah [11:31:24] ok I am done. [11:31:29] we can also write tutorials in the jquery mobile section of the learn site (being released very soon) [11:31:46] yeah I plan on contributing to that when I get some air [11:31:51] problem is, it's hard to library-ize a lot of RWD layouts. some people try, but I think it's a mistake. [11:32:03] and writing a few media queries is easy [11:32:06] <_|Nix|_> I have an idea re: responsive stuff: Is there a systematic way of doing stuff like this: if the width is greater than x, you get widget y, otherwise you get widget z. [11:32:46] swapping widgets is an interesting one [11:33:01] That sounds like something you could plug into a container [11:33:08] what happens when people rotate the device? [11:33:12] classic example would be a horizontal navbar that swaps to a menu [11:33:45] agcolom: rotating the device is the same as re-sizing the browser so if you cross a breakpoint, it will adapt [11:33:55] ok. [11:33:58] <_|Nix|_> The naïve way is to instantiate both, and hide one. Then, upon orientation change, hide it and reveal the other one. [11:35:03] <_|Nix|_> Anyway ... just a thought ... [11:35:17] _|Nix|_: i think this is an interesting pattern to explore [11:35:37] a widget to swp widgets ! [11:35:41] swap [11:35:53] <_|Nix|_> I guess the same way that the solution for MQs is to educate, the solution for widgets that are responsive in the way I describe is also app-level, rather than framework-level. [11:35:57] one option is to bake this into a widget so a navbar can have a point where it becomes a menu [11:36:12] <_|Nix|_> toddmparker__: That's the other option. [11:36:30] <_|Nix|_> toddmparker__: Not sure if that'll complicate our widgets much. [11:36:31] toddmparker__: pure CSS you mean? [11:36:51] there are a lot of things to think about - whether content is duplicated, source order, ARIA [11:37:02] <_|Nix|_> uGoMobi: I doubt that's possible. Maybe if the DOM structure can be kept identical between the two looks. [11:37:38] _|Nix|_: I agree [11:37:43] you can swap from a navbar to menu with the same html and different css [11:38:09] yes, swapping between widget will difficult though [11:38:28] but i can see other situations where you might need to literally destroy widget A and call widget B on the same markup. might be too complex to build that in and instead make some demos [11:39:03] this all seems like demo territory [11:39:07] <_|Nix|_> toddmparker__: Actually, if wew properly implement _destroy(), like we're planning for 1.4, we'll be well along towards that goal - assuming performance doesn't kill us. [11:39:18] right [11:39:38] i have some ideas on this we should talk about _|Nix|_ too much for in here i think though [11:39:41] _|Nix|_: you want to go next? [11:39:48] <_|Nix|_> toddmparker__: Yeah, demos - definitely. Those should help us identify what, if anything needs to go into the framework. [11:39:53] right [11:40:03] <_|Nix|_> Sure, I'll go next. [11:40:09] Worry that some of these ideas will make the library heavier in file size. [11:40:24] <_|Nix|_> So, I fixed a bunch of bugs. I also partially fixed https://github.com/jquery/jquery-mobile/issues/5009 (active state for buttons). [11:40:44] saw that - great [11:40:55] <_|Nix|_> enhanced native buttons now get the active state, if the form they're a part of is AJAX-submitted. [11:41:09] cool [11:41:26] seems like we can't really go much further on this, can we? [11:41:27] <_|Nix|_> Then, I have a bunch of stuff pending on the nav refactor ... [11:41:45] <_|Nix|_> toddmparker__: Not without a major design discussion. [11:42:03] so i'd close and say that's as far we we'll go [11:42:18] <_|Nix|_> One dicy thing is that nav completely dies if a pageshow handler throws an error. [11:42:45] oh, _|Nix|_ one thing I just remembered: for popup, the new option should be "dismissible" not "dismissable" [11:43:08] <_|Nix|_> toddmparker__: Is that the officially correct spelling? Like dirigible? [11:43:11] hopefully a quick change [11:43:13] yeah :) [11:43:28] <_|Nix|_> toddmparker__: Just out of curiosity: where'd you find that? [11:43:38] <_|Nix|_> toddmparker__: I looked everywhere for an authority on the spelling ... [11:43:44] maybe we should add spell checker to unit tests :) [11:43:44] http://www.thefreedictionary.com/dismissible [11:43:56] <_|Nix|_> toddmparker__: Cool. [11:43:58] google corrected jlembeck and that's how we got clued in [11:44:08] <_|Nix|_> toddmparker__: Oh, really! Cool! [11:44:13] uGoMobi: heh, seriously. [11:44:14] <_|Nix|_> toddmparker__: OK. dismissible it is. [11:44:19] thanks google [11:44:29] :) [11:45:00] _|Nix|_: re: "nav completely dies if a pageshow handler throws an error." [11:45:11] <_|Nix|_> Then I had an idea for making history change preventable via pagebeforechange - but that's assuming johnbender's refactor doesn't already make that possible. [11:45:14] <_|Nix|_> toddmparker__: Yeah. [11:45:17] johnbender - is that something you can look at with _|Nix|_ [11:45:24] <_|Nix|_> toddmparker__: Had a discussion with the core guys. [11:45:25] seems bad [11:45:32] and... [11:45:41] <_|Nix|_> toddmparker__: This is a fundamental problem with callback-based event handling systems. [11:45:45] ah [11:46:03] <_|Nix|_> toddmparker__: When the browser fires an event, it'll tear down the whole stack frame handling that event upon error. [11:46:12] <_|Nix|_> toddmparker__: The solution? one event handler per event. [11:46:29] that workable? [11:46:47] <_|Nix|_> toddmparker__: So, if you have 5 handlers bound to an event, you emit 5 fake events when you receive the real event, and hook one of the five handlers up to each of the fake events. [11:46:54] actually, seems like a good to to discuss offline, esp with johnbender and core [11:46:55] <_|Nix|_> toddmparker__: Workable, but performance is 0. [11:47:00] eh [11:47:07] <_|Nix|_> toddmparker__: Core will have none of it. [11:47:12] i see why [11:47:18] _|Nix|_: it does make it possible [11:47:19] <_|Nix|_> toddmparker__: Yeah, that's insane. [11:47:20] we can chat [11:47:23] it's used in popup [11:47:25] ok [11:47:36] <_|Nix|_> johnbender: OK, let's talk after. [11:47:37] anything else _|Nix|_ [11:47:44] <_|Nix|_> That's about it. [11:47:47] cool [11:47:51] uGoMobi? [11:47:55] <_|Nix|_> I'll try and repro that table failure. [11:47:56] ok [11:47:58] <_|Nix|_> In the unit tests. [11:48:12] textinput clear button landed https://github.com/jquery/jquery-mobile/issues/1834 [11:48:12] fixed iOS preventFocusZoom issue iOS [11:48:12] https://github.com/jquery/jquery-mobile/issues/5333 [11:48:12] https://github.com/jquery/jquery-mobile/issues/3690 [11:48:15] <_|Nix|_> uGoMobi: Sorry. [11:48:23] _|Nix|_: thanks - jlembeck can help fix that if you can narrow down [11:48:36] np [11:48:41] made some changes to demo source code view: max height + scroll, better performance [11:48:58] i'll need to check those demo changes out [11:49:10] scroll doesn't work on mobile so i should add a MQ [11:49:15] do we have demos for the clear button feature? [11:49:28] almost... hang on [11:49:34] http://jquerymobile.com/test/docs/demos/textinput/index.html [11:49:35] ? [11:49:57] those work nicely [11:50:13] I will clean up that page [11:50:16] is that 2nd example of the false clear button doing much? it's the default, right? [11:50:28] but that's a nice page to demo it [11:50:56] yes no clear btn is default [11:51:04] right [11:51:31] wasn't sure if we needed so many clear button examples [11:51:33] so maybe only search needs the false example since that defaults to true [11:51:44] I mean... with and without fieldcontain, etc. [11:51:47] probably only need 1-2 true examples [11:51:51] yeah [11:52:00] toddmparker__: you can't disable it on search [11:52:14] yeah? [11:52:27] didn't we discuss that on -dev [11:52:28] might be nice for consistency [11:52:30] sure [11:52:40] Textarea: data-clear-btn="true" >> not needed, not supported [11:52:41] ok [11:52:49] that is a nice feature [11:52:54] arschmitz: do you remember what we discussed? [11:53:18] type="search" has a native clear button so it always should [11:53:19] but we can add the option for search, np [11:53:29] cool [11:53:46] more consistent that way, just different defaults [11:53:50] I am adding few textinput examples to other form demo pages too [11:54:02] oh, do we have an issue for the range slider tagged for 1.3? [11:54:07] that's true [11:54:07] uGoMobi: great [11:54:22] not sure what to do with these Symbian issues (can we reproduce? should we degrade?) [11:54:22] https://github.com/jquery/jquery-mobile/issues?direction=desc&labels=Symbian&milestone=&page=1&sort=updated&state=open [11:54:34] not high priority issues [11:54:34] if not, we should and link up the prototypes such [11:54:58] toddmparker: not currently but i can add one [11:55:01] but if we want to degrade we should to it in main release [11:55:09] uGoMobi: on symbian, the problem is that the page dies = blank screen? [11:55:22] <_|Nix|_> uGoMobi: I have a Series 60 phone - just need to charge it. [11:55:24] yes that was the series 40 [11:55:37] series 40 is proxy browser [11:55:48] <_|Nix|_> uGoMobi: Oh, OK. Series 40 ... [11:55:53] but also crashing on series 60 [11:56:12] i'd lean towards playing it safer with symbian and only letting the newer series 60 versions in and having 40 and older 60 be C grade [11:56:17] series 440 is C grade but still blank page [11:56:32] <_|Nix|_> uGoMobi: Oh, OK ... well, since they're low prio, we should probably wait until after 1.3 ... although I think we'll be knee-deep in refactors fater that so, I dunno ... [11:56:35] the 2-3 symbian 60's I tested worked great at the office [11:56:55] <_|Nix|_> uGoMobi: If these issues linger much longer, Series (40|60) will disappear off the radar. [11:57:05]