2011/8/15 Vincent Massol <[email protected]>

>
> On Aug 15, 2011, at 2:12 AM, 许凌志(Jamesxu) wrote:
>
> > On Mon, Aug 15, 2011 at 1:34 AM, Vincent Massol <[email protected]>
> wrote:
> >
> >> Hi James,
> >>
> >> On Aug 14, 2011, at 11:43 AM, 许凌志(Jamesxu) wrote:
> >>
> >>> Hi, Last week I have done following things:
> >>> 1.Implemented the relative references for link generation
> >>> 2. implemented the default suggestions for sub-trigger "attach:", "."
> and
> >>> "@"
> >>>   The default suggestion for trigger "attach:" is the attachments that
> >>> belongs to recently modified pages.
> >>>   The default suggestion for trigger "." has two different situations:
> >>>     1). when "." is after "attach:" the default suggestion is the
> >>> attachments that belongs to recently modifed pages under the specific
> >> space
> >>>     2). when "." is not after "attach:" the default suggestion is the
> >> wiki
> >>> pages under specific space.
> >>>   The default suggestion for trigger "@" is the attachments that
> belongs
> >>> to the specific wikipage.
> >>> 3. Re-design the interface of the suggestion box according to Marius'
> >>> suggestions, and it attracts some advantages from the suggestion box of
> >>> confluence wiki.
> >>>
> >>> Till now the Major functions for link suggestion of wiki editor has
> been
> >>> done, here is the video of the link suggestion for wiki editor.
> >>> Please see the demo video: http://www.youtube.com/watch?v=2_be-3oqgzE
> >>> In next week, I will do the following things;
> >>> 1. Design the image suggestion functions and discuss with mentors.
> >>> 2. Test the link suggestion functions in IE, chrome, to consider the
> >>> compatibility of the functions.
> >>> 3. Refine the functions accroding to the review of mentors.
> >>
> >> Sounds cool.
> >>
> >> Some questions:
> >> - What's the status of the integration of your code into the platform?
> Is
> >> it ready to be integrated?
> >>
> > Till now, all the functions for link suggestion has been almost done, but
> > indeed I need to clean up the codes, and also make sure it works fine in
> > various mainstream browsers, till now, I only tested it in firefox 4 and
> 5,
> > I think I need a list of browers which the functions should be tested on
> it.
> > Because all I have done is related to js, no java codes, so I think test
> is
> > a problem, I think selemium is a good test tools to test some of the
> > functions, but I still need to discuss with Mentors about the test
> strategy.
>
> Indeed. Jerome Velociter has also committed a JS test framework last week
> (don't remember its name though). Might be interesting for you.
>
So, Jermoe Velociter could you give me some documents about your test
framewokr? and could you give me your irc id?

>
> > - Is it clean code or do you need to clean things up?
> >>
> > Yes, I need to clean some things up, I will do these things this week
> >
> >
> >> - Do you have automated tests for it to prove that it works and that
> it'll
> >> continue to work in the future?
> >>
> > Till now I didn't do automated tests, I need to discuss with mentors
> about
> > the test method and strategies for js and this functions
> >
> >
> >>
> >> Basically I think you should start to focus on the integration
> part/clean
> >> up/stabilization/testing part since the end of summer is approaching
> fast :)
> >>
> > Ok, in this week I will focus on the clean up stabilization and testing
> > part.
>
> Thanks!
> -Vincent
>
> >> Is there a way to test what you have written so far? (it's ok if I have
> to
> >> build it).
> >>
> >> Thanks
> >> -Vincent
> >>
> >>> --
> >>> Best wishes,
> >>>
> >>> 许凌志(Jame Xu)
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>



-- 
Best wishes,

许凌志(Jame Xu)

MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University

Department of Computer Science and Technology, Xi’an Jiaotong University
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to