Thank you Richard Carlton.
I suspected as much, but a very nice demo on how to do it.
That's pretty sweet -- thanks for sharing!
FileMaker Database Superhero,
Spafford Data Solutions
Tel: 613 838 9956
FileMaker User Group in Ottawa:
Hi Folks...I am mostly in the middle of producing various FMGo Videos...and product lunches with RCC, etc...by one of my engineers... Garrett ...came to me babbling about CSS...and so I figured we'd have him make a quick video.
I entirely expect a whole bumper crop of products and consultants selling stuff to assist or enhance this functionality.
Ha ha! Don't let "CSS" scare you if you are a FileMaker developer. Richard is referring to creating *custom* themes. You don't need to rush over to the W3C and learn CSS.
Watch the video that RCC announced. And watch for lots of great assisance and demos coming shortly!
-- sent from my iPhone4 --
This was one of the first things I looked at as well - how are the Themes done.
Adding my 0.02 (soon to be 0.05 as Canada gets rid of the penny) - FileMaker has not given us the ability to create or modify themes - as Richard pointed out in the video. This makes it difficult to distribute any customized theme with a solution.
- The theme is stored within the application, not the database (on OS X, haven't looked at Windows yet).
- After looking at the CSS for a theme - there's a lot of it in there. Plenty of things to mess up for the CSS novice.
- Since the theme resides with the application, we'd have to modifiy the app - potentially against the EULA.
- For our clients, they may not have the admin rights to modify anything in the application folder, making installation of any customized theme more difficult. This likely isn't like installing a plugin.
- I'd be interested to examine how modified Themes are stored. We can change components of the Theme via the Inspector - also seems easy to break things. I changed a header in the Inspector, changed it back and it did not restore to the Theme defaults.
Once a theme is applied to a Layout...that theme is copied into the layout structure itself and cannot be editted. This is a one time action...when the theme is applied to the layout. From that point forward, the layout only references its internal copy of the CSS. That also means that recipiants of the layout (your customers) do not need the original CSS library from which it came. The CSS was already scraped out of the txt file, and sucked into the layout itself for permenent storage...or until the theme is changed again.
So this is useful...as even though I might create custom themes for my customers...I don't see a need to install those themes into their individual computers. No need.
- Richard Carlton
Thank you, Richard, for the quick and easy info. I'll definitely be developing in in-house company theme before we migrate to 12.
I, too, had been looking for this ability in the pre-release software, but with so any other new toys to play with, I didn't get as far as opening the app-package. Can be a risky business to just go poking about in there if you don't know where you're going.
Good to know. Thanks Richard.
Great, thanks, that's interesting!
Actually, come to think of it, what do you think might happen when there's an update? I guess you could just drop them back in again, but would be interesting to see, I guess it would overwrite them? Definitely keep the themes backed up.
Um...yourtalking like a FM Pro rev...like 12.0v2? Um well...safe money is that the CSS will get nuked. Won't know for a while either way.
Yeah, maybe not a while though ;)