Date   

Re: Xway b1 - idea: CSS blank canvas or CSS paint by numbers

Tim Plumb
 

On Fri, Nov 8, 2019 at 04:46 AM, Jeremy Hughes wrote:
They’re already there in Xway (not “Xweb” - is that some kind of autocorrect problem?)
Just a typo Jeremy. You can't believe how many times Xway gets autocorrected here.

I'll take a look at the figure output. I'm sure it'll be just fine.


Re: How do I: replace an image?

Jeremy Hughes
 

Hi Tim,

It’s possible that you could have replaced the image with an identically named image in the Finder, but I’m not sure that would have worked properly. Xway would have used the updated image but it might have been confused about its size.

Graphics (and resources) are an area that needs more work (it's an area that we're currently working on).

There are a lot of areas that need more work. What we’ve tried to do with Xway is to produce something that is usable (and mostly bug-free) in its current state - but we’re aware of many areas that need to be worked on.

Generally, unless we’ve said that we’re not going to do something (e.g. table layout) you can assume that missing or incomplete functionality is somewhere on our to-do list.

Jeremy


Xway and MacOS Dark Mode

robtin1@...
 

Jeremy --
Running MacOS Mojave 10.14.6 in Dark Mode, parts of the Xway Toolbar are difficult to see, particularly "Go", "Select" and first/last tools of "Insert". Hovering over a tool does cause the tool name to appear, so it is useable. However, in the future can Xway change aspects of its appearance based on Dark / Light Mode?
-- Bob


Re: Xway and MacOS Dark Mode

Jeremy Hughes
 

Hi Bob,

We need to improve that.

We haven't actually done any work on supporting Dark Mode, so the fact that it works at all is quite impressive!

But now that Dark Mode has been mentioned on our web site we need to fix the stuff that is difficult to read.

Jeremy


Re: Will Xway support user defined styles?

Jim Feeney
 

On Thu, Nov 7, 2019 at 04:10 AM, Tim Plumb wrote:
I totally appreciate that most users tended to style their elements in an ad-hoc fashion and that is fine although, as you say, unless they get the styling exactly correct each time you'd end up with dozens of styles that all were pretty much identical. I've seen Freeway stylesheets that are huge and bloated with hundreds of class styles that were (I suspect) only used once.
So true! My early ad-hoc styling in Freeway Express ended in my having one of those bloated stylesheets with, as I recall, about 600-700 styles. That bogged down the speed of Freeway to a snail's pace. When I moved to Fwy Pro and learned to create a custom stylesheet, I got that down to about two dozen styles, which work perfectly for my website's ~470 pages. And once more, the speed of working within the Freeway software is fast.


XHTML-ishy output?

leif halvard silli
 

Congratulations on the new beginning! The best news is probably that the new program speaks HTML rather than DTP - this should simplify many things in day to day usage.

Two questions:

1) Pronunciation: Is Xway to be pronounced as "crossway" or as "exway"?

2) XHTML (aka "dirty HTML"): The "X" when it comes to markup, usually means "a dialect of XML" - such as XHTML. And, in that regard, Freeway could output pages as XHTML and as HTML. Will Xway get that feature?

By the way: My primary preference would be that Xway published just one format - but that that that one format was "dirty HTML" - by what I mean XHTML5 crafted to be fully HTML5-compatible. But if I end up using Xway a lot, I could also live with "pure" HTML5 as long as I could configure Xway to do XHTML5 output as well.

Leif Halvard Silli


Re: XHTML-ishy output?

Jeremy Hughes
 

1) Pronunciation: Is Xway to be pronounced as "crossway" or as "exway”?
eks-way

2) XHTML (aka "dirty HTML"): The "X" when it comes to markup, usually means "a dialect of XML" - such as XHTML. And, in that regard, Freeway could output pages as XHTML and as HTML. Will Xway get that feature?
We will support XHTML5 in future.

Jeremy


ID's and Classes in Construction

max.izzat@...
 

Jeremy, a few days ago suggested. I could open up a new thread around to discuss classes and ID and the problems associated with using just ID's instead of ID's and Class as the construction attribute in a little more detail and why this would be useful. so without further ado here goes 

 

So to recap for people who are unsure and this is just, so people can see some of the benefits and issues Please note: these aren't all the benefits and problems for each attribute type, but it does give a quick basic overview.

 

ID's are unique

  • Each element on your page can have only one ID
  • Each page can have only one element with that ID
  • ID's can be used in URLs 

The advantage for Xway is it can create a style structure that's based on ID's, and because it is probably the most important attribute for an HTML item, it can be reasonably sure it's going to work correctly because each item on the page has a different ID hook... COOL easy peasy.  

So what's the problem with just using ID's... so to explain that we need to know what classes are good for.

 

Classes are NOT unique

  • You can use the same class on multiple elements.
  • You can use multiple classes on the same element.

One advantage is if you have multiple divs as inline items within your page and all that's different is the text within that box, then the construction styles are the same. Technically you could have a 1000 inline boxes all of them with different text but one overall style rather than 1000 styles.

In reality, this doesn't really happen in the real world, but the main point is it has the potential to reduce the number of what I will call the construction styles. 

The other issue is when it comes to a content management system, which duplicates blocks. For example, a div with a chunk of editable text in it a CMS could potentially repeat that block, and if page construction were to rely purely on ID's, then the HTML would become invalid. (As mentioned in the ID's section above: you can have only one id of that specific name on the page.

 

 

So here comes the crunch to make things a lot easier Xway just like its predecessor Freeway used ID's as the main attribute for its construction. But going forward that's going to cause issues (just like it did for Freeway) when it comes to introducing a content management system.

 

What some of us in the past have done is written actions that basically swop the ID for a class of the same name, and in some actions, we have introduced the capacity to drop the ID completely, add other classes, rename the id etc. The issues I think all of us that have undertaken that task this is that ist BLOOMING complicated to get to work flawlessly. It really is like trying to catch the proverbial horse after it's bolted out of the gate. Not only does the action have to change the HTML pages naming items convention, but it needs to write to the styles in the head or in an external style sheet and or in a master page, and or within breakpoints. Honestly, it took us months last time along with a colleague of mine to get that action to work and even then there were certain elements it didn't work on.

 

Personally, I would prefer to have the ability to choose if something uses classes as its main attribute, no class or id at all or have a class name of my choosing, via the main programs interface. At least that way we aren't trying to undo a big portion of the program's output construction, via an action after its all published.

 

Anyway, it would be nice to have some feedback from some of the others and their thoughts. 

All the best Max


Re: ID's and Classes in Construction

Tim Plumb
 

Thanks for the writeup Max.

From a development point of view I can see the attraction of IDs over classes as you should only have to keep keep track of a single item per page with that ID. Multiple items with the same class names, I suspect, are harder to deal with, not only from a tracking perspective but also from a workflow one as well. If you have a host of items that all share the same class, for example, and the user does something to adjust one of those items does the application;
a. create a new style based on the previous class (style1b, style1c etc) or
b. warn the user that they can't do that and if they want a different border, padding, font style etc they need to create a new style or
c. keep the original style and create a new style for the unique changes (with or without the application sighing disappointedly)

One thing that occurred to me over the weekend while I was contemplating all of this was the Name/ID field in the Inspector. At the moment I think I'm correct in saying that the application assumes the item will have an ID. What if this allowed us to change the item to a class either directly or indirectly? What I was thinking was something along the lines of;
a. create an item and call it 'item1'
b. create a new item and also call it 'item1'
>> The application would then pop a dialog saying;
Hey! Item1 already exists. Would you like this item to share the same style information as 'Item1'
No Yes
If you click yes then the two items will share the same class name and will use the same identical style. If you click No then you'll create a unique ID or class for this item.

I think classes are SOOO much more useful than IDs and tend to steer towards 'utility classes' ('.red' to make something red, '.btn' to make a link a button, '.red .btn' to make a red button!) but I suspect there are a LOT of former FW users who really don't care what happens under the hood as long as their web site works and makes them look good in front of their boss.


Re: ID's and Classes in Construction

Jeremy Hughes
 

One thing that occurred to me over the weekend while I was contemplating all of this was the Name/ID field in the Inspector. At the moment I think I'm correct in saying that the application assumes the item will have an ID.
Not always - markup items don’t have an ID, for example.

(It’s just markup, and Xway doesn’t wrap it in anything that an ID could be assigned to.)

But generally, yes.

Jeremy


Re: ID's and Classes in Construction

Walter Lee Davis
 

I think that one way you could work this principle into Xway is to consider the notion of "master objects". Illustrator calls them Symbols, I think. Sketch has another word for them. But the idea is: you draw an item, modify it to your desired look and feel, and then designate it as a master item that can be duplicated over and over. If you go back to the original instance and make some adjustments, they propagate across all of the derived instances.

So that's the interface for this, from the WYSIWYG side. At an HTML/CSS implementation level, I would happily code that using classnames, and expose that "class style" as a set of attributes that could be modified in one place. If you wanted to add another of these styled items to a page, I could see a palette similar to the Styles palette, with an ad-hoc list of named master elements. Drag a "sidebar1" onto the page, modify the content, and Bob's your uncle.

Walter

On Nov 11, 2019, at 1:15 PM, Jeremy Hughes <jeremy@softpress.com> wrote:

One thing that occurred to me over the weekend while I was contemplating all of this was the Name/ID field in the Inspector. At the moment I think I'm correct in saying that the application assumes the item will have an ID.
Not always - markup items don’t have an ID, for example.

(It’s just markup, and Xway doesn’t wrap it in anything that an ID could be assigned to.)

But generally, yes.

Jeremy




Re: ID's and Classes in Construction

Paul Dunning
 

Affinity designer does this too - but you can edit any of the instances and the changes are repeated throughout all the instances in the file. There is a way to turn this off, so only the instance you are working on gets the change. Turn the instance syncing on, and all edited will cascade again, APART from those custom ones on the solo-edited item.

All the best,

Paul Dunning

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

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




On 11 Nov 2019, at 22:32, Walter Lee Davis <waltd@...> wrote:

I think that one way you could work this principle into Xway is to consider the notion of "master objects". Illustrator calls them Symbols, I think. Sketch has another word for them. But the idea is: you draw an item, modify it to your desired look and feel, and then designate it as a master item that can be duplicated over and over. If you go back to the original instance and make some adjustments, they propagate across all of the derived instances.

So that's the interface for this, from the WYSIWYG side. At an HTML/CSS implementation level, I would happily code that using classnames, and expose that "class style" as a set of attributes that could be modified in one place. If you wanted to add another of these styled items to a page, I could see a palette similar to the Styles palette, with an ad-hoc list of named master elements. Drag a "sidebar1" onto the page, modify the content, and Bob's your uncle.

Walter

On Nov 11, 2019, at 1:15 PM, Jeremy Hughes <jeremy@...> wrote:

One thing that occurred to me over the weekend while I was contemplating all of this was the Name/ID field in the Inspector. At the moment I think I'm correct in saying that the application assumes the item will have an ID.

Not always - markup items don’t have an ID, for example.

(It’s just markup, and Xway doesn’t wrap it in anything that an ID could be assigned to.)

But generally, yes.

Jeremy










Re: Xway b1 - idea: CSS blank canvas or CSS paint by numbers

Paul Dunning
 

Damn. I’ve been pronouncing it “Zway” - with the X sounding like the X in “Xena”.

Ho hum…. ;-)

All the best,

Paul Dunning

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

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




On 8 Nov 2019, at 12:15, Jeremy Hughes <jeremy@...> wrote:

NB Xway (not “Xweb”) rhymes with Freeway (not “Freeweb”)


Re: Xway b1 - idea: CSS blank canvas or CSS paint by numbers

Jeremy Hughes
 

Hi Paul,
Damn. I’ve been pronouncing it “Zway” - with the X sounding like the X in “Xena”.
You could also pronounce it with silent x as in “faux pas”
 
… or as Y as in “Don Quixote”
 
Personally I enjoy mispronouncing XR in iPhone XR to be the the same as XR in Extinction Rebellion

Jeremy


Is there a method to add HTML Markup eg before </head>

ant@...
 

Firstly well done Jeremy XWAY looks great and I like the way it works & can't wait to seem the rest of it as it rolls out.

I have read the manual and notice that the HTML Markup from the menu hasn't been implemented yet.

Is there a workaround for this heres an example I have in one of my Freeway sites for the favicon which I add before </head>

<link rel="icon" 
      type="image/png" 
      href="https://drainforceuk.co.uk/favicon.ico">
 
<link href='http://fonts.googleapis.com/css?family=Lato:300+700|Righteous' rel='stylesheet' type='text/css'>

Sorry if this is a stupid question but I use things like that a lot.

Cheers

Anthony
 


Re: Is there a method to add HTML Markup eg before </head>

Jeremy Hughes
 

Hi Anthony,

There isn’t a way to do that at present, I’m afraid. (Unless you edit the source code, but Xway will overwrite that next time you publish.)

We’re planning to add generic HTML markup in the next beta version of Xway.

Jeremy

On 12 Nov 2019, at 11:00, ant@anthonygallagher.co.uk wrote:

Firstly well done Jeremy XWAY looks great and I like the way it works & can't wait to seem the rest of it as it rolls out.

I have read the manual and notice that the HTML Markup from the menu hasn't been implemented yet.

Is there a workaround for this heres an example I have in one of my Freeway sites for the favicon which I add before </head>

<link rel="icon"
type="image/png"
href="https://drainforceuk.co.uk/favicon.ico">

<link href='http://fonts.googleapis.com/css?family=Lato:300+700|Righteous' rel='stylesheet' type='text/css'>

Sorry if this is a stupid question but I use things like that a lot.

Cheers

Anthony


Photo galleries + display text

Geoff Mullett
 

The first I suspect of many questions. Having used Freeway since its inception, Xway is like starting over!

I’ve been creating galleries of photos using Showcase and the Sequence Timer action. Will Showcase eventually be supported, or would Exhibeo be a better bet? In which case, would Exhibeo work in place of the ST action?

Freeway handles a greater variety of fonts and point sizes well using graphic boxes, will I need to turn display type into a jpeg in Photoshop etc then insert that format into Xway?

Apologies for the questions being so basic!

Geoff


Re: Photo galleries + display text

Jeremy Hughes
 

Hi Geoff,

I’ve been creating galleries of photos using Showcase and the Sequence Timer action. Will Showcase eventually be supported, or would Exhibeo be a better bet? In which case, would Exhibeo work in place of the ST action?

We're planning to provide better support for Exhibeo in a future version of Xway (currently you need to export HTML and use markup).

Freeway handles a greater variety of fonts and point sizes well using graphic boxes, will I need to turn display type into a jpeg in Photoshop etc then insert that format into Xway?

It's best to avoid using graphic text, because it isn't searchable and it's not very accessible. Freeway supports graphic text because it was written a long time ago!

If you really need to use graphic text, you can use Photoshop or something else to create it.

Otherwise, web fonts (e.g. Google fonts) are a much better option if you want to specify a particular font family. In Freeway, you need to use markup to specify web fonts - but Xway supports them directly. As for font sizes, Xway supports any font size that you care to use (and gives you a wider choice of measurements for specifying sizes).

Jeremy


Re: Photo galleries + display text

Jeremy Hughes
 
Edited

Just to elaborate on font sizes:

If you want 36px text, type "36px" in the Size field.
If you want 36pt text, type "36pt" in the Size field - and note that points are not the same as pixels in Xway or in CSS (Freeway wrongly treats them as being identical).
If you want text that is twice as large as the current (inherited) size, type "2em" in the Size field.

For web fonts see "Working with fonts" in the Xway User Guide.

Jeremy


Re: XHTML-ishy output?

Jeremy Hughes
 

Hi Leif,

Apologies for not greeting you on your first message to Xway Talk!

Jeremy

161 - 180 of 918