Skip to end of metadata
Go to start of metadata

[09:06:16 CDT(-0500)] <vevo_> hello I am a student from India. I want to be a part of fluid and want to work on HTML5 Image editor. I have good experience in html,css and js and have some familiarity with HTML5 too. Where should I start working. Should I start by building a simple fluid component?

[09:07:58 CDT(-0500)] <jessm> vevo_: welcome, you'll need to get information from Justin_o or jhung when he's around

[09:08:31 CDT(-0500)] <Justin_o> vevo_: hello.. it would be good to get some experience working with Infusion. I think that would be a good place to start.

[09:10:53 CDT(-0500)] <jhung> Hi vevo_ let me know if you have any questions about the Image Editor project.

[09:13:21 CDT(-0500)] <vevo_> jhung: have you already started developing the editor?

[09:14:50 CDT(-0500)] <jhung> Not for this specific editor.

[09:15:44 CDT(-0500)] <jhung> There was a project from last year's GSoC that is similar, but we're encouraging new ideas, vevo_.

[09:15:44 CDT(-0500)] <pulkit> Hi Justin_o, jhung I worked on HTML5 Image Editor project last year. Would this year's image editor be done as an extension of that?

[09:16:22 CDT(-0500)] <jhung> Hi pulkit, yes this would be an extension or a sibling to the project you did last year.

[09:17:37 CDT(-0500)] <pulkit> Thanks. I had some questions about the JSON exports. Should it contain the operations that have been applied on the image and then have the importer reapply the same operations again when the image is imported back?

[09:20:23 CDT(-0500)] <jhung> Pulkit, yes that's the idea. This way an image can remain intact while its processing information accompanies it.

[09:26:36 CDT(-0500)] <pulkit> Yes. Thanks

[09:30:10 CDT(-0500)] <pulkit> And for skew correction, the image editor is probably expected to correct a known skew or should it also try to detect the skew angle itself?

[09:38:42 CDT(-0500)] <jhung> Hi pulkit, it would be great if it did both (automatic and manual) skew correction. In the end we have to think about the end user and try to figure out what will be most useful to them.

[09:39:19 CDT(-0500)] <pulkit> jhung: Thanks. Just one last question. Would the browser support be the same as last year?

[09:41:20 CDT(-0500)] <pulkit> Yes, I thought that if we could give good visual feedback to the user (e.g. if the user could just correct the skew in real time), the detection might not be required.

[09:41:49 CDT(-0500)] <jhung> Firefox is the primary browser, although it would be great to see it working in other browsers as well.

[09:44:56 CDT(-0500)] <jhung> pulkit, you may be right about that (re: good visual feedback vs. automatic skew correction). The implementation will be important to how well it works out.

[09:45:17 CDT(-0500)] <pulkit> Yes

[13:04:54 CDT(-0500)] <RUPO> I want to talk about the gsoc project ,is the mentor online?

[13:05:20 CDT(-0500)] <greggy> RUPO: which project?

[13:05:45 CDT(-0500)] <RUPO> html5 image editor

[13:07:47 CDT(-0500)] <greggy> Justin_o: ^

[13:07:58 CDT(-0500)] <greggy> jhung: ^

[13:09:19 CDT(-0500)] <Justin_o> greggy: thanks

[13:09:23 CDT(-0500)] <Justin_o> RUPO: hello..

[13:09:33 CDT(-0500)] <RUPO> hi..

[13:10:10 CDT(-0500)] <RUPO> I am from India.

[13:10:39 CDT(-0500)] <RUPO> I am pursuing undergrad in computer science.

[13:11:03 CDT(-0500)] <Justin_o> RUPO: great, what made you interested in this project?

[13:12:20 CDT(-0500)] <RUPO> I am very much interested in HTML5. I think I good at what your project searches for.

[13:12:44 CDT(-0500)] <RUPO> I have made UI with HTML5 and Jquery.

[13:15:23 CDT(-0500)] <RUPO> I have also created web app for android.

[13:19:07 CDT(-0500)] <RUPO> Since I have just completed 1 and half a year of my course, I have been trying to work for an open source project. But could not succeed. I think this is my opportunity to contribute.

[13:23:47 CDT(-0500)] <RUPO> Justin_o: Are you there?

[13:24:13 CDT(-0500)] <Justin_o> RUPO: sorry, missed your replies

[13:25:02 CDT(-0500)] <RUPO> should I reply again?

[13:25:53 CDT(-0500)] <Justin_o> RUPO: okay.. 2 things 1) you'll need to write up a proposal for the project and we'll take a look at it to consider for GSoC.. 2) you are more than welcome to volunteer for our open source projects whether or not your take part in GSoC

[13:26:44 CDT(-0500)] <RUPO> Thank you for your reply.

[13:27:08 CDT(-0500)] <RUPO> Where shall I send my reply?

[13:27:22 CDT(-0500)] <Justin_o> RUPO: you mean your proposal?

[13:27:50 CDT(-0500)] <RUPO> yes sir.

[13:30:11 CDT(-0500)] <RUPO> waiting for your reply sir.

[13:30:41 CDT(-0500)] <Justin_o> RUPO: sorry was looking up the url.. you should be able to find info about applying on this page

[13:31:00 CDT(-0500)] <RUPO> Thank You. (smile)

[13:31:08 CDT(-0500)] <Justin_o> no problem, good luck

[13:32:17 CDT(-0500)] <RUPO> I will try to make it as soon as possible and hope to get selected. Thanx for wishing me luck.

[13:48:02 CDT(-0500)] <Justin_o> fluid-everyone: new jira project for Floe at

[13:48:17 CDT(-0500)] <Bosmon> Thanks, O KINGG

[14:17:27 CDT(-0500)] <Justin_o> Bosmon: np

[14:35:17 CDT(-0500)] <michelled> alexn, anastasiac: I've updated the demo plan page that Alex put up with our names:

[14:48:45 CDT(-0500)] <am33sh> hi everyone

[14:49:47 CDT(-0500)] <am33sh> yura : i have made a sample page to know how the UI options of fluid works

[14:51:15 CDT(-0500)] <yura> am33sh: that's awesome

[14:54:55 CDT(-0500)] <am33sh> yura : its been working but when i change the text display property then property of all the page change so to use it in another page i have made use of iframe tag, so that only the text between iframe tag changes

[14:55:46 CDT(-0500)] <Bosmon> am33sh - to make UIOptions work across frame boundaries is a current project, but it can't be achieved simply from standard HTML and JavaScript

[14:55:57 CDT(-0500)] <Bosmon> This requires either a GreaseMonkey plugin or a browser extension

[14:56:30 CDT(-0500)] <Bosmon> Security restrictions prohibit a web page from modifying the state of a page which was served from a different domain

[14:56:50 CDT(-0500)] <am33sh> bosmon : okay

[15:00:09 CDT(-0500)] <am33sh> bosmon, yura : so to use the reader, one has embedd it using iframe tag in his/her website. is it okay?

[15:00:36 CDT(-0500)] <yura> am33sh: it it not desirable as it has some accessibility implications

[15:00:40 CDT(-0500)] <yura> it is*

[15:00:49 CDT(-0500)] <Bosmon> am33sh - I'm not fully familiar with the details of the project - but if the reader's interface is required to be affected by UIOptions, you will need to use a different embedding strategy

[15:01:02 CDT(-0500)] <Bosmon> The reader's interface will have to become a "widget" which can be hosted in any HTML page

[15:01:23 CDT(-0500)] <Bosmon> So, for example, to render using markup templates which are fetched via AJAX or a similar approach

[15:01:46 CDT(-0500)] <am33sh> yura, bosmon : i get it

[15:02:36 CDT(-0500)] <yura> thanks, Bosmon

[15:25:36 CDT(-0500)] <colinclark> michelled: The last ISO version of, as they call it, "Access for all" is available in our wiki:

[15:26:00 CDT(-0500)] <colinclark> At some point, you'll be interested to take a quick scan over Part 3, the "Digital Resource Description," or DRD

[15:26:17 CDT(-0500)] <michelled> thx colinclark

[15:26:45 CDT(-0500)] <colinclark> There are some interesting pieces of metadata that we can probably automatically fill out by nature of the authoring tool itself...

[15:27:06 CDT(-0500)] <colinclark> "Adaptability," such as "Display transformability" for example

[15:28:00 CDT(-0500)] <colinclark> Put another way, I think this "conceptual checkbox" can always be checked for an authoring tool that is Learner Options-aware

[15:28:05 CDT(-0500)] <colinclark> "Display transformability specifies how the display or presentation of a resource (e.g., font colour, font size, background colour, layout, image size) is amenable to transformation. It can be determined using a number of available Web content evaluation and repair tools 4)."

[15:30:40 CDT(-0500)] <michelled> ah, that's great

[15:31:20 CDT(-0500)] <colinclark> We'll be able to find a few of these things that are either very straightforward or easy to derive

[15:36:55 CDT(-0500)] <Bosmon> colinclark - what kind of scheme are we expecting to use to associate this metadata with the described resource?

[15:37:00 CDT(-0500)] <Bosmon> Some kind of "microformat"?

[15:37:44 CDT(-0500)] <colinclark> Yeah, I think something in harmony with or a micro format is probably our best bet.

[15:37:53 CDT(-0500)] <colinclark> For now, we probably only need the user interface for it

[15:38:04 CDT(-0500)] <Bosmon> To display the record somehow, on demand?

[15:39:06 CDT(-0500)] <colinclark> I more meant that we need to show a little bit of this accessibility metadata in the "Describe this Resource" section of the authoring tool

[15:39:26 CDT(-0500)] <Bosmon> ok, cool

[15:39:34 CDT(-0500)] <colinclark> for now, I can imagine data- attributes or something might be the easiest way to store it, if we need to

[15:39:46 CDT(-0500)] <Bosmon> How are we planning to integrate our work with ANDREY?

[15:39:59 CDT(-0500)] <Bosmon> I assume, in the first instance, we will just make a github fork and hack on his stuff directly?

[15:40:04 CDT(-0500)] <colinclark> Interestingly, I think latest IMS draft of AccessForAll is probably even more amenable this this sort of "micro format" storage of the metadata

[15:40:30 CDT(-0500)] <colinclark> I think we'll probably do the best we can to work in small chunks and make useful pull requests

[15:40:40 CDT(-0500)] <colinclark> Ideally, we'll just contribute this stuff back quickly

[15:40:48 CDT(-0500)] <colinclark> in practice, maybe we'll have to work faster than that

[15:40:53 CDT(-0500)] <colinclark> but we'll try to realize the ideal

[15:41:02 CDT(-0500)] <colinclark> and otherwise fork and hack

[15:41:30 CDT(-0500)] <Bosmon> Have we confirmed that his stuff is in COFFESCRIPT?

[15:41:34 CDT(-0500)] <Bosmon> Will our contributions be in that language?

[15:41:45 CDT(-0500)] <colinclark> Yes, he has confirmed that he's making a wholesale migration to CoffeeScript

[15:41:55 CDT(-0500)] <colinclark> He still has some JavaScript, but it's headed towards Coffee

[15:42:09 CDT(-0500)] <colinclark> Love it or hate it, we'll contribute back in CoffeeScript, too

[15:42:27 CDT(-0500)] <colinclark> Since, as we noticed yesterday, it's just largely JavaScript with less punctuation

[15:43:26 CDT(-0500)] <Bosmon> It appears that at least JSON literals are supported in COFFESCRIPT (smile)

[15:43:47 CDT(-0500)] <Bosmon> Which means that, in theory, we shouldn't be bothered too much by whatever other syntax it provides......

[15:44:09 CDT(-0500)] <Bosmon>

[15:44:16 CDT(-0500)] <Bosmon> I'm intrigued by the comment "almost all"...........

[16:06:44 CDT(-0500)] <colinclark> Bosmon: Slightly scary, but I guess we'll see how it goes

[16:08:47 CDT(-0500)] <Bosmon> I am yet to find examples of what valid JSON are not valid Coffescript, but hopefully the examples are negligible

  • No labels