Bug 17135 - too much complexity in debugging for development, slim it down
Summary: too much complexity in debugging for development, slim it down
Status: RESOLVED DUPLICATE of bug 17134
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC All
: P2 Enhancement
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-01 08:07 PST by Mike Walters
Modified: 2008-03-13 22:36 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Walters 2008-02-01 08:07:45 PST
safari needs an simpler approach to debug and develop. There are too many hoops (and instances, like drosera, etc) to jump through just to get to css/javascript/html and seems like they are view only in most cases. Please take note of the implimentation of  Firebug for firefox. Put them all in one place! maybe just hitting F12 opens a plugin that has everything all-in-one. No reason to re-invent the wheel, keep it simple.

Per convo with apple dev:

<MikeL> i wrote a (very simple) script that runs and evaluates javascript in real-time. im not sure why you would say you cant particulary

<MikeL> (Drosera)freezes alot (very frustrating), non-intuitive design, wheres the custom var watches, real-time updating, etc.... laundry list of missing tools

<MikeL> ... just take notice of how firebug works for instance, its a proven design, built by developers

<MikeL> picture using firebug and your used to editing css and *poof* it responds in the browser

<aroben> MikeL: and you can do that now with the Web Inspector
<aroben> MikeL: but we want to have JavaScript debugging and CSS editing in one tool
<aroben> MikeL: like Firebug does

<aroben> MikeL: the biggest thing the Web Inspector is lacking right now is a JS debugger

<bdash> there are technical reasons why we can't do that at the moment though
<aroben> MikeL: we're working towards it, but as andersca said we have some technical challenges to fix first
<MikeL> u can, but i have to spawn another instance for web inspector, another instance for drosera, another console for the javascript (which i havent gotten to work)

<MikeL> i program at a rapid pace, and i want people to be able to use safari as well as other browsers. w/o the tools it just slows me down
Comment 1 Adam Roben (:aroben) 2008-02-01 08:11:43 PST
See bug 17134, which is about integrating JavaScript debugging into the Web Inspector. This should streamline the process quite a bit, but there's clearly more work to be done.
Comment 2 Mike Walters 2008-02-01 08:15:55 PST
the quotes are a bit out of context, please read with caution. I was attempting to cut/paste the important info from our conversation - Mike
Comment 3 Adam Roben (:aroben) 2008-03-13 22:36:45 PDT
Given that we have bugs filed for the specific issues filed here, closing as a dupe of bug 17134, since the biggest complaint listed here was for Drosera and the Inspector to be unified. Any other specific issues should be filed as new bugs.

*** This bug has been marked as a duplicate of 17134 ***