bbct-list — BBCT Mailing List

Re: [bbct-list] [bbct] java.lang.IllegalStateException: trying to requery an already closed cursor (#197)

[Charanya A. <cha...@gm...>]

I am working on Issue172-Take Picture of Cards and I am facing the same
issue.
When I fill one of the AutoCompleteTextViews, then start the camera
activity to take picture and come back to BaseballCardDetails from camera
activity, the app crashes with the same exception.

When I was debugging, I found that there is a 'startManagingCursor' in
SingleColumnCursorAdapter:runQueryOnBackgroundThread, but there is no
corresponding stopManagingCursor. Is the startManagingCursor necessary
there? Would the CursorAdapter's changeCursor take care of it? If we need
startManagingCursor, can we call it in changeCursor?
I found this link which may be helpful.
http://stackoverflow.com/questions/12793274/can-someone-explain-to-me-on-runqueryonbackgroundthread

Also, according to android developer manual, the CursorAdapter constructor
that is in SingleColumnCursorAdapter is not recommended now. Should that be
changed too?

On Mon, Jun 1, 2015 at 2:33 PM, Code Apprentice <not...@gi...>
wrote:

> I finally reproduced this issue on my tablet with the following recipe:
>
>    1. Select one of the autocomplete fields (Brand, Name, or Team)
>    2. Enter some text
>    3. Put device to sleep
>    4. Wake device up
>
> The next step is to write a UI Automator test that illustrates the issue
> and verifies when it is fixed.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/BaseballCardTracker/bbct/issues/197#issuecomment-107718660>
> .
>

[bbct-list] New mailing list

[Code G. <cod...@gm...>]

Dear BBCT Users and Contributors,

The BBCT mailing list is moving to Google Groups. If you wish to continue
to follow developments of this app, please visit
https://groups.google.com/forum/#!forum/bbct and join the new group.

This changes is due to the increase of spam which is sent to the current
list hosted at Source Forge. SF doesn't appear to have automatic spam
filters and instead requires me to manually log into the admin account and
discard any undesirable emails.

I apologize for the inconvenience. I believe that Google Groups will
provide a much better experience for communicating among the BBCT team and
to our users.

Thank you for your time.

Regards,

Code Guru

Re: [bbct-list] Git Commits

[Charanya A. <cha...@gm...>]

Hi,

No problem. I welcome your suggestions to improve my programming skills and
management. I read your commit guidelines and will try my best to stick to
it.

Thanks,
Charanya

On Thu, Jun 11, 2015 at 6:31 AM, Code Guru <cod...@gm...> wrote:

> Dear Charanya,
>
> I accidentally sent the previous email before finishing it. I have a
> concern that we need to address. I've been struggling with how to express
> my ideas because I want to help you improve your programming skills, and
> especially your project management skills with git. However, at the same
> time, I value your time and effort with BBCT, so I don't want to chase you
> away by being too blunt.
>
> The problem is with the way you are using git. Over the last several years
> as I've learned to do version control with git, I have also gradually
> adopted some conventions. I would like you to use these same conventions
> with your own commits as well. So I have attempted to explain my
> expectations in the Commit Guidelines (
> https://github.com/BaseballCardTracker/bbct/wiki/Commit-Guidelines) on
> our project's wiki. I still don't always make commits that completely
> follow these guidelines, so I don't expect everything to be exactly
> perfect. As long as you are making an effort towards these goals, I will be
> happy. The two important guidelines are to have a descriptive comment for
> each commit and to properly use `git merge` or `git rebase` so that you
> don't create a commit which repeats changes that someone else (including
> yourself) already made earlier in another commit.
>
> With that said, I absolutely don't care *how* you make your commits.
> Please use whatever process which is comfortable for you. I don't want to
> micromanage every little detail. I'm trying to avoid that at all cost while
> still maintaining some standards as general guidelines. The main place
> where this plays a part is in creating "small commits". This is your
> judgement call. If it helps, look at the existing commit history. There are
> many good examples of small commits I have made. Of course, there are also
> bad examples of some very large commits as well. Avoid following those
> examples. A general rule of thumb is that if you have programmed all day,
> or even for an hour or two, without making a commit, then you probably need
> to figure out how to split it up into related chunks that compile and can
> be commited to your repo.
>
> Before I end this letter, I have a suggestion to help you continue with
> Issue 172. You have certainly made a lot of progress on this, and I'm
> excited to see it finished and integrated into the existing app.
> Unfortunately, I have made a lot of changes since you first started which,
> as you have probably seen, makes more work for you to merge my changes with
> your own work. The transition to Android Studio is the largest change that
> affects this. Because of all of these changes, I suggest that you create a
> brand new branch on top of the current `devel/android` branch. From there
> commit your work according to the published guidelines. You can certainly
> copy and paste your work as much as possible from the existing branches.
> For example, copy over your changes to the `card_details.xml` layout file
> and commit those changes. Note that this commit won't be fully functional,
> however, it will still compile and display the new interface elements.
> Continue creating similarly small commits and build up to the same state as
> your current work.
>
> I need to emphasize that the above is just a suggestion. The important
> thing is that you work on following the commit guidelines, not the exact
> details of how you get there. I apologize for the length of this letter.
> This is important enough to me that I feel the need to take the time
> explaining my thoughts. This is intended to help improve our project. I
> hope you will take in that light. As always, please contact me if you have
> any questions or concerns. I look forward to continuing to work with you.
>
> Regards,
>
> Layne
>
> On Thu, Jun 11, 2015 at 6:55 AM Code Guru <cod...@gm...> wrote:
>
>> Charanya,
>>
>> I have updated the guidelines for creating commits (
>> https://github.com/BaseballCardTracker/bbct/wiki/Commit-Guidelines).
>> Please review these
>>
>

Re: [bbct-list] Git Commits

[Code G. <cod...@gm...>]

Dear Charanya,

I accidentally sent the previous email before finishing it. I have a
concern that we need to address. I've been struggling with how to express
my ideas because I want to help you improve your programming skills, and
especially your project management skills with git. However, at the same
time, I value your time and effort with BBCT, so I don't want to chase you
away by being too blunt.

The problem is with the way you are using git. Over the last several years
as I've learned to do version control with git, I have also gradually
adopted some conventions. I would like you to use these same conventions
with your own commits as well. So I have attempted to explain my
expectations in the Commit Guidelines (
https://github.com/BaseballCardTracker/bbct/wiki/Commit-Guidelines) on our
project's wiki. I still don't always make commits that completely follow
these guidelines, so I don't expect everything to be exactly perfect. As
long as you are making an effort towards these goals, I will be happy. The
two important guidelines are to have a descriptive comment for each commit
and to properly use `git merge` or `git rebase` so that you don't create a
commit which repeats changes that someone else (including yourself) already
made earlier in another commit.

With that said, I absolutely don't care *how* you make your commits. Please
use whatever process which is comfortable for you. I don't want to
micromanage every little detail. I'm trying to avoid that at all cost while
still maintaining some standards as general guidelines. The main place
where this plays a part is in creating "small commits". This is your
judgement call. If it helps, look at the existing commit history. There are
many good examples of small commits I have made. Of course, there are also
bad examples of some very large commits as well. Avoid following those
examples. A general rule of thumb is that if you have programmed all day,
or even for an hour or two, without making a commit, then you probably need
to figure out how to split it up into related chunks that compile and can
be commited to your repo.

Before I end this letter, I have a suggestion to help you continue with
Issue 172. You have certainly made a lot of progress on this, and I'm
excited to see it finished and integrated into the existing app.
Unfortunately, I have made a lot of changes since you first started which,
as you have probably seen, makes more work for you to merge my changes with
your own work. The transition to Android Studio is the largest change that
affects this. Because of all of these changes, I suggest that you create a
brand new branch on top of the current `devel/android` branch. From there
commit your work according to the published guidelines. You can certainly
copy and paste your work as much as possible from the existing branches.
For example, copy over your changes to the `card_details.xml` layout file
and commit those changes. Note that this commit won't be fully functional,
however, it will still compile and display the new interface elements.
Continue creating similarly small commits and build up to the same state as
your current work.

I need to emphasize that the above is just a suggestion. The important
thing is that you work on following the commit guidelines, not the exact
details of how you get there. I apologize for the length of this letter.
This is important enough to me that I feel the need to take the time
explaining my thoughts. This is intended to help improve our project. I
hope you will take in that light. As always, please contact me if you have
any questions or concerns. I look forward to continuing to work with you.

Regards,

Layne

On Thu, Jun 11, 2015 at 6:55 AM Code Guru <cod...@gm...> wrote:

> Charanya,
>
> I have updated the guidelines for creating commits (
> https://github.com/BaseballCardTracker/bbct/wiki/Commit-Guidelines).
> Please review these
>

[bbct-list] Git Commits

[Code G. <cod...@gm...>]

Charanya,

I have updated the guidelines for creating commits (
https://github.com/BaseballCardTracker/bbct/wiki/Commit-Guidelines). Please
review these

Re: [bbct-list] Learning Android Studio

[Charanya A. <cha...@gm...>]

I was planning to continue with my Issue172:Take Picture of cards ticket.

On Sat, Jun 6, 2015 at 7:13 AM, Code Guru <cod...@gm...> wrote:

> Good to hear. What are your plans to continue from here?
>
> On Fri, Jun 5, 2015, 7:35 PM Charanya Arvind <cha...@gm...>
> wrote:
>
>> Hi,
>>
>> I was able to import the "gradle" project and run it.
>> Thanks for your help.
>>
>> Thanks,
>> Charanya
>>
>> On Wed, Jun 3, 2015 at 5:21 PM, Code Guru <cod...@gm...> wrote:
>>
>>> Yes BBCT is fully migrated to the gradle build system. The new project
>>> structure lives in the "gradle" subdirectory. This is the folder you need
>>> to open. The old "android" folder should only contain "functional-tests"
>>> and "release.sh". It no longer has the old Eclipse projects.
>>>
>>> After you open the project under the gradle folder please let me know if
>>> you encounter any other problems.
>>>
>>> Layne
>>>
>>> On Wed, Jun 3, 2015, 5:20 PM Charanya Arvind <cha...@gm...>
>>> wrote:
>>>
>>>> Yes I did. I checked out your branch with latest changes.
>>>> But I still am getting few issues. The run configuration was not done,
>>>> build variants is not showing anything and I get a notification that I
>>>> should migrate to gradle build system. Did you migrate to gradle build
>>>> system too?
>>>> So I am figuring these out now.
>>>>
>>>> Thanks,
>>>> Charanya
>>>>
>>>> On Wed, Jun 3, 2015 at 11:26 AM, Code Guru <cod...@gm...>
>>>> wrote:
>>>>
>>>>> Have you had a chance to download the new version of Android Studio?
>>>>>
>>>>> On Sat, May 30, 2015, 8:27 AM Code Guru <cod...@gm...> wrote:
>>>>>
>>>>>> I just pushed a new branch to my personal repo. You should install
>>>>>> the most recent version of Android Studio, download Build Tools version
>>>>>> 22.0.1, and API 22. Then pull my branch and try to compile. Please let me
>>>>>> know if you encounter any problems.
>>>>>>
>>>>>> On Fri, May 29, 2015, 4:21 PM Charanya Arvind <
>>>>>> cha...@gm...> wrote:
>>>>>>
>>>>>>> Ok. I will wait for your update then.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Charanya
>>>>>>> On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:
>>>>>>>
>>>>>>>> My immediate goal with BBCT is to update it to work with the most
>>>>>>>> recent version of Android Studio. When I merge these changes into the
>>>>>>>> android/devel branch of the main GitHub repo, I suggest that you start with
>>>>>>>> that branch in order to be sure that you can compile BBCT with Android
>>>>>>>> Studio. Once you get a baseline version to run and compile, it will be a
>>>>>>>> little easier to work on your changes.
>>>>>>>>
>>>>>>>> Code-Guru
>>>>>>>>
>>>>>>>
>>>>
>>

Re: [bbct-list] Learning Android Studio

[Code G. <cod...@gm...>]

Good to hear. What are your plans to continue from here?

On Fri, Jun 5, 2015, 7:35 PM Charanya Arvind <cha...@gm...>
wrote:

> Hi,
>
> I was able to import the "gradle" project and run it.
> Thanks for your help.
>
> Thanks,
> Charanya
>
> On Wed, Jun 3, 2015 at 5:21 PM, Code Guru <cod...@gm...> wrote:
>
>> Yes BBCT is fully migrated to the gradle build system. The new project
>> structure lives in the "gradle" subdirectory. This is the folder you need
>> to open. The old "android" folder should only contain "functional-tests"
>> and "release.sh". It no longer has the old Eclipse projects.
>>
>> After you open the project under the gradle folder please let me know if
>> you encounter any other problems.
>>
>> Layne
>>
>> On Wed, Jun 3, 2015, 5:20 PM Charanya Arvind <cha...@gm...>
>> wrote:
>>
>>> Yes I did. I checked out your branch with latest changes.
>>> But I still am getting few issues. The run configuration was not done,
>>> build variants is not showing anything and I get a notification that I
>>> should migrate to gradle build system. Did you migrate to gradle build
>>> system too?
>>> So I am figuring these out now.
>>>
>>> Thanks,
>>> Charanya
>>>
>>> On Wed, Jun 3, 2015 at 11:26 AM, Code Guru <cod...@gm...> wrote:
>>>
>>>> Have you had a chance to download the new version of Android Studio?
>>>>
>>>> On Sat, May 30, 2015, 8:27 AM Code Guru <cod...@gm...> wrote:
>>>>
>>>>> I just pushed a new branch to my personal repo. You should install the
>>>>> most recent version of Android Studio, download Build Tools version 22.0.1,
>>>>> and API 22. Then pull my branch and try to compile. Please let me know if
>>>>> you encounter any problems.
>>>>>
>>>>> On Fri, May 29, 2015, 4:21 PM Charanya Arvind <
>>>>> cha...@gm...> wrote:
>>>>>
>>>>>> Ok. I will wait for your update then.
>>>>>>
>>>>>> Thanks,
>>>>>> Charanya
>>>>>> On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:
>>>>>>
>>>>>>> My immediate goal with BBCT is to update it to work with the most
>>>>>>> recent version of Android Studio. When I merge these changes into the
>>>>>>> android/devel branch of the main GitHub repo, I suggest that you start with
>>>>>>> that branch in order to be sure that you can compile BBCT with Android
>>>>>>> Studio. Once you get a baseline version to run and compile, it will be a
>>>>>>> little easier to work on your changes.
>>>>>>>
>>>>>>> Code-Guru
>>>>>>>
>>>>>>
>>>
>

Re: [bbct-list] Learning Android Studio

[Charanya A. <cha...@gm...>]

Hi,

I was able to import the "gradle" project and run it.
Thanks for your help.

Thanks,
Charanya

On Wed, Jun 3, 2015 at 5:21 PM, Code Guru <cod...@gm...> wrote:

> Yes BBCT is fully migrated to the gradle build system. The new project
> structure lives in the "gradle" subdirectory. This is the folder you need
> to open. The old "android" folder should only contain "functional-tests"
> and "release.sh". It no longer has the old Eclipse projects.
>
> After you open the project under the gradle folder please let me know if
> you encounter any other problems.
>
> Layne
>
> On Wed, Jun 3, 2015, 5:20 PM Charanya Arvind <cha...@gm...>
> wrote:
>
>> Yes I did. I checked out your branch with latest changes.
>> But I still am getting few issues. The run configuration was not done,
>> build variants is not showing anything and I get a notification that I
>> should migrate to gradle build system. Did you migrate to gradle build
>> system too?
>> So I am figuring these out now.
>>
>> Thanks,
>> Charanya
>>
>> On Wed, Jun 3, 2015 at 11:26 AM, Code Guru <cod...@gm...> wrote:
>>
>>> Have you had a chance to download the new version of Android Studio?
>>>
>>> On Sat, May 30, 2015, 8:27 AM Code Guru <cod...@gm...> wrote:
>>>
>>>> I just pushed a new branch to my personal repo. You should install the
>>>> most recent version of Android Studio, download Build Tools version 22.0.1,
>>>> and API 22. Then pull my branch and try to compile. Please let me know if
>>>> you encounter any problems.
>>>>
>>>> On Fri, May 29, 2015, 4:21 PM Charanya Arvind <
>>>> cha...@gm...> wrote:
>>>>
>>>>> Ok. I will wait for your update then.
>>>>>
>>>>> Thanks,
>>>>> Charanya
>>>>> On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:
>>>>>
>>>>>> My immediate goal with BBCT is to update it to work with the most
>>>>>> recent version of Android Studio. When I merge these changes into the
>>>>>> android/devel branch of the main GitHub repo, I suggest that you start with
>>>>>> that branch in order to be sure that you can compile BBCT with Android
>>>>>> Studio. Once you get a baseline version to run and compile, it will be a
>>>>>> little easier to work on your changes.
>>>>>>
>>>>>> Code-Guru
>>>>>>
>>>>>
>>

Re: [bbct-list] Learning Android Studio

[Code G. <cod...@gm...>]

Yes BBCT is fully migrated to the gradle build system. The new project
structure lives in the "gradle" subdirectory. This is the folder you need
to open. The old "android" folder should only contain "functional-tests"
and "release.sh". It no longer has the old Eclipse projects.

After you open the project under the gradle folder please let me know if
you encounter any other problems.

Layne

On Wed, Jun 3, 2015, 5:20 PM Charanya Arvind <cha...@gm...>
wrote:

> Yes I did. I checked out your branch with latest changes.
> But I still am getting few issues. The run configuration was not done,
> build variants is not showing anything and I get a notification that I
> should migrate to gradle build system. Did you migrate to gradle build
> system too?
> So I am figuring these out now.
>
> Thanks,
> Charanya
>
> On Wed, Jun 3, 2015 at 11:26 AM, Code Guru <cod...@gm...> wrote:
>
>> Have you had a chance to download the new version of Android Studio?
>>
>> On Sat, May 30, 2015, 8:27 AM Code Guru <cod...@gm...> wrote:
>>
>>> I just pushed a new branch to my personal repo. You should install the
>>> most recent version of Android Studio, download Build Tools version 22.0.1,
>>> and API 22. Then pull my branch and try to compile. Please let me know if
>>> you encounter any problems.
>>>
>>> On Fri, May 29, 2015, 4:21 PM Charanya Arvind <cha...@gm...>
>>> wrote:
>>>
>>>> Ok. I will wait for your update then.
>>>>
>>>> Thanks,
>>>> Charanya
>>>> On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:
>>>>
>>>>> My immediate goal with BBCT is to update it to work with the most
>>>>> recent version of Android Studio. When I merge these changes into the
>>>>> android/devel branch of the main GitHub repo, I suggest that you start with
>>>>> that branch in order to be sure that you can compile BBCT with Android
>>>>> Studio. Once you get a baseline version to run and compile, it will be a
>>>>> little easier to work on your changes.
>>>>>
>>>>> Code-Guru
>>>>>
>>>>
>

Re: [bbct-list] Learning Android Studio

[Charanya A. <cha...@gm...>]

Yes I did. I checked out your branch with latest changes.
But I still am getting few issues. The run configuration was not done,
build variants is not showing anything and I get a notification that I
should migrate to gradle build system. Did you migrate to gradle build
system too?
So I am figuring these out now.

Thanks,
Charanya

On Wed, Jun 3, 2015 at 11:26 AM, Code Guru <cod...@gm...> wrote:

> Have you had a chance to download the new version of Android Studio?
>
> On Sat, May 30, 2015, 8:27 AM Code Guru <cod...@gm...> wrote:
>
>> I just pushed a new branch to my personal repo. You should install the
>> most recent version of Android Studio, download Build Tools version 22.0.1,
>> and API 22. Then pull my branch and try to compile. Please let me know if
>> you encounter any problems.
>>
>> On Fri, May 29, 2015, 4:21 PM Charanya Arvind <cha...@gm...>
>> wrote:
>>
>>> Ok. I will wait for your update then.
>>>
>>> Thanks,
>>> Charanya
>>> On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:
>>>
>>>> My immediate goal with BBCT is to update it to work with the most
>>>> recent version of Android Studio. When I merge these changes into the
>>>> android/devel branch of the main GitHub repo, I suggest that you start with
>>>> that branch in order to be sure that you can compile BBCT with Android
>>>> Studio. Once you get a baseline version to run and compile, it will be a
>>>> little easier to work on your changes.
>>>>
>>>> Code-Guru
>>>>
>>>

Re: [bbct-list] Learning Android Studio

[Code G. <cod...@gm...>]

Have you had a chance to download the new version of Android Studio?

On Sat, May 30, 2015, 8:27 AM Code Guru <cod...@gm...> wrote:

> I just pushed a new branch to my personal repo. You should install the
> most recent version of Android Studio, download Build Tools version 22.0.1,
> and API 22. Then pull my branch and try to compile. Please let me know if
> you encounter any problems.
>
> On Fri, May 29, 2015, 4:21 PM Charanya Arvind <cha...@gm...>
> wrote:
>
>> Ok. I will wait for your update then.
>>
>> Thanks,
>> Charanya
>> On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:
>>
>>> My immediate goal with BBCT is to update it to work with the most recent
>>> version of Android Studio. When I merge these changes into the
>>> android/devel branch of the main GitHub repo, I suggest that you start with
>>> that branch in order to be sure that you can compile BBCT with Android
>>> Studio. Once you get a baseline version to run and compile, it will be a
>>> little easier to work on your changes.
>>>
>>> Code-Guru
>>>
>>

Re: [bbct-list] Learning Android Studio

[Code G. <cod...@gm...>]

I just pushed a new branch to my personal repo. You should install the most
recent version of Android Studio, download Build Tools version 22.0.1, and
API 22. Then pull my branch and try to compile. Please let me know if you
encounter any problems.

On Fri, May 29, 2015, 4:21 PM Charanya Arvind <cha...@gm...>
wrote:

> Ok. I will wait for your update then.
>
> Thanks,
> Charanya
> On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:
>
>> My immediate goal with BBCT is to update it to work with the most recent
>> version of Android Studio. When I merge these changes into the
>> android/devel branch of the main GitHub repo, I suggest that you start with
>> that branch in order to be sure that you can compile BBCT with Android
>> Studio. Once you get a baseline version to run and compile, it will be a
>> little easier to work on your changes.
>>
>> Code-Guru
>>
>

Re: [bbct-list] Learning Android Studio

[Charanya A. <cha...@gm...>]

Ok. I will wait for your update then.

Thanks,
Charanya
On May 29, 2015 2:41 PM, "Code Guru" <cod...@gm...> wrote:

> My immediate goal with BBCT is to update it to work with the most recent
> version of Android Studio. When I merge these changes into the
> android/devel branch of the main GitHub repo, I suggest that you start with
> that branch in order to be sure that you can compile BBCT with Android
> Studio. Once you get a baseline version to run and compile, it will be a
> little easier to work on your changes.
>
> Code-Guru
>

[bbct-list] Learning Android Studio

[Code G. <cod...@gm...>]

My immediate goal with BBCT is to update it to work with the most recent
version of Android Studio. When I merge these changes into the
android/devel branch of the main GitHub repo, I suggest that you start with
that branch in order to be sure that you can compile BBCT with Android
Studio. Once you get a baseline version to run and compile, it will be a
little easier to work on your changes.

Code-Guru

[bbct-list] GitHub Flow

[Code G. <cod...@gm...>]

https://guides.github.com/introduction/flow/index.html

I recently found this page which explains the general workflow suggested by
GitHub. It has some great ideas that I want to incorporate into our
project. Please read this when you have some time. I will start a wiki page
with our own workflow guidelines. Please contribute your thoughts as we
refine this process.

Code Guru

Re: [bbct-list] About Issue103 and Issue104

[Code G. <cod...@gm...>]

We probably should reopen the relevant issues. I may have even removed the
tests. I don't remember for sure.

On Wed, Oct 8, 2014 at 8:18 PM, Code Guru <cod...@gm...> wrote:

> These were commented out when I changed BaseballCardDetails to a Fragment.
> Your original solution only worked when BaseballCardDetails was an
> Activity. I haven't yet figured out a way to fix this with the changes
> involving Fragments.
>
> Layne
>
> On Wed, Oct 8, 2014 at 5:57 PM, Charanya Arvind <cha...@gm...
> > wrote:
>
>> Hi Layne,
>>
>> I just noticed in my updated devel branch that onKeyUp method in
>> BaseballCardDetails is commented. This method was introduced to address
>> issues 103(Next Button and AutoCompleteTextViews) and 104 (Removing
>> on-screen keyboard after entering team).  Was this done for a reason?
>> How will these issues work if the code is commented? I tested and I could
>> not get it to work.
>>
>> Thanks,
>> Charanya
>>
>
>

Re: [bbct-list] About Issue103 and Issue104

[Code G. <cod...@gm...>]

These were commented out when I changed BaseballCardDetails to a Fragment.
Your original solution only worked when BaseballCardDetails was an
Activity. I haven't yet figured out a way to fix this with the changes
involving Fragments.

Layne

On Wed, Oct 8, 2014 at 5:57 PM, Charanya Arvind <cha...@gm...>
wrote:

> Hi Layne,
>
> I just noticed in my updated devel branch that onKeyUp method in
> BaseballCardDetails is commented. This method was introduced to address
> issues 103(Next Button and AutoCompleteTextViews) and 104 (Removing
> on-screen keyboard after entering team).  Was this done for a reason? How
> will these issues work if the code is commented? I tested and I could not
> get it to work.
>
> Thanks,
> Charanya
>

[bbct-list] About Issue103 and Issue104

[Charanya A. <cha...@gm...>]

Hi Layne,

I just noticed in my updated devel branch that onKeyUp method in
BaseballCardDetails is commented. This method was introduced to address
issues 103(Next Button and AutoCompleteTextViews) and 104 (Removing
on-screen keyboard after entering team).  Was this done for a reason? How
will these issues work if the code is commented? I tested and I could not
get it to work.

Thanks,
Charanya

Re: [bbct-list] Rearranging Input Boxes

[Code G. <cod...@gm...>]

No problem. That's definitely more than a full load. (Are you in the United
States?) Good luck with your schooling. As you find time to contribute,
feel free to send your ideas to the mailing list or start issues on GitHub.

CodeGuru

On Fri, Sep 19, 2014 at 5:37 PM, Dan Kondratyuk <hyp...@gm...>
wrote:

> I haven't told you, but I'm taking 21 credits at a university. As such
> I've been given gobs of homework. It will be very difficult for me to
> contribute, but I will see what I can do over the weekend.
>
> On Fri, Sep 19, 2014 at 2:51 PM, Code Guru <cod...@gm...> wrote:
>
>> Sorry that I haven't kept in touch over the last couple of weeks. My
>> tutoring business is getting busier with the new fall semester.
>>
>> I see that you have some ideas for changing the order of the input box.
>> Can you create an issue with your suggestions? You might want to include
>> screenshots to illustrate. I know the current UI is quite boring and I'm
>> definitely open to suggestions to improve this part of the app.
>>
>> Code Guru
>>
>
>
>
> --
> -Dan Kondratyuk
>

[bbct-list] Rearranging Input Boxes

[Code G. <cod...@gm...>]

Sorry that I haven't kept in touch over the last couple of weeks. My
tutoring business is getting busier with the new fall semester.

I see that you have some ideas for changing the order of the input box. Can
you create an issue with your suggestions? You might want to include
screenshots to illustrate. I know the current UI is quite boring and I'm
definitely open to suggestions to improve this part of the app.

Code Guru

Re: [bbct-list] Issue #201: Adding support for other sports

[Code G. <cod...@gm...>]

It looks like the SQL query is missing quotes around the String "Baseball".


On Sun, Aug 24, 2014 at 12:55 PM, Dan Kondratyuk <hyp...@gm...>
wrote:

> I tried merging your devel/android/sports code with the devel/android code
> in my repo, but when I run either version, I get a fatal runtime error:
>
> java.lang.RuntimeException: Unable to start activity
> ComponentInfo{bbct.android/bbct.android.lite.provider.LiteActivity}:
> android.database.sqlite.SQLiteException: no such column: Baseball (code 1):
> , while compiling: UPDATE baseball_cards SET sport=Baseball
>
> I would try to find out the problem myself, but I don't want to waste time
> if there is a simple fix.
>
>
> On Sat, Aug 23, 2014 at 9:05 PM, Code Guru <cod...@gm...> wrote:
>
>> I see that you have started working on this issue. I just wanted to let
>> you know that I have a branch with some work on this issue as well. I would
>> love for you to finish this up. At the same time, you shouldn't redo all
>> the work that I've already done. Please look at
>> https://github.com/codeguru42/bbct/tree/android/sports.
>>
>> I suggest you pull the "android/sports" branch from my personal repo and
>> work on it from there. You should also merge this with the current
>> "devel/android" branch from the main repo as well.
>>
>> Of course, if you have any questions about using git or anything else
>> related to this project, don't hesitate to post here.
>>
>> Code Guru
>>
>
>
>
> --
> -Dan Kondratyuk
>

[bbct-list] Issue #201: Adding support for other sports

[Code G. <cod...@gm...>]

I see that you have started working on this issue. I just wanted to let you
know that I have a branch with some work on this issue as well. I would
love for you to finish this up. At the same time, you shouldn't redo all
the work that I've already done. Please look at
https://github.com/codeguru42/bbct/tree/android/sports.

I suggest you pull the "android/sports" branch from my personal repo and
work on it from there. You should also merge this with the current
"devel/android" branch from the main repo as well.

Of course, if you have any questions about using git or anything else
related to this project, don't hesitate to post here.

Code Guru

Re: [bbct-list] (no subject)

[Code G. <cod...@us...>]

To switch to the Premium version, click on "Build Variants" on the left
side. (If you don't see it, then click on the command tray in the bottom
left corner.) Then select `premiumDebug` from the drop down in the "Build
Variant" column.

Code Guru


On Fri, Aug 22, 2014 at 6:30 PM, Dan Kondratyuk <hyp...@gm...>
wrote:

> I managed to be able to compile and run the lite version of the
> application in Android Studio. How can I run the other versions?
>
> --
> -Dan
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> bbct-list mailing list
> bbc...@li...
> https://lists.sourceforge.net/lists/listinfo/bbct-list
>
>

[bbct-list] (no subject)

[Dan K. <hyp...@gm...>]

I managed to be able to compile and run the lite version of the application
in Android Studio. How can I run the other versions?

-- 
-Dan

Re: [bbct-list] Greetings

[Code G. <cod...@us...>]

p.s. You should check out the "devel/android" branch to be sure that you
have the current development version. The default branch is "master" which
is only updated when I make a release.


On Thu, Aug 21, 2014 at 6:15 PM, Code Guru <cod...@us...>
wrote:

> The wiki is a bit out of date and only has instructions how to use
> Eclipse. We have recently migrated to Android Studio. You need to download
> AS and import the project under the "gradle" subdirectory. If you have any
> problems, feel free to post to this list. I will answer your questions as
> soon as I can.
>
> Code Guru
>
>
> On Thu, Aug 21, 2014 at 5:26 PM, Dan Kondratyuk <hyp...@gm...>
> wrote:
>
>> I would like to help out on this open source project.
>>
>> I have 2+ years of formal Java development, including Swing. I also have
>> a fairly good knowledge on how to use Photoshop for icons, images, etc.
>> However, I'm quite new to GitHub/Sourceforge, so forgive me if I start to
>> ask a lot of questions. I just want to gain experience with open source
>> projects by helping out.
>>
>> I have downloaded the code and I have successfully been able to compile
>> and run the desktop version. I have no idea how to work with the android
>> version, though (I'm looking through the wiki on how to do this, but I keep
>> getting errors).
>>
>> What would you recommend to get me started?
>>
>> -Dan
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> bbct-list mailing list
>> bbc...@li...
>> https://lists.sourceforge.net/lists/listinfo/bbct-list
>>
>>
>