[OT] Interesting Article on Form Design

Peter Haworth pete at mollysrevenge.com
Tue Nov 23 14:04:04 EST 2010


I'm kind of in the same boat there!  Busy trying to document this  
stuff right now with a hope to having some other people give it a try  
in the first couple of months of next year.

Pete Haworth

On Nov 23, 2010, at 10:40 AM, Bob Sneidar wrote:

> Hi Pete. That is pretty much what I am doing. I can't help but think  
> about reusing the work I do in other apps later, so I am trying to  
> make my forms reusable by forming a method like you. Since I am  
> really a hobbyist when it comes to developing, I never get close to  
> finishing. <sigh>
>
> Bob
>
>
> On Nov 23, 2010, at 9:47 AM, Peter Haworth wrote:
>
>> I wrote something like this years ago in a galaxy far away on  
>> Hewlett Packard 3000 computers!  My experience was that it could  
>> provide simple add/change/delete/display capabilities for a single  
>> table with forms that could look really bad if there were a lot of  
>> columns in the table so good luck with your project!
>>
>> I've developed a methodology for getting database applications up  
>> and running pretty quickly using Livecode, based on various naming  
>> conventions, custom properties, and a library of controls/ 
>> behaviors.  That lets me concentrate on good form design because I  
>> know the amount of code I have to write for 90% of application  
>> logic is practically zero.
>>
>> Pete Haworth
>>
>> On Nov 22, 2010, at 4:32 PM, Bob Sneidar wrote:
>>
>>> Thanks Scott. I have been mulling around in my head about some  
>>> kind of form generator, that when given a set of database columns,  
>>> will auto layout input fields for them in order selected based  
>>> upon the column size and what have you. I call it a field dropper,  
>>> and I have a working model which gathers the columns of a  
>>> connected SQL database table, and then presents the user with list  
>>> fields of columns which have not been dropped on the form yet. but  
>>> I would like to place the input fields in some kind of grid,  
>>> instead of dropping them center card and having the user drag them  
>>> to where he wants them.
>>>
>>> Is there anything written up on some acceptable standards about  
>>> distance between input fields, and distance to top and bottom of  
>>> form?
>>>
>>> Bob
>>>
>>>
>>> On Nov 22, 2010, at 1:26 PM, Scott Rossi wrote:
>>>
>>>> Folks building data entry forms in LC may find this article of  
>>>> interest (not
>>>> because it has to do with Apple, but rather because it analyzes  
>>>> newer
>>>> methods of dealing with design/data collection in forms):
>>>>
>>>> The Apple Store's Checkout Form Redesign
>>>> <http://www.lukew.com/ff/entry.asp?968>
>>>>
>>>> Regards,
>>>>
>>>> Scott Rossi
>>>> Creative Director
>>>> Tactile Media, UX Design
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your  
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>>>
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your  
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your  
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>





More information about the Use-livecode mailing list