[enh] Warnings during builds

[Larpoux]

When we build the App on Android we have the following warning :

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

This is not clean.

[Larpoux]

WARNING: [Processor] Library '/Volumes/Macos-Ext/Users/larpoux/.gradle/caches/modules-2/files-2.1/io.flutter/flutter_embedding_debug/1.0.0-11d756a62ed0ddf87a9ce20b219b55300ec6b67d/ac5a060db9325ec08f7a9285b3847685f1fb69f4/flutter_embedding_debug-1.0.0-11d756a62ed0ddf87a9ce20b219b55300ec6b67d.jar' contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.
 Example of androidX reference: 'androidx/annotation/NonNull'
 Example of support library reference: 'android/support/annotation/NonNull'
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

[Damanotra]

Looking forward to the release where this bug fixed 👍

[Larpoux]

Yes,

I have also this :

contains references to both AndroidX and old support library. 
This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.  

Also : gradle-lint gives many warnings in TauEngine

Also : Bintray Upload tries to do a javadoc but gives many errors. I think that it is not important but this is not clean.

I spent a few time on those points, but did not fund the reasons. If someone can help, it will be great.

[Damanotra]

I never participate in any open source development, would try my best if you guide me, what should I do and where do I start?

[Larpoux]

Every body can do something on a free project. Even very simple things are great, because Free projects are very often the result of many, many people doing just simple things.

What you can do depends only on you :

• Some people can re-read documentation and correct it
• Some people can fix some bugs
• Some people can improve and simplify the setup
• Some people can improve the API
• Some people can add new features
• Some people can re-build the architecture
• ...

Everything you do on a free project that can be useful for others is great

And because we have no boss and nos clients/customers, we can do what we want to do and when we want tod do. This is FREEDOM.

[Larpoux]

But also : If someone decide he/she wants to work on a specific thing, better to tell it to the Project Manager (me 😆 ) before beginning so that we can be sure not two people working at the same time on the same point. And the Project Manager (me 🤣 ) can give some main directions.

[Larpoux]

I am currently working on three area :

• The documentation
• The architecture
• Cleaning the API

Probably better for you not working on those points today. Please have a look to this.

[Larpoux]

V 6.4.3 will use gitbook for the documentation.

This will be better than now. But I am not completely satisfied by gitbook :

• The license is ambiguous. Flutter Sound will never use any tool not free. Gitbook is (was) released under an Apache license. This is a free license. But if you look to the Gitbook repo, you will notice that this project is deprecated and no more supported, in favor of there own project. But their own project seems not to be free anymore. This is what happens for Projects which does not have a Copyleft clause (GPL 😄 ).

• There is bugs when we want to link one of the doc page to an HTML page (dartdoc, for ex.). We cannot use a relative link. This means that we must use absolute URL and so, the link of one branch will always libnk to the master branch. This is not OK.

• Hard absolute links open a new tab in Firefox/Chrome instead of using the current tab. I do not like that

• The menu on the left panel cannot be collapsed/expanded. I miss this feature

I do not have enough time to spend on finding another tool which would be FREE and better. This is an example of a task to do. But there are many others, and you certainly have your own preference. We are FREE.

Another area where I am currently naked :

• Javascript
• React Native
• I do not speak English correctly and I cannot write a good documentation

Other things :

• Actually the FlutterSound Recorder does not work on Webkit (Safari). This is really something missing for supporting correctly Flutter Web

• Actually Recording to Stream and Playback from Stream does not work on Flutter Sound Web

• There is a bug in Playback from Stream in iOS, and I did not found the reason

• ... (many other bugs)

[Larpoux]

You are in love with Flutter. But you must understand one thing : I disagree with @bsutton who wants to do everything in Dart. My opinion is that the code in Flutter/Dart should be as smaller as possible, for several reasons that I prefer not to explain here.

It means that most development will be done with :

• Objective C on iOS
• Java on Android
• Javascript on Flutter Web

[Larpoux]

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.

gradle lint in tau_core has errors Many erros during Bintray upload

Internal documentations of sources

warning: unresolved doc reference [Category], from player.FlutterSoundPlayer.openAudioSession: (file:///Volumes/Macos-Ext/Users/larpoux/projmac/flutter_sound/flutter_sound/lib/public/flutter_sound_player.dart:454:30)

warning: dartdoc generated a broken link to: topics/utilities.md warning: dartdoc generated a broken link to: topics/ui_widget.md warning: dartdoc generated a broken link to: topics/mediaformat.md warning: dartdoc generated a broken link to: topics/track.md warning: dartdoc generated a broken link to: player/FlutterSoundPlayer/track.md warning: dartdoc generated a broken link to: api/track.md

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Leave a comment or this will be closed in 7 days.