The viewport key alone looks like this:

<key>viewport</key>
<string>width=device-width, initial-scale=1</string>

So do I really need to make a drastic change to make this: <meta name="viewport" content="width=772" />, become this <meta name="viewport" content="width=device-width, initial-scale=1" />? (maybe that code doesn't work, is that where its breaking?)

No, as stated before, this is a new feature in Sandvox 2.2 for designers to take advantage of if they wish, not a mandatory change.

I'm not quite sure what you mean here. Could you perhaps paste the relevant bit of the plist (from a text editor, so includes the tags ideally) for me to see what you've ended up with please?

So do I really need to make a drastic change to make this: <meta name="viewport" content="width=772" />, become this <meta name="viewport" content="width=device-width, initial-scale=1" />? (maybe that code doesn't work, is that where its breaking?)

::edit::
Hmm, tested the code and it seems to work. It seems to me that if it supports a string, it should just paste the value as it does with the number and the code carries out the rest. Perhaps i'm just an ignorant newbie

If you are changing the viewport, and you get past this issue, then you might need to change the CSS, in a drastic way.  As I said, this isn't really a user-editable property, you are boldly going .... well, not where no one has gone before, but where only CSS designers have.  So you are kind of on your own unlesss you want to rope in some help from some CSS designers.....

We should note that the ability to specify the viewport value in the info.plist is really a feature for CSS designers who are building their own designs. It's not really a feature for tweaking from within Sandvox - otherwise we would have made some interface for adjusting that from within the actual program. :-)

Well I understand this, and maybe i'm overstepping my boundaries in this forum (posted here because of the viewport code) - but I do need to know this. As for unstable, I mean just that (atleast how I define it). It doesn't work. The design won't load (also tried starting with other design, and switching to it). I did this one step at a time, so I know the viewport change is the issue.

I appreciate the response (additionally to my other thread), but could you tell me what i'm doing wrong? What code would I need to put in? Do I need to edit the main.css file as well?

I changed the value to string, and put exactly what you had above: width=device-width, initial-scale=1

Sandvox 2.2 beta 1 is out, available in-app for everybody.

Importantly for designers, we now support alternate bundle IDs. What does this mean you ask?

Well, imagine you produce a design with the bundle identifier "com.mycompany.design1". But then later you decide you want to change it to "com.adifferentcompany.design1". So you change the identifier. But now, anybody who updates their design from old to new will have to re-pick it in Sandvox since the identifier has changed.

Fortunately, Sandvox 2.2 has a handy way around this. As well as the bundle identifier (CFBundleIdentifier), you can add in your plist multiple other identifiers for the key SVAlternateIdentifiers. Sandvox will register the design for all of them, so existing documents keep working with no changes required. You can have a look at any of our built-in designs to see this in practice.

Thanks for this Mike. Will have to check it out. Will be very helpful for my Sandvox 2 design updates and their Sandvox users.

Best,
Charlie

Also an intruder. I like the bullets / numbering feature but on the design I use, No parking anytime, I cannot get the indents to work. I can only get 1 level of bullets/numbers.

Thanks for pointing that out Harry. Some of our designs presently lay out all bullets at the same level visually. We're looking into improving that.

Importantly for designers, we now support alternate bundle IDs. What does this mean you ask?

Well, imagine you produce a design with the bundle identifier "com.mycompany.design1". But then later you decide you want to change it to "com.adifferentcompany.design1". So you change the identifier. But now, anybody who updates their design from old to new will have to re-pick it in Sandvox since the identifier has changed.

Fortunately, Sandvox 2.2 has a handy way around this. As well as the bundle identifier (CFBundleIdentifier), you can add in your plist multiple other identifiers for the key SVAlternateIdentifiers. Sandvox will register the design for all of them, so existing documents keep working with no changes required. You can have a look at any of our built-in designs to see this in practice.

http://karelia.com/beta/_Sandvox-beta-24071.dmg?

Makes list editing a lot tighter!

I'm also look at offering control over the type of numbers used in an ordered list (roman numerals, letters, etc.). As far as I can see, everybody's designs stick to the default of numbers. Please let me know if I'm wrong on that. I can see two ways of controlling this:

1. Sitewide control over how ordered lists are styled

2. Each list can be individually styled, starting from a default of numbers. Sandvox would supply classnames for these scenarios, and default CSS rules, which your designs would be free to improve upon

Let me know what you think.

I suggest I like the bullets and indent, and would use them together - one level down, not more.