[brailleblaster] Re: push by francois...@xxxxxxxxx - Updated by F.O. on 2012-07-18 22:53 GMT
- From: François Ouellette <braille@xxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Thu, 19 Jul 2012 07:51:15 -0400
Michael: I could not push small incremental changes, there were too
many things interrelated. When I started working on the GUI there was
almost nothing functional, every time you clicked on a button you were
getting the message that the function was unavailable! I am new to
mercurial so I am still learning its usage. Thanks for the tips I will
keep this in mind for the next time.
François
On Thu, Jul 19, 2012 at 6:31 AM, Michael Whapples <mwhapples@xxxxxxx> wrote:
> Hello,
> OK, a few comments:
> 1. If you are using the -m option for committing, then just a short comment
> describing would be better than nothing, eg. "Improvements to the GUI,
> adding importing for various file types, emboss command, translate command,
> etc".
> 2. As mercurial is a distributed version control system you can make smaller
> commits on your local system and then push them all in one go. This means
> each commit can be focussed on one task and so the commit message can be
> shorter, eg. one commit for importing, one commit for the emboss command,
> one commit for the translate command, etc.
> 3. If you have the EDITOR or HG_EDITOR (I think that is correct) environment
> variables set then if you don't give the -m option your editor will be
> opened where you can give a commit message, this may be better if you need
> to write a lot in the commit message.
>
> Hope this helps.
>
> Michael whapples
> On 19/07/2012 05:49, François Ouellette wrote:
>>
>> Michael: I agree, but when using the command-line commit it is not
>> easy to put a meaningful description of what is included in an in-line
>> comment field. Hence the need for release notes, I admit I should have
>> included some. So here they are.
>>
>> Basically these changes add lots of functionality to the GUI, including:
>> - An Import command that can import doc, docx, rtf, txt, odt, pdf and
>> other types of documents that have text in them.
>> - Opening and saving UTD files that have text only or text and
>> translated braille content
>> - A Translate command that displays translated Braille in the Braille view
>> - A radio button to display the translation as SimBraille or text in
>> the Braille view
>> - A working EmbossNow command available in the File menu or from a
>> button on the toolbar. This currently supports character-based
>> embossers. I tested it with a Romeo 25.
>>
>> The tika-app-1.1.jar file is required in the dist/lib folder, as well
>> as font files in the dist/programData/fonts folder. I guess we will
>> make these available in the distribution kit. The files have been sent
>> to John already. If you need them I can supply them to you otherwise.
>> Apache just released Tika 1.2 and this is the one you find on their
>> main web site, but I haven't tested the application with it yet. The
>> release 1.1 is available here:
>> http://archive.apache.org/dist/tika/
>>
>> I also tried the BB non-gui command-line functions 'translate' and
>> 'emboss' and they seem to work fine on Windows.
>>
>> I tested this release on Windows 64-bit, so those on 32-bit machines
>> and also Linux and Mac are welcome to try it and provide feedback.
>>
>> Let me know if there is anything else you need to know.
>>
>> Best regards,
>>
>> François.
>>
>> On Wed, Jul 18, 2012 at 7:46 PM, John J. Boyer
>> <john.boyer@xxxxxxxxxxxxxxxxx> wrote:
>>>
>>> Maybe we need instructions for new committers somewhere. Also if someone
>>> replies to a push notice the body of the notice should be deleted,
>>> because ikt is likely to be very lengthy.
>>>
>>> John
>>>
>>> On Thu, Jul 19, 2012 at 12:09:39AM +0100, Michael Whapples wrote:
>>>>
>>>> Hello,
>>>> Would it be possible in future to ensure your commits have more
>>>> useful/descriptive log messages?
>>>>
>>>> We know who made the update as the author field shows that, it would be
>>>> useful to know what the intent of the commit is.
>>>>
>>> O
>>>>
>>>> Michael Whapples
>
>
>
Other related posts:
