fossasia / open-event-droidgen Goto Github PK

@mananwason I didn't find any issue regarding it so I am creating it here.
On clicking on any member starting from member number 6 (i.e starting from guy named Tarek Ahmed) either app get crashed or lead us to the home screen. It is giving CursorIndexOutOfBoundsException.
I have resolved the issue and now it is working fine for all the rest members of the list as well.
Please can anyone help me how can I commit my changes in the main project.

Requirements

1. Provide an easy share link for event.

Will be useful to spread awareness on Social Networks.

Also, alternatively, if app is installed, then the URL scheme could be used to share the info like

1. Twitter https://twitter.com/intent/tweet?text=%s where text can be a tweet about event and official hashtag.
2. Facebook: Info here

This definitely is not within Material Style.

2 issues here:

• The edit overlay (cut, copy & paste) should happen over the primary action bar, there isn't a concept of secondary navigation on Android, also title should not be Text Selection
• The selection cursor pointer is white shouldn't be the case, should be yellow or whatever according to the theme.

in json data there are int array in form of "[1, 2, 3]". For eg ids of speakers in each session.

These need to be serialised/deserialised as per need.

getTrackList
getSessionList
getSpeakerList
getSponsorList
getSpeakerById
getSessionById

I'll be making another api so that I don't I have to depend on the main orga server because when it is changed by rafal, all data is lost.

Relevant links and data here https://events.ccc.de/camp/2015/wiki/Apps

When we tag a commit and push it, it should create a release.

When I bookmark an already bookmarked event, the app crashes.

I would like to fix it as some new GCI task :)
Screenshot:

@championswimmer I suggest we first make some milestones/issues based on what all we have to do, and daily assign ourselves to those milestones/issues and complete the self assigned work.

Till now we have been working on pretty much same things which lead to conflicts in our work. This will help us work better in a team. Please feel free to give any other ideas.

Requirements

Each event can have its own color style, we need each open-event-android app for each event to look and feel differently. For a start we can target color schemes particular to the app, either generate them at build time through a gradle task of sorts or use a script. Either way, the end product is have event A's app look different from event B's.

Once we have isolated what we need, we can extract this configuration out to be supplied by the API. The build system can pick up the configuration variables from the API or read from a configuration file.

One example can be the action bar color and status window color, both of these are widely used and demarcated as colorPrimary and colorPrimaryDark in the styles.xml. However, to the app these are just configuration variables, which we can override.

Display data from the database in the app UI.

Location fragment - where all locations where the sessions are scheduled to take place are displayed.

Objective

To inform user which sessions are starting soon

Requirement

1. Display notification
2. Allow user to control when to display notification (maybe 1 hour before event, in morning, 10 before event starts and so on). Start with a default value and let user to customise.
3. Further there can be actions associated with notifications displayed like Snooze etc something like this:

Related to #59 (At least the notification part)

Application acting abruptly (even crashes few times) on clicking on star icon several times and start downloading data again taking to the main screen.Ideally I think should remain on that screen itself.

When I am trying to bookmark any session app crashes. Though on running the app again I can see it as bookmarked.

There might be some issue with the code running after database transaction.

Removing bookmark works good though.

Requirements

Search functionality for:

• Sessions
• Locations
• Speakers
• Topics/Abstract etc.

App crashes when refreshing on no Internet connection

Objective

To add some support for wearables

Requirements

1. Implement all (or some parts) of screens as documented in the Google I/O App
2. Possible screens
   • Notify user of bookmarked session starting soon
   • Allow to see some session details
   • Allow to unBookmark the session for which they got notification on watch
   • Allow user to browse through sessions happening during the time (or at location)

Problem:
On orientation change app comes back to the TracksFragment when MainActivity is recreated
https://github.com/mRokita/open-event-android/blob/master/app/src/main/java/org/fossasia/openevent/activities/MainActivity.java#L79
I can fix it using the savedInstanceState Bundle, it would be nice to add it as another GCI task :)

Hi i am proficient in android programming and also in backend development using flask . How can i help in this?

DISCUSSION :
So, when we compare timestamp, get new data, and fetch it, what would we do ?
I think best would be, to drop each table and refresh the whole data. When sessions.json is downloaded, drop sessions table, and create new table with the new data.

What do you guys think ?

I am thinking we should best use Volley for this ? My experiences with fetching Json data have been the best with Volley.

Objective is to download data (in a background thread, not the Main Thread) and do a version-based sync of the resources stored in the server. The client needs to have the most updated copy of the data, because in an ongoing event, this may be important. We shall sync the resources by comparing the version of the resources already stored in our local database. Some background

1. Main activity is created -> register with bus -> show data from db -> if nothing in DB -> UI should show refreshing status and show some kind of empty view
2. if all data is downloaded (Not just the versions but everything, you can have a counter for this) -> post success event -> you will get the event in Main activity -> refresh from DB again -> Stop progress bar animation
3. If there is error fire an error event -> UI changes to show there has been network error (Or other error) -> Stop progress animation -> Display a manual refresh button
4. If user chooses to manually refresh -> Trigger data download -> Wait for event to come in. Repeat from 2 onwards
5. If the application is already refreshing (downloading data), disable/hide the manual refresh button.

Minimum requirements are these, tests for these an added bonus.

Developers URL- For testing new features and improvements
User's URL - Live version of the api, which is tested and deployed for all users to use.