Command to open a file in HE's integrated browser

[cichlasoma]

Is there a (commandline) command to open a html file in HE's integrated browser?

[alex]

No, it does not exist.
You can see all available options with hippoedit --help.
What is the scenario for this?

[cichlasoma]

What is the scenario for this?

I defined one tool converting the current file from textile to html (creating another target file) and another tool displaying the new file in a browser. (Currently, it's an external browser.)

[alex]

there was a similar topic some time ago you can check.
But, generally, right way will be using internal scripting coming in 1.50 and use script command to pass url to it.
You want to open hippoedit as single instance passing url to it to be open in internal browser?


BTW: if you will publish you syntax schema for textile you will get a free license
From another side I am waiting for one more bug reported from you. It will be also enough, but with a new syntax schema definitely
Of course , if you already do not have one.

[cichlasoma]

there was a similar topic some time ago you can check.
But, generally, right way will be using internal scripting coming in 1.50 and use script command to pass url to it.
You want to open hippoedit as single instance passing url to it to be open in internal browser?

Thanks for the link. Yes, I want to open the file which has the same name as the current one and is located in the same folder but has another extension (html instead of textile) and which was created by another tool. I'd like to open it in another tab of the same instance of HE (which is easy to do for the html source code).

BTW: if you will publish you syntax schema for textile you will get a free license
From another side I am waiting for one more bug reported from you. It will be also enough, but with a new syntax schema definitely
Of course , if you already do not have one.

Great! (No, I don't have a licence still.)
As for publishing textile scheme, I plan to do so, but I'd like to polish it a bit first.
(Not all textile features are implemented so far even where HE would make it possible and colors of styles are hard-coded, not using colors from palette so far. Morover, it's not a classical syntax highliting in a sense, but a highlighting making a sort of WYSIWYM textile editor from HE (e.g., not just "tags" indicating italics are highlighted, but all the text between them is shown in italics). (But perhaps, that would be not a problem...)
Another issue is, my scheme doesn't make a proper use of inheritance so far, I'm afraid, as I don't understand the working of the feature properly so far...)
So, I have to improve it first a bit, definitelly...)
EDIT: Moreover, I should write a "civilized" comments on "special" features of the highlighting and on its shortcomings due to HE's syntax definition limitations.

[alex]

Thanks for the link. Yes, I want to open the file which has the same name as the current one and is located in the same folder but has another extension (html instead of textile) and which was created by another tool. I'd like to open it in another tab of the same instance of HE (which is easy to do for the html source code).

OK, clear. Of course I can add some "special" tag for tools to use internal browser, but this will be misuse...  Normally command window should contain name of the tool, and name should be valid file name (there is already trick to open current file with associated app if command field contain %FileName%, I think, but I do not like this). So better wait till scripting, and as workaround you can use Context Help Items - you can assign a shortcut for executing them

As for publishing textile scheme, I plan to do so, but I'd like to polish it a bit first.

No problem. Just send it to me when you will be finished and I will help you to make it "standard" and to use all features of HE which are possible or come in 1.50. But please send me also example file for testing.
About WYSIWYG representations - this is a good idea, I already thought about this, but have not used for HTML because, I think, not everybody will like it (because of embedded syntaxes, it will not always work right). But if you think this is OK, for textile, and will be useful for others, let use it and see how people will comment.

[cichlasoma]

OK, clear. Of course I can add some "special" tag for tools to use internal browser, but this will be misuse...  Normally command window should contain name of the tool, and name should be valid file name (there is already trick to open current file with associated app if command field contain %FileName%, I think, but I do not like this). So better wait till scripting, and as workaround you can use Context Help Items - you can assign a shortcut for executing them

Thank you for the tips!
(Currently, I use the "%FileDir%\%FileNameWOExt%.html" argument for the command starting a browser.)

No problem. Just send it to me when you will be finished and I will help you to make it "standard" and to use all features of HE which are possible or come in 1.50. But please send me also example file for testing.
About WYSIWYG representations - this is a good idea, I already thought about this, but have not used for HTML because, I think, not everybody will like it (because of embedded syntaxes, it will not always work right). But if you think this is OK, for textile, and will be useful for others, let use it and see how people will comment.

OK. Thank you for the offered help!
BTW - do you think, it would be possible to publish a scheme with hardcoded colors or do you think colors from pallete have to be used? (I'm inclined to hardcoding a bit not (only) because of my laziness but because I find using lot of carefully selected special font and background colors convenient for textile.
As for WYSIWYM representation - I find it convenient, but in HE, there's a problem with textile that the representation cannot be 100% correct, mainly because formatting blocks end with"\n\n" in textile...

[alex]

BTW - do you think, it would be possible to publish a scheme with hardcoded colors or do you think colors from pallete have to be used? (I'm inclined to hardcoding a bit not (only) because of my laziness but because I find using lot of carefully selected special font and background colors convenient for textile.
As for WYSIWYM representation - I find it convenient, but in HE, there's a problem with textile that the representation cannot be 100% correct, mainly because formatting blocks end with"\n\n" in textile...

As I wrote, I am against of this, because this make it complex to use the schema with different color schemes.
The only way, if hardcoded colors are used, to make it working always, is to override all inherited style colors (as normal and window), to forbid using of palette colors.

As for WYSIWYM representation - I find it convenient, but in HE, there's a problem with textile that the representation cannot be 100% correct, mainly because formatting blocks end with"\n\n" in textile...

We can check this at the end, the HE was not built to design this by default, but if standard style definitions are used, then it should work...

[cichlasoma]

We can check this at the end, the HE was not built to design this by default, but if standard style definitions are used, then it should work...

(Anyway, imlementig the possibility to define blocks ending with "\n\n"  would be quite an important feature request as for me...)

[alex]

I do not see this feasible in 1.4x. I need to do too much to implement such extension.
Maybe in 1.5x I will think about it: or as build in or as regular expression.