Is the SideDrawer not working in NativeScript? If so, I can leave it and look for another solution.
I'm testing out NativeScript to see if it is something for my project. Doing this tutorial http://docs.nativescript.org/angular/tutorial/ng-chapter-1 it felt really promising.
But then I tried to add a sideDrawer and everything just became extremely confusing. It seems like there are a lot of different versions on how to use the SideDrawer and the tags are different: RadSideDrawer, SideDrawer etc.
I tested these (and others):
https://www.nativescript.org/blog/using-cross-platform-native-sidedrawer-component-in-nativescript
http://www.techumber.com/navigation-drawer-side-drawer-for-nativescript/
All of the attempts I've made have resulted in different kind of errors from segmentation fault when starting up or null pointer exception when not being able to call openDrawer on the RadSideDrawer (or whatever it is supposed to be called).
I just want to have a sidedrawer in my app... Had no idea that it could be so complex.
A good sample (also listed in nativescript-snacks and tweeted by nativescript) ist the sidedrawer-template from shripalsoni04:
https://github.com/shripalsoni04/nativescript-angular-drawer-template
It worked well for me on Android (just make sure you download everything, including the icons from App_Resources! Otherwise, the sidedrawer won't display!). Also good to know: It actually uses the nativescript-telerik-ui sidedrawer (so make sure everything is installed correctly there as well => also check package.json for right dependencies).
Related
When I run composer updates I'll occasionally get messages that packages are abandoned and I should use a different one instead, like Package webflo/drupal-core-require-dev is abandoned, you should avoid using it. Use drupal/core-dev instead. I don't have experience with Composer so I'm curious as to what is seen as the best practice for replacing outdated packages.
Where do these messages come from? I'm unsure if the source is always reliable.
I think the best practice is quite clear from the message "you should avoid using it". How/When to do this is not as clear. Abandoned packages will not receive updates, but composer will not be able to tell you how difficult it will be to transition to the recommended alternative. It might be that all you have to do is replace the package, because it was only a name change or having to modify your code as well.
In your case webflo/drupal-core-require-dev only contains a composer.json and the required packages match with what the alternative drupal/core-dev provides. That means replacing the package should be as easy as changing the name in your composer.json and then do a composer update drupal/core-dev.
For packages where the answer is not as straightforward, you have to rely on automated/manual tests to see if everything still works. Static code analysis tools might help as well. You will have to set them up before you do the change, so that you can see how their output differs and fix the new issues that come up.
You should do the switch to the new dependency as early as possible. Leaving it in will likely cause more work in the future when replacing it and might pose a security risk (if it is outdated and insecure). I understand that this is not always possible and using something like roave/security-advisories to tell you when there are known security issues in a package might help postponing it and giving some sense of security.
I began a very helpful discussion with Alessandro Pignotti (#alexp-sssup) on
https://gitter.im/leaningtech/cheerpj?at=5f189bf76279c91f420801af
about how to get Java applet byte-code to work with CherrpJ in present-day browsers.
Hopefully the two examples referenced there in this post can serve as a guide to others who might also be struggling with getting the basics of java applet conversion with CheerpJ going.
As I mentioned there I would, I am now putting this follow-up question in stackoverflow:
I was hoping to get this page to work in which I am trying to run the same byte-code with both the <cheerjp-applet> and <applet> tags on the same page. However the page never loads properly. The best I can achieve is (with page loading seeming to hang) to force some hung script to stop, which then often ends up bringing the CheerjP button up, but I have yet to the get button in the original applet to show on the same page (in a java-enabled browser-setup where the legacy applet does work properly from this page). Sometimes the browser completely hangs before even the Cheerpj script gets to work.
So my question is: Is what I am attempting even possible, and if so what could be wrong with this first attempt of mine?
P.S.: The stackoverflow tag [cheerpj] does not exist, so the suggestion on Gitter to use it fails for me: I don't have a reputation of 1500 :( !!! Since a pretty thorough web search has revealed very little in-depth technical discussion about CheerpJ besides what's in the Gitter CheerpJ room I reference at the start of this post, I am not sure how far the attempt to move discussion in to stackoverflow is going to go.
What you are trying to achieve is not supported by CheerpJ. When CheerpJ starts it will automatically replace any <applet>, <object> or <embed> tag containing Java applets and execute them internally. The special prefixed tags, such as <cheerpj-applet> are designed to avoid accidental execution by the native plugin if installed.
We don't plan to support this use case in the future since for the vast majority of users the native Java plugin does not work anymore anyway.
You may consider using two <iframe> tags to get the behavior you want using 2 independent pages.
Sorry for such broad question, but after some attempts I'm not sure how to use python bindings. I tried to just import "request.py" or "capi.py" but all I got were errors. After adding missing libraries to my search path, I ended with missing symbol "_dispatch queue_attr_concurrent" (which suggest wrong library version?).
My question isn't about that particular error, but rather correct way of interacting with python bindings (and SourceKit itself). I have tried to use precompiled version, and compile it myself (https://stackoverflow.com/a/40033117/1117854), but result was all the same.
Is there something obvious that I'm missing? Or maybe someone with similar experience succeed and have some tips? It's not well documented and I'll probably find solution sooner or later, but I believe I'm not the only one who felt lost after first contact with SourceKit.
I have a plugin's resource codes and I want to edit. Because I want to change plugin's prefix but it isn't possible unless edit plugin. I tried edit with Eclipse but I had a lot of errors.
If you have source codes of some plugins, there meight be a problem, that they are using some api for example WorldEdit api, but you don't have it added in your project. You have to look into code and find out what they use. Then download the api and add it in Build Path - Right Click the project->Build bath->add external Jars. I hope this will help.
You may be getting errors from imports, API's, etc.
The best way to change this is to contact the developer of the plugin, who has the project themselves. It's not a good idea to change code unless you have full permission; but I will still tell you some possible ways to fix it.
Your imports may be faulty, check those.
Actually REVIEW the code yourself– Don't mess around with things you don't know what they do.
CHANGE YOUR PACKAGE NAMES (This got me before, simple mistake)
If there are comments in the code, use those to your advantage
Google your errors.
If you are new to Java, don't skip to changing code already. TRUST ME. Learn all you can before skipping to other "higher level" developer styles.
Like I said, these are vague and simple ways to fix it; the best way to have your feature implemented is to contact the developer.
*I understand that this thread is old; I'm just saying this because there are currently no answers that describe this for other Google travelers of the internet.
Anyone want to share an Xcode project that has MGTwitterEngine in it? Mine won't compile. Are there certain project settings to set? I just made a stock tab bar app for iPhone and added the MGTwitterEngine files. Tons of compiler errors. What am I missing?
I had same problem. To get it to compile I added "$SDKROOT/usr/include/libxml2" to the Header Search Paths list. I also checked Recursive checkbox.
Make sure that you're adding "$SDKROOT/usr/include/libxml2" to header search paths in your Target settings and not just the Project.
I managed to get the library path right eventually. However, in the end, I got rid of the whole MGTwitterEngine thing and went with the TwitterHelper stuff that I noticed the folks from the Stanford iPhone class using. It uses the synchronous calls and it's not as full-featured. But it's lighter and I understand it better. I just use threading to counter the synchronicity. (Hey, wasn't that a song?!) Anyway, a little JSON code and it's all under control. Most of you are probably going to think I'm a noob but it just feels cleaner and easier to handle. I know there are plenty of good reasons to use MGTwitterEngine.
Bottom line is, even though I got it to work by getting the library path right, I don't even need to worry about any paths by adding the very small TwitterHelper stuff to my project. Seems more Mac-like than to have to go into too much tinkering (I can already hear the experts saying that setting paths is not too much but I absolutely detest the Project Settings dialog.)
You also need to add
libxml to Header Search Path ( should be something like /usr/library/libxml2 )
I just wanted to add something that tripped me up. You have to make sure the Target header search path is also set because it may override the default project search path headers. If you are unable to find some header files that the path is definitely pointing to correctly in your project search path headers, then this is probably the reason.
You're probably missing the libxml library. You need to add that to your linked frameworks. Here's a question that has a little more information, but that's the gist of it.
Best approach for XML parsing on the iPhone