Ticket #1446 (closed defect: fixed)

Opened 13 years ago

Last modified 13 years ago

Resources created with Kupu in Safari look messed up

Reported by: hans Owned by: gabor
Priority: major Milestone:
Component: generic Version:
Keywords: Cc:
Time planned: Time remaining: 0h
Time spent: 23.0h

Description (last modified by hans) (diff)

Resources created with Kupu in Safari look messed up, because line breaks are not handled in any way: http://lemill.net/methods/connect-the-dots/view

HTML code (without <p> tags):

<h2>Or 'Travel the subject area with tickets'</h2>

If the subject of course has clear borders -- timeframe, area, anatomical area, some ecosystem etc, it often divides itself into subsections and research topics. However, having a student or group to do project from one of these topics or subsections easily transforms into learning something about one special topic and repeating it to other students. It gets difficult to grasp the whole picture.

One way to really <b>explore</b> the course area is to set two points for each student/group and have them to examine how they affect each others, aka map the route from one topic to another.

The way how course material is organized usually provides one route that goes through all of the topics in some order. Topics that are too close to each others in course material are not so good, as the most interesting routes are between two far-away subjects.

So we'll find unintuitive combinations by picking topics randomly.

Course material is usually organized so that subjects that are closely related are also close to each other in time spent studying and the flow of text tries to create links between sections and chapters. This creates the basis for some subjects being 'close' to each others and their relationship being easy to explain by just repeating what was said in course material.

One quick and easy method for creating topics is to take all of the subheadings from the text (you don't have to use only headings, add keywords and interesting bits as you like) and write each of them to small piece of paper. Now each student picks randomly two of these 'tickets' and then student and teacher together try to figure out if there could be any meaningful connection between them, connection or story worth telling. If the connection is obvious, then one of the tickets is dismissed and another ticket taken. If the connection is difficult to find, but can be found, then the task is good. Student doesn't have to understand the route yet, but teacher should provide some hints about where to go. 

When several students share one same ticket in their route, it should be possible to connect their routes too, but at this point there can rise differences between interpretation of topic. This happens in science all the time and should be noted. 

At some point it will be natural to draw a map of all of these topics and draw the links that students have created into it. The original 'text-book-route' should also be there.  

With older students essay topics can be created this way, but again, choosing the two topics should be supervised so that obvious ones are not used. 




kupu_safari_line_breaks.png (150.8 KB) - added by hans 13 years ago.

Change History

Changed 13 years ago by hans

comment:1 Changed 13 years ago by hans

  • Description modified (diff)

comment:2 Changed 13 years ago by gabor

It looks like kupu's visual editor is not working under Safari, only the basic one. So currently people must write exact HTML codes with <br /> tags to create line breaks. But if the author writes the text in the visual editor with another browser the page will look fine in Safari, too.

comment:3 Changed 13 years ago by hans

Majority of our users are teachers. They know nothing about HTML tags and the idea of LeMill is to enable them to create web-based learning resources without knowledge of HTML.

People who use Mac and Safari probably do not even know that they will see a different editor in IE/Mozilla. If they create seperate paragraphs with two line breaks, then these line breaks should be converted to </p><p> and displayed correctly.

We have fixed and recreated this defect for several times. Maybe Jukka can join this discussion?

comment:4 Changed 13 years ago by gabor

  • Owner changed from anonymous to gabor
  • Status changed from new to assigned

comment:5 Changed 13 years ago by gabor

  • Status changed from assigned to closed
  • Time spent set to 6.0h
  • Resolution set to fixed
  • Time remaining set to 0h

(In [1898]) fixed #1446 spent 6h

comment:6 Changed 13 years ago by gabor

Fixed, but this problem only occured when there were some HTML tags in the text. So if there were HTML tags <br /> tags would be necessary. If there were no HTML tags kupu would automatically formatted the texts with HTML tags.

But now it works ok with HTML texts that don't have <br /> tags.

comment:7 Changed 13 years ago by gabor

  • Status changed from closed to reopened
  • Resolution fixed deleted

I reopen this ticket because I'm not happy with the solution. I think there should be a checkbox to disable/enable the replace of the new line characters. So people who copy HTML text won't have a problem.

comment:8 Changed 13 years ago by gabor

  • Status changed from reopened to new

comment:9 Changed 13 years ago by gabor

  • Status changed from new to closed
  • Time spent changed from 6.0h to 23.0h
  • Resolution set to fixed

(In [1904]) fixed #1446 spent 17h

comment:10 Changed 13 years ago by gabor

(In [1905]) ref #1446

Note: See TracTickets for help on using tickets.