<div dir="ltr">Today's Work, <div>all of the time went in building the Font Manager GUI</div><div>I got stuck at creating a clickable CellRendered Icon (you can find the issue <a href="https://github.com/sugarlabs/edit-fonts-activity/issues/16">here</a>) which will be used for both setting fonts at favorites(in the first column) and another one to activate/deactivate the font(in the last column)</div><div>@Dave I think I'll leave this bug for now until someone comes forward with a hint and complete rest of the things</div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">I apologise for the delay in this, I didn't account for the excess time gone in this bug</span><br></div><div><div><span style="line-height:1.5">I plan to build the stable .xo over the weekend </span></div><br class="inbox-inbox-Apple-interchange-newline"></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 24, 2016 at 12:45 PM Yash Agarwal <<a href="mailto:agrwal.ysh94@gmail.com">agrwal.ysh94@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span style="line-height:1.5">Yesterday's Work</span><br></div><div>I stumbled onto this issue in my glyph rendering module </div><div><a href="https://github.com/sugarlabs/edit-fonts-activity/issues/44" target="_blank">https://github.com/sugarlabs/edit-fonts-activity/issues/44</a></div><div>so this took a lot of time, but is still not implemented, I will look at Trufonts source later for this</div><div><br></div><div>I was having issue's in implementing Treeview to show the font list, now I would say its at about 80%, this includes solving the stars bug and adding a text box which will change the default text (currently hardcoded to "the quick brown fox.....") for the Font Manager</div><div><br></div><div>Also importing ttf and otf in working through Object Chooser now</div><div class="gmail_quote"><div dir="ltr"><br></div><div>Today's Goal:</div><div>Plan to complete the GUI and release a stable .xo so that the activity can be tested</div><div><br></div><div>Questions:</div><div>No Questions today :)</div></div></div><div dir="ltr"><div class="gmail_quote"><div><br></div><div dir="ltr">On Thu, Jun 23, 2016 at 9:12 AM Dave Crossland <<a href="mailto:dave@lab6.com" target="_blank">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"><div dir="ltr"><p dir="ltr">Hi</p>
<p dir="ltr">On Jun 22, 2016 10:50 PM, "Yash Agarwal" <<a href="mailto:agrwal.ysh94@gmail.com" target="_blank">agrwal.ysh94@gmail.com</a>> wrote:<br>
><br>
> Today's Work</p>
<p dir="ltr">Boom!!!</p></div><div dir="ltr">
<p dir="ltr">> Import module is working for ttf files</p>
</div><div dir="ltr"><p dir="ltr">Sweet! Do you convert tt outlines to cff?</p></div><div dir="ltr">
<p dir="ltr">> Export module is working with fontmake</p>
</div><div dir="ltr"><p dir="ltr">Great </p>
<p dir="ltr">> Activation/Deactivation module is done</p>
<p dir="ltr">Awesome. Is the star button fixed? </p></div><div dir="ltr">
<p dir="ltr">> I started adding making changes to the UI for "creating a new font" but ended up adding a lot more around it, I'll make a blog post about it later<br>
> it still requires a little debugging so no gif today </p>
</div><div dir="ltr"><p dir="ltr">Looking forward to it :)</p></div><div dir="ltr">
<p dir="ltr">> what I plan to do next:<br>
> sort out the bugs in the UI and make a blog post about the new features</p>
</div><div dir="ltr"><p dir="ltr">Yes!</p></div><div dir="ltr">
<p dir="ltr">> for importing UFO files Trufont asks for a link to the metainfo.plist file which has an "application/x-plist" MIME type, so also going to use that</p>
</div><div dir="ltr"><p dir="ltr">Sounds good enough for a first pass. I think in the second round, ufoz makes more sense, then its a single file. Additionally, we could get Sugar to understand nextstep bundles but its a rathole. </p></div><div dir="ltr">
<p dir="ltr">> questions:<br>
> What all information is needed in the Create New Font Form?<br>
> this is what I currently have:<br>
> Family name, </p>
</div><div dir="ltr"><p dir="ltr">Yes, ask for this</p>
<p dir="ltr">> style name, </p>
<p dir="ltr">Only have "Regular" for now</p>
<p dir="ltr">> version, </p>
<p dir="ltr">1.000</p>
<p dir="ltr">> trademark, </p>
<p dir="ltr">Blank<br></p>
<p dir="ltr">> author info, </p>
<p dir="ltr">Copyright $year The $familyname Authors. </p>
<p dir="ltr">> license,</p>
<p dir="ltr">Use,</p><p dir="ltr">This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: <a href="http://scripts.sil.org/OFL" target="_blank">http://scripts.sil.org/OFL</a><br></p><div>> license URL</div><div><br></div><div>Use,</div><div><div><br></div><div><a href="http://scripts.sil.org/OFL" target="_blank">http://scripts.sil.org/OFL</a></div></div><div><br></div>
<p dir="ltr">> cap height, </p><p dir="ltr">800</p><p dir="ltr">> x-height, </p><p dir="ltr">500</p><p dir="ltr">> ascender, </p><p dir="ltr">800</p><p dir="ltr">> descender, </p><p dir="ltr">-200</p><p dir="ltr">> units per em</p><p dir="ltr">1000</p></div><div dir="ltr"><p dir="ltr">
> or should I shorten the list?<br><br></p></div><div dir="ltr"><p dir="ltr">These defaults make a short list :)<br></p></div><div dir="ltr">
<p dir="ltr">> Similarly, what all info for creating a new glyph?</p>
</div><div dir="ltr"><p dir="ltr">Just a glyph name. </p><p dir="ltr">Please file an issue for a second round that the input should allow a space separated list of names to create a bunch at once, if this is not easy for you to add in the first round (ie, tomorrow)<br></p>
<p dir="ltr">Then, you can guess unicode values from the names using <a href="https://github.com/LettError/glyphNameFormatter/" target="_blank">https://github.com/LettError/glyphNameFormatter/</a> - and else when the code can't guess, leave it blank. </p>
<p dir="ltr">Please file an issue for the someday/later milestone to add some UI for checking the encoding of glyphs and correcting them. </p>
</div>
</blockquote></div></div></blockquote></div>