Payments gateways are very useful components of any e-commerce store. One of the popular payment gateways is Stripe. it's becoming more popular nowadays.
Stripe's simple definition is :
We bring together everything that’s required to build websites and apps that accept payments and send payouts globally. Stripe’s products power payments for online and in-person retailers, subscription businesses, software platforms and marketplaces, and everything in between. ~ Stripe
To begin this laravel tutorial, I hope you already have fresh laravel repo.
Stripe Configuration with Laravel
Run the following command to install stripe :
composer require stripe/stripe-php
if you don't have a Stripe account, you'll want to set that up and add your API keys. Add the following to your .env file.
Here we are going to create stripe session from backend and redirect to stripe checkout page once we will receive the sessionId from backend.
Assume that makePaymentURL is something like "APP_URL/stripe-charge".
Now let's say when you hit the submit form of stripe it will call MakePaymentURL and that URL returns your session ID which we will use to redirect to the stripe checkout page.
$(document).on('click', '#makePayment', function () {
The fault life cycle or defect life cycle is the specific set of states that a fault goes through before it is closed or resolved. When a fault is detected - by a tester or someone else on the team - the life cycle provides a tangible way to track the progress of a bug fix, and during the fault's life multiple individuals touch it - directly or indirectly. Troubleshooting is not necessarily the responsibility of a single individual. At different stages of the life cycle, several members of the project team will be responsible for the error. This blog will help you understand how many cases the error goes through varies from project to project. The life cycle diagram covers all possible situations
What’s The Difference Between Bug, Defect, Failure, Or Error?
Bug : If testers find any mismatch in the application/system in testing phase then they call it as Bug. As I mentioned earlier, there is a contradiction in the usage of Bug and Defect. People widely say the bug is an informal name for the defect. Defect : The variation between the actual results and expected results is known as defect. If a developer finds an issue and corrects it by himself in the development phase then it’s called a defect. Failure : Once the product is deployed and customers find any issues then they call the product as a failure product. After release, if an end user finds an issue then that particular issue is called as failure Error : We can’t compile or run a program due to coding mistake in a program. If a developer unable to successfully compile or run a program then they call it as an error.
Software Defects Are Basically Classified According To Two Types :
Severity
Bug Severity or Defect Severity in testing is a degree of impact a bug or a Defect has on the software application under test. A higher effect of bug/defect on system functionality will lead to a higher severity level. A Quality Assurance engineer usually determines the severity level of a bug/defect.
Types of Severity
In Software Testing, Types of Severity of bug/defect can be categorized into four parts : Critical: This defect indicates complete shut-down of the process, nothing can proceed further Major: It is a highly severe defect and collapses the system. However, certain parts of the system remain functional Medium: It causes some undesirable behavior, but the system is still functional Low: It won't cause any major break-down of the system
Priority
Priority is defined as the order in which a defect should be fixed. Higher the priority the sooner the defect should be resolved.
Priority Types
Types of Priority of bug/defect can be categorized into three parts : Low: The Defect is an irritant but repair can be done once the more serious Defect has been fixed Medium: During the normal course of the development activities defect should be resolved. It can wait until a new version is created High: The defect must be resolved as soon as possible as it affects the system severely and cannot be used until it is fixed
(A) High Priority, High Severity
An error which occurs on the basic functionality of the application and will not allow the user to use the system. (E.g. A site maintaining the student details, on saving record if it, doesn't allow to save the record then this is high priority and high severity bug.)
(B) High Priority, Low Severity
High Priority and low severity status indicates, defect have to be fixed on immediate bases but does not affect the application while High Severity and low priority status indicates defect have to be fixed but not on immediate bases.
(C) Low Priority Low Severity
A minor low severity bug occurs when there is almost no impact on the functionality, but it is still a valid defect that should be corrected. Examples of this could include spelling mistakes in error messages printed to users or defects to enhance the look and feel of a feature.
(D) Low Priority High Severity
This is a high severity error, but it can be prioritized at a low priority as it can be resolved with the next release as a change request. On the user experience. This type of defect / defect can be classified in the category High severity but Low priority.
New: When a new defect is logged and posted for the first time. It is assigned a status as NEW. Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team Open: The developer starts analyzing and works on the defect fix Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as "Fixed." Pending retest: Once the defect is fixed the developer gives a particular code for retesting the code to the tester. Since the software testing remains pending from the testers end, the status assigned is "pending retest." Retest: Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and changes the status to "Re-test." Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed and the status assigned is "verified." Reopen: If the bug persists even after the developer has fixed the bug, the tester changes the status to "reopened". Once again the bug goes through the life cycle. Closed: If the bug is no longer exists then tester assigns the status "Closed." Duplicate: If the defect is repeated twice or the defect corresponds to the same concept of the bug, the status is changed to "duplicate." Rejected: If the developer feels the defect is not a genuine defect then it changes the defect to "rejected." Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status "Deferred" is assigned to such bugs Not a bug:If it does not affect the functionality of the application then the status assigned to a bug is "Not a bug".
The tester finds the defective status assigned to the defect. 2. A defect is forwarded to the project manager for analysis. 3. The project manager decides whether a defect is valid. 4. Here the defect is invalid. The status is "Rejected". The project manager assigns a rejected status. If the bug is not resolved, the next step is to check that it is in scope. Suppose we have another function - email functionality for the same application, and you find a problem with it. However, it is not part of the current version if such errors are assigned as a deferred or deferred status. 7. Next, the manager checks to see if a similar error has occurred earlier. If so, a duplicate status is assigned to the error. 8. If not, the bug is assigned to the developer, who starts correcting the code. 9. During this phase, the defect is assigned a status in process, Once the code is fixed. A defect is assigned a status fixed. Next, the tester tests the code again, If the test case is passed, the defect is closed. If the test cases fail again, the bug is reopened and assigned to the developer. 12. Consider a situation where, during the first release of the flight reservation, an error was detected in the fax order, which has been fixed and a status of closed has been assigned. The same error occurred again during the second upgrade version. In such cases, a closed defect is opened again.
Here we will learn, how to export annotation drawn using PDFTron.
Events for export annotation
When we draw any annotation "annotationChanged" event will be fired, then we cache that event and we can export that annotation using "exportAnnotations". When we draw annotation we'll save them in the database and when we reload the same document we can retrieve saved annotations from database and can again show them, we will learn that in my next blog post. Here is example of how to save and annotation in database.
Example
WebViewer({
path: 'path_to_the_PDFTron_'lib'_folder_on_your_server',
css: 'webviewer_css',
licenseKey: 'YOUR_PDF_TRON_LICENSE_KEY',
initialDoc: 'YOUR_FILE URL' //url of a file to load
}, document.getElementById('viewer'))
.then(function (instance) {
let docViewer = instance.docViewer;
let annotManager = instance.annotManager;
annotManager.on('annotationChanged', (annots, action, e) => {
if (e.imported) return;
annotManager.exportAnnotations({
links: false,
widgets: false,
annotList: annots
}).then(function (xfdfStrings) {
annots.forEach(function (annot) {
if (action === "delete") {
deleteAnnotation(annot.mu);
} else {
saveAnnotation(annot.mu, xfdfStrings);
}
});
if (action === "add") {
annotManager.selectAnnotation(annots[0]);
if (annots[0]['Subject'] !== 'Comment') {
// to open comment box
document.getElementById('viewer').childNodes[0].contentWindow.document.querySelector('div[data-element="annotationCommentButton"]').click();
}
}
});
});
});
let saveAnnotation = function (annotationId, annotationXfdf) {
let saveAnnotationUrl = '';
if (fromExtension) {
saveAnnotationUrl = `YOUR_PROJECT_URL/annotations/${annotationId}`;
} else {
saveAnnotationUrl = `YOUR_PROJECT_URL/annotations/${annotationId}`;
}
$.ajax({
url: saveAnnotationUrl,
type: 'POST',
data: {annotation: annotationXfdf},
success: function (result) {
console.log(result);
},
error: function (result) {
console.log(result);
}
});
};
let deleteAnnotation = function (annotationId) {
let deleteAnnotationUrl = '';
if (fromExtension) {
deleteAnnotationUrl = `YOUR_PROJECT_URL/annotations/${annotationId}`;
} else {
deleteAnnotationUrl = `YOUR_PROJECT_URL/annotations/${annotationId}`;
}
$.ajax({
url: deleteAnnotationUrl,
type: 'DELETE',
success: function (result) {
console.log(result);
},
error: function (result) {
console.log(result);
}
});
};
Cardview is a widget provided by Android to create a new look and functional UI. You can build your app with the following examples to make it look more professional. Cardview is a wonderful concept that makes your user experience better than the Android UI. Cardview is an Android Lollipop released with Android 5.0.
Customized CardView
First, add a CardView dependency to the application-level build.gradle file.
Then create a drawable background for the cards. For that, create a new drawable resource file inside the drawable folder. res > drawable > New > Drawable Resource File.
Screenshot 2020-12-19 at 10.52.25 PM.png4.75 KBNow create a card view in the main XML file. Here I used LinearLayout as the root widget, after using the card view. Below the codes that give you an idea of how to customize the card. You can change it according to your needs.
The technical skills outlined above are necessary for graphic designers to execute the actual tasks assigned to them. But there are several transferable skills needed in order to successfully bring an idea from concept to creation. Our analysis helped us identify five important qualities employers are seeking in graphic design candidates. Here's what we found
Creativity:
This one probably goes without saying, but graphic designers are tasked with identifying creative solutions to deliver a message or solve a problem. This requires an innate ability to think outside the box and bring forth innovative ideas on a regular basis. Creativity.png184.09 KB
Analytical:
A graphic designer should be able to step outside their own mind and view the product or service analytically and from different perspectives. That way they can help anticipate how the audience will receive it. Analytical.png145.11 KB
Communication:
Graphic designers must possess strong written and oral communication skills in order to effectively work with team members and clients alike. Asking inquisitive questions helps them understand expectations so their designs will align with their client's vision.
Designers are often faced with the challenge of working on several projects with various deadlines at the same time. Being able to juggle multiple projects and meet stringent deadlines is essential to a successful design career.
Graphic design techniques and trends are constantly evolving, which means the learning is never done for designers. In order to ensure their designs are meeting client objectives, they need to be willing to dig up insights about their audience and explore new strategies. Research.png193.8 KB
Nowdays, laravel livewire is becoming more trendy for geeks. as most of developers are using it, more and more issues they are facing while developing the products. one of them is searching the records.
Recently we have developed the livewire common searchable component which makes your searching easier, as you can specify which fields you want to search by just giving the field name into the component.
What you have to do is just create SearchableComponent a class into your App\Http\Livewire directory. just copy the following class on the given namespace.
<?php
namespace App\Http\Livewire;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\Model;
use Livewire\Component;
use Livewire\WithPagination;
use Str;
abstract class SearchableComponent extends Component
{
use WithPagination;
/**
* @var string
*/
public $search = '';
/**
* @var int
*/
protected $paginate = 12;
/** @var Builder */
private $query;
/**
* SearchableComponent constructor.
*
* @param $id
*/
public function __construct($id)
{
parent::__construct($id);
$this->prepareModelQuery();
}
/**
* Prepare query
*/
private function prepareModelQuery()
{
/** @var Model $model */
$model = app($this->model());
$this->query = $model->newQuery();
}
/**
* @return mixed
*/
abstract function model();
/**
* Reset model query
*/
protected function resetQuery()
{
$this->prepareModelQuery();
}
/**
* @return Builder
*/
protected function getQuery()
{
return $this->query;
}
/**
* @param Builder $query
*/
protected function setQuery(Builder $query)
{
$this->query = $query;
}
/**
* @param bool $search
* @return \Illuminate\Contracts\Pagination\LengthAwarePaginator
*/
protected function paginate($search = true)
{
if ($search) {
$this->filterResults();
}
$all = $this->query->paginate($this->paginate);
$currentPage = $all->currentPage();
$lastPage = $all->lastPage();
if ($currentPage > $lastPage) {
$this->page = $lastPage;
}
return $this->query->paginate($this->paginate);
}
/**
* @return Builder
*/
protected function filterResults()
{
$searchableFields = $this->searchableFields();
$search = $this->search;
$this->query->when(! empty($search), function (Builder $q) use ($search, $searchableFields) {
$searchString = '%'.$search.'%';
foreach ($searchableFields as $field) {
if (Str::contains($field, '.')) {
$field = explode('.', $field);
$q->orWhereHas($field[0], function (Builder $query) use ($field, $searchString) {
$query->whereRaw("lower($field[1]) like ?", $searchString);
});
} else {
$q->orWhereRaw("lower($field) like ?", $searchString);
}
}
});
return $this->query;
}
/**
* @return mixed
*/
abstract function searchableFields();
}
Now you have to extend your existing laravel component by SearchableComponent. let's say we already have Tags livewire component. and its looks like following.
<?php
namespace App\Http\Livewire;
use App\Models\Tag;
use Illuminate\Contracts\Pagination\LengthAwarePaginator;
class Tags extends SearchableComponent
{
public function render()
{
$tags = $this->searchTags();
return view('livewire.tags', [
'tags' => $tags,
])->with("search");
}
/**
* @return LengthAwarePaginator
*/
public function searchTags()
{
$this->setQuery($this->getQuery());
return $this->paginate();
}
function model()
{
return Tag::class;
}
function searchableFields()
{
return [ 'name', ]; } }
So here we have extended our existing Tags component by SearchingComponent.
In searchable fields you can specify the field name that you want to search. and replace the Model with your records Model.
That it. Now you don't need to write search queries again and again. just extend your livewire component by searchable component.
Here are some Interesting livewire tutorials that you need to check :
Persuasion is a method of communication aimed at influencing the attitudes, beliefs, or behaviors of others. In terms of sales, understanding usually occurs when a sales representative tries to convince a prospect that their product or service is the best solution to their problem. Let's review the persuasion strategy you can implement today to close your next deal.
1. Personalize your message
If you want to explain the possibility of considering your product, resist the request to follow the general sales script. When you make excessive rehearsal noise or don’t share messages or information that seems to suit your prospect, your efforts go to one ear and go to the other. This doesn't mean you need to fully wing your sales calls, it does mean you need to be prepared to adjust your message based on what interests you in the potential.
2. Focus on problem-solving
Instead of telling the prospect all the reasons why they should buy your product (which may feel pressure and emotion), focus on sharing all the reasons why your product can help them solve their problem. By focusing on their concerns and locating your offer fur as a solution, you are showing the value of your product without excessive pressure.
3. Give social proof
Letting your past customers sell to you - knowing when to take advantage of social proof can be a powerful persuasive trick. While buyers may take your point as a sales representative with a grain of salt because they know you want to sell, they are more likely to trust a testimonial or story from a previous customer who was looking for a similar solution.
4. Assume goals
Picture: You feel ready to call your sales call. You think you have a solid understanding of who the prospects are and what they are looking for. Your notes have been typed and you are ready to close the deal. Then during a call, potentially throws out several turns, asking you questions and mentioning objections that you weren’t prepared to account for - the dream of every sales rip. But don't go too far. This is a valuable learning experience.
5. Empower empowerment decision making
After all, you want your customers to buy from you because they really want to, not because they feel pressured. And let’s be realistic - including your prospects, don’t like to tell anyone what to do, so you’ll avoid being too directive in your approach. As a sales representative, it is your job to provide the context and information that makes your product a thought-provoking product.
6. Make personal connections
It's a basic rule of human interaction - we're all ready to trust and engage with people we really love on a deeper level. While buyers can choose your product or brand as a sales representative, you are the main source of human engagement representing your company.
7. Don’t rush into the process
Last but not least, don't rush your prospect through the sales process. We get it - you have goals on a regular basis. However, effective persuasion should seem natural to the prospect. They do not feel pressured or rushed to sign the dotted line. This doesn’t mean you can’t implement a sense of urgency or be on time - in fact making a little sense of urgency (such as paying a special price for a limited time) can be an effective trick.
First, create a new Android Studio project and add the dependencies and plugin. First set up OneSignal in your project. Add OneSignal dependency and plugin to your build.Gradle app-level.
Today I’m going to write on Create Floating Widget never stop closing the app from the background. First of all, you must know what is the service in Android.
What is a service in Android?
A service is a component that runs in the background without direct interaction with the user. Since the service has no user interface, it is not bound to the life cycle of the activity. If you want to repeat a task, using the service is the best way. Service stops are one of the biggest problems when you clear the application from background functions.
My service is below:
public class FloatingViewService extends Service {
private WindowManager mWindowManager;
private View mFloatingView;
private View floatingButton;
private final static float CLICK_DRAG_TOLERANCE = 10;
private float downRawX, downRawY;
private float dX, dY;
int LAYOUT_FLAG;
private SpeechRecognizer speechRecognizer;
public FloatingViewService() {
}
Context context;
public FloatingViewService(Context applicationContext) {
super();
context = applicationContext;
Log.i("HERE", "here service created!");
}
@Override
public IBinder onBind(Intent intent) {
return null;
}
@Override
public int onStartCommand(Intent intent, int flags, int startId) {
KeyguardManager myKM = (KeyguardManager) this.getSystemService(Context.KEYGUARD_SERVICE);
if( myKM.inKeyguardRestrictedInputMode()) {
Intent i = new Intent(this,FloatingViewService.class);
startService(i);
// //it is locked
} else {
Intent i = new Intent(this, FloatingViewService.class);
startService(i);
//it is not locked
}
return START_STICKY;
}
@Override
public void onCreate() {
super.onCreate();
mFloatingView = LayoutInflater.from(this).inflate(R.layout.floating_layout, null);
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
LAYOUT_FLAG = WindowManager.LayoutParams.TYPE_APPLICATION_OVERLAY;
} else {
LAYOUT_FLAG = WindowManager.LayoutParams.TYPE_PHONE;
}
final WindowManager.LayoutParams params = new WindowManager.LayoutParams(
WindowManager.LayoutParams.WRAP_CONTENT,
WindowManager.LayoutParams.WRAP_CONTENT,
LAYOUT_FLAG,
WindowManager.LayoutParams.FLAG_NOT_FOCUSABLE,
PixelFormat.TRANSLUCENT);
mWindowManager = (WindowManager) getSystemService(WINDOW_SERVICE);
mWindowManager.addView(mFloatingView, params);
floatingButton.setOnTouchListener(new View.OnTouchListener() {
private int initialX;
private int initialY;
private float initialTouchX;
private float initialTouchY;
@Override
public boolean onTouch(View v, MotionEvent event) {
switch (event.getAction()) {
case MotionEvent.ACTION_DOWN:
initialX = params.x;
initialY = params.y;
initialTouchX = event.getRawX();
initialTouchY = event.getRawY();
downRawX = event.getRawX();
downRawY = event.getRawY();
dX = v.getX() - downRawX;
dY = v.getY() - downRawY;
return true;
case MotionEvent.ACTION_UP:
float upRawX = event.getRawX();
float upRawY = event.getRawY();
float upDX = upRawX - downRawX;
float upDY = upRawY - downRawY;
return true;
case MotionEvent.ACTION_MOVE:
params.x = initialX + (int) (event.getRawX() - initialTouchX);
params.y = initialY + (int) (event.getRawY() - initialTouchY);
mWindowManager.updateViewLayout(mFloatingView, params);
return true;
}
return false;
}
});
}
@Override
public void onDestroy() {
super.onDestroy();
}
}
AndroidManifest.xml file and update your service declarations under the application tag. Also, add FOREGROUND_SERVICE, INTERNET and WAKE_LOCK .Make sure you don't forget to include them as they won't work otherwise.
You can use the following code to check if the service is running. If the service is already in running mode, it does not need to be restarted otherwise start in your MainActivity.
FloatingViewService mFloatingService = new FloatingViewService(getApplicationContext());
Intent mServiceIntent = new Intent(getApplicationContext(), mFloatingService.getClass());
if (!isMyServiceRunning(mFloatingService.getClass())) {
startService(mServiceIntent);
}
Method isMyServiceRunning() is below add this in your MainActivity.
private boolean isMyServiceRunning(Class<?> serviceClass) {
ActivityManager manager = (ActivityManager) getSystemService(Context.ACTIVITY_SERVICE);
for (ActivityManager.RunningServiceInfo service : manager.getRunningServices(Integer.MAX_VALUE)) {
if (serviceClass.getName().equals(service.service.getClassName())) {
Log.i ("isMyServiceRunning?", true+"");
return true;
}
}
Log.i ("isMyServiceRunning?", false+"");
return false;
}
Then Create a Floating Widget design. Create File floating_layout.xml Like This
