This module is awesome! Speeds up design alot.
I use firebug all the time and find that having firebug and sweaver open kinda removes the whole browser screen. Of course i could use sweaver as my firebug , but firebug has alot more which i use aswell. Of course i do minimize sweaver to get it working ;) I actually open firebug as its own window.
But it got me thinking it would be cool to be able to add sweaver to firebug like drupal for firebug. If this were the case it would become its own little drupal IDE with drupal for firebug ... add devel onto firebug .. oh my .
Any thoughts of this type of developments happening?
Comments
Comment #1
jyve CreditAttribution: jyve commentedI recognize the issue, and the idea has crossed our minds, but we'll be focusing on Sweaver as it is now, so no sweaver in firebug, sorry :)
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedok .. would it be in any way likely that the function to be able to make sweaver its own floating box? so that it is not attached to the bottom .
Again thanks for this module and the hard work, it makes designing so much more interesting. If i could or if i can, how could I contribute to the development of this module. I am not much of a developer, have a design background but maybe a donation or something.
Comment #3
TimelessDomain CreditAttribution: TimelessDomain commentedAllowing Firebug, or a similar program, to display the selection areas css while also having the ability to edit the selection area through the sweaver interface would improve the effectiveness of sweaver. Right now a user may have to select multiple variations of elements (classes & ids) to be able to trigger the exact changes that they want. By displaying the firebug results alongside the sweaver element selector interface, you would be able to see exactly what elements you need to click on. Sweaver could even automatically highlight these through css or automatically select them to save the user clicking.
There could be an option in sweaver preferences
Just allowing the 2 scripts to run alongside one another is the main goal, but i just threw everything else out there to show you what could be possible. Thanks
Comment #4
TimelessDomain CreditAttribution: TimelessDomain commentedComment #5
Anonymous (not verified) CreditAttribution: Anonymous commentedThis would be great but we're still not there yet. I have many other request to fulfill first, most of them are about stability and interaction with other modules. The road map is as you see quite full for now but we'll get there one day, sorry.
Comment #6
TimelessDomain CreditAttribution: TimelessDomain commented