carpo

Looks like a lot of the time you've been doing things for or with other people. Why not think of something you are really passionate about and do it exclusively for a while. Do it for yourself, not anyone else. That way you only need to be persistent to succeed. And you never know, there might be other people out there that like it and want to use it too.

In practice this can increase the amount of requests required to get at the information you want, and also the size of each request, as it must then include information about the actions that can be taken on the resource. It could be argued that this constraint is more for the benefit of systems or programs that need to interact with the API without knowing anything but the initial URL, and not necessarily a programmer who can work these things out. owever, if a REST API uses this constraint, and application developers follow it, deep changes can be made to the URL structure of the API without breaking the applications that use it.

Thank you both for your comments too, I appreciate it.

Once you've culled some features like this, it's much easier to get excited and stay focused on that first release, as it will seem so much closer than before.

This literally made me laugh out loud with all the fond memories of the dogs I've had in my life.

It's funny, because I always spend a fair bit of time writing notes when programming ... but it's usually a stream of consciousness straight to a notebook via pencil - sometimes with dialog as I ask and later answer questions to myself. This really helps me find solutions to problems I'm currently working on - but is not so good at later turning into user documentation. I've tried to use a word processor, thinking that it would be easier to manipulate later into docs, but it seems that the pencil, the paper and the process all contribute to the end product.

In this case though, writing the user documentation really helped me think about the overall picture, as not only was I trying to work out the best way to implement something, but also about how my users were going to use and learn it.

United States - 47 Australia - 13 United Kingdom - 8 Canada - 6 New Zealand, Romania - 2 India, Ireland, Netherlands, Portugal, Sweden, China - 1

ErrantX's job is to determine the intent of the viewer by seeing if they actively downloaded and used the produce of an illegal activity. If he does his job well, I see no problem with putting people in jail for this crime.

If someone downloads Child Porn, or knowingly copies it from somewhere, this could be giving someone the idea that they better keep producing it.

It's a monty-pythonish thought, but I keep imagining the letter you receive having the offending link blacked out by the censor's pen, and all the while new fines turning up every day and you frantically removing each link until you get the right one.

It's true that determination can help you do wonders. And in my case, that initial rejection just added more steel to mine.

Currently, forms need to be created using our WYSIWYG design tool - this creates the layout of the web-form and the resulting PDF. There is no way at the moment to import an existing PDF form to mark up - though I am working on a solution to this. (To get around this, some users have used a screenshot of their static PDF form, and then placed the text fields and checkboxes over this image - it works, is quick, and they don't have to pay someone to make them a fillable PDF - though, this is less than ideal if you already have a dynamic acro-form)

Our forms will work from behind a login. It uses iframes to embed the form, so as long as the user has access to the 'net, they will see, and be able to use the form. We also have an authorisation script that you can put on your site to protect the iframe embed code so that people can't copy the HTML and put your form on their own site.

Please feel free to contact me if you have any other questions - my email is in my profile.

Yeah, I've seen that site before. Probably time to have a look around the 'net again to see what's out there :)

Entry storage is always up to the doculicious member who embeds a template on their site, never the public person who fills it in (is that what you were getting at, or am I off the mark?). Setting a template to save entries will automatically save all entries by anyone who fills it in and submits it. If the doculicious member who embeds the template turns off auto entry saving, the person filling in the form just gets the PDF, and only stats like date downloaded, IP address etc are saved for the member to view. (We are in the process of writing a more advanced reporting system for this).

We use a concept of "activating" templates, allowing members to create multiple templates, but only have some active, and in the future, to activate a template created by someone else. When you activate a template you then get to define it's web form settings - things like automatically saving entries, disabling pdf download (making it work just like a standard web form), adding notification emails and stuff like that. Currently, only doculicious staff can create shareable templates - but I think I need to defined the term "form creator" better .. as later this could mean someone other than yourself or doculicious.

All the forms can use SSL, so the submission of data is secure. On form completion, the data is stored in our database for creating the PDF and to save multi-page forms. If the template owner has not opted to store the entry, this data is deleted after 2 days. If they opt to store the entry, it will stay in the system until deleted by them. If they delete it, the data is removed completely, leaving only stats on when it was downloaded, IP address of downloader etc

Access to stored entries is only available to the template owners account through an entries search facility. All this is behind SSL too.

I should elaborate on this more in the TOS, but is that what you wanted to know?