I tried to store my EWB projects on a NAS.
In the project's options | Compilation | Output Path is set to a local
directory, e.b. c:\beckersoft\Websites\MySite

That doesn't seem to work. EWB tries to compile into an output path
relative to the project's path.

Example:

Project is stored here:
\\nas\EWB\Projekte EWB2\TippligaM

Output Path in the project's options:
c:\beckersoft\Websites\TippligaM

Error:
[Content]
Error creating output path: \\nas\EWB\Projekte
EWB2\TippligaM\c:\beckersoft\Websites\TippligaM

Is that a feature or a bug? And if it's a feature: can the output path
and the project path be separated?

Thanks Uli

Uli Becker wrote:

> Is that a feature or a bug? And if it's a feature: can the output path and the project path be separated?

It's a feature - always has been relative. Your case does show it should be "unrelatived" if the output is outside of the core path. I think that one level up matching would be fine, after that just use absolute path.

So project in:

c:\src\BigProject\WebBuilder

and output in :

c:\src\BigProject\Server\html

would stay as relative:
...\Server\html

But output in:

c:\src\Different\Server\html

would be absolute.

And paths with \\ at the start would always be absolute.

(Just my ideas...)

--

Matthew Jones

Matthew,

> It's a feature - always has been relative. Your case does show it should be "unrelatived" if the output is outside of the core path. I think that one level up matching would be fine, after that just use absolute path.

Yes, since I am allowed to enter an absolute path in the project's
options, I expect this path to be used.

Anyone using a NAS for EWB projects?

Thanks Uli

Uli Becker wrote:

> Anyone using a NAS for EWB projects?

It's not so much NAS as server generally - depends on your definitions etc. Me, I don't, but there are many who say you shouldn't use even mapped drives any more it is so 1990's. I guess as more users push EWB in ways outside expectations that this will become important to change.

--

Matthew Jones

On 1/19/2017 4:32 AM, Uli Becker wrote:
> That doesn't seem to work. EWB tries to compile into an output path
> relative to the project's path.

That's "as designed" as per manual : " This path is relative to the main
project source folder. If you specify an absolute path here, the IDE
will automatically convert it to a relative path when the Project
Options dialog is closed by clicking on the OK button."

In your case it's a UNC path so there is no relative path equivalent -
however even if you used drive+path with different drive it would likely
not work either.

> Is that a feature or a bug? And if it's a feature: can the output path
> and the project path be separated?

This is something for Tim to look into.

You can use deployment path that is completely separate but then you'd
need to deploy each time but that should work.

I did a quick test and UNC path in deploy path did work for me

Raul

Raul,

> You can use deployment path that is completely separate but then you'd
> need to deploy each time but that should work.

Good idea - as soon as just .html and .js can be deployed, I'll do it
this was.

Thanks. Uli

On 1/19/2017 10:55 AM, Uli Becker wrote:
> Good idea - as soon as just .html and .js can be deployed, I'll do it
> this was.

Curious what else are you deploying ?

As long as the items are added as external files into the project EWB
should deploy them all properly.

There is also "deploy on run" option which (might) simplify the delpoy
step during development.

Raul

Raul,

> Curious what else are you deploying ?

All Images- and subfolders e.g.
..html and .js files cannot be deployed separately. And with many files
that takes some time.

See here:
http://tinyurl.com/ztg5rj5

> As long as the items are added as external files into the project EWB
> should deploy them all properly.
>
> There is also "deploy on run" option which (might) simplify the delpoy
> step during development.

Yes, I know.

Uli