I guess everyone will have their own favourite feature (or not), but for me the popovers alone make it worth upgrading. Also the absence of the current record indicator in List view!
I guess for a solution already in production, there's no compelling reason to upgrade. But for new developments, I think it might be interesting.
Here's a list of what I really find interesting and useful for me in 13:
- Perform script on server (I have around 50 users through WAN, and some have to do some heavy reporting from time to time...)
- Get (modified fields) ( being able to log when some specific fields where modified and by whom is really nice)
- Refresh object (instead of the entire layout)
- Hiding Object from a layout (FINALLY!!!)
- The Font management is FINALLY as it's supposed to on mac (no more arial, arial bold, arial italic etc... under the font list). I can finally play with font styles without having to deal with double bold and double italic
I just started to play with filemaker go, so I can't really compare with older version, but as far as I know there are some really useful new features like the choice of several different keyboards, barcode scanner etc... as input type.
Those are the ones that I'm really happy about, but of course I'm sure there are losts of other things I haven't noticed yet.
Message was edited by: Thomas Staehli
I almost forgot... NO MORE JAVA FOR SERVER ADMIN CONSOLE!!!
Yes, many. ;-)
marianco was referring to only FMPA, not the server stuff. I would say if you're happy with 12, then by all means stay. But if you want to keep current, and have a plethora of improved UI/UX tools at your disposal, 13 is a must.
It's too early to say about how performance is in 13 vs. 12, but I'd imagine some blog articles and test files are already being written to test it out. I would *assume* the performance is better, but have not had enough time to prove it myself.
- HTML5 Server Admin tool.
- WebDirect - by far the best web implementation we have seen with FM. Includes real-time data updates in the browser. HTML5 compliant.
- Record indicator - option to remove.
- Native show/hide of objects.
- Better Theme integration - can be deployed, changed, applied file-wide.
- Native Gradient tool.
- Object Refresh.
- Get ( ModifiedField ) function.
- A few additions to the ExecuteSQL functionality.
I guess only you can decide if it's worth it for your business/customers.
• the data viewer is fixed - no need to toggle it On/Off to see its display.
• a new page break option for reporting
• get summary option list to accumulate data - this is computationally big!
• server side script execution option
• 64 bit container content encoding amazing feature to exchange files not as files
but you are right about speed - it is still a 32 bit compliation unfortunately.
even my clients ask me about 64 bit - i guess as soon as all iOS devices like iPod touch are on A7 there is hope ..
//suggesting to request it as a feature: 64 bit version
I ask the question. What featrues does FMP13A have that you could not achive with FMP13 and FMP12A. I see some security but not much else. I would think I could run FMP12A at the same time and go back and forth for debugging, binding and other advanced tasks. Format is the same correct? I have 12A but think I'm just going to go with FMP13. Thoughts?
One thing to consider, as is always the case when new features are added but the file format itself doesn't change, is that when opening the file in FMP12A, any new features, such as the new layout objects, new functions or script steps, new triggers, etc., won't work in 12. That could possibly affect the ability to debug an FMP13 file in FMP12A, and my (untested) guess is that it would almost certainly affect the ability to properly bind the file, if any 13-specific features were included in the file. (I could be wrong. ;-) I'm guessing that one or more FMP13 features have caught your eye, or you wouldn't be looking to upgrade at all, correct?
I suspect that the single biggest new feature specifically in Advanced, however, is going to be the ability to encrypt the file at rest. That is really huge and plugs the final hole in the FileMaker security matrix. Data-transit security has long been handled by SSL encryption, but the file itself has always remained unencrypted (if perhaps heavily obscured by a proprietary unicode encoding). No longer, however.
Just some thoughts for consideration.
Since you mentioned "binding" -- keep in mind that you cannot bind files with FMP13, only 13Adv. If you bind with 12Adv, you get a 12 runtime application, which will not support any 13 features.
For me, the true hidden objects (rather than obscured as in earlier versions), and the introduction of popup layout regions fully justify the move to 13 for my layout design work.
what is that new page break option you're talking about? I couldn't find it in the Part Options. and the get summary option list? Is it a function? a script step?
Thomas - in help there is a section on top right "What's new in FM13"
then you see this:•••
Show or hide page breaks in Layout mode by choosing View menu > Page Breaks. See Defining page breaks and numbering.
In my eyes for new developments the hidden objects could be a game changer - more modular programming would be possible. Think of different screens in one layout for
- Mac/Windows/iOS, for example a "call iCal" button on Mac and no print button on iOS
- software with InApp Sales feature: Show a button or feature only, when the user has bought it
- an EASY mode not showing everything your software can do
- responsive layout design - big wide screen with a navigation list to the left, a small high screen with a navigation list at the bottom
Great ideas, intex!
I agree that this feature is most welcome.