Quote:
Originally Posted by blackest
Chrome gives you more than a html view, you can have an iphone 6 view a touchscreen laptop view an ipad view and more ...
There are other things which can be used too such as git for versioning
I think one thing i do like is bigger windows i'm working on a 13" Laptop so it helps i can move between brackets and Chrome its kinda handy to be able to highlight an object in chrome and bring up the quick edit for the class in use
I've attached a screen shot with brackets open and chrome displaying the xhtml file. Because its brackets as the server and chrome the client i can use chrome at the window size i want and have the code near full screen. It can be full screen.
|
Yabbut, all you're doing is using something like Developer Tools, to set approximate sizes, and seeing how a BROWSER would render it--which doesn't always, and often does not, track to how the content is actually displayed in a real eReader. You mentioned iBooks and Google's app as being the "nicest," which tells me that you expect/want ebooks to render like webpages--and they don't.
I mean, it doesn't matter to me if you can't live without Brackets, etc., but making eBooks so that they work on a browser means pretty much nothing, in the development and production of eBooks. I would never--
never--use a browser as a development tool, not at this time.
Spoiler:
(I just endured a conference call with a client, who develops webpages, and was absolutely CONVINCED that of course, we could nest tables to create a faux Bootstrap mechanism so that if a table was made untenable by a user making their font too large, that the table would effectively degrade to vertically-stacked cells. [Which, he adivsed, is what HE would do, to achieve tables that worked in every eBook environment regardless of font sizing.] Oh, and that we could manipulate uls and ols all we wanted, starting with a given number, changing margins, yadda-yadda, most of which is NOT doable.)
I can understand the attraction of the quasi-Firebug functionality,
certainly. I'm sure everyone can see that. But I'm simply saying, assuming that you're doing this for some commercial purpose--your own, or for clients, etc.,--browser views are, in my opinion, wildly misleading.
Offered solely FWIW.
Hitch