Closed rabyunghwa closed 10 years ago
Not sure what you mean by it's missing methods. Are you having compilation issues?
Yes man. On compilation, it shows 4 errors:
Can you post your gradle file for reference?
Gradle file? You mean the build.gradle file? Or my source code?
On Sat, Jun 21, 2014 at 12:54 AM, Anton Lopyrev notifications@github.com wrote:
Can you post your gradle file for reference?
Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46701253 .
If you love something, let it go. If it comes back, it is yours forever. If it doesn't, it never was to begin with.
Yes, the build file.
On Sun, Jun 22, 2014 at 11:06 AM, ByungHwa Ra notifications@github.com wrote:
Gradle file? You mean the build.gradle file? Or my source code?
On Sat, Jun 21, 2014 at 12:54 AM, Anton Lopyrev notifications@github.com wrote:
Can you post your gradle file for reference?
Reply to this email directly or view it on GitHub < https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46701253
.
If you love something, let it go. If it comes back, it is yours forever. If it doesn't, it never was to begin with.
—
Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46788067 .
Anton Lopyrev Co-Founder & CTO • Umano Follow me @tokudu http://twitter.com/tokudu http://umanoapp.com
Sorry for the late reply. My build.gradle file is like this: apply plugin: 'android'
android { compileSdkVersion 19 buildToolsVersion "19.1.0"
defaultConfig {
applicationId "my.application"
minSdkVersion 16
targetSdkVersion 19
version code 1
version name "1.0"
} build types{ release { runProguard false proguardFiles getDefaultProguardFile('pro guardian droid.txt'), 'proguard-rules.pro' } } } dependencies { ..... ..... } On Jun 24, 2014 12:09 AM, "sothree" notifications@github.com wrote:
Yes, the build file.
On Sun, Jun 22, 2014 at 11:06 AM, ByungHwa Ra notifications@github.com wrote:
Gradle file? You mean the build.gradle file? Or my source code?
On Sat, Jun 21, 2014 at 12:54 AM, Anton Lopyrev < notifications@github.com> wrote:
Can you post your gradle file for reference?
Reply to this email directly or view it on GitHub <
https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46701253
.
If you love something, let it go. If it comes back, it is yours forever. If it doesn't, it never was to begin with.
Reply to this email directly or view it on GitHub < https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46788067>
.
Anton Lopyrev Co-Founder & CTO * Umano Follow me @tokudu http://twitter.com/tokudu http://umanoapp.com
Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46865844 .
I don't see you importing slidinguppanel at all
Actually I did man. I defined the repository inside the dependency block as mentioned in the descriptions. On Jun 25, 2014 12:02 AM, "Anton Lopyrev" notifications@github.com wrote:
I don't see you importing slidinguppanel at all
Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46991344 .
I put SlidingUpPanel repository in the dependencies section like this: dependencies { compile 'com.so three.slidinguppanel:library:2.4.0+' ....a bunch of other repositories... }
Anyway I don't think I'm the only one who is experiencing this issue. Do you know how I can fix this? Thank you. On Jun 25, 2014 12:31 AM, "ByungHwa Ra" rabyunghwa@gmail.com wrote:
Actually I did man. I defined the repository inside the dependency block as mentioned in the descriptions. On Jun 25, 2014 12:02 AM, "Anton Lopyrev" notifications@github.com wrote:
I don't see you importing slidinguppanel at all
Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46991344 .
So far, it's seems that it's just you. I haven't seen any other reports. Try using compile 'com.sothree.slidinguppanel:library:+'
On Wed, Jun 25, 2014 at 12:51 AM, ByungHwa Ra notifications@github.com wrote:
I put SlidingUpPanel repository in the dependencies section like this: dependencies { compile 'com.so three.slidinguppanel:library:2.4.0+' ....a bunch of other repositories... }
Anyway I don't think I'm the only one who is experiencing this issue. Do you know how I can fix this? Thank you. On Jun 25, 2014 12:31 AM, "ByungHwa Ra" rabyunghwa@gmail.com wrote:
Actually I did man. I defined the repository inside the dependency block as mentioned in the descriptions. On Jun 25, 2014 12:02 AM, "Anton Lopyrev" notifications@github.com wrote:
I don't see you importing slidinguppanel at all
Reply to this email directly or view it on GitHub < https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-46991344
.
— Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-47070724 .
Anton Lopyrev Co-Founder & CTO • Umano Follow me @tokudu http://twitter.com/tokudu http://umanoapp.com
Dude I decided to create a new class called SlidingUpPanelLayout myself in my package and just copied the code from the library to it. And then add some required attributes and stuff. Now everything works. So I'm pretty sure the error had something to do with the repository.
I can assure you there is nothing wrong with the repository and what is retrieved by gradle in Android Studio. I've been using it successfully for the past 4-5 weeks and it took me literally less than a minute to get auto-complete access to the library classes while typing, just after I pasted the one line compile dependency and hit "sync."
I'd suspect there's something wrong with your development environment (outdated SDK, Build-Tools, IDE, etc), a serious misconfiguration of the project somehow, or a conflicting library in your dependency list before suspecting this library or it's repository. Had you posted your gradle file in it's entirety, the community may have been able to spot something such as a conflict, but you didn't and omitted ALL of your dependencies. To that note, please only omit or mask requested information if it's sensitive, such as API keys, account information, passwords, NDA contract limitations, personal info, etc.
No no dude I think there is some misunderstanding here. I truly admire your work. The reason I didn't put all my repositories there was that my laptop didn't have access to the Internet at that moment so I had to type in the whole file myself on my phone. Besides I did not think that it mattered at all. Anyways dude I think there were some conflicts with other libraries. And I will type the whole build file here.
apply plugin: 'android'
android {
compileSdkVersion 19
buildToolsVersion "19.1.0"
defaultConfig {
applicationId "..........."
minSdkVersion 16
targetSdkVersion 19
versionCode 1
versionName "1.0"
}
buildTypes {
release {
runProguard false
proguardFiles getDefaultProguardFile('proguard-android.txt'), '
proguard-rules.pro'
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.romainpiel.shimmer:library:1.2.0@aar'
compile 'com.android.support:support-v4:19.1.0'
compile 'com.github.gabrielemariotti.cards:library:1.7.3'
compile 'com.squareup.picasso:picasso:2.3.1'
compile 'com.nhaarman.listviewanimations:library:2.6.0'
compile 'com.etsy.android.grid:library:1.0.5'
compile 'com.nineoldandroids:library:2.4.0+'
compile 'com.github.flavienlaurent.discrollview:library:0.0.2@aar'
compile files ('libs/KenBurnsView-1.0.2.jar')
compile project(':libraries:PanningViewLibrary')
}
Thanks.
On Thu, Jun 26, 2014 at 3:38 PM, John S. notifications@github.com wrote:
I can assure you there is nothing wrong with the repository and what is retrieved by gradle in Android Studio. I've been using it successfully for the past 4-5 weeks and it took me literally less than a minute to get auto-complete access to the library classes while typing, just after I pasted the one line compile dependency and hit "sync."
I'd suspect there's something wrong with your development environment (outdated SDK, Build-Tools, IDE, etc), a serious misconfiguration of the project somehow, or a conflicting library in your dependency list before suspecting this library or it's repository. Had you posted your gradle file in it's entirety, the community may have been able to spot something such as a conflict, but you didn't and omitted ALL of your dependencies. To that note, please only omit or mask requested information if it's sensitive, such as API keys, account information, passwords, NDA contract limitations, personal info, etc.
Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-47196255 .
If you love something, let it go. If it comes back, it is yours forever. If it doesn't, it never was to begin with.
Glad that you found a way to get it work.
On Wed, Jun 25, 2014 at 11:35 PM, ByungHwa Ra notifications@github.com wrote:
Dude I decided to create a new class called SlidingUpPanelLayout myself in my package and just copied the code from the library to it. And then add some required attributes and stuff. Now everything works. So I'm pretty sure the error had something to do with the repository.
—
Reply to this email directly or view it on GitHub https://github.com/umano/AndroidSlidingUpPanel/issues/204#issuecomment-47192168 .
Anton Lopyrev Co-Founder & CTO • Umano Follow me @tokudu http://twitter.com/tokudu http://umanoapp.com
The repository seems to miss a methods called 'onBackPressed'. If I import the library project it would be fine.