|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Comment:
Changes (1)
View Page History
...
\[09:41:57 CDT(-0500)\] {color:black} <jhung> justin_o: I will be doing a little testing of genpdf today, especially the DPI and width/height options. I want to see how these two options interact.{color} \[09:42:24 CDT(-0500)\] {color:black} <Justin_o> jhung: great thanks.. i'm still testing out the 12.04 upgrade stuff{color}
\[09:43:19 CDT(-0500)\] {color:black} <jhung> justin_o: cool. I'm using 10.04{color}
\[09:45:35 CDT(-0500)\] {color:black} <Justin_o> jhung: okay.. good to start with that{color}
\[09:50:34 CDT(-0500)\] {color:black} <jhung> justin_o: I was just thinking about when we do automate the genpdf test plan, the output files can be named according to the input file(s) and the options used.{color}
\[09:51:16 CDT(-0500)\] {color:black} <Justin_o> jhung: that makes sense.. will help keep track of them{color}
\[09:51:24 CDT(-0500)\] {color:black} <Justin_o> and hopefully reduce confusion{color}
\[09:56:17 CDT(-0500)\] {color:black} <Justin_o> jhung: are we putting off the upgrade to Ocropus 0.5 till a later release?{color}
\[10:01:35 CDT(-0500)\] {color:black} <jhung> justin_o: I hope not. We need to get Hasan to give us a plan on how he expects to upgrade.{color}
\[10:01:58 CDT(-0500)\] {color:black} <Justin_o> jhung: yes.. from the last meeting it didn't sound like he wanted to upgrade at all{color}
\[10:03:10 CDT(-0500)\] {color:black} <jhung> justin_o: hesitant, yes, but I think he'd be willing to if given the right reasons (i.e. quality improvements).{color}
\[10:03:32 CDT(-0500)\] {color:black} <jhung> the tough part is that it's probably a heavy investment to do the upgrade.{color}
\[10:04:24 CDT(-0500)\] {color:black} <Justin_o> jhung: could be.. i guess we don't really know what's involved.. at least i don't{color}
\[10:04:36 CDT(-0500)\] {color:black} <jhung> yeah. Neither do I justin_o.{color}
\[10:04:49 CDT(-0500)\] {color:black} <jhung> I guess we should talk to him about it.{color}
\[10:04:53 CDT(-0500)\] {color:black} <Justin_o> jhung: okay{color}
\[10:04:59 CDT(-0500)\] {color:black} <jhung> But let's sort out the Ubuntu 12.04 issue first.{color}
\[10:05:11 CDT(-0500)\] {color:black} <jhung> Get that stable, then let's try to tackle Ocropus 0.5{color}
\[10:07:40 CDT(-0500)\] {color:black} <Justin_o> jhung: sounds like a plan..{color}
\[10:08:21 CDT(-0500)\] {color:black} <Justin_o> jhung: still trying to test out avatar's install changes.. but it's going slow.. also setting up a new dev vm in Ubuntu 12.04{color}
\[10:12:04 CDT(-0500)\] {color:black} <jhung> okay justin_o.{color}
\[10:44:52 CDT(-0500)\] {color:black} <jhung> justin_o: is it feasible to implement a unit picker for the exporter UI? Idea is the user can choose between inches, cm, and pixels, and labels and units change to reflect their choice.{color}
\[10:50:28 CDT(-0500)\] {color:black} <Justin_o> um.. i'm not sure i follow completely{color}
\[10:50:50 CDT(-0500)\] {color:black} <Justin_o> so we wouldn't expose the dpi option in that case?{color}
\[10:50:53 CDT(-0500)\] {color:black} <Justin_o> jhung: ^{color}
\[10:52:08 CDT(-0500)\] {color:black} <jhung> justin_o: the units is an internationalization preference.{color}
\[10:53:29 CDT(-0500)\] {color:black} <jhung> Example: there is a selector for output dimensions of common page sizes (i.e. A4, 8.5x11, etc). Their units would be displayed as cm, inches, or pixels.{color}
\[10:54:21 CDT(-0500)\] {color:black} <jhung> (although the pixels value for this selector would change depending on the DPI){color}
\[10:57:13 CDT(-0500)\] {color:black} <Justin_o> jhung_away: yes i was specifically wondering about how we would handle that.. i suppose for inches we could just do the conversion in the UI.. the pixels would be the more confusing one for the user i think{color}
\[10:59:12 CDT(-0500)\] {color:black} <logiclord> yura : can we discuss about pagination issue ?{color}
\[10:59:28 CDT(-0500)\] {color:black} <yura> logiclord: sure{color}
\[11:00:10 CDT(-0500)\] {color:black} <logiclord> yura : now I have managed to parse and load chapter content for validated epub 2 and mostly epub 3 as well{color}
\[11:00:24 CDT(-0500)\] {color:black} <yura> logiclord: awesome{color}
\[11:00:43 CDT(-0500)\] {color:black} <logiclord> and the issue is how do I divide chapter (which you can think as an html file){color}
\[11:01:07 CDT(-0500)\] {color:black} <logiclord> multiple solutions are there but I think we should according to our case{color}
\[11:01:28 CDT(-0500)\] {color:black} <logiclord> 1 preprocess entire page and divide to store in an array of pages{color}
\[11:01:42 CDT(-0500)\] {color:black} <logiclord> pro - easy next - prev{color}
\[11:02:13 CDT(-0500)\] {color:black} <logiclord> cons - even a small change in css by UI option component will reset our chapter{color}
\[11:02:27 CDT(-0500)\] {color:black} <logiclord> and no preview for UI option ?{color}
\[11:03:16 CDT(-0500)\] {color:black} <logiclord> other way could be that I tried to keep entire chapter separate and current page being maintained and extracted everytime we go next-prev{color}
\[11:03:30 CDT(-0500)\] {color:black} <logiclord> any other option you would like to suggest ?{color}
\[11:04:04 CDT(-0500)\] {color:black} <logiclord> and which to choose.. I am really confused{color}
\[11:04:27 CDT(-0500)\] {color:black} <logiclord> moreover editing features will make things even more complicated{color}
\[11:05:55 CDT(-0500)\] {color:black} <yura> logiclord: right, so for the second option you would need to recalculate things on the fly everytime presentation changes ?{color}
\[11:07:17 CDT(-0500)\] {color:black} <logiclord> yura : for presentation changes I would have to recalculate in both the cases but I would be easy in second case{color}
\[11:07:33 CDT(-0500)\] {color:black} <yura> logiclord: and what would be the drawback ?{color}
\[11:07:39 CDT(-0500)\] {color:black} <yura> for the second case{color}
\[11:08:36 CDT(-0500)\] {color:black} <logiclord> yura : for every next-previous page click we would have to recalculate (basically DOM tree traveral to reach nearest leaf){color}
\[11:09:55 CDT(-0500)\] {color:black} <logiclord> yura : actually having images make things complicated{color}
\[11:09:57 CDT(-0500)\] {color:black} <cindyli> anastasiac: can you clarify what "current page has text shadow; get rid of in high-contrast" means in jira: http://issues.fluidproject.org/browse/FLOE-15{color}
\[11:11:08 CDT(-0500)\] {color:black} <anastasiac> cindyli, in the main navigation bar, whichever page is the current page (i.e. with the green background in the regular theme), the text has a shadow. We should get rid of the shadow in high-contrast{color}
\[11:12:11 CDT(-0500)\] {color:black} <yura> logiclord: and the calculation takes significant time ?{color}
\[11:12:58 CDT(-0500)\] {color:black} <cindyli> ok, thanks, anastasiac{color}
\[11:13:35 CDT(-0500)\] {color:black} <anastasiac> alexn, if you're looking for something to work on this one: "Search results "details" toggle" I didn't actually get anything done yesterday, so you could work on that{color}
\[11:13:37 CDT(-0500)\] {color:black} <logiclord> yura : actually I have not tried it{color}
\[11:15:11 CDT(-0500)\] {color:black} <yura> logiclord: I think in case of an actual e-book , it generally recalculate things once things update, so maybe it makes sense to test the second approach and see how demanding it is{color}
\[11:15:52 CDT(-0500)\] {color:black} <alexn> anastasiac: sure! I just need to push a pull request to Andrey and will start working on this :){color}
\[11:16:06 CDT(-0500)\] {color:black} <logiclord> yura : okay I will implement second option and test it{color}
\[11:17:41 CDT(-0500)\] {color:black} <logiclord> yura : I think we should edit entire chapter in WYSIWYG editor rather then individual pages{color}
\[11:17:52 CDT(-0500)\] {color:black} <logiclord> yura : just from experience{color}
\[11:31:54 CDT(-0500)\] {color:black} <logiclord> yura : forgot to mention in second option we can't move directly to a particular page in a chapter but we can in first one{color}
\[11:32:39 CDT(-0500)\] {color:black} <logiclord> bascially second will not give much indication of content left and alreay read in current chapter{color}
\[11:43:28 CDT(-0500)\] {color:black} <anastasiac> michelled, my fix for the failed login accessibility is ready for your review: https://github.com/acheetham/OER-Commons/tree/584-failed-login{color}
\[13:05:18 CDT(-0500)\] {color:black} <jhung_away> justin_o: re DPI. I guess only inches and cm are required as a view option. So is this a feasible thing to do on the UI?{color}
\[13:06:17 CDT(-0500)\] {color:black} <Justin_o> jhung_away: sure i think so.. the conversion between the two shouldn't be too hard{color}
\[13:12:23 CDT(-0500)\] {color:black} <anastasiac> cindyli, you mentioned a way to configure screen readers to read the longest label/title/text. Do you know how to do this in Jaws and NVDA?{color}
\[13:13:34 CDT(-0500)\] {color:black} <cindyli> anastasiac: i will dig out from Jaws and let u know. not sure about NVDA. As alexn mentioned, the default NVDA setting might already reads out the label{color}
\[13:14:26 CDT(-0500)\] {color:black} <alexn> yes NVDA should read out the label - at least it is default behaviour{color}
\[13:14:29 CDT(-0500)\] {color:black} <alexn> although !{color}
\[13:15:06 CDT(-0500)\] {color:black} <alexn> if you use keys 7 and 9 to read through the content. NVDA just reads a chunk of text and then waits for user input so you have to press 7 or 9 multiple times through the content to listen{color}
\[13:15:09 CDT(-0500)\] {color:black} <anastasiac> alexn, NVDA is not reading out a label attached to a link that has link text, it's only reading the link text{color}
\[13:16:19 CDT(-0500)\] {color:black} <alexn> anastasiac: let me double check{color}
\[13:16:42 CDT(-0500)\] {color:black} <cindyli> anastasiac: with Jaws menu: settings center -> web/html/pdfs -> links -> "speak" section -> select the option "longest of above"{color}
\[13:17:04 CDT(-0500)\] {color:black} <alexn> anastasiac: NVDA reads it perfectly fine on the production website{color}
\[13:17:11 CDT(-0500)\] {color:black} <alexn> I'm using default settings{color}
\[13:17:15 CDT(-0500)\] {color:black} <alexn> and IE8{color}
\[13:17:15 CDT(-0500)\] {color:black} <anastasiac> alexn, what does it read?{color}
\[13:17:16 CDT(-0500)\] {color:black} <cindyli> btw, "settings center" inside menu "utility"{color}
\[13:17:27 CDT(-0500)\] {color:black} <jhung> justin_o: glad to hear it! So likely it'll appear as a pair of radio buttons near the top (near the reset link).{color}
\[13:18:02 CDT(-0500)\] {color:black} <anastasiac> cindyli, I choose "settings centre" and nothing happens!{color}
\[13:18:08 CDT(-0500)\] {color:black} <alexn> anastasiac: http://www.oercommons.org/ when I keyboard focus on No Strings Attached - it reads out No Strings Attached and then the content of the popup{color}
\[13:18:30 CDT(-0500)\] {color:black} <anastasiac> ok, alexn, I'll look at that for a model for the mockup{color}
\[13:20:12 CDT(-0500)\] {color:black} <Justin_o> jhung: i'm not sure how the rest of your ui looks.. would it be better to include that close to the actual units{color}
\[13:20:24 CDT(-0500)\] {color:black} <Justin_o> i'm assuming it's for entering units{color}
\[13:20:27 CDT(-0500)\] {color:black} <Justin_o> or is there emore to it{color}
\[13:20:34 CDT(-0500)\] {color:black} <Justin_o> jhung: ^{color}
\[13:24:54 CDT(-0500)\] {color:black} <michelled> alexn: I took a look at your 575 branch - looks good to me{color}
\[13:25:04 CDT(-0500)\] {color:black} <michelled> alexn: please issue a pull request against staging{color}
\[13:26:03 CDT(-0500)\] {color:black} <alexn> michelled: ok. some JS optimization there :P with fluid.each{color}
\[13:27:09 CDT(-0500)\] {color:black} <michelled> sorry, am I missing something alexn - is there some code duplication I didn't notice?{color}
\[13:29:44 CDT(-0500)\] {color:black} <alexn> well yeah. Andrey had like 4 copy pastes{color}
\[13:29:49 CDT(-0500)\] {color:black} <alexn> I made them all into 1 loop{color}
\[13:29:51 CDT(-0500)\] {color:black} <alexn> :p{color}
\[13:30:07 CDT(-0500)\] {color:black} <alexn> https://github.com/anvk/OER-Commons/commit/726207b9f9eadbdba96aaebdd3faf28aecce8c4c{color}
\[13:30:20 CDT(-0500)\] {color:black} <alexn> my branch has only 1 commit really{color}
\[13:30:25 CDT(-0500)\] {color:black} <alexn> so it is easier to see my changes here{color}
\[13:30:27 CDT(-0500)\] {color:black} <michelled> am I looking at the wrong branch alexn? https://github.com/anvk/OER-Commons/compare/ISKME:staging...OER-575{color}
\[13:31:10 CDT(-0500)\] {color:black} <alexn> oh sorry I asked you to review 2 pull requests for 545 and 575{color}
\[13:31:16 CDT(-0500)\] {color:black} <alexn> sorry - I thought you are talking about 545{color}
\[13:31:18 CDT(-0500)\] {color:black} <alexn> :){color}
\[13:31:23 CDT(-0500)\] {color:black} <michelled> ah :){color}
\[13:32:09 CDT(-0500)\] {color:black} <michelled> alexn: I'm still confused - according to our chart 545 is already on production{color}
\[13:32:17 CDT(-0500)\] {color:black} <anastasiac> cindyli, reinstalling Jaws worked - thanks!{color}
\[13:32:19 CDT(-0500)\] {color:black} <michelled> alexn: is there another branch that needs to go in?{color}
\[13:32:39 CDT(-0500)\] {color:black} <alexn> well my change is a part of that 545 major ticket about improving alt text{color}
\[13:32:44 CDT(-0500)\] {color:black} <alexn> should I create a separate ticket{color}
\[13:33:30 CDT(-0500)\] {color:black} <michelled> yes, you should create another ticket - that one was big enough to begin with{color}
\[13:33:36 CDT(-0500)\] {color:black} <alexn> ok my bad - I should open a separate ticket. For some reason I saw the issue in the list of things there hmm{color}
\[13:33:54 CDT(-0500)\] {color:black} <alexn> ok then please ignore my 545 branch for now{color}
\[13:36:02 CDT(-0500)\] {color:black} <michelled> anastasiac: you have 2 563 branches - which one should I look at for the login drop down fix?{color}
\[13:36:45 CDT(-0500)\] {color:black} <anastasiac> sorry michelled: look at 563-account-settings-menu{color}
\[13:36:55 CDT(-0500)\] {color:black} <michelled> thx anastasiac{color}
\[13:42:37 CDT(-0500)\] {color:black} <alexn> michelled: https://github.com/anvk/OER-Commons/tree/OER-595 is the branch now. not sure how to change the comment though.{color}
\[13:50:04 CDT(-0500)\] {color:black} <michelled> anastasiac: there's a conflict when I merge that branch in - could you take a quick look please?{color}
\[13:54:05 CDT(-0500)\] {color:black} <michelled> anastasiac: your 563-account-settings-menu branch looks good - I think you should issue your pull request for staging.{color}
\[13:54:17 CDT(-0500)\] {color:black} <anastasiac> k, thanks michelled{color}
\[13:55:10 CDT(-0500)\] {color:black} <anastasiac> michelled, my fix for the Add OER bookmarked is ready for review: https://github.com/acheetham/OER-Commons/tree/592-add-oer-button{color}
\[14:20:25 CDT(-0500)\] {color:black} <alexn> michelled: I submitted a pull request for OER-596 which should add MyInfusion on production website{color}
\[14:20:32 CDT(-0500)\] {color:black} <alexn> hopefully it will be merged soon{color}
\[14:23:40 CDT(-0500)\] {color:black} <michelled> thx alexn - good find!{color}
\[14:48:30 CDT(-0500)\] {color:black} <michelled> anastasiac: did you mean to add an id to the anchor in 592?{color}
\[14:48:59 CDT(-0500)\] {color:black} <anastasiac> ah, good catch, michelled. That's leftover from when I was testing the label solution. No longer necessary, without the label{color}
\[14:53:35 CDT(-0500)\] {color:black} <michelled> anastasiac: cool - once you remove it from your branch I think you should do a pull request to staging :){color}
\[14:54:08 CDT(-0500)\] {color:black} <anastasiac> k, I'll do that now, michelled{color}
\[15:21:12 CDT(-0500)\] {color:black} <Justin_o> jhung: interesting thing happened.. was just trying to get port forwarding working in my vagrant vm for ubuntu 12.04 and avtar ended up finding a bug in our server code, pretty easy to fix, but could cause a bunch of problems for users trying to configure the server{color}
\[15:22:12 CDT(-0500)\] {color:black} <jhung> justin_o: great. Thanks avtar for catching that.{color}
\[15:22:48 CDT(-0500)\] {color:black} <avtar> glad i could have helped{color}
\[15:25:02 CDT(-0500)\] {color:black} <Justin_o> jhung: here's the jira http://issues.fluidproject.org/browse/DECA-285{color}
\[15:26:59 CDT(-0500)\] {color:black} <Justin_o> jhung: i've added it to our planning page too{color}
\[15:41:43 CDT(-0500)\] {color:black} <anastasiac> michelled, I have a branch for 598 (on of greg's findings) ready for review: https://github.com/acheetham/OER-Commons/tree/598-folder-delete-add-buttons{color}
\[15:42:46 CDT(-0500)\] {color:black} <michelled> thx{color}
\[15:45:19 CDT(-0500)\] {color:black} <michelled> anastasiac: I've looked at your branch for 584 and I think it looks good{color}
\[15:45:25 CDT(-0500)\] {color:black} <michelled> I think you should do a pull request to staging{color}
\[15:45:31 CDT(-0500)\] {color:black} <anastasiac> thanks, michelled, will do{color}
\[15:54:21 CDT(-0500)\] {color:black} <michelled> anastasiac: I think alex already started on 598 - can you check in with him tomorrow? I'm also thinking that we are better to use an image of an 'x' along with a title that says 'delete this folder'.{color}
\[15:55:11 CDT(-0500)\] {color:black} <anastasiac> ok, I'll check with alex tomorrow. I didn't know he was looking at that{color}
\[15:55:39 CDT(-0500)\] {color:black} <michelled> looks to me like cindyli might also have started on this :({color}
\[15:56:03 CDT(-0500)\] {color:black} <anastasiac> how can youtell?{color}
\[15:56:07 CDT(-0500)\] {color:black} <michelled> actually no - I read her assembla issue wrong{color}