[Libreoffice-bugs] [Bug 86846] EDITING Feature request: Add code window for editing

2015-01-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=86846

--- Comment #6 from Dr. Matthias Weisser matthias.weis...@gmx.de ---
Thank you Robinson !

Yes - editing XML seems to be more complex compared to the html that I am doing
manually. Therefore having some help for doing correctly would be appreciated.

Often there are same formats used in a text. Seems to be that LO often does not
see that but open up a new format. This makes the code more complex. 

Tools like LaTex are code related - but unfortunately no WYSIWYG feature
simultaneously is possible. 

With LO WYSIWYG is there but unfortunately code quickly is getting much bigger
than needed causing also trouble not forseen when looking on design. 

Therefore a synthesis of LaTex-like code and instantaneous WYSIWYG would be a
good solution.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 86846] EDITING Feature request: Add code window for editing

2015-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=86846

Robinson Tryon (qubit) qu...@runcibility.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #5 from Robinson Tryon (qubit) qu...@runcibility.com ---
(In reply to Dr. Matthias Weisser from comment #4)
 I agree that Reveal Codes (bug 34002) sounds useful. But this must not be
 the same implementation as intended here. It might differ.

Ok

 My feeling is that just having a window showing the Code and having the
 possibility of changing this will be useful as a first step. 

Editing the XML directly sounds kind of cool, but I imagine that it will be
much harder to do (correctly) than editing HTML by hand. For success, I'd
suggest that such an enhancement only be added in conjunction with a validator,
to ensure that whatever a user does by hand is confirmed to be correctly
formatted before we go back to the WYSIWYG environment.

Status - NEW

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 86846] EDITING Feature request: Add code window for editing

2015-01-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=86846

Dr. Matthias Weisser matthias.weis...@gmx.de changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #4 from Dr. Matthias Weisser matthias.weis...@gmx.de ---
I agree that Reveal Codes (bug 34002) sounds useful. But this must not be the
same implementation as intended here. It might differ.

My feeling is that just having a window showing the Code and having the
possibility of changing this will be useful as a first step. 

In addition to this - a Reveal Code feature might be implemented. 

So I see 2 steps of implementation:
1. having this window to see and change source code (I would prefer that).
2. having a feature quickly showing formatting like Reveal Code and being
able to modify easily. A Crossed Eyes feature might be of value. I did not
work with it until now. So hard to tell for me how convenient this is.

Having implemented point 1 it would be more easy finding out about the code
that LO produces and how to influence and change this to a more useful code. So
I feel having point 1 implemented would help getting better code.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 86846] EDITING Feature request: Add code window for editing

2015-01-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=86846

Robinson Tryon (qubit) qu...@runcibility.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||qu...@runcibility.com
   See Also||https://bugs.freedesktop.or
   ||g/show_bug.cgi?id=34002
 Ever confirmed|0   |1

--- Comment #3 from Robinson Tryon (qubit) qu...@runcibility.com ---
(In reply to Dr. Matthias Weisser from comment #0)
 If there is a possibiliy there so have a look at the source code format
 problems can be seen more quickly. They can be changed directly in the code
 window. 

Sounds like you want to add Reveal Codes (bug 34002).

 The feature request consists of:
 Implementation of a code window - may be at the place of the status line.
 This could be switched on and off. The code where the cursor is will be
 shown and can be edited. Change of code will be able to see immediately in
 the normal text.

Ayup.

(In reply to Dr. Matthias Weisser from comment #2)
 There is another issue for this which seems to be of value: Bug 34002.

So is this a dupe of bug 34002, or something different?

Status - NEEDINFO

(please change status back to UNCONFIRMED after replying)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 86846] EDITING Feature request: Add code window for editing

2014-12-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=86846

--- Comment #2 from Dr. Matthias Weisser matthias.weis...@gmx.de ---
Dear Jean Baptiste. I agree that the code in content.xml looks rather chaotic.
But parts of it are quite easy to read and to understand. For example this
clearly can be understood:  

text:p text:style-name=StandardVorbemerkung des Verlags:/text:p 
  text:p text:style-name=StandardDieses Buch dient der Information. Das
Gesagte ist nicht als Therapieempfehlung oder Ersatz professioneller
medizinischer Behandlung bei gesundheitlichen Beschwerden zu
verstehen./text:p 
  text:p text:style-name=P64 / 
  text:p text:style-name=P64 / 
  text:p text:style-name=P64 / 
  text:p text:style-name=P64 / 

text:h text:style-name=P323 text:outline-level=2Besser überleben trotz
Krebs/text:h 
- text:p text:style-name=Standard
  Am Ende des zweiten Weltkriegs litten die meisten Krankenhauspatienten an
Lungenentzündung. Es dauerte nicht lange, bis sich die Bakterien so weit
vermehrt hatten, dass sie von den Lungen ins Blut gelangten. Das Fieber stieg
auf 40.5°C. Wenn die Haut dabei trocken und heiß blieb starb das Opfer.
Schwitzen bedeutete die Rettung. Die Chance zu überleben lag bei etwa 50%. Fast
10 Amerikaner starben jedes Jahr, bis dann Hilfe kam durch Penicillin in
Form eines weißen Pulvers 
- text:note text:id=ftn61 text:note-class=footnote
  text:note-citation61/text:note-citation 
- text:note-body
  text:p text:style-name=FootnoteBecker, Seldon: „The body electric“
S.17f/text:p 
  /text:note-body
  /text:note

For me it would be helpful seeing this in a window and being able to edit.
Sometimes its much easier seeing this code instead of clicking through a lot of
menues. 

There is another issue for this which seems to be of value: Bug 34002. For Word
there is a tool CrossEyes for detecting/fixing problems in code not so easy
to be seen without such a tool. Productivity seems to be improved that way.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 86846] EDITING Feature request: Add code window for editing

2014-12-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=86846

Jean-Baptiste Faure jbfa...@libreoffice.org changed:

   What|Removed |Added

 CC||jbfa...@libreoffice.org

--- Comment #1 from Jean-Baptiste Faure jbfa...@libreoffice.org ---
How do you handle styles in such a code window? I suggest you to have a look at
what is really an OpenDocument file. To do that, take some .odt file, rename it
as .zip and open it in your preferred archive manager software. The text of
your document is managed in content.xml and styles are in styles.xml.

Best regards. JBF

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs