Chelsea Sample App Play Thing

[Geoff Bowers]

Folks,

The current RC installer for SHINY is a sample project called "Chelsea".  It's the first of several sample projects we plan to release with the installer.

It's based on the Chelsea open source design we released a while back. "Chelsea" leverages the new FarCry CMS plugin, and showcases a variety of project level modifications.  You can use it as is, or just as a reference for the sorts of things you can do easily in FarCry.

If you don't have time to download it and have a play as I've uploaded and installed onto a small CloudBees instance:

  http://chelsea.daemonite.cloudbees.net/

You can login and have a play around here:

  http://chelsea.daemonite.cloudbees.net/webtop

  username: farcry

  password: chelsea

Every time the app service gets restarted it should wipe everything back to the initial installation state.  If you see anything in there that looks a little bit off colour, please let me know and I'll reset the app.

Enjoy,

GB 

[Jeff Coughlin]

I'm loving if so far. Got a question for ya.

Not sure if this is a bug, but with the previous version if FC my clients would often use their mobile devices (iPhone) to edit content. But when I try to use an iPhone to use the webtop, any of the popup tools (edit forms, preview screen, etc) don't seem to fit properly and I can't scroll. Hopefully this is an easy fix since it's using Bootstrap under the hood. Or is content editing with mobile devices no longer supported? (Note: everything else seems to work fine)

--

Jeff Coughlin

--
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: farcr...@googlegroups.com
To unsubscribe, email: farcry-dev+...@googlegroups.com
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 farcry-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Geoff Bowers]

On 7 February 2014 16:31, Jeff Coughlin <je...@jeffcoughlin.com> wrote:

Not sure if this is a bug, but with the previous version if FC my clients would often use their mobile devices (iPhone) to edit content. But when I try to use an iPhone to use the webtop, any of the popup tools (edit forms, preview screen, etc) don't seem to fit properly and I can't scroll. Hopefully this is an easy fix since it's using Bootstrap under the hood. Or is content editing with mobile devices no longer supported? (Note: everything else seems to work fine)

Hmm.. should be working well at the iPad/tablet scale.  I don't think we have tested editing in the webtop with screens the same resolution as iphones -- if that's a popular format we could look at putting in some more media queries.

Interestingly, the richtext editor should also be working for mobile users which is a very nice improvement.

GB

[Geoff Bowers]

On Friday, 7 February 2014 16:44:08 UTC+11, Geoff Bowers wrote:

On 7 February 2014 16:31, Jeff Coughlin wrote:

Not sure if this is a bug, but with the previous version if FC my clients would often use their mobile devices (iPhone) to edit content. But when I try to use an iPhone to use the webtop, any of the popup tools (edit forms, preview screen, etc) don't seem to fit properly and I can't scroll. Hopefully this is an easy fix since it's using Bootstrap under the hood. Or is content editing with mobile devices no longer supported? (Note: everything else seems to work fine)

Hmm.. should be working well at the iPad/tablet scale.  I don't think we have tested editing in the webtop with screens the same resolution as iphones -- if that's a popular format we could look at putting in some more media queries.

Have had a closer look at the modal issue. Looks a lot like a iOS webview bug -- finger scrolls the underlying parent not the modal iframe, unless you focus on a field in the modal iframe.  We'll put it in the backlog and see if we can't find some genius way to get around it.

GB