Hello my teacher and masters, I appreciate your time for reading this known issue, I really do.
I respect Google by Android and everthing. This gradle thing, instead, all of problem coming back to gradle. Anyway, since we are not allowed to ask in other question and since I did a lot of search in this 3 days with no success for now by Showcase View. Here is my problem:
First I found out this solution (answer by AndyGable), and tried to follow his tutorial, but here is my problem:
First question is, what exact folder of Showcase library (I want the name) should I put in which folder of project? I assume that the destination folder is app\lib of my project. Here are the pictures.
Second question:
How can I add showcase library to my project? Unfortunately, all tutorial was not brief and explained for amateurs, even one above. I want to know the steps like you give it to dummy for android studio 0.8.xx.
full version picture for detail (just in case) here
I tried these steps:
Open project structure > hit dependency > hit + .. and here is stuck. In the above picture I show how my project, setting.gradle, and other things are.
And one other thing:
I decided to avoid "2 - Add the showcase directory as a module to your project." step and followed others :
"3 Change your app's build.gradle file to include:
dependencies {
compile project(':libraries:showcase')
}
and so on and now I have showcase library included in my dependency but getting the error shown in the picture above: configuration with name 'default' not found!!!
I am really tired and this transparent activity is inevitable for me. Appreciate all of you as my brothers teachers and real masters. I just want to use this library in my project.
after asking and researching every nook and cranny TheLiTTle my good frend in xda-developer (BILLyTheLiTTle nick name in github ) give me a showcase that works like a charm now without any problem .. thanks to "amlcurran "for awesome free source saved me .
if someone want implement showcase on android studio and can't import it to gradle build system here i found fully working showcaseview , i was so confused and sad before i found this and now i really feels happy , hope it help you my friend reading my post .
you can download it here and open it with studio Gradle build system .
https://github.com/amlcurran/ShowcaseView
also again great thank to billytheLittle , there is more detail of showcaseview working . his work and all code is available to you guy need to see codes in detail , you can fork it if you like for sure :
https://github.com/BILLyTheLiTTle/Sepals/commit/056dc80dc0bcc3e235a46fd7dd6253487d676a04
Related
I am doing a project in my server. I am searching a simple dashboard to use in a project. I found a free coreui.io (https://coreui.io/demo/4.0/free/docs.html) dashboard. I works great when i run npm. But it's combined with so many part, thats its hard to master. How can I simplify it ? I mean I want 1 css file, 1 js file and htmls. Why ? well its easy to handle it when everything is in one place. (hate sass...) So is there a way to do so ? Or maybe someone knows simple but simmilar free (of not so expensive) dashboards.
Recently I've started to work with Maven JavaFX11 (openJFX11) and I noticed that there are many issues with javadoc in NetBeans. After some research I found that there is a bug with NetBeans that doesn't download the source+docs dependecies the right way (I mean it downloads it, but the next step to make it work is that you rename the source+docs files
issue & solution right here
But after I did that I noticed another docs issue and I have not found any similar topic on this so i dont know if it's just me or somebody have/had the same problem
When i type something like this:
private Label label;
label.[something...]
It only shows some of the docs.
It describes object Label the right way
After I type the dot, it only tells me about like 1/5 of the docs. Let me show you simple example.
And here is example of one that works
I looked into the javafx docs (.jar) and opened the Note.html and there ARE as the same things as in the docs they have on their websites, including all the methods, etc.
So... Dont you know, where the problem might be? I'm using the openJFX 11
It looks like you have encountered a known issue. See these NetBeans Bug Reports:
NETBEANS-1396 Maven: Downloaded javadoc / sources not attached to artifact with classifier.
NETBEANS-2197 Missing code completion and Javadocs in maven projects with classifier.
Also see these OpenJFX issues:
How to add javadoc in Netbeans #44
Attached Javadoc does not follow Maven convention #6
The fix is being implemented through a pull request for NetBeans 1396.
That fix is already included in NetBeans 11.3 which has a target release date of "January 15, 2020".
As title suggests, I am creating open source project that is in .net core 2.0. here is the architecture of it.
Now, it's working fine with everything including code first, seeders, swagger UI, TDD etc.
But there are many places where I have to add/modify classes when I want to add new Table in Database (see SimpleCRUD.Model > Entities)
So, I think I can reduce that boilerplate code, but I am not sure what is best way to do it.
What I did so far?
I tried to create a windows app, which will check and generate code for new added entity.
What I am trying to achieve?
Is there anyway I can add some kind of code in my current project and that will check after each build? is it feasible? any other suggestion to make it working perfectly?
Reference
I have checked this working in few other frameworks like serenity, asp.net boilerplate etc.
T4 temples can help cut down the boiler plate...
https://dotnetthoughts.net/generate-your-database-entities-using-t4-templates/
You've asked for my help here
I agree with other posters that you might want to look into T4. It sounds like you also want to create an MSBuild task.
I outlined the steps to do this for a different question in post here
You can find my code generators under this folder, CodeGen.SessionProxies
The t4 example can be found here: AppSessionPartials.tt
The MSBuild task can be found here: GenerateSessionProxies.cs
I had it generating a nuget file through the CodeGen.SessionProxies.nuspec. You won't find it on nuget.com; I had a local nuget repository. It would be helpful to you to look at the corresponding install.ps1 to understand how to set the generator up as a msbuild task.
Disclaimer: All of the GitHub links are subject to break if I ever decide to clean up that repo.
Cheers
at the moment I try to experiment a little bit with Atom for writing an API documentation with RAML. Everything works fine but one damn thing:
Everytime I type some file paths (e.g. !include schemas/file.schema Atom auto creates the file when I'm not quick enough with typing. So, in some cases I have a hole bunch of file-zombies in my schema folder. That's kind of annoying.
My setup is standard Atom on MacBook, with api-workbench plugin, which includes linter as well. I already had a look at all those settings concerning auto completion - nothing found there. Also, Google doesn't show any hints. Any Tips?
Best regards,
Chris
It looks like this is a defect in the api-workbench package:
Api workbench creates new schemas, while i type their paths. For example below, i can see two-three files created while i type full name:
E.g:
schemas:
- myschema: !include schemas/myschema.json
Will create following files:
schemas/my
schemas/mysche
schemas/myschema
schemas/myschemas.json - this file is existing, i've created it before. all other files are redudant and i have to delete them.
Bug is not reproduced with examples, which i can also include in my document. Having issues while edition RAML 0.8 files.
If you want to help the package maintainers fix the defect, can I suggest you put together a minimal but complete example that reproduces the issue, this will make it easier for them to identify and resolve the issue.
I seek a little help to wrap a package for meteor. It has always been my weakness on this framework. I know it is not difficult, I read tutorials and some articles like :
https://www.discovermeteor.com/blog/wrapping-npm-packages/
http://www.meteorpedia.com/read/Packaging_existing_Libraries
However I get lost in export and stuff, and it is time to understand !
I tried to wrap this package :
https://github.com/fians/Waves
(I knew one day I was going to not find the package already made by someone on atmosphere :()
So I wanted to do the thnings right, following guidelines made by dandv. I forked the repo, add the meteor packages with the files : export.js and package.js. Following the example of moment As you can see here :
https://github.com/Voyag3r/Waves
Finally, in my app, I created the local package folder with the meteor command : meteor create --package voyag3r:waves I tried to called the waves variable, bit it is not defined. I tried with and without a capital letter. (like in the source code waves.js). No, I tried with this.Waves instead of just Waves in export.js, neither.
There is something I do not understand with namespace and visibility I think, and errors are not displaying useful information this time. Is there someone to explain to me ? Because I would like to do a lot of other packages !
Thanks !
Glad to see that you read through those documents above, as they're quite helpful. However, I understand that it can be confusing to work through the details. Hopefully, I can assist you.
I recently finished packaging up a couple of libraries for Meteor, so you should take a look at those repositories as examples:
jspdf:core
jspdf:autotable
More specifically, take a look at the jspdf:core repository above and inspect the meteor-pre.js and meteor-post.js files for how to handle exporting variables:
meteor-pre.js
var window = {};
meteor-post.js
jsPDF = window.jsPDF;
Other important files include package.js and package.json, and of course autopublish.json, for integrating version updates with http://autopublish.meteor.com/, a fantastic tool written by Luca Mussi #splendido.
Additionally, I would recommend that you review the Official Meteor integration directly from 3rd party libraries discussion and ask #splendido or #dandv for assistance with reserving the namespace for this library.
This process has gone through rapid change over the last few months, and although not perfect, it's improving steadily. I'm encouraged to see that, like me, you want to assist the Meteor ecosystem.