In DOCROOT folder of Kohana 3.3 there is a new vendor folder.
What is it for?
It's not supposed to be there. It was leftover from composer.
It is where you can drop external libraries for use with Kohana.
For example, this is where I put my 3rd party Twitter API.
May be irrelevant but for newbies to KOHANA 3.3, that Vendor directory is meant for extending/adding custom vendor based functionality, similar to the plug-ins concept. And it's not new addition to kohana 3.3.
Also as #zombor mentioned it's a-left-over in DOCROOT.
Rest is all clear in my opinion.
Related
There is an option in Drupal 7 to drag and drop files (https://www.drupal.org/project/dragndrop_upload). But couldn't find one for Drupal 8. Please help me out.
In Drupal 8 drag and drop files feature is possible using the PLupload (https://www.drupal.org/project/plupload) and PLUPload Widget (https://www.drupal.org/project/plupload_widget) combination. Provides integration between for the Plupload widget to upload multiple files and Drupal.
I also search for this but not found any module for that.
You need to do it by custom by using any third party library.
E.g: you can use Dropzone library, they have good documentation also.
Work is being done directly in Drupal 8 core. All efforts should be directed there so that contrib/custom modules are not necessary for this purpose.
See File Field design update for details.
What IDE can I use to edit OpenCart?
I dont see any specific,
I have been using Sublime and PHP storm (Prefer sublime if your system is slow else PHP Storm).
I don't think there is a specific application for developing an OpenCart website. Moreover, this question also depends on the system you use...
I currently use Eclipse, but I'm certain that softwares like Atom or Brackets can be perfectly appropriate: in my opinion, the only feature you need is a tree view to be able to manage the whole project.
I think NetBeans is very good with Opencart. Give it a try.
I have an instance of Nuxeo 5.8 installed and running on s3 and I want to extend it so I can add customized metadata to an asset. E.g., say a normal asset has metadata like "title", "description" and "author", I want to be able to add my own fields like "brand" and "SKU" (among others).
From what I understand it's only possible to do this via the front end when you have upgraded to Studio, so what I'm looking at doing is somehow extending the API (and the related XSDs?) to allow extra metadata. Also, once I've extended the API I'm aware that I'll have to provide my own front end that interfaces with my extended API, and will have to bypass the out-of-the-box Nuxeo front end.
What exactly do I need to do to achieve this? I'm guessing I'll need to write a Java app that interfaces with the Nuxeo API somehow?
I'm struggling a bit to find documentation for 5.8 - I did come across Customizing metadata for 5.5, but I'm guessing this is out of date?
Any insight would be much appreciated.
I've also posted this question on Nuxeo's answers site here.
This was answered on the Nuxeo answers site.
I have to design a mobile application as my mini project. I cannot find the documentation of javax.microedition in my java folder. I tried searching it online, but all the websites have vague information. I need proper details of this package. Where can I find it?
tried searching it online, but all the websites have vague information
Did you try different search engines? I always switch to alternative engine when I feel that one I usually prefer doesn't do the trick.
Don't know if your case but to me results of search for "javax.microedition package" were totally different depending on engine. While one engine ("good") gave me a needed link at the top of the very first page, another had it buried at 7th page ("bad", really bad).
Anyway, there's pretty detailed and accurate answer at SDN Mobility Reference FAQ - J2ME Package Listing:
Question
What package names are defined in the J2ME environment?
Answer
The J2ME environment introduces a number of Java packages. These are almost exclusively placed into the package javax.microedition. The few exceptions are technologies that could be used in one or more other editions of the Java platform as well. For example, because you might use Bluetooth technology in either J2ME or J2SE, the Java APIs for Bluetooth specification (JSR 82) uses the package names javax.bluetooth and javax.obex.
The table shows the package names specified by the J2ME JSRs, as defined by the Java Community Process (JCP). It includes...
...continue reading at above link if you're interested in more details
I've been using Kohana 2.3.7. There are somethings that are holding us back to using Kohana 3 and one is the lack of modules compared to 2.3.7. For instance, I can't seem to find the Payment module (Paypal, 2C0, Authorize.net, etc) present in 2.3 to 3. If there is already, can you please direct me to it?
Thanks for the help.
There are a few payment modules for Kohana 3.
Paypal
Google Checkout
Both created by Woody Gilk.
You also have the option of porting the Kohana 2 libraries. Takes no longer than half a day and gets the job done.
You can load the official authorize.net PHP SDK as a Kohana module.
http://dev.strategystar.net/2011/10/authorize-net-module-for-kohana-3-x/
I hope it helps. The two resources that Pixel Developer posted work nicely for Paypal and Google Checkout.