Hi Jason,
I have gone through the attached document, on a quick glance I could
get the structure but understanding the details is taking time for me. I
would like to know how my work can compliment yours on the front end. In
sense it would great if you could sketch an outline of what features from
the backend (There was a section in the document on what you expected from
the backend) you would like me to work on so that the editor could be more
complete. I guess we need to work on this as the deadline is fast
approaching. I would like to know if we could communicate via irc at some
particular time. It would give a more clearer picture to construct our
proposals as well. Thanks.
On Mon, Mar 17, 2014 at 11:21 PM, Jason Suagee <[email protected]> wrote:
> Hi Amit, I looked at your proposal and it looked good. I also look forward
> to potentially working with you.
>
> I still have to upload official documentation that I am a current student
> at my university, so I am unable to submit the proposal at the moment.
> There is a big snow storm where I am now which will prevent me from going
> to my university to get this document until tomorrow. I will go in tomorrow
> so that I can submit the proposal. In the meantime I will include a draft
> in a pdf attachment. (I'll have to translate it to the appropriate format
> later before I submit it.)
>
> In the draft I do not talk about the interface between the Sage notebook
> and the javascript/canvas element where the knot plotting will be done. The
> canvas element is what I would like to use to do the rendering of the knot.
> This is a good reason to have a contact point who knows about the Sage
> interface to the canvas (specifically, the show() or plot3d() methods, if
> you pass them the keyword viewer=canvas3d, will use the use the canvas
> element to display the plot. How all this comes together I haven't figured
> out yet.)
>
> The draft does not contain any mention of classes or deliverables yet. I
> mainly thought out most of the algorithmic details. I also have not
> included a timeline yet. Your comments would be appreciated.
>
> On Monday, March 17, 2014 1:07:45 PM UTC-4, Amit Jamadagni wrote:
>
>> Hello all,
>> I am been working on my proposal for the implementation on the
>> back-end. I have posted the link to my proposal on the other google thread
>> (I kindly request to refer to it for all the details). I am really looking
>> forward to discuss the ideas of how we can get the entire machinery
>> (back-end + front-end) to work. I hope we (It would be great if the
>> discussion can be done in the presence of our mentor) can discuss it here
>> or on irc chat about what we require in common and on how one could
>> facilitate as well compliment each other's work keeping it as independent
>> as possible. Thanks.
>>
>>
>> On Mon, Mar 17, 2014 at 6:53 PM, Miguel Angel Marco <[email protected]
>> > wrote:
>>
>>> How is the proposal writing going? Amit Jamadagni is working on a
>>> proposal for the backend part. Maybe it could be a good idea if you two got
>>> in contact and shared some ideas.
>>>
>>>
>>> El martes, 4 de marzo de 2014 13:25:59 UTC+1, Jason Suagee escribió:
>>>
>>>> Hello Sage mentors and fellow posters,
>>>>
>>>>
>>>> My name Jason Suagee and I'm a 4th year PhD student in mathematics at
>>>> George Washington University in Washington DC. I am primarily interested in
>>>> working on a javascript editor for manipulating knot diagrams as part of
>>>> the knot theory project. My background in knot theory comes mostly from
>>>> Rolfsen's classical Knots and Links book, which was the primary textbook
>>>> for a two semester course in knot theory that I am currently taking this
>>>> academic year.
>>>>
>>>>
>>>> In my own work I focus on symmetric combinatorial decompositions of
>>>> 3-manifolds, which is a cross between low dimensional topology and
>>>> topological graph theory. Where this intersects with knot theory is that
>>>> much of knot theory is actually used as a tool to describe 3-manifolds. In
>>>> particular, one of the most useful methods to present a 3-manifold is by
>>>> performing Dehn surgery on the components of a link in S^3. So manipulation
>>>> of link diagrams can be a big part of what low dimensional topologists do
>>>> on a regular basis.
>>>>
>>>> But manipulating a link diagram on paper can be a real headache, as I
>>>> have found out this year. It would be beneficial if there was a graphical
>>>> way by computer to do these manipulations. I have thought out a rough
>>>> framework with which to approach this design problem and will share it in
>>>> the post below.
>>>>
>>>>
>>>> By the way, I have been a Sage user for the past 4 years and love it!
>>>> I was quite happy to sport a Sage sticker at the joint math meeting this
>>>> year in Baltimore.
>>>>
>>>>
>>>> Best,
>>>>
>>>> Jason
>>>>
>>>> [email protected]
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-gsoc" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>>
>>> Visit this group at http://groups.google.com/group/sage-gsoc.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "sage-gsoc" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/sage-gsoc.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"sage-gsoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-gsoc.
For more options, visit https://groups.google.com/d/optout.
