Page 1 of 1

Convert a QEWB / Linux to a WWB project

Posted: Mon Aug 30, 2021 12:43 pm
by alex4orly
I need some functionality in an existing project
Can I somehow convert it to Windows WWB?

How?

Thanks

Re: Convert a QEWB / Linux to a WWB project

Posted: Mon Aug 30, 2021 1:27 pm
by Pablo
I'm sorry, that is not possible.

Re: Convert a QEWB / Linux to a WWB project

Posted: Mon Aug 30, 2021 8:45 pm
by alex4orly
OK, just that IMPORTING a html page function, does not bring in much

Cheers

Re: Convert a QEWB / Linux to a WWB project

Posted: Mon Aug 30, 2021 9:29 pm
by BaconFries
Sorry Alex but the "HTML import" isn't meant to fully import your project back to its original state. It will only recover "Text and Images" including the following form elements and body attributes (link colors, background images, meta tags). You can read more at the following:
Importing an existing HTML page in to Web Builder
http://wysiwygwebbuilder.com/import_html.html

Re: Convert a QEWB / Linux to a WWB project

Posted: Mon Aug 30, 2021 10:35 pm
by alex4orly
BaconFries wrote: Mon Aug 30, 2021 9:29 pm Sorry Alex but the "HTML import" isn't meant to fully import your project back to its original state. It will only recover "Text and Images" including the following form elements and body attributes (link colors, background images, meta tags). You can read more at the following:
Importing an existing HTML page in to Web Builder
http://wysiwygwebbuilder.com/import_html.html
Hello my teacher,
Yes, I am aware of that, nor do I expect it to import any custom code or any javascript.
But, Please examine the file I just uploaded below and see how much is missing....

https://nmaa-rc.org.au/imported.txt

Can I do anything about it? I am NOT trying to import the entire project at once, just page by page

Cheers
Alex

Re: Convert a QEWB / Linux to a WWB project

Posted: Tue Aug 31, 2021 12:07 am
by BaconFries
When using the HTML Import it is really just the basic HTML that will get imported. The likes stylesheets, Layout Grids, Flexbox, events and any advanced features will not get imported this is why so much is missing sorry.

Re: Convert a QEWB / Linux to a WWB project

Posted: Tue Aug 31, 2021 12:34 am
by alex4orly
Well, until know, all that I did was
1) create a new blank page
2) copy paste into the relevant sections from the existing page.

This works in most cases.
My only question to Pablo and to you, why not have an option to create really just a blank / empty page?
It will make life, so much easier for such cases.
Or, creat a blank page and let me delete the content to make it really empty.

Why not?
Thanks

Re: Convert a QEWB / Linux to a WWB project

Posted: Tue Aug 31, 2021 1:20 am
by BaconFries
My only question to Pablo and to you, why not have an option to create really just a blank / empty page?
Because WYSIWYG Web Builder is not a HTML Editor it is a HTML Generator (Visual Tool) this means that no HTML excists till you actually publish.
Or, creat a blank page and let me delete the content to make it really empty
.
As already mentioned the software is not a HTML Editor so you cannot create a blank page to Add / Modify / Delete content that you wish like copy and pasting the full source from one page into the program it is not possible for the reason mentioned.

I am sure Pablo will give his input when he reads this.

Re: Convert a QEWB / Linux to a WWB project

Posted: Tue Aug 31, 2021 2:05 am
by alex4orly
OK, I know that WWB is NOT a html editor.
1) I created a blank page.html - uploaded it to my site
2) Went into WWB in my Windows VirtualBox
3) Imported the page into the project, here is the result:
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Untitled Page</title>
<meta name="generator" content="WYSIWYG Web Builder 15 - http://www.wysiwygwebbuilder.com">
<link href="importing.css" rel="stylesheet">
<link href="blank.css" rel="stylesheet">

</head>
<body>
</body>
</html>
WWB added the two lines marked in RED, I can't remove them in WWB, why can't those two lines be ommitted - just let me import the original html?

Otherwise, I am forced to create two dummy files with nothing inside them, what for?
Just make an option / tick box to check with / without... Is that a bad idea? There are many html pages with no need for any css in them, they are just doing a function, not at all visible to anyone.

After I review the generated html page, I see that all the css code that I imported, was generated as an external css file instead. Did I ask for that? As I suggested, maybe WWB can have an option - generate css or embed? let the user have a choice please

Thanks again

Re: Convert a QEWB / Linux to a WWB project

Posted: Tue Aug 31, 2021 6:12 am
by Pablo
Did I ask for that?
Yes!
You can control this in Tools -> Options -> HTML -> General external CSS file.
just let me import the original html?
WWB does not work with HTML internally, this is what makes it possible to give you so much control over the layout and you can even what between different layout modes.
When you import HTML, then WWB will basically makes a snapshot of the visible layout (text and images) and convert this to WWB's internal format, so it can work with the data.
There is no way for the software to make sense of layout grid's or other layout structures so only absolute/fixed layout can be imported.

In the Site Manager, you can add external files. So, that gives you the ability to add a blank page or a page with code of your choice.

Re: Convert a QEWB / Linux to a WWB project

Posted: Tue Aug 31, 2021 6:31 am
by alex4orly
Hello again,

Not clear what that means:
In the Site Manager, you can add external files. So, that gives you the ability to add a blank page or a page with code of your choice.
Can you please give me an example

Interesting too :

My original page (in Linux) is this : https://nmaa-rc.org.au/committee21.html
The new page generated by WWB : https://nmaa-rc.org.au/com21.html

But, when I look in the generated code, an entire section is missing from the code
#Button6
{
display: block;
width: 100%;
height: 23px;
z-index: 4;
}
#Button9
{
display: block;
width: 100%;
height: 23px;
z-index: 9;
}
#Button7
{
display: block;
width: 100%;
height: 23px;
z-index: 7;
}
#Button11
{
display: block;
width: 100%;
height: 23px;
z-index: 6;
}
#Button12
{
display: block;
width: 100%;
height: 23px;
z-index: 10;
}
#Button10
{
display: block;
width: 100%;
height: 23px;
z-index: 5;
}
#Button5
{
display: block;
width: 100%;
height: 22px;
z-index: 3;
}
#Button8
{
display: block;
width: 100%;
height: 23px;
z-index: 8;
}
#wb_Image1
{
display: inline-block;
width: 108px;
height: 158px;
z-index: 0;
}
@media only screen and (max-width: 480px)
{
#wb_LayoutGrid1
{
visibility: visible;
display: table;
font-size: 13px;
font-weight: normal;
}
#wb_LayoutGrid1
{
margin-top: 0px;
margin-bottom: 0px;
}
#LayoutGrid1 .row
{
margin-right: -0px;
margin-left: -0px;
}
#LayoutGrid1 > .row > .col-1, #LayoutGrid1 > .row > .col-2
{
}
#LayoutGrid1 > .row > .col-1
{
display: block;
width: 100%;
border-radius: 0px;
text-align: center;
}
#LayoutGrid1 > .row > .col-2
{
display: block;
width: 100%;
border-radius: 0px;
text-align: center;
}
#wb_Text37
{
visibility: visible;
display: block;
}
#wb_Text37
{
margin: 0;
}
#wb_Text38
{
visibility: hidden;
display: none;
}
#wb_Text38
{
margin: 0;
}
#wb_Image1
{
width: 108px;
height: 158px;
visibility: visible;
display: inline-block;
margin: 0;
}
#Image1
{
width: 108px;
height: 158px;
}
#wb_LayoutGrid3
{
visibility: visible;
display: table;
font-size: 13px;
font-weight: normal;
}
#wb_LayoutGrid3
{
margin-top: 0px;
margin-bottom: 0px;
}
#LayoutGrid3 .row
{
margin-right: -0px;
margin-left: -0px;
}
#LayoutGrid3 > .row > .col-1, #LayoutGrid3 > .row > .col-2
{
}
#LayoutGrid3 > .row > .col-1
{
display: block;
width: 100%;
border-radius: 0px;
text-align: left;
}
#LayoutGrid3 > .row > .col-2
{
display: block;
width: 100%;
border-radius: 0px;
text-align: left;
}
#wb_LayoutGrid4
{
visibility: visible;
display: table;
font-size: 13px;
font-weight: normal;
}
#wb_LayoutGrid4
{
margin-top: 0px;
margin-bottom: 0px;
}
#LayoutGrid4 .row
{
margin-right: -0px;
margin-left: -0px;
}
#LayoutGrid4 > .row > .col-1
{
}
#LayoutGrid4 > .row > .col-1
{
display: block;
width: 100%;
border-radius: 0px;
text-align: left;
}
#Button5
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#Button6
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#Button10
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#Button11
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#Button7
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#Button8
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#Button9
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#wb_LayoutGrid5
{
visibility: visible;
display: table;
font-size: 13px;
font-weight: normal;
}
#wb_LayoutGrid5
{
margin-top: 0px;
margin-bottom: 0px;
}
#LayoutGrid5 .row
{
margin-right: -0px;
margin-left: -0px;
}
#LayoutGrid5 > .row > .col-1
{
}
#LayoutGrid5 > .row > .col-1
{
display: block;
width: 100%;
border-radius: 0px;
text-align: left;
}
#Button12
{
width: 100%;
visibility: visible;
display: block;
margin: 0;
}
#wb_Text1
{
visibility: visible;
display: block;
}
#wb_Text1
{
margin: 0;
}
}
But, both pages work the same - how is that?

Thanks

Re: Convert a QEWB / Linux to a WWB project

Posted: Tue Aug 31, 2021 9:04 am
by Pablo
WWB is not an HTML editor, it does not work with HTML code internally.
When you import an HTML page then it will converted to WWB's internal format. No HTML will be used internally.

If you want to make an external HTML page part of your project then you can use the 'Insert external file' option in the Site manager.
https://wysiwygwebbuilder.com/site_manager.html