Skybound Support Forum

Add New Post

nathanwells
Member

Is there any way to preview with Chrome?

Thanks,
Nathan

Posted 1 year ago #
Skybound_Paul
Key Master

No, but we have Safari previews working internally in the Mac version (both browsers use the webkit rendering engine).

Posted 1 year ago #
ForTheLose
Member

Will it be possible to have Webkit as an option on the Windows version? That seems like a really essential need since:
a) Chrome is picking up in usage percentage, and
b) Webkit is very likely the #1 rendering engine for the good mobile browsers at this moment in time (thanks to Android and iPhone)

Posted 1 year ago #
Skybound_Andrew
Key Master

Chrome integration is labeled "Someday/Maybe" in the to-do list.

Posted 1 year ago #
kcwebguy
Member

I would agree that Chrome and Safari are critical browsers to have in Stylizer.

I would not concern myself with Opera, however. Their death is pending.

Posted 1 year ago #
bobbravo2

I'd add my vote for chrome - I'm finding that I use it more and more for work/speed of rendering.

Posted 1 year ago #
Skybound_Andrew
Key Master

@kcwebguy: Unless Opera changes their draconian licensing policy, it's practically impossible for us to include it anyway.

Posted 1 year ago #
vmadman
Member

I'm a bit of a cross-roads personally. While most of our clients use IE and Firefox many of them are on Macs. I have no reliable way of developing CSS for Safari & Chrome, which kinda removes the point (at least for me) in using stylizer at all.

I mean, it would be fine, except that since I've adopted Stylizer I have moved away from tables and html into purely css driven sites.. so hand editing is now a nightmare. Stylizer has encouraged me to be less aware of each css definition.. it has enabled me to be lazier in my css design planning.

I can understand the challenge of getting any rendering engine into stylizer, considering that stylizer does things I've never seen done before on any browser/platform... but man, I think getting webkit support into stylizer should be a pretty high priority. I imagine you'd be surprised how many people would consider it a deal breaker.

I suppose, on the bright side, many of us who now realize we need it have already purchased Stylizer Ultimate (its not something that immediately came to mind when I was considering Stylizer).. and given that Stylizer is reasonably priced I cant say I regret the purchase. But, had I known then what I know now I likely would not have purchased it, since I've managed to work myself into a horrible position.

Thanks,
Luke

Posted 6 months ago #
spiral

vmadman, what is the problem exactly with developing for webkit with stylizer?
Let me tell you my usual workflow:

I code my html, open up in stylizer, style using almost exclusively the firefox preview (if it's something I know is going to be tricky in ie, i switch back and forth). When I'm more or less done, I switch to IE and troubleshoot any issues I see. When I'm done, I open up any additional browsers I want to test on (typically ie7/8 through ietester and safari), open up my page and make any changes on stylizer while i have the other browser open.

Sure it's not as smooth as if I had those browsers actually integrated into stylizer, but usually the tweaking is minimal, especially on safari, since the webkit engine is not that different from the mozilla one.

what's your workflow? where are you getting stuck?

Posted 6 months ago #
Skybound_Paul
Key Master

> I think getting webkit support into stylizer should be a pretty high priority. I imagine you'd be surprised how many people would consider it a deal breaker.

True, but consider that the web design industry is driven by Mac junkies who won't even look at Windows software, let alone consider using it, you can guess where our priorities are right now. That being said, WebKit in Stylizer is important to us.

Posted 6 months ago #

RSS feed for this topic

Reply

You must log in to post.