I'm posting this here because if I post it on the babel GitHub I get told it's not a bug and to start a post here. So here goes.
Since I started using Babel 7 a lot of issues in development are because of Babel issues. One day I installed a babel plugin and noticed a red warning and a link to a blog post about removing staging.
Yet nowhere is there a comprehensive guide on how to use babel without staging. Considering a lot of people will be jumping from babel 6 to babel 7 I feel it's kind of important. The decision to remove staging from what I read is to define the transforms and plugins explicitly.
I don't knock that decision, but how are people who relied on staging meant to make the switch?
I've been wandering about babel 7 for a few weeks now and end up falling into problems that cause painful hours of Googling because most of the results are for previous babel versions.
Today I got a warning about decoratorBeforeExport not being set. So I headed to the docs: https://babeljs.io/docs/en/next/babel-plugin-proposal-decorators
Nowhere on that page does it say decoratorBeforeExport is required.
A lot of tutorials and guides are on older versions that will not be compatible with 7 and as a seasoned developer - however stupid I may be - I struggled. And if I struggled you can bet your bottom dollar many others will.
I hope I'm wrong and there already exists information on this. But I can't find it.
Related
I need some of your help.
I searched everywhere on the internet, but I could not find how to create a plugin for Gaim, the predecessor of Pidgin.
I do NOT want to create a Pidgin plugin. I want to create a Gaim plugin, but since Gaim is very old, well, it is hard to find documentation for it.
(PS : If you know how to write a plugin for Gaim, please note I want to make one for Windows - not Linux.)
(PPS : I'm french. Sorry for my bad English.)
You're going to run into a number of issues here...
First off, Gaim hasn't existed for 15 years, and of course we (the Pidgin core team many of who got involved during the Gaim days) aren't going to support it for that reason.
Secondly, building on windows has always been a pain for us as we had to carry all of the dependencies. I imagine most of the links that you might find are all long dead because of the 15 years that have passed since that. That said you might be able to get away with using our win32-dev directory from https://data.imfreedom.org/pidgin/win32-dev.7z but of course that's completely untested and that directory is used to build the Pidgin 2.x.y releases.
Finally, as you've found out, most of the documentation from Gaim has been gone for a very long time. We did set up https://gaim.pidgin.im as a joke which was the last copy of the site we had before the rename, but there's not much there when it comes to development documentation. So your best bet is to look at existing plugins. I still have the source code for guifications1 available at https://keep.imfreedom.org/grim/guifications1/file/default.
Very little has changed in a while for BIRT. Since the project seems still heavily used, it would be interesting to know if there are future plans and if so, what is entailed in those plans. Subsequently, based on the development status: Is BIRT still a safe platform to base development on or is it expected to just be conserved in the current state such that occuring bugs probably won't get fixed?
We decided to use BIRT instead of Jasper 8 years ago.
We are still using 4.2.1 for development and 4.3.0 for production runtime.
I reported several bugs since then and only very few of them got fixed.
Furthermore, I developed some patches to enhance the word emitter output - with no reaction from any one at all.
I also developed a patch to allow kind of a vertical tab (to place something at a fix y position on the page (but not in the page footer). With my previous experience of the community, I did not publish that one.
I can say that while the source code is quite easy to read, it is nevertheless almost impossible to understand what is actually going on, because the functions are extremely deeply nested.
My conclusion with 8 years experience of using BIRT for production:
PROS:
BIRT is very powerful and flexible, you can achieve some very cool results.
The quality of the resulting PDFs.
There are only very few things I miss and cannot work around.
The runtime engine is very stable and fast enough, very few problems.
The community is helpful.
CONS:
From an open-source perspective, it is one of the weakest projects I know of.
New versions tend to introduce more bugs than they fix.
Bugs, ideas and patches from the community seem to be ignored most of the time.
Lack of internal code quality and documentation.
Update Dec 2021:
BIRT is back again!
The open source project is quite busy (see answer by Alexander Fedorov) and every help is welcome.
It looks like there will be a new release soon.
Until then, building BIRT yourself (with Eclipse 2021-09 and Java 11) has become quite easy thanks to the common effort of the community.
Metadata and information about the health of an Eclipse project can be found on projects.eclipse.org:
The Birt project is still alive, but not as active as before:
there has been only one release per year since 2016 and
in the last three months there have been more than 20 commits from 11 contributors.
Like all open source projects, the success of the project depends on participation. Therefore, I encourage everybody to report bugs and propose changes to Birt and other open source projects.
Update: Good news, Eclipse Birt has been rebooted. It is under active development again, there have been more than 100 commits in two and a half months and the release 4.9.0 is scheduled for March 16, 2022.
The Eclipse BIRT project has been restarted recently, and we are working to prepare Eclipse BIRT 4.9 release.
Contributors are very welcome. Here is the brief instruction regarding steps how to join this effort: https://eclipse.github.io/birt-website/docs/community
Latest versions of BIRT are not available in maven.
I've been going nowhere but in circles trying to understand the odd relationships between and varying levels of "standalone-ness" of these tools.
I've been using Aptana Studio on OSX for about 4 years and been happy with it, however my recent update to 3.6 blew up so many things I ended up rolling back to 3.4 just so I could work.
For better or worse, I do like Aptana, but I'm not bound to it and am now very frustrated with the latest version, specifically that all the python stuff went haywire. Searching for help is painful, as threads and advice are many years old.
So, in way of questions:
can anyone explain the relationship between Eclipse, Aptana, PyDev, and LiClipse? And more importantly:
a recommendation that meets the following criteria
What I need/want is:
something free and open source
with a current and active community
easily themeable with dark colors so I'm not staring at the sun 8 hours a day
tight python features (pep, pylint, ability to jump to references with a keypress, etc)
tight html/css/javascript features
Like I said, I do like Aptana, just frustrated in the apparent lack of a current community and how it seems to be falling apart.
Well, I'm not sure this is a good question for stackoverflow... anyways, I'll try to explain how it goes:
Aptana Studio 3 is an IDE which is currently supported by Appcelerator. Their main focus is currently on supporting the Appcelerator mobile platform (actually that's Titanium Studio, but Aptana Studio 3 is the basis for it -- the languages they aim for are html/css/javascript, which is what's needed for Titanium)... Although they do integrate a pretty old version of PyDev too (as PyDev requires a newer java whereas they're still on an older version of Java, so, I guess it's currently hard for them to keep it up to date).
Back in the day, they supported the development of PyDev, but decided to stop that support some time ago -- there's a bit more history at: http://pydev.blogspot.com.br/2013/03/keeping-pydev-alive-through-crowdfunding.html.
After that, LiClipse (http://www.liclipse.com/) was created out of my frustration to support dark themes and have support for more languages (it was a crowdfunded project -- it should've been an open source project, but didn't reach its goals for that, so, in the end it's closed source, and its revenue is a part of what keeps the PyDev development going on).
And at last, Eclipse is the basis for both platforms -- so, external plugins should integrate nicely into any of those.
Now, on the recommendation front:
LiClipse should meet your dark/python/html/css/javascript issues (its focus on the editors front is on being dark-themed/lightweight and easy to add support for new languages), but it's not completely open source (some parts of it have been made open source though: http://www.liclipse.com/text).
Aptana Studio 3 should still work and give support for the dark/python/html/css/javascript too, but given that they have to convert some things from the PyDev Java to its own version, Python support is always a bit outdated (as for the current community/support, I can't really comment, but I guess you should be able to report problems to them to try to solve the issues you have).
And the other choice (which may be a bit more work to configure) would be using a bare Eclipse and installing PyDev and separate plugins for html/css/javascript (it seems there are multiple available, but I can't really comment on any of those).
While doing some analysis on the usage details for the SquishIt framework, I came across a link as mentioned below:
https://danielsaidi.wordpress.com/tag/squishit/
which describes that SquishIt is having some problems with getting to work with JavaScript closures.
I am currently using the latest version :0.9.3.0 of SquishIt.Mvc. Can anyone help me to know whether this version has still the issues while working with JavaScript closures.
I am not aware of any issues at this time (was not aware of any in 2010 either however). It seems like any issues with closures are probably really issues with the minification library used, or files incorrectly terminated. At some point in the last couple years I think we did start adding semicolons between concatenated files if not present to deal with the latter. If you do find any I would love to hear about them.
This chart works fine in Google charts, but when rendered in Eastwood, it doesn't use the 2nd provided color, rather it applies the first color to both bars in the chart.
http://chart.apis.google.com/chart?cht=bvg&chs=150x150&chd=t:18,81&chco=FFF000|00FFFF&chxt=x,y&chl=Bar1|Bar2&chtt=Chart
Any suggestions as to why this could be? Unfortunately it looks like Eastwood is somewhat abandoned.
Confirmed in my 1.1.0 Eastwood installation. It should be noted that the author doesn't have time to do releases anymore, but he's given commit access to others who are patching with bugs regularly.
You can get the latest and greatest with:
svn co https://eastwood.svn.sourceforge.net/svnroot/eastwood eastwood
Unfortunately, the problem is still present in the trunk, and they also broke backward compatibility with Google Charts API (graphs just don't look the same; they tried to add some colorization effects).
I tried to dig through the Eastwood trunk to see what was going wrong, but the code is a complete mess of spaghetti. I don't know enough about Tomcat servlets to do much more debugging right now. Sorry I couldn't be more helpful.