How to add plugin to shopware shop when vendor is too big? - shopware

I have a problem with my plugin. I want to add it to Shopware shop but it has some composer dependencies and vendor folder have almost 70MB, after compressing 30MB. Shopware allows the vendor folder to have a maximum of 10MB.
Is there any solution of this problem? Can I add plugin in any other way without vendors?
I tried compress vendors but it's still too big.

You mean the shopware store (for store.shopware.com)?
There is no other possibility. You might want to check the dependencies. What makes the vendor so big? Images?
In your Shopware shop you can upload/add whatever you want.

Related

Is there a custom module to drag and drop files in drupal 8?

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.

add custom informations to ghost posts

I am searching an CMS to publish a blog based on nodejs. One of the cms I found was ghost. It looks easy. But I am not sure if it is to simple.
What I want to do is, to add Infomationens like a location or a city name, to show Post or Images on a Map. I found no informations about. Is it possible?
If not, are there other Blog systems base on nodejs which have possibilty to add custom information?
This isn't built into the Ghost core, but you could write your own plugin to do this! Check out the development documents here https://github.com/TryGhost/Ghost/wiki/Apps-Getting-Started-for-Ghost-Devs

material design to a stock AOSP ROM app (like Settings, Email etc)

Is it possible to use the AppCompat library for material design in a complete pre-Lollipop ROM. When I mean ROM, example Email, Settings, Browser everything. I can see for a single app I could use app compat
compile 'com.android.support:appcompat-v7:21.+'
But how could I do it for app inside a ROM? I am very confident that this must be possible, as if I install PlayServices in a Kitkat-AOSP ROM (from Galaxy S), I can get material design email (Gmail) which is propreitary.
I am wondering if one needs to make changes to Android.mk or AndroidManifest.xml to some how include "appcompat"?
many thanks
Many thanks,
Apps have to be specifically written to use Material Design. The AppCompat support library helps you add MD to pre-Lollipop devices.
Apps like Gmail were updated to include Material Design. There is no way to simply update an existing APK to include MD.

Dart asset vs web directories?

I've seen Dart code that places all CSS, HTML, JS, images, etc. in an asset subdirectory, and other projects that place those same files under a web directory. Even the Dart package layout spec is ambiguous on the subject.
So I ask: when to put client-side resources under asset, and when to put them under web?
This is a new feature/convention.
The problem is, that the web server integrated into Darteditor doesn't yet support the asset directory. It's only supported by pub serve yet. But I guess Darteditor will support it soon and then this is the way to go.

What is VENDOR folder for in Kohana 3.3?

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.

Resources