hi,

how many would help / participate working on a branch of views_pdf using mPDF as the pdf library? there already is a module using mPDF -> https://drupal.org/project/PDF_using_mPDF

@Simon Georges: would you add a branch so I could start porting stuff over?

greets,

attisan

Comments

killua99’s picture

HI attisan,

I'm not the full maintainer but I can push to git.

But before I say "I'm up" why it's the main reason to add this new library? I was follow this module for a while ago almost from sandbox and as you can see they're working I believe 100% on that module. Require a lot of work to have it done. That library seen more easy to use but, with that library we can do all the functionality this module provide? for example the "text hyphenation".

If you can add more info about the features about this library will be great.

killua99’s picture

Status:Active» Postponed (maintainer needs more info)
attisan’s picture

hi killua99

thanks for the offer!

to clarify - I'm neither the developer of mPDF, nor developing for the mentioned drupal module. I merely stumbled upon mPDF on my search for good pdf generators written in php.

the main reason for me to beg for this pdf lib to be given a chance is the fact that I have been struggling for what seemed to me as years, though most probably only were a few days, getting some basic layout done using css with views_pdf.

tcpdf surly is a great lib. but handling css with this lib seemed to me as if I would have been drawn back in time to the dark ages of css, where it was some sort of trial and error voodoo like stuff. at some point I even stated to a colleague that it felt like having to design a ie5 compatible webpage.

that said, I can only tell about mPDF as much as anyone could after browsing through the examples shown on their page. I am impressed ;-).

the css support seems to be much wider, even including some handy css3 settings. this, however, seems to be at the cost of rendering speed.

hyphenation seems to be supported btw – using the last revision of mPDF it seems to be the css3 hyphen setting.

perhaps we will have to stop this branche half way – but at least we would have tried.

greets,

attisan

candelas’s picture

@attisan i am working and have not time to collaborate seriously until agost. some questions about your proposal:

can the module PDF_using_mPDF work with views?
would you like to collaborate during agost to betatest and make documentation? or programing?

and i agree with you about

I have been struggling for what seemed to me as years, though most probably only were a few days, getting some basic layout done using css with views_pdf.

tcpdf surly is a great lib. but handling css with this lib seemed to me as if I would have been drawn back in time to the dark ages of css, where it was some sort of trial and error voodoo like stuff. at some point I even stated to a colleague that it felt like having to design a ie5 compatible webpage.

but i dont know if the reason that css was a matter of trial and error woodoo was the library or this module... as for example float doesnt work but in the library they say that yes....

what i see it is that maintain two libraries would be too much work... and to change too. so it has to be done after a serious study of the possibilities.

attisan’s picture

Hi candelas,

I personally don't know if the existing module (pdf_using_mpdf) could work with views_pdf.

My idea would be to have both version of views_pdf available. Something like

  • 7.x-1.x-dev → main views_pdf release
  • 7.x.4.x-dev → release using mPDF

I did actually just ask about having an own branch for this as I will be working on this either way (programming, documenting ...). The difference would be, that by having a public branch, others could collaborate, share ideas, enhance my code adoption …

Regarding the css question; it most definitely is a shortcoming of the lib and has little to do with the module. Float, as an example, is stated as working – whereas it isn't. It's not just not working for this module, users all around the internet encounter similar problems.

So my proposal:
I will be re-writing (programming), doing some necessary documentation and sharing code. All I ask for would be to have a public branch to work on. Otherwise I'll just publish (post in the issue queue) some chunk of code when I'm done ;-)

greets,

attisan

killua99’s picture

Status:Postponed (maintainer needs more info)» Active

Attisan,

Now I'm also a full maintainer. So can take decisions.

I like the idea to support other library more. But if we're going to do that we can't forget the other library.

So, that mean the branch x.x have to support the current library. If you're ok with that, we can start work with a 2.x branch.

But I want to start not in d.org, We're going to start coding in github, and when we have a alpha version then come to d.org again.

If you're fine with this I create every to start working on this new version.

killua99’s picture

Adding taggin

attisan’s picture

hi killua99,

I'm fine with that - just post the git link and I'll apply / start working in the upcoming days.

greets,

attisan

killua99’s picture

Attisan,

this is the github repo: https://github.com/killua99/views_pdf if you can contact me there to add you as collaborator.

killua99’s picture

Version:7.x-1.x-dev» 7.x-2.x-dev
killua99’s picture