<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi, Sam<br>
<br>
I don't see any relevance to a package manager for an installed
Sugar system. One of Sugar's major benefits is that users can modify
the source of any file and immediately see the consequences. Any
user who can open the Terminal activity can type 'sudo rm -rf' to
great effect. <br>
<br>
If we are going to introduce users to creating and editing fonts
they need to learn CRUD (Create, read, update, delete). Naturally,
the editor can caution about the effect of modifying or deleting
system fonts (and probably identifying them). Hopefully, our user
will be able to make her font the system font.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 07/03/2016 12:49 PM, Sam Parkinson
wrote:<br>
</div>
<blockquote cite="mid:1467542958.1994.1@smtp.gmail.com" type="cite">Hi
Tony,
<div><br>
</div>
<div>I agree with you that we should avoid "training wheels".
However, I don't think that we should unintentionally let users
break the system - we still need to have clear ui. If we are
going to let users uninstall system files, we should at least
warn them.</div>
<div><br>
</div>
<div>Also, in my opinion, if we are going touch files the package
manager installed, we should do that via the package manager.
Package managers are amazing, and we don't need to make their
job harder. However, integrating package manger support would
be a very hard task, and maybe it would be easier to just not
expose a delete ui for system fonts?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam<br>
<br>
On Sun, Jul 3, 2016 at 8:33 PM, Tony Anderson
<a class="moz-txt-link-rfc2396E" href="mailto:tony_anderson@usa.net"><tony_anderson@usa.net></a> wrote:<br>
<blockquote type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
Hi Sam,<br>
<br>
I have enjoyed this sort of comment before. We go to great
trouble to show users the source code of Sugar with the
apparent intent that they should <br>
experiment with making changes. Then developers comment, but
'they could break the system!'. What is wrong with giving the
users the opportunity to delete a font and see the
consequences. That is how we learn. Do we really want a Sugar
with 'training wheels'?<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 07/02/2016 02:40 PM, Sam
Parkinson wrote:<br>
</div>
<blockquote cite="mid:1467463253.2045.2@smtp.gmail.com"
type="cite"> <br>
<br>
On Sat, Jul 2, 2016 at 6:35 PM, Yash Agarwal <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:agrwal.ysh94@gmail.com"><a class="moz-txt-link-rfc2396E" href="mailto:agrwal.ysh94@gmail.com"><agrwal.ysh94@gmail.com></a></a>
wrote:<br>
<blockquote type="cite">
<p dir="ltr">Work report <br>
I worked on the following issues:<br>
Adding support for ufoz format <br>
Adding git submodules<br>
The editor has been integrated with the activity </p>
<p dir="ltr">I'll begin adding the features for
manipulating the bezier curves over the weekend <br>
I'll make the complete week report on Sunday </p>
<p dir="ltr">A question to ponder upon:<br>
Should we make 2 separate activities <br>
A font manager <br>
A font editor<br>
The manager will have root access and be integrated into
sugars glucose module (correct me if I'm wrong) so that
it's there with the pre installed activities<br>
The editor will be separate and will only deal in ufoz
/ufo format </p>
</blockquote>
<div>Hi Yash,</div>
<div><br>
</div>
<div>Why do we need root to install fonts? Can't you just
manage the fonts in "~/.fonts" and call the rest of the
fonts system fonts. We really shouldn't make it easy for
users to delete system fonts - it will annoy the package
manager and it will probably break applications. We don't
want users thinking "I don't use Deja Vu Sans" and then
having a very odd looking Sugar because they uninstalled
the font we use in the UI.</div>
<div><br>
</div>
<div>Maybe it would be best to add a control panel for
fonts? Activities must have state, and write something to
the journal. Control panels don't have to write a state
to the journal. Control panels are "extensions" in sugar
terms, meaning they are loaded from either
"/usr/share/sugar/extensions/cpsection/" or
"~/.sugar/$SUGAR_PROFILE/extensions". This means that you
could include the font control panel extension with your
app, and then install it on your app's first run.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam</div>
<br>
<blockquote type="cite"> <br>
<div class="gmail_quote">
<div dir="ltr">On Thu, 30 Jun 2016 21:28 Dave Crossland,
<<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:dave@lab6.com">dave@lab6.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Great
stuff Yash!<br>
<br>
The blog needs a bit of attention...<br>
<a moz-do-not-send="true"
href="https://github.com/sugarlabs/edit-fonts-activity/commit/cbdfaf2a2c5320ac417124ebd050087588cd4e6c"
rel="noreferrer" target="_blank">https://github.com/sugarlabs/edit-fonts-activity/commit/cbdfaf2a2c5320ac417124ebd050087588cd4e6c</a><br>
is posted 10 days ago, but it wasnt on a friday, which
is when we have<br>
to check in with walter, so I renamed it to<br>
<a moz-do-not-send="true"
href="https://sugarlabs.github.io/edit-fonts-activity/bezier-editing-works"
rel="noreferrer" target="_blank">https://sugarlabs.github.io/edit-fonts-activity/bezier-editing-works</a><br>
<br>
However, you've then duplicated this file and appended
to it -<br>
<a moz-do-not-send="true"
href="https://sugarlabs.github.io/edit-fonts-activity/week-5-work"
rel="noreferrer" target="_blank">https://sugarlabs.github.io/edit-fonts-activity/week-5-work</a>
- so that<br>
its the same at the top<br>
<br>
Please remove duplicate content :)<br>
<br>
Also <a moz-do-not-send="true"
href="https://github.com/sugarlabs/edit-fonts-activity/blob/gh-pages/_posts/2016-06-28-week-5-work_wip.md"
rel="noreferrer" target="_blank">https://github.com/sugarlabs/edit-fonts-activity/blob/gh-pages/_posts/2016-06-28-week-5-work_wip.md</a><br>
seems to be not needed, so I made a PR to remove it,<br>
<a moz-do-not-send="true"
href="https://github.com/sugarlabs/edit-fonts-activity/pull/47"
rel="noreferrer" target="_blank">https://github.com/sugarlabs/edit-fonts-activity/pull/47</a><br>
<br>
Since (a) you can set a post to not be published if
you want to draft<br>
it on gh-pages, and (b) you can draft it in a git
branch and only<br>
merge it when its ready, I suggest not creating such
WIP files in<br>
future :) I have been trying to make blog posts with
the (b) process<br>
but (a) is also fine, as you did in<br>
<a moz-do-not-send="true"
href="https://github.com/sugarlabs/edit-fonts-activity/commit/6507a9efbb266d31deadd3d4fccf5f190e6f8af0"
rel="noreferrer" target="_blank">https://github.com/sugarlabs/edit-fonts-activity/commit/6507a9efbb266d31deadd3d4fccf5f190e6f8af0</a><br>
:)<br>
<br>
Secondly, the filename of a Jekyll post must be unique
after the date,<br>
so I made a PR to rename the latest features
checklist,<br>
<a moz-do-not-send="true"
href="https://github.com/sugarlabs/edit-fonts-activity/pull/48"
rel="noreferrer" target="_blank">https://github.com/sugarlabs/edit-fonts-activity/pull/48</a><br>
<br>
Please do review and merge these when you can :)<br>
</blockquote>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>