Date   

Re: Graphics in Xway

Jeremy Hughes
 
Edited

Hi Geoff,

I can't see your Freeway example (I don't think it's possible to send attachments to Xway Talk) but how about:

1. Insert a photograph
2. Set Vertical Align to Middle (Margins and Alignment in the Box Inspector)
3. Press right-arrow and type the caption

Is there a different way of doing this in Freeway?

Jeremy


Graphics in Xway

Geoff Mullett
 

Perhaps it’s early days for this, but having inserted a photograph that sits on the left of the page, is it possible to insert a caption to the right of it, preferably centrally aligned?
Freeway example attached.

Thanks
Geoff


Re: Add 'return/enter' to instructions for entering commands

Doug vanderHoof <doug@...>
 

Hi Jeremy,
The very first dropdown or blank to be filled in was the sticking point.
After it occurred to me to hit a return, from there on, no problem.
Thanks,
Doug


On Wed, Nov 20, 2019 at 6:37 AM Jeremy Hughes <jeremy@...> wrote:
Hi Doug,

Thanks for your feedback!

Do you have a page number for the place where you got stuck?

Jeremy



--
Doug vanderHoof
Producer, modern media
773-394-0029


Re: Add 'return/enter' to instructions for entering commands

Jeremy Hughes
 

Hi Doug,

Thanks for your feedback!

Do you have a page number for the place where you got stuck?

Jeremy


Re: Working with Spans

Jeremy Hughes
 
Edited

Hi Paul,

Firstly, I think I’d like to see the <span></span> as an object - something that can be easily seen and selected
We’re planning to have options to display spans (and links, and paragraphs) in the Site panel - clicking on a span (or link or paragraph) will select it.

You can also select a span (or link or paragraph) today by putting the cursor in it and choosing Select Parent from the toolbar or Edit menu, or pressing the keyboard shortcut...

A key modifier to select all the text in a span would be useful too.
… keyboard shortcut: Command-Option-UpArrow

Having some kind of visual cue in Xway to show where spans are would be nice - even if it’s an option that needs to be turned on (for example, like Show Invisibles in Freeway).
I’ve logged this as a suggestion.

Being able to drag an “ear” to edit the span’s range would be useful, as it seems that making such changes right now could involve removing and reapplying the settings to a new text selection.
Logged as a suggestion.

Jeremy


Working with Spans

Paul Dunning
 

HI,
Like the way that spans are more readily editable. However, I’ve got a couple of thoughts on this.

Firstly, I think I’d like to see the <span></span> as an object - something that can be easily seen and selected, rather than remembering how much of the text was set to that span. For example, does it include any leading or trailing spaces?

Being able to drag an “ear” to edit the span’s range would be useful, as it seems that making such changes right now could involve removing and reapplying the settings to a new text selection.

Also, having some kind of visual cue in XWay to show where spans are would be nice - even if it’s an option that needs to be turned on (for example, like Show Invisibles in Freeway). A key modifier to select all the text in a span would be useful too.


All the best,

Paul Dunning

web design - http://www.pauldunning.com

freeway actions - http://www.actionsworld.com





Re: Xweb first thoughts

Jeremy Hughes
 

On 19 Nov 2019, at 19:52, Walter Lee Davis <waltd@wdstudio.com> wrote:

Is there an auto-grow text field control, like you can hack together with JS and a <textarea> in a Web form? (The idea being that it grows in height to continue to show all entered text (or up to a limit) so that it would only require scrolling vertically if there was a serious amount of code paste-bombed into it.) I haven't tried this exact field yet, but does it currently allow vertical scrolling? Or is it just a regular text field that ignores line-feeds and just accepts up to some (generous) limit of characters of text?
It’s a text view (NSTextView) rather than a text field (NSTextField). Text fields are simplified text views.

We had “stretchy” (auto-grow) text fields in Freeway (e.g. Title field in the Inspector palette) - but they weren’t standard controls.

Xway's markup views do allow vertical scrolling.

Jeremy


Re: Xweb first thoughts

Walter Lee Davis
 

Is there an auto-grow text field control, like you can hack together with JS and a <textarea> in a Web form? (The idea being that it grows in height to continue to show all entered text (or up to a limit) so that it would only require scrolling vertically if there was a serious amount of code paste-bombed into it.) I haven't tried this exact field yet, but does it currently allow vertical scrolling? Or is it just a regular text field that ignores line-feeds and just accepts up to some (generous) limit of characters of text?

Walter

On Nov 19, 2019, at 2:49 PM, Jeremy Hughes <jeremy@softpress.com> wrote:

On 19 Nov 2019, at 19:41, Jeremy Hughes via Groups.Io <jeremy=softpress.com@groups.io> wrote:

Maybe it’s also worth pointing out that if you want to type directly into the fields, you can make them wider by increasing the width of the Inspector panel.

There isn’t currently a way to make them taller.
We could make it so that the height increases in proportion to the width (e.g. making the field wider would also make it taller).

Jeremy




Re: Xweb first thoughts

Jeremy Hughes
 

On 19 Nov 2019, at 19:41, Jeremy Hughes via Groups.Io <jeremy=softpress.com@groups.io> wrote:

Maybe it’s also worth pointing out that if you want to type directly into the fields, you can make them wider by increasing the width of the Inspector panel.

There isn’t currently a way to make them taller.
We could make it so that the height increases in proportion to the width (e.g. making the field wider would also make it taller).

Jeremy


Re: Xweb first thoughts

Jeremy Hughes
 

I suspect what Tim was alluding to (please do correct me if I'm speaking for you erroneously) with opening "a file in an external editor" is to be able to open the markup in one's preferred editor, probably with syntax highlighting and other useful features, then save and Xway would update the markup. This is quite a handy approach that I've seen in similar contexts.
The comment about trying to be non-modal was a response to Tim’s other suggestion (display a sheet). Opening an external editor seems to me to have similar context issues to the issues you mention in connection with opening a separate window. Another possibility that doesn’t have these issues is that we could have a code view in the main window.

Maybe it’s also worth pointing out that if you want to type directly into the fields, you can make them wider by increasing the width of the Inspector panel.

There isn’t currently a way to make them taller.

Jeremy


Re: Xweb first thoughts

Tim Plumb
 

On Fri, Nov 15, 2019 at 07:39 AM, Simon Manning wrote:
I suspect what Tim was alluding to (please do correct me if I'm speaking for you erroneously) with opening "a file in an external editor" is to be able to open the markup in one's preferred editor, probably with syntax highlighting and other useful features, then save and Xway would update the markup. This is quite a handy approach that I've seen in similar contexts.
Exactly Simon. What I want to move away from is the constant need to copy and paste code from an editor into Xway. I can see how this would be fine for most users but copying and pasting more than a few times soon gets rather repetative. I suspect that in future I'd just link an external stylesheet to the page and leave that markup area blank.


Add 'return/enter' to instructions for entering commands

Doug vanderHoof <doug@...>
 

Hi All,
I was, stupidly I admit, stymied because I entered a value in a window and the next thing the tutorial told me to do was grayed out.
Please don't discriminate against the stupid. We run the world.
Doug vanderHoof
Chicago


Re: Xweb first thoughts

Rick Auricchio
 

An excellent explanation, Simon. Thanks. I hadn't really thought it through.


Re: Xweb first thoughts

Rick Auricchio
 

Gotcha. The semantics with the word Modal.

Copy/paste is of course fine. Allowing launch of an external editor would be a nice addition, but not imperative.


Re: Xweb first thoughts

Simon Manning
 


On Fri, Nov 15, 2019 at 9:49 AM Jeremy Hughes <jeremy@...> wrote:
Hi Rick,

> If a separate window were opened for the text, rather than an NSPanel, would that still be modal?

No. Modal just means that you’re locked into a particular view.

Expanding on this, a window is not necessarily modal but an issue with a non-modal window for something that is part of a document, is that it can become non-obvious which document such a window is associated with.

A user might have a window with multiple document tabs open and/or multiple document windows open. This can introduce the confusion that if a code editor window is opened and then the document tab/window is switched, bringing the code editor to the front might have a different document behind it.

Off the top of my head, this raises some questions that would need to be considered such as:
Should it commit changes when it loses focus?
Should it always bring the corresponding document to the front (behind it) when it gains focus?
Should it be a contextual panel that's always in front and displays content based on selection? (Press cmd+alt+i in Finder to get an idea of what I mean)
Should it be something else?

In general, my preference is for anything that is part of a document to be a part of that document's window or closely attached to it. i.e. A part of the document window, a modal sheet if modal is warranted or a popover such as with the Extended Properties + popover.

I suspect what Tim was alluding to (please do correct me if I'm speaking for you erroneously) with opening "a file in an external editor" is to be able to open the markup in one's preferred editor, probably with syntax highlighting and other useful features, then save and Xway would update the markup. This is quite a handy approach that I've seen in similar contexts.

Simon


Re: Xweb first thoughts

Jeremy Hughes
 

Hi Rick,

If a separate window were opened for the text, rather than an NSPanel, would that still be modal?
No. Modal just means that you’re locked into a particular view.

But why not use your favourite text editor to edit code? It’s easy to copy and paste, and there are lots of good text editors: BBEdit, Xcode etc.

TextEdit is OK if you don’t have anything else. I sometimes use it to write notes, or to compose text before I paste it into Slack or Facebook.

Jeremy


Re: Xweb first thoughts

Rick Auricchio
 
Edited

On Fri, Nov 8, 2019 at 03:11 AM, Jeremy Hughes wrote:
Xway (in contrast to Freeway) tries to avoid being excessively modal, and sheets are a modal option - you can't do anything else in that document until you dismiss the sheet.
If a separate window were opened for the text, rather than an NSPanel, would that still be modal?

Edit: Perhaps I'm misinterpreting when I say NSPanel. Perhaps the modality is that you can't do much (if anything) until the edit is actually committed.)


Re: Managing XWay’s generated files

David Ledger
 

On 14 Nov 2019, at 20:18, Jeremy Hughes wrote:

The default for HFS+ and APFS is that they are case-insensitive. ‘Resources’ = ‘resources’ = ‘RESOURCES’.

That’s true, but most web servers are case-sensitive - so it does matter.

Jeremy

If you’re still doing a normal (secure) FTP from Mac to server you can’t FTP to ‘resources’ and ‘Resources’. You would have to do some fiddle like “server-side ‘resources’ comes from Mac ‘resources’, but server-side ‘Resources’ comes from Mac ‘_resources’. Not easy to explain to users.

David.


Re: Managing XWay’s generated files

Jeremy Hughes
 

The default for HFS+ and APFS is that they are case-insensitive. ‘Resources’ = ‘resources’ = ‘RESOURCES’.
That’s true, but most web servers are case-sensitive - so it does matter.

Jeremy


Re: Managing XWay’s generated files

David Ledger
 

On 14 Nov 2019, at 10:31, Jeremy Hughes wrote:

Hi Max,

I have in the past changed Resources to lowercase resources

Xway uses lowercase “resources”

Jeremy

The default for HFS+ and APFS is that they are case-insensitive. ‘Resources’ = ‘resources’ = ‘RESOURCES’.

David

701 - 720 of 971