You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I come here and that is the use case I am in search for. Like it could do anyone: show up a hello world and basic usage command line: extract info, alter some info, and push it back into the pdf via fdf
Why is it, with all due respect, that you do not have this basic use case within a testsuite, to see your tool intact. Well, anyway, this usecase is such basic, that any user wants/needs to have it as a tool chain "hello world." So the request: build a command demo line script, and put it to the docs.
Btw. I would do it, right now. If you help me, it is going to be easier, is not it? First: is it feasible? first and half: are there templates for it? Where? Tia.
3, Second one needed template pdf form for the demo, I could take mine, but that could result, embarrassing, for others. Probably due to the fact that forms in themselves are human-humiliating techniques. So in the end of the talk it resulted less embarrassing not to to nothing in front of these barriers.
Then there comes out a a script file, that does some sparse feedback operations on a pdf form. This elaborate should be attended in a Testsuite. So every user gets the "on key, out of box feedbacked pdf form filling functionality" shipped.
Do you imagine how much user time you could spare, by freeing every new user of doing the course of figuring out his personal "hello World" and keep it hidden after? That make the difference.
Regards and Thanks for your tool
The text was updated successfully, but these errors were encountered:
@qemu-buro-point-dpkg I think what you're asking is to have a demo script in the README. If you have time, can you go through it and see if it helps unblock you?
Hi,
I come here and that is the use case I am in search for. Like it could do anyone:
show up a hello world and basic usage command line: extract info, alter some info, and push it back into the pdf via fdf
Why is it, with all due respect, that you do not have this basic use case within a testsuite, to see your tool intact. Well, anyway, this usecase is such basic, that any user wants/needs to have it as a tool chain "hello world."
So the request: build a command demo line script, and put it to the docs.
Btw. I would do it, right now. If you help me, it is going to be easier, is not it? First: is it feasible? first and half: are there templates for it? Where? Tia.
3, Second one needed template pdf form for the demo, I could take mine, but that could result, embarrassing, for others. Probably due to the fact that forms in themselves are human-humiliating techniques. So in the end of the talk it resulted less embarrassing not to to nothing in front of these barriers.
Then there comes out a a script file, that does some sparse feedback operations on a pdf form. This elaborate should be attended in a Testsuite. So every user gets the "on key, out of box feedbacked pdf form filling functionality" shipped.
Do you imagine how much user time you could spare, by freeing every new user of doing the course of figuring out his personal "hello World" and keep it hidden after? That make the difference.
Regards and Thanks for your tool
The text was updated successfully, but these errors were encountered: