Finding Help

We are always happy to help new users; please don't feel bad about asking! The two best ways to get help are the firebreath-dev google group and the IRC chat room.

Subscribe to firebreath-dev

Email:

Visit this group

Web Forum

Another place you can look for help is the web forums. Use your firebreath.org login in the forums as well!

Getting in touch via IRC

Most of the core developers can be found in the #firebreath channel on irc.freenode.net.  There is a web client that you can use for quick questions.

Если говорите по-русски, то можно `#firebreath-ru`.

You can also look at the [channel logs|http://logs.firebreath.org/].

Join the firebreath-dev google group

The next best way to get in touch with us (or the best way if we're not around on IRC) is to join the FireBreath Google Group:

• http://groups.google.com/group/firebreath-dev

  firebreath-dev Google Group (Dedicated to the design, development, and use of the FireBreath project: http://firebreath.googlecode.com Open to all who wish to use FireBreath.)
  Windowless redraw is slow in Window Safari While other browsers are fine, I do find that windowless drawing of 20 ms cycle in Safari is not achievable. I've done up a simple test which shows a small rectangle moving left to right on a 20 ms interval. If compare Safari with other browsers, the rectangle moves slower than the rest. If I set it
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits heinob, As I mentioned that the DLL could be found after execute register32 by hand. Up to now, I still don't know why I can't build WiXInstall.vcxproj on Win2008 Server 64 bits, and I have no idea how to fix it. Richard, I am not sure how to use heat.exe. I try to use heat.exe to generate wxs
  Re: [firebreath-dev] Expose the C# classes in JavaScript through Firebreath Framework You will likely need to have your wrappers in a second dll called by fb on instantiation. Framework. property from C# in JavaScript I have to instantiate the wrapper in Firebreath. and Please let me know "firebreath-dev" group. email to firebreath-dev+unsubscribe@goo glegroups.com.
  Expose the C# classes in JavaScript through Firebreath Framework Hi, I need to expose the C# classes in JavaScript through Firebreath Framework. I have created the wrapper for the same but to invoke each method, property from C# in JavaScript I have to instantiate the wrapper in Firebreath. So Could you please suggest any centralized solution for Wrapper? and
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits WiX can only successfully "compile", if it can successfully register your plugin. So to exclude that error reason you should try to register your plugin-DLL "by hand". If that succeeds, there is another reason. if it fails --> find the reason why. 2013/5/14 YoKo Lo <yoko...@gmail.com>
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits heinob, My problem is compile fail when build WiXInstall. :( Richard, I find build\projects\MyPlugin\npfbPl ugin_auto.wxs in 64-bits seems to leak some information. Why this file miss some content? How could I make this file correct? ***incorrect in 64-bits***: <?xml version="1.0" encoding="utf-8"?>
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits That is quite easy: Try to register your DLL with regsvr32.exe. If it succeeds all DLL's shich are loaded by your DLL are there. If it fails, something is missing. Remember that all dependend DLL's have to be reachable (means staying in the same directory as your DLL or in \Windows\System32).
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits Is there a particular reason why you need 64 bit support on windows? I don't know why wix wouldn't be working; you'll have to troubleshoot that yourself. Try using heat.exe from wix to harvest the com info from a 64 bit dll, that will shed light on it. Also, if you're using vs2010 pro (not express) you shouldn't need the windows sdk.
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits Thanks for your reminder, I use IE64/Firefox(64) to run the 64-bits DLL (directly build code without running WiX), and it works well. You say maybe it is missing a DLL in 64 bits.-->It means maybe WiX ToolSet is missing a DLL in 64 bits? If yes, How could I find the root cause and come out solution?
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits the 64 bit DLL is only needed if you're using a 64 bit browser; I don't know why wix doesn't support 64 bit COM correctly, but it seems to sometimes have issues. Maybe it's missing a DLL in 64 bit? I don't know. It's worth noting that while 64 bit versions of windows do come with IE 64 bit, they still default to 32 bit. Other browsers also default to 64 bit so far.
  Re: [firebreath-dev] Expose the C# Classes from JavaScript through Firebreath Framework There is no easy solution to do what you want to do. Sorry. Richard
  Re: [firebreath-dev] WiX compile fail on Win2008 64-bits Hi Richard, But build code successfully without running WiX. Why there are different in these two situations? How could I check the missing DLL dependency issue? Thanks. YoKo Richard Bateman (taxilian)於 2013年5月11日星期六UTC+8上午4時12分24秒寫道 ：
  Expose the C# Classes from JavaScript through Firebreath Framework Hi, I need to expose the complex C# classes in javascript through Firebreath Framework. Suppose take the example like: In C#, public Class ImageDraw { } public Class ImageProcessing { public void TestImage(ImageDraw imageDraw) {
  Re: [firebreath-dev] Not sure if Firebreath issue or Chrome issue Well, I don't know of any reason why Chrome wouldn't be able to give you a ICA model on a 10.7 box; AFAIK that should work. If you tell it that CG is a valid option, though, it could quite possibly give you that. I really don't have any idea why ICA wouldn't be avail, however. That's a bit disturbing.
  Re: [firebreath-dev] Not sure if Firebreath issue or Chrome issue Yes Richard. I generally run builds such that prep command gets called by default before building the slns or xcodeprojs. However, I didn't try a clean build as you mentioned. I will give it s hot too. But since you have confirmed the main point that I should expect a CG from Chrome, then that settles it.