Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for Segmentation #3243

Closed
tsteur opened this issue Jun 23, 2012 · 3 comments
Closed

Support for Segmentation #3243

tsteur opened this issue Jun 23, 2012 · 3 comments
Labels
enhancement
Milestone
2.1.0

Comments

@tsteur
Copy link
Member

tsteur commented Jun 23, 2012

Depends on #2135 . That will make it possible to get existing segments from the mobile app, eventually the app could even create/modify segments.
@mattab
Copy link
Member

mattab commented Feb 22, 2014

Now that Custom Segments are implemented, and that users can create and store custom segments, it makes sense to integrate viewing reports for an segment, within Piwik Mobile. In fact it would be super cool & powerful!

Piwik Mobile could get list of segments for the currently selected website via SegmentEditor Web APIs.

To allow users to create and edit segments, maybe we could widgetize the Segment Editor and make it available in a Web View within Piwik Mobile?

@tsteur tsteur added this to the Piwik Mobile Client milestone Jul 8, 2014
@tsteur tsteur removed the C: Core label Jul 25, 2014
@tsteur tsteur added this to the Future milestone Jul 25, 2014
@tsteur tsteur modified the milestones: 2.2.0, 2.1.0 Jul 30, 2014
This was referenced Jul 30, 2014
Closed
Closed
tsteur added a commit that referenced this issue Jul 30, 2014
@tsteur
refs #3243 this adds the possibility to use all existing segments in …
a29065c 
…the mobile app. I have not tested each possible use case (error handling etc) but it works on all platforms including iOS, Android and Web App so far
tsteur added a commit to matomo-org/matomo that referenced this issue Jul 30, 2014
@tsteur
refs matomo-org/matomo-mobile-2#3243 added translation key
0a3858e
tsteur added a commit that referenced this issue Jul 30, 2014
@tsteur
refs #3243 segmentation was not applied in real time map
a0c72b9
tsteur added a commit that referenced this issue Jul 30, 2014
@tsteur
refs #3243 as we load the list of segments only if a user clicks on i…
fd6a887 
…t we can cache for only 4 hours
@tsteur
Copy link
Member Author

tsteur commented Jul 30, 2014

Missing:

tsteur added a commit to matomo-org/matomo that referenced this issue Aug 1, 2014
@tsteur
refs matomo-org/matomo-mobile-2#3243 added translation key
4833f78
tsteur added a commit that referenced this issue Aug 6, 2014
@tsteur
refs #3243 segment rows should be larger on Android
7cde66e
tsteur added a commit that referenced this issue Aug 8, 2014
@tsteur
refs #3243 make sure the titleBar is shown on iPhones, prevent memory…
c190d30 
… leak on Android
tsteur added a commit that referenced this issue Aug 12, 2014
@tsteur
refs #3243 added a first version of segment chooser icon until we get…
60a6f56 
… it in higher resolution
tsteur added a commit that referenced this issue Aug 12, 2014
@tsteur
refs #3243 added segments icon in different sizes
4fe5d61
tsteur added a commit that referenced this issue Sep 1, 2014
@tsteur
refs #3243 looks like this makes the segment chooser on iOS finally w…
ed0a27e 
…orking. We cannot use Alloy there as it would lead to a crash due to a bug in alloy see https://jira.appcelerator.org/browse/TC-4502. Still needs to be tested on iPad
@tsteur
Copy link
Member Author

tsteur commented Sep 1, 2014

Only a test on iPad is missing

@tsteur tsteur closed this as completed Sep 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
2 participants
@tsteur @mattab