I think the gecko activeX control would make the most sense, seeing as how one of the features of Dev-PHP is its small size. Not to say that Gecko is a large product, but adding an entire html rendering engine into the IDE would greatly increase its size.
(My two cents)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know Gecko is the best (In fact, my default browser is Mozilla Firefox), but I can't see a good reason to include it in Dev-PHP. I know it respects the web standards and it is much more secure than IE, but I also have some good reasons to keep using IE inside Dev-PHP:
* Unless you use Dev-PHP as a web browser, the security issues of IE will not affect you.
* Dev-PHP is a PHP editor, not an HTML editor.
* Gecko does NOT support CHM files. A lot of people told me "well, they can still use HTML manuals", but I think this would not be convenient since HTML manuals are a lot bigger than CHM manuals.
Correct me if I am wrong, but I think that using Gecko as the Dev-PHP Internal Browser would only increase the editor's size and would not add any interesting feature to the editor.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For me it would indeed create advantages. I also use FireFox as standard browser. Not just for fun, but mostly becease it comes in very handy when developing in php.
When developing I have to debug a lot. So I want to be certain that the php-code that I wrote, brings the desered effect. There for I use the "View Page Source" a lot to see the generated HTML with source code highlighting. IE is not that easy in use.
Better still. When selecting a piece of html, you can actually use "View Selection Source" wich enhances this, by only showing you the selected piece of raw HTML.
There are more features when clicking the right mouse button. For instance the "Page Info" option. Or the "This Frame..." options.
When size maters, why not give an option to use either one. And if some nerd want's to use gecko, he has to supply the necessary files. No problem! Everybody happy. Or am I missing something?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've just tested the Mozilla ActiveX Control. You're right. Just a few options are available. View Source and Page info features are not included.
So, no hurry to implement gecko. I use the browsers to check on cross-browser behaviour.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I noticed that Dev-PHP uses the Internet Explorers engine to render html docs in the internal browser. Why not use Gecko? Or better: offer a choice between both render engines.
For more reading on this, see:
http://www.mozilla.org/why/embed.html
http://www.mozilla.org/projects/embedding/faq.html
http://www.iol.ie/%7Elocka/mozilla/mozilla.htm
Greatings!
I think the gecko activeX control would make the most sense, seeing as how one of the features of Dev-PHP is its small size. Not to say that Gecko is a large product, but adding an entire html rendering engine into the IDE would greatly increase its size.
(My two cents)
The gecko ActiveX control is probably the most easiest to implement.
and who cares about standards knows that Gecko rules :)
I know Gecko is the best (In fact, my default browser is Mozilla Firefox), but I can't see a good reason to include it in Dev-PHP. I know it respects the web standards and it is much more secure than IE, but I also have some good reasons to keep using IE inside Dev-PHP:
* Unless you use Dev-PHP as a web browser, the security issues of IE will not affect you.
* Dev-PHP is a PHP editor, not an HTML editor.
* Gecko does NOT support CHM files. A lot of people told me "well, they can still use HTML manuals", but I think this would not be convenient since HTML manuals are a lot bigger than CHM manuals.
Correct me if I am wrong, but I think that using Gecko as the Dev-PHP Internal Browser would only increase the editor's size and would not add any interesting feature to the editor.
For me it would indeed create advantages. I also use FireFox as standard browser. Not just for fun, but mostly becease it comes in very handy when developing in php.
When developing I have to debug a lot. So I want to be certain that the php-code that I wrote, brings the desered effect. There for I use the "View Page Source" a lot to see the generated HTML with source code highlighting. IE is not that easy in use.
Better still. When selecting a piece of html, you can actually use "View Selection Source" wich enhances this, by only showing you the selected piece of raw HTML.
There are more features when clicking the right mouse button. For instance the "Page Info" option. Or the "This Frame..." options.
When size maters, why not give an option to use either one. And if some nerd want's to use gecko, he has to supply the necessary files. No problem! Everybody happy. Or am I missing something?
If I remember well, the View Source and Page info features are not included in the ActiveX component.
I've just tested the Mozilla ActiveX Control. You're right. Just a few options are available. View Source and Page info features are not included.
So, no hurry to implement gecko. I use the browsers to check on cross-browser behaviour.