<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Axel, I'm on the list (though i
haven't had the time to be particularly vocal).<br>
<br>
-Magnus<br>
<br>
P.S. Yes, this is the email i use for mozilla related activities.<br>
<br>
On 17/07/2012 04:14 PM, Axel wrote:<br>
</div>
<blockquote cite="mid:5005652A.2020902@gmail.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
I would also like to involve Magnus Melin (:mkmelin)[*] and
whoever wrote (could have been John or Jonathan N, but I could be
wrong - not sure) some prototype code on Composer replacement in
this discussion. <br>
<br>
If you know who I mean, can somebody forward this to them on
behalf of Tb-Planning?<br>
<br>
Axel<br>
<br>
[*]Magnus' email link is on the Modules page, but it is broken or
beyond my understanding<br>
<br>
<br>
<blockquote class=" cite" id="mid_50054AE6_7050203_gmail_com"
cite="mid:50054AE6.7050203@gmail.com" type="cite">
<div id="smartTemplate4-template"><i>Following up: </i>What's
the status of papercuts?<br>
<i><br>
</i></div>
<br>
<div id="smartTemplate4-template">Since replacing the complete
composer is probably to big a task for the scope of papercuts
I would like to discuss a number of enhancements to enhance
the current (html) composer functionality:<br>
<br>
<h3>Color Selection</h3>
<a moz-do-not-send="true"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=453853"><b>Bug 453853</b></a>
-<span id="summary_alias_container"> <span
id="short_desc_nonedit_display">Unable to set hex value
for background color in the color picker</span> </span><br>
<br>
I would like to rename this to (upgrade color picker to allow
more color selections). Unfortunately I do not have
Thunderbird bugzilla admin rights, and maybe there is another
bug on this elsewhere [I searched for Tb/Compose + {color
picker} and for Tb/Compose + {colors} ]?<br>
<br>
A quick way would probably be if we could include
rainbowpicker into the core code (obviously after asking its
author)?<br>
<br>
<h3>Format Painter</h3>
"A copy format" function is badly needed. One problem
currently is that a lot of the built in formatting tools
actually insert tags (such as <big> <b> <i>)
rather than styles, so a more fundamental problem must be
addressed first:<br>
<br>
<h3> CSS Property Editor</h3>
Image > Advanced property editor Enhancements<br>
<br>
I wonder if this could be generalized to apply CSS properties
to all sorts of tags (not just img). Ideally I would like the
possiblity to select a paragraph (which we should be able to
turn from a <br>....section...<br> into a
<p>..</p> pair, and then select something like a
"layout" option.<br>
<br>
As a starting point we could use the "Inline Style" tab of the
"Advanced Property Editor" and add a dropdown to the Attribute
field. The tricky bit is to select the correct tag (probably
the nearest enclosing tag) and to visually represent this in
the Editor window.<br>
<br>
<img src="cid:part2.09030207.03040502@iki.fi" alt=""><br>
For this particular purpose (increasing style expressiveness
in the WYSIWIG editor, via inline styles) I would chose to
remove the tabs "HTML attributes" and "Javascript Events" and
focus on css styles alone. ONe thing that Thunderbird does
very badly at the moment is to expose the current expressive
power it has via CSS3 to the ordinary user. Most other rich
editors have some sort of a "x-ray" mode where special
(meta-)characters such as tabs, line feeds, section breaks
etc. are displayed; what I would like to have is something
generic that shows enclosing tag pairs (or an outline around
html constructs) so that they can easily be spotted and
manipulated. This is actually the hard part of this
enhancement, but I think discussion of this would be fruitful.<br>
<br>
Rationale:<br>
<br>
Currently, the only way to create an email with "clean
markup" is by using extensions that expose HTML source, which
works for me, but not most ordinary users. As <i>first step</i>
we could make it easier to add inline styling via the method
above; this will make it easier for users to discover layout
features of Composer. As a <i>second</i> <i>step</i> we
might then later encapsulate the interface so it can be used
by users who do not know CSS.<br>
<br>
I would love to be involved in such composer improvements, but
I would also like to assess as to what other ideas or maybe
code fragments are already out there. Therefore I am currently
holding off on filing new (or re-appropriating existing) bugs
on this and adding them to the papercuts list, until I have a
feel for what the opinions on the list on this are.<br>
<br>
I would also hope that we can spend some time during MozCamp
to discuss the composer piece in order to devise a short term
strategy for pulling this thing back into the 21st century.<br>
<br>
regards<br>
Axel<br>
<br>
<div id="mySignature" style="width: 65%; padding: 0.8em 1.2em;
font:x-small verdana; color: #444; box-shadow: 4px 4px 9px
-2px rgba(0,0,0,0.65); border-radius: 1em; padding: 0.4em
2em; border: 1px dashed #444; background:
-moz-linear-gradient(top, rgba(230,240,163,1) 0%,
rgba(210,230,56,1) 50%, rgba(195,216,37,1) 51%,
rgba(219,240,67,1) 100%);"> <b class="myName"
style="text-shadow: 1px 1px 2px
#DDD;cursor:pointer;-moz-transition-property:font-size;
-moz-transition-duration: 0.5s;">Axel Grude</b> <br>
Software Developer <br>
Thunderbird Add-ons Developer <span style="color:#666666;
font-size:xx-small">(QuickFolders, quickFilters,
QuickPasswords, Zombie Keys, SmartTemplate4)</span> <br>
AMO Editor </div>
<hr>
<div id="newHeader"> <b>To: </b>"tb-planning"<a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:tb-planning@mozilla.org"><tb-planning@mozilla.org></a>
<br>
<b>From: </b>"Chris Ilias"<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:tb-planning@ilias.ca"><tb-planning@ilias.ca></a><br>
<b>Sent: </b>Saturday, 09/06/12 06:49:37 06:49 GMT Daylight
Time +0100 <br>
<b>Subject:</b>What's the status of papercuts?</div>
</div>
<blockquote class=" cite" id="mid_4FD2E3F1_7060000_ilias_ca"
cite="mid:4FD2E3F1.7060000@ilias.ca" type="cite">In late
March, Blake sent an email listing UX priorities, including
papercuts. If I do a search for TB and mailnews core bugs with
[UXprio] that are fixed since March 24, I only get one bug
(508776). Has there been any priority given to those bugs? <br>
_______________________________________________ <br>
tb-planning mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
<br>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tb-planning mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>