Git Menu Not Becoming Active about gitweaver HOT 11 CLOSED

the system checks for a .git or _git folder at the root of the site.
What version of DW are you on?

from gitweaver.

I'm using DW 11.5 Build 5315, I checked and the folder was at the root of the site and it still wasn't giving me the options

from gitweaver.

Ah CS5.5 then. I'll have a look later. Guessing you have tortoise git installed.

Can you give me...
Verision of Windows (I.e. Windows 7 64 if its the 64 bit version)
Version of TortoiseGIT

have to check these things as ive had no other issues :)

from gitweaver.

Yes i have that installed as well

Sent from Samsung MobileChris McKee [email protected] wrote:Ah CS5.5 then. I'll have a look later. Guessing you have tortoise git installed.

Reply to this email directly or view it on GitHub:
#3 (comment)

from gitweaver.

• DW CS6 (12.1)
• Win 7 64
• TortoiseGit 1.7.15.0

Unfortunately no luck with GITWeaver 1.4.0.

from gitweaver.

Hi,
I've made a quick chop of the current state of play

https://www.dropbox.com/sh/mq20ynkrp0tx7lx/BLp_kHsp50

Basically contains a copy of 1.4 but with the resolution check (checking that the workpath contains _git or .git at the root killed off)

I built this over 3 years ago to fit a need in the frontend devs work cycle (and to assist in getting source control integrated) its not had much love.

Once I've finished the docs I'll push the source and working test projects up.

from gitweaver.

Thanks, works w/

• DW CS6 (12.2)
• Win 7 64
• TortoiseGit 1.8.1.0

from gitweaver.

Ace; I attempted adding git checking using a command line test but Dreamweavers API is still the dire pile of crap Macromedia built in 2002.

from gitweaver.

Chris, the more thanks to you for making this available to us others.
Let's see if Adobe will add native Git support, as they have for SVN.
Would be high time, if they asked me..

from gitweaver.

Have you ever tried the built in SVN support

JS/XML/OtherStuff -> C-API > SVN

Works fine with tiny projects; drove me utterly mental; the advantage to hooking into tortoise or even shell is simply that it runs a separate app in a separate process taking DW out of the process altogether. The downside of course is you dont get the status icons :|

Hard to tell what will happen with DW in the future; I have a feeling it will either make a huge evolutionary jump and be rebuilt from the ground up in something other than sawdust or they'll kill it off for a similar product.

from gitweaver.

I've used the built in SVN for a couple projects a while ago, and was OK
with it. As I'm a designer / frontend guy, I guess my expectations might
not be / have been that high. Good point on the advantages of running
VCS in a separate process, and by now I'm also fine with using
TortoiseGit and/or shell (I might have to be actually grateful to Adobe
for forcing me out of my comfort zone, to actually learn Git etc).
However, as DW is my main coding IDE, it's still very much convenient to
have those (Tortoise)Git commands available there, so thanks again..

Have had similar thoughts on the future of DW. I would probably bet on
them not killing it -- the thing seems to be too popular for that. In
theory they could just keep the brand, and switch the underlying
codebase more or less completely. Personally I would like to see a fork
of DW w/ most of its code editing features (completion mainly), FTP
stuff, and some other things kept (eg. also easy
customization/personalization of the IDE comes to mind), but otherwise
they could throw out most of the bloat they have there. So, I'll go and
dream on now.. :)

from gitweaver.