Hello,On the line endings, I don't think anything has been agreed, however it might be good to agree something simply for standardisation. If you want to there are some mercurial extensions which you could install which try dealing with line endings.
On the point of making things standard throughout the project, may be a coding style should be agreed. Certainly using code indentation would help, there are some files where no indentation has been done and they are hard to read/navigate.
Michael Whapples On 11/01/2013 14:39, Keith Creasy wrote:
Hi, I did find the option to use my log-in password, thanks. I did not see an email regarding my push. Did it work?I did end up having to resolve a couple of conflicts, that only involved white space on a few lines. Not sure what's up with that. Do I need to be forcing any particular new-line order? I think my Eclipse is just using whatever the source file is, not sure about Mercurial. I am running on Windows.Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx Phone: 502.895.2405 Skype: keith537*From:*brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] *On Behalf Of *Michael Whapples*Sent:* Thursday, January 10, 2013 4:05 PM *To:* brailleblaster@xxxxxxxxxxxxx *Subject:* [brailleblaster] Re: Daisy view?Please be aware that repository passwords are different to your logon password for your google account. To find out your commit password you need to go to https://code.google.com/p/brailleblaster whilst logged into your account, go to the source page and you will find a link relating to your repository password.I do believe if you want to then there is an option in your google account to tell it to use your logon password for repository commits.Michael Whapples On 10/01/2013 19:58, Keith Creasy wrote: Hi Michael. I guess I don't have things set up right to push. I get the dreaded "Error 403 Forbidden!" message when I use the credentials for my Google account. What should I be doing? I'm trying to just push my changes of DaisyView and DaisyContent to TextView. Thought I'd start with something really simple. G Th Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx <mailto:KCreasy@xxxxxxx> Phone: 502.895.2405 Skype: keith537 *From:*brailleblaster-bounce@xxxxxxxxxxxxx <mailto:brailleblaster-bounce@xxxxxxxxxxxxx> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] *On Behalf Of *Michael Whapples *Sent:* Thursday, January 10, 2013 1:54 PM *To:* brailleblaster@xxxxxxxxxxxxx <mailto:brailleblaster@xxxxxxxxxxxxx> *Subject:* [brailleblaster] Re: Daisy view? nks. Go ahead with renaming that as far as I am concerned. I think it has lead to misunderstanding in the past by implying that daisy would be the underlying format which BrailleBlaster would use when it seems people are thinking other formats. Michael Whapples On 10/01/2013 18:01, Keith Creasy wrote: John and all. Any problem with me changing DAISY view to TextView? I actually think that, with the element references and offsets, we can use StyledText and StyledContent to update the text nodes in the DOM. Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx <mailto:KCreasy@xxxxxxx> Phone: 502.895.2405 Skype: keith537