flyve-mdm / android-mdm-dashboard Goto Github PK

Is your feature request related to a problem? Please describe.
Add the application of the bottom navigation at every fragment.

Describe the solution you'd like
Clicking on the sort button, sort the list.
Clicking on the reload button, reload the list to view if someone isn't on the list.
Clicking on the add button, include a new device.

Some information:
https://material.io/develop/android/components/bottom-navigation-view/

Write a welcome article for the page, this first article should give a brief introduction to the product and serve as an entry point for for new users. The idea is to be able to use this for promotion.

Said article should be written in Markdown and be published in the branch of gh-pages within the folder "_post"

Steps to follow for publication:

1. Enter http://prose.io/
2. Select the Flyve MDM organization
3. Enter in repository where you want to publish the article
4. Change to the branch gh-pages
5. Click on the "NEW FILE" button
6. Write your article
7. Save your work

Is your feature request related to a problem? Please describe.
Add the library to import the data.

Hi, @rafaelje

Could you update the Circle CI to deploy the test report to the project site?

http://flyve.org/flyve-mdm-android-admin-dashboard/reports/androidTests/connected/

Thank you.

Hi, @rafaelje

Please, create changelog file for library

https://github.com/conventional-changelog/standard-version

Hi, @rafaelje

We need to build and upload the APK with Travis CI.

Documentation:
https://docs.travis-ci.com/user/deployment/releases/

Banner:

*Is your feature request related to a problem? Please describe.
We put manually the number phones and it will get directly from GLPI.

Create releases of the library

Is your feature request related to a problem? Please describe.
Appear the number of devices, user, fleets, applications that we have in the dashboard.

Describe the solution you'd like
Show in a cardview the quantity.

Hi, @rafaelje

Please, integrate this feature into the Mobile Admin Dashboard of the MDM platform.

Ping request by SMS

Source code base:
https://github.com/itds-consulting/android-silent-ping-sms

Best regards.

Hi, @rafaelje

@ajsb85 is building a web service for the Help Center here:
https://github.com/flyve-mdm/flyve-mdm-graphql-service/

Best regards.

This error is showing on API 16 to 19

W/dalvikvm( 3937): threadid=1: thread exiting with uncaught exception (group=0x418d6ce0)
E/AndroidRuntime( 3937): FATAL EXCEPTION: main
E/AndroidRuntime( 3937): Process: org.flyve.admin.dashboard, PID: 3937
E/AndroidRuntime( 3937): java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{org.flyve.admin.dashboard/org.flyve.admin.dashboard.SplashActivity}: java.lang.ClassNotFoundException: Didn't find class "org.flyve.admin.dashboard.SplashActivity" on path: DexPathList[[zip file "/data/app/org.flyve.admin.dashboard-2.apk"],nativeLibraryDirectories=[/data/app-lib/org.flyve.admin.dashboard-2, /vendor/lib, /system/lib]]
E/AndroidRuntime( 3937): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2131)
E/AndroidRuntime( 3937): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2271)
E/AndroidRuntime( 3937): 	at android.app.ActivityThread.access$800(ActivityThread.java:144)
E/AndroidRuntime( 3937): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1205)
E/AndroidRuntime( 3937): 	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 3937): 	at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 3937): 	at android.app.ActivityThread.main(ActivityThread.java:5146)
E/AndroidRuntime( 3937): 	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3937): 	at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 3937): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 3937): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 3937): 	at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3937): Caused by: java.lang.ClassNotFoundException: Didn't find class "org.flyve.admin.dashboard.SplashActivity" on path: DexPathList[[zip file "/data/app/org.flyve.admin.dashboard-2.apk"],nativeLibraryDirectories=[/data/app-lib/org.flyve.admin.dashboard-2, /vendor/lib, /system/lib]]
E/AndroidRuntime( 3937): 	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
E/AndroidRuntime( 3937): 	at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
E/AndroidRuntime( 3937): 	at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
E/AndroidRuntime( 3937): 	at android.app.Instrumentation.newActivity(Instrumentation.java:1061)
E/AndroidRuntime( 3937): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2122)
E/AndroidRuntime( 3937): 	... 11 more
W/ActivityManager( 2270):   Force finishing activity org.flyve.admin.dashboard/.SplashActivity
W/ActivityManager( 2270): Activity pause timeout for ActivityRecord{41dd2bb0 u0 org.flyve.admin.dashboard/.SplashActivity t2 f}
I/Timeline( 2576): Timeline: Activity_idle id: android.os.BinderProxy@41d37f70 time:48527
I/ActivityManager( 2270): Killing 3532:android.process.acore/u0a4 (adj 15): empty #17
I/Timeline( 2270): Timeline: Activity_windows_visible id: ActivityRecord{41ddc000 u0 com.cyanogenmod.trebuchet/org.cyanogenmod.trebuchet.CustomHomeLauncher t1} time:48942

Observed Results:

We must change the workflow to publish the documentation on the project site

Expected behavior:

The documentation and code coverage must be created for the following branches

• master
• develop
• support/(version number) -> according to the version supported

The structure of the folders is as it follows

development/
|---- code-documentation/
|     |---- develop/
|     |---- master/
|     |---- support/
|           |--- 2.0.0/
|           |--- 3.0.0/
|---- coverage/
|     |---- develop/
|     |---- master/
|     |---- support/
|           |--- 2.0.0/
|           |--- 3.0.0/
|---- test-report/
      |---- develop/
      |---- master/
      |---- support/
            |--- 2.0.0/
            |--- 3.0.0/

Ref. #678

Hi, @rafaelje

Here the research about the new build environment of Travis CI:

Ref: https://docs.travis-ci.com/user/trusty-ci-environment/

Gradle 3.2.1
—------—
id: 1 or "tools"
     Type: Tool
     Desc: Android SDK Tools, revision 25.2.5
—------—
id: 2 or "platform-tools"
     Type: PlatformTool
     Desc: Android SDK Platform-tools, revision 26
—------—
id: 3 or "build-tools-26.0.0"
     Type: BuildTool
     Desc: Android SDK Build-tools, revision 26
—------—
id: 35 or "android-26"
     Type: Platform
     Desc: Android SDK Platform 26
           Revision 1
—------—
id: 170 or "extra-android-m2repository"
     Type: Extra
     Desc: Android Support Repository, revision 47
           By Android
           Local Maven repository for Support Libraries
           Install path: extras/android/m2repository
—------—
id: 178 or "extra-google-m2repository"
     Type: Extra
     Desc: Google Repository, revision 55
           By Google Inc.
           Local Maven repository for Support Libraries
           Install path: extras/google/m2repository

Hi, @rafaelje

You can send Slack-compatible simple webhooks to the Telegram dev chat using the URL in the environment var of Travis CI.

Example of usage: https://git.io/vQjP3

Regards.

Hi, @rafaelje

It is necessary to change the code generated by Javadoc, currently the returned code is not compatible with our sites in Jekyll. The most advisable thing would be to generate markdown files instead of HTML, but also it would be acceptable to customize the generated HTML.

I am currently researching on the subject so I can help as much as possible. this is the only thing I have found to be moderately useful so far:

• https://github.com/delight-im/Javadoc-to-Markdown/blob/gh-pages/_js/javadoc-to-markdown.js#L4
• https://github.com/todesking/nyandoc

Resources:
https://medium.com/google-design/designing-adaptive-icons-515af294c783

Is your feature request related to a problem? Please describe.
Add the login layout.

Describe the solution you'd like
It will be a normal login layout with the Flyve icon and he must to ask for a tokken.

Observed Results:

General review

Expected behavior:

• How tos section
  • Installation
  • Getting started
  • How it works
  • Use cases
  • How to contribute
• Development section
  • Code Documentation
  • Coverage
  • Test reports
• Screenshots (When applied)
• Versioning (Develop, Master, Support)

Build the APK with Travis CI by tags

API Documentation
https://developers.google.com/android-publisher/api-ref/edits/apks/upload

Hi, @Naylin15

Could you split the code of conduct from the contributing guidelines?

Thank you.

Is your feature request related to a problem? Please describe.
Edit the cardview textviews with the edit botton at the sms ping layout.

Describe the solution you'd like
When clicking in the botton, it will appear a popup dialog and let change the textviews.

Hi, @Naylin15

Change the name "Wiki" to "How-tos" and add these articles; and add the sub menu items to the Development section. If these pages does not exist, please, create an issue and request it. 👍

How-tos

• How to install
• How to use
• Use Cases
• How it works
• How to contribute
• How to Translate

Development

• Code documentation
• Code coverage
• Test report

Hi, @rafaelje
I will create gh-pages as requested in this issue: flyve-mdm/flyve-mdm.github.io#13
Regards.

Is your feature request related to a problem? Please describe.
When you are searching for the agents mobile phone, an option to call directly when you find the phone number.

Describe the solution you'd like
Add a new button to call directly.

Is your feature request related to a problem? Please describe.
Change every component of the application with material design to give a beautiful design.

Describe the solution you'd like
Changin the buttons and cardview from support.v7 to material.design.

Some information.

• Continuous integration
• Continuous deployment
• Changelog
• Test reports
• Coverage reports
• Code documentation
• Artifacts for downloads and release description

Hi, @rafaelje

It is necessary that all the .html files of the coverage have the following header:

---
layout: coverage
---

This is because the Jekyll pages used them to integrate the files into the template.

Thanks.

Describe the bug
I clone the project with the library already included but it gives me and error and I can't work with that.