We've migrated the config storage to JSON instead of WDDX, and I think arrays might be supported now... I can't remember how well I tested that though :)
As for complexity, yeah that's basically why I went with one option for each device. It's easy to map device webskins and easy to pick a width that does the job "good enough", and the user doesn't have to deal with a list of resolutions. I think it's worthwhile continuing to improve the feature in 7.1 or 7.2 once we have a better idea of how it's getting used, or not used. I'd really like a preview that is always visible and updates immediately while you are editing the object, but that requires a certain minimum desktop resolution, affects tablet/mobile usability or design decisions, and involves reworking how modals are displayed (or involves removing them). But hopefully the new webtop will now make this progress possible, we've just got to get FC7 over the line! On 30/10/2013 5:48 PM, "Jeff Coughlin" <[email protected]> wrote: > The configuration is a bit more complex than some widths in an array > because the buttons also map to device-specific webskins in the case of > "non-responsive" or hybrid designs. In addition to animating the width of > the window, it can reload the page using the device specific webskins where > needed. > > > That's just because it's hard-coded that way. No reason it can't be > dynamic. But I'm not asking to go back and re-code that anyway (it really > wouldn't be needed). I was just having hopeful wishes that configs would > someday support arrays :) > > So, are you saying that the existing "Desktop" mode would be fine as a > synonym for "landscape iPad" (anything >960px), but you'd also need a "Wide > Desktop" preview so that you can have a preview of >1200px? Or really, in > general that we just need multiple resolutions per device. I was hoping to > avoid that and just go for the lowest common denominator :) > > > Yeah, multiple resolutions per device would probably be best. But when it > comes to actually using the preview button, simplicity for the end user is > the key objective. They want to see a something simple like a tablet or > mobile button (with maybe an orientation option), not a button with a > string of text that says 480px :) > > Yeah I know. This sucks trying to decide what's the best direction to > take without over-complicating it? > > Jeff > > On Oct 30, 2013, at 2:34 AM, Justin Carter <[email protected]> > wrote: > > The configuration is a bit more complex than some widths in an array > because the buttons also map to device-specific webskins in the case of > "non-responsive" or hybrid designs. In addition to animating the width of > the window, it can reload the page using the device specific webskins where > needed. > > So, are you saying that the existing "Desktop" mode would be fine as a > synonym for "landscape iPad" (anything >960px), but you'd also need a "Wide > Desktop" preview so that you can have a preview of >1200px? Or really, in > general that we just need multiple resolutions per device. I was hoping to > avoid that and just go for the lowest common denominator :) > > > cheers, > Justin > > -- > Justin Carter > http://www.madfellas.com/blog > http://twitter.com/justincarter > > > On Wed, Oct 30, 2013 at 5:05 PM, Jeff Coughlin <[email protected]>wrote: > >> We have been supporting the suggestions from bootstrap ( >> http://getbootstrap.com/2.3.2/scaffolding.html#responsive). Our clients >> have been very happy with the results. Perhaps we should start convincing >> our clients to move away from 960px support and just support 1200px only >> for desktop/tablet, but the downside is that most of our clients are >> hospitals and internally the number of computers that only support 960px is >> astonishing (pretty much every hospital I've worked with has this problem). >> It's getting better, but it's a slow process. Too bad form configs in >> FarCry don't allow arrays or this wouldn't be an issue and we could add >> them as needed (and you wouldn't have to hard-code these in). >> >> Regarding a split-button, that's exactly what I was thinking. I'm not >> sure I like it visually, but space is limited so it might be the best >> option if you added orientation support. Unless someone else can think of >> a better way to offer it (like ipadseek.com uses a rotate button. I >> like that idea). >> >> Here's a thought, in the config maybe add orientation values for both >> devices as optional fields. If the developer doesn't want to offer it, >> leave it blank (or use a show/hide disable checkbox in the config to >> disable it). At least it's a simple workaround and not everyone has to use >> it (and you can disable them by default in the offered skeleton/installer). >> But for those clients who absolutely need it (and I'm sure there are >> plenty of use-cases that we're not thinking of - I know I've seen many >> eCommerce solutions who use different orientation layouts) it will be >> natively supported as a webtop preview option. >> >> Also, I don't know about you, but I was planning to use these config >> values possibly in some conditional code in a webskin or two (not sure >> where yet, but it's nice to know I'll have these handy if needed for >> conditional logic). >> >> -- >> Jeff Coughlin >> >> >> On Oct 30, 2013, at 1:33 AM, Justin Carter <[email protected]> >> wrote: >> >> Thanks Jeff! I'm not sure yet about adding orientations. Even just adding >> another button would cause a (small) problem because the mobile preview >> isn't wide enough to support an extra button (need to put it into a split >> button), hehe :) But I think with responsive designs we generally find the >> landscape iPad view to be the same as the Desktop view (i.e. anything >> larger than 960 pixels wide), and the line is made blurrier when most >> Android tablets are 1280+ pixels wide in landscape mode, so I'd be inclined >> to tell clients "Just use Desktop, it's the same". >> >> I considered going the whole hog and showing the previews inside a device >> skin, ala http://ipadpeek.com/, but it's only a rough guide and it can't >> really be considered a substitute for actual device testing. It does look >> very pretty though! >> >> cheers, >> Justin >> >> >> cheers, >> Justin >> >> -- >> Justin Carter >> http://www.madfellas.com/blog >> http://twitter.com/justincarter >> >> >> On Wed, Oct 30, 2013 at 3:02 PM, Jeff Coughlin <[email protected]>wrote: >> >>> configDevice.cfc is definitely a nice touch (thanks). Any chance we can >>> support custom widths for both portrait and landscape on both tablet and >>> mobile devices? >>> >>> Every responsive site I've been working on for the past couple years has >>> been doing multiple widths based on orientation (which of course is just >>> simple html5 conditional width detection). So far my clients have only >>> cared about tablet landscape and portrait, and for phone/mobile they've >>> only cared about portrait. But I'm sure it's only a matter of time. >>> >>> -- >>> Jeff Coughlin >>> >>> >>> On Oct 27, 2013, at 3:51 AM, Justin Carter <[email protected]> >>> wrote: >>> >>> The quick preview feature I mentioned in the blog post is also now >>> supported on ft:objectadmin grids, it looks great and the device widths are >>> now configurable using a new config :) >>> >>> cheers, >>> Justin >>> >>> >>> >>> -- >>> You received this message cos you are subscribed to "farcry-dev" Google >>> group. >>> To post, email: [email protected] >>> To unsubscribe, email: [email protected] >>> For more options: http://groups.google.com/group/farcry-dev >>> -------------------------------- >>> Follow us on Twitter: http://twitter.com/farcry >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "farcry-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> -- >> You received this message cos you are subscribed to "farcry-dev" Google >> group. >> To post, email: [email protected] >> To unsubscribe, email: [email protected] >> For more options: http://groups.google.com/group/farcry-dev >> -------------------------------- >> Follow us on Twitter: http://twitter.com/farcry >> --- >> You received this message because you are subscribed to the Google Groups >> "farcry-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> -- >> You received this message cos you are subscribed to "farcry-dev" Google >> group. >> To post, email: [email protected] >> To unsubscribe, email: [email protected] >> For more options: http://groups.google.com/group/farcry-dev >> -------------------------------- >> Follow us on Twitter: http://twitter.com/farcry >> --- >> You received this message because you are subscribed to the Google Groups >> "farcry-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: [email protected] > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry > --- > You received this message because you are subscribed to the Google Groups > "farcry-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: [email protected] > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry > --- > You received this message because you are subscribed to the Google Groups > "farcry-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry --- You received this message because you are subscribed to the Google Groups "farcry-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
