CWP User Group

FileMaker DevCon 2014

  • Joel Shapiro @jsfmp
  • Andrew Duncan @aduncan_au
  • Mark DeNyse @mdenyse
  • Tim Dietrich @tdietrich

Joel Shapiro

by the numbers:

  • 1 : Independent consultant FBA, 12/11/10/9 Cert.
  • 94110 : based in San Francisco, CA
  • 21 : yrs developing in FileMaker
  • 15 : yrs in business jsfmp.com
  • 9 : yrs developing PHP websites w/ FM
  • 8 : yrs hosting CWP User Group at DevCon
  • 3 : yrs blogging blog.jsfmp.com
blog.jsfmp.com
f-n-web

Today:

  1. Super-quick tip: Chrome Duplicate Tab
  2. Couple <input> UI quickies (html & css)
  3. A conversation…

2) Handy <input> attributes:

						autofocus

for mobile-friendliness:

autocomplete="off" 
autocorrect="off" 
autocapitalize="off" 
spellcheck="false"
					
<input type="text" name="username" value="" autofocus autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false">

Buttons on iOS:

<input type="submit/button">

Buttons 
						-webkit-appearance: none;

3) OK, let's talk...

Once upon a time...

It all started with a casual mention of OO

and then a bite of humble pie*

Humblepie

used with permission: williambeem.com

The best pie chart ever:

Piechart

But back to our story

Humbling, because I chose to admit that I don't do OO code

(I barely know it)

& then I thought:

“but should I?”

*btw: I've since learned that that's not what "humble pie" means :(

So I've been thinking…

“Salt worthiness”

Salt

Developers who are “worth their salt”

good or competent at the job or profession specified
deserve the pay or reward that they get

i.e. reasonable expectations

Yet balanced with our wedge of the world

Cwpwedge

keeping a responsiblity to our clients (e.g. maintainability)

and without splintering into too many CWP ‘factions’

(i.e. Joel’s conundrum)

Not about creating Standards or Rules for CWP developers

But maybe we can come up with some recommendations …?

The benefits of our collective experience:

  • What are you glad you learned?
  • What have you learned that was not so useful?
  • What do you want to learn? (why?)
  • What do you think you should learn? (why?)
  • For each:
  • What’s the value to CWP Developers?
  • What’s the value to your general web development?
Table Example
  • Some things (e.g. PHP arrays) require writing different code, but I believe they are absolutely worth learning and using.
  • Other things (e.g. Sass) may be less valuable to most CWP developers, but because they produce regular CSS files I can use Sass and not worry about burdening my client with a technology that someone new would be required to learn.
  • So with all the things that do require different code… we get to decide whether they're appropriate to use in our CWP projects.

Maybe we could all contribute to a list of “learnable things” for CWP,
sortable by priority, with resources etc.

Full Table

If you've got ideas on how to best implement this, please contact me…

Thanks

Joel Shapiro

@jsfmp

jsfmp.com