(858) 586 7777 | About | Testimonials | Contact
vteams vteams vteams vteams
  • How does it work?
    • Startup Process
    • Your First Day
  • Technologies
    • Hire PHP Developer
    • Hire App Developer
    • Hire JavaScript Developer
    • Hire ROR Developer
    • Hire IOS Developer
    • Hire .NET Developer
    • Hire AI Developer
    • Hire Robotics Engineer
  • Sample Budgets
  • Meet The Team
  • Experiments
  • Captain’s Log
  • Blog
vteams vteams
  • How does it work?
    • Startup Process
    • Your First Day
  • Technologies
    • Hire PHP Developer
    • Hire App Developer
    • Hire JavaScript Developer
    • Hire ROR Developer
    • Hire IOS Developer
    • Hire .NET Developer
    • Hire AI Developer
    • Hire Robotics Engineer
  • Sample Budgets
  • Meet The Team
  • Experiments
  • Captain’s Log
  • Blog
Blog
  1. vteams
  2. Blog
  3. FPDF/FPDI Libraries Integration with PSR-4 Standards
Dec 21
vteams- blog

FPDF/FPDI Libraries Integration with PSR-4 Standards

  • December 21, 2015

An event and ticketing management system (software) uses a desktop application built in C# language. Moreover, there are RESTful web services interface for tickets and events management built using Laravel 5.0. Using these web services, customers can:

  • Update their profile
  • Generate tickets
  • Reserve tickets
  • Cancel reservation
  • Get event details
  • Get invoices and all related operations
    .

Problem:

During web services usage, one of the services’ end point have to accept PDF file as binary input and split PDF into multiple PDF files per page and store those on Server. For this, vteams engineer Faisal Siddiq have to integrate FPDF/FPDI libraries as part of the ultimate solution.

The problem faced was that this libraries were not using PSR-4 standards for coding, testing, documentation and directory structure. He then had to do it in Laravel 5.0 that actually supports PSR-4 auto loading and namespace convention.

Solution:

For FPDF/FPDI libraries integration, Faisal converted both of them in PSR-4 standards manually. There were some bridge classes between both the libraries used for connecting both classes. After conversion to PSR-4 standards, classes that were inheriting the parent classes were not actually loading the default functions. To load that function, parent::callParentNeededmethod way was used.

After applying the above mentioned solution, vteam #164 was able to integrate both the libraries with desktop application and split PDF files.

  • Facebook
  • Twitter
  • Tumblr
  • Pinterest
  • Google+
  • LinkedIn
  • E-Mail

Comments are closed.

SEARCH BLOG

Categories

  • Blog (490)
  • Captain's Log (1)
  • Closure Reports (45)
  • Experiments (7)
  • How-To (56)
  • Implementation Notes (148)
  • Learn More (156)
  • LMS (8)
  • Look Inside (10)
  • Operations Log (12)
  • Programmer Notes (20)
  • R&D (14)
  • Rescue Log (4)
  • Testimonials (25)
  • Uncategorized (4)

RECENT STORIES

  • GitHub Actions- Automate your software workflows with excellence
  • Yii Framework – Accomplish Repetitive & Iterative Projects with Ease
  • A Recipe for CRM Software Development
  • Are Agile and DevOps the same?
  • The Data Scientist’s Toolset

ARCHIVES

In Short

With the vteams model, you bypass the middleman and hire your own offshore engineers - they work exclusively for you. You pay a reasonable monthly wage and get the job done without hassles, re-negotiations, feature counts or budget overruns.

Goals for 2020

  • Open development center in Australia
  • Complete and Launch the Robot
  • Structural changes to better address Clients' needs

Contact Us

Address: NEXTWERK INC.
6790 Embarcadero Ln, Ste 100,
Carlsbad, CA 92011, USA

Tel: (858) 586 7777
Email: fahad@nextwerk.com
Web: www.vteams.com

© 2020 vteams. All Rights Reserved.

Content Protection by DMCA.com