Is jWYSIWYG editor too buggy for production use? - javascript

After reading the comments on this site:
http://www.webresourcesdepot.com/jwysiwyg-jquery-inline-content-editor-plugin/
There is a bit of consensus that jWYSIWYG editor is too buggy (especially in the last few recent comments). Has anyone had experience with it in a large production site?
I haven't run a huge sample of markup through it yet, but so far it has seemed to do the job fine.

I have been using jwysiwyg (https://github.com/akzhan/jwysiwyg) for about 4 months now on several production sites and I have to say that it is the best lightweight wysiwyg editor that I have used. It is small, fast, and reliable. I strongly recommend it for anyone that doesn't need a full-featured editor. If you need to work with complex source code and html markup then this may not be for you, but for business-level users it works very well.
I am guessing that the original question and all comments until here are out-dated. This is a great plugin.

are u tried to find some other place where this editor can be located? for example: http://github.com/akzhan/jwysiwyg/downloads ? There u can find v. 0.9 released few days ago

This answer may no longer reflect the current state of the project.
Checkout out the current version on https://github.com/akzhan/jwysiwyg and decide yourself.
I don't know the project but I conclude: Don't use it (at least at the moment)
the google code page jwysiwyg contains no documentation
the download also doesn't contain any
there are 91 open issues in the tracker (which for such a small project isn't a good indicator)
last commit (r33) was on the 21. September 2009
the second-last commit (r32) was on 21. April 2009
so no frequent updates to codebase either
no new download file (current is jwysiwyg-0.5.zip which dates from January 2009), although he made 3 commits after publishing v0.5 of which:
2 contain fixes for issues
1 restructures directory layout and adds a minimal example to the codebase

jwysiwyg has grown year-to-year development activity and community.
It hosted on GitHub more than1 year, so feel free to use, fork, patch and do pull request.

Related

Visual Studio 2015 CE Javascript editor not recognizing '(?' in regex

I'm looking for your help because I'm having a weird issue with the Visual Studio 2015 editor. I have a javascript file that contains a regular expression that uses a lookbehind, something like this:
var regexStr = /(?<=[0-9a-zA-Z]+)(\/{2,})(?=[0-9a-zA-Z]+)/;
For some reason, the question mark is "breaking" the syntax and the code editor shows it as an error, although the regex is working as expected.
Do you guys know if the '(?' is defined as a special char in the Visual Studio 2015 editor?
Greetings fellow programmers!
First thing I would say is that Visual Studio 2015 is a sub-optimal tool for JavaScript development. There are much better tools for web development that are available for free. This could potentially be seen as opinion based, but developers vote with their feet when it comes to tooling and what makes their workflow easier and faster, and very few people are picking VS 2015 for JS development in 2020. So I have to ask, is there a reason you are locked into using particular piece of software and version for JavaScript? Are you open to using a different tool? If so, comment below and I will add a list of choices for editors and IDE's that are more popular choices and that will most likely make your life as a developer easier.
Assuming though that you want to continue using VS 2015, regardless of its myriad flaws, and just want this particular thing solved, I think that what you are seeing may be the result of updated ECMAScript/JavaScript syntax leaving VS 2015 in the dust. It could also be that this was always just a bug. I first suggest ensuring that you have updated the base application as much as VS 2015 will allow you to. Are you using a pro or community version? Even if you stuck with Visual Studio, you could still get a more recent year's version, and if you are already using the community version that update would be free. Once you are sure you have updated the software as much as possible, I would suggest looking for an extension that could help you with this particular issue.
You can search the Visual Studio Extension Marketplace yourself, and I would look for one that offers things like "JavaScript syntax highlighting" or "updated JavaScript grammar".
Here is an extension I just found that may help you as well:
Regex Editor - "IntelliSense, syntax coloring, in-place testing and more for your regular expressions, right inside the editor!"

Semver is too difficult or what’s going on?

I noticed that in JavaScript world something changed over time. Previously backend and frontend used semver approach when it comes to version a library or app. Now, in JS world some and I see more and more libraries or frameworks follow the approach to release major version 2 or even more times per year. Let’s take Angular, Ionic for example. Some of my ex or just colleagues also are using the approach.
Why is that? I am asking this as I am a backend developer but I am about to release a JS - powered library and I am a bit confused how to version this.
They release much more frequently major versions precisely to comply with server requirements: they gradually introduce some breaking changes (even if most of the time they are small), therefore release with a new major version.
In the case of Angular, as you notice they plan to release a new major version about every 6 months. The idea is to keep freedom to improve the library without being constantly stuck with full backwards compatibility requirement.

Cordova/Phonegap OpenEars speech recognition

I am trying including the OpenEars plugin into phonegap/cordova using this plugin https://github.com/karljacuncha/OpenEarsPlugin
I followed the Readme but i ended up with an error of missing files, all these files are not found :(
Any help/suggestion on how to integrate the library?
thank you any advice appreciated!
As already mentioned on a comment, new, non-backwards compatible version (2.0) of OpenEars was released on 5th of December in 2014. This of course prevents it from working with old code such as the plugin in this case.
Basically there would be two options to get it working:
Use older version of OpenEars (last one was 1.7.1) but that doesn't seem to be possible as I wasn't able to download it from anywhere after extensive search.
Fix the code to work on newest OpenEars. It shouldn't be that hard and the code of plugin is only ~400 lines of code. Most of the changes are quite straightforward as described in the upgrade guide. Feel free to fork the project in GitHub or try to contact the original author of that plugin to make the fixes necessary.

MS Dynamics CRM 2012: Script Editor Enhancements

I have been trying to find some more information about the next Microsoft Dynamics CRM product (2012 / 6). Mainly I am interested in any enhancements that will be made to the scripting editor.
There was great improvements between version 4 and 5 (2011), the most welcome for me being the ability to share script functions across form/field events.
What I really miss though is the complete lack of formatting in the editors. Yes, it would be great to have intellisense and the likes, but I would be happy just to settle for a better formatting function (auto-tab) and some highlighting for better readability.
Does anybody have any information on where Microsoft is going in this respect? I am happy to do some reading if anybody has a good link to share.
Maybe there is a 3rd party tool that has good integration? I would be interested in taking a look into some of them if they exist, or somebody can recommend through experience.
Looking forward to hearing other peoples opinions on this one.
Thanks
I use a modified version of Tanguy's JavaScript Web Resource Manager for Microsoft Dynamics CRM 2011 project to store, edit, and publish my JS files, and I use Patrick Verbeeten's XRM intellisense js for intellisense. It's mostly seamless/painless, with the biggest bottleneck in deployment speed being the time it takes for the js files to publish. Other than that, no real complaints here.
The built-in script editor isn't scheduled for any enhancements that I know of right now. However, the SDK includes the Developer Toolkit, which makes working with CRM in Visual Studio a heck of a lot easier. Have a look here for documentation: http://msdn.microsoft.com/en-us/library/hh372957.aspx
~Matt Cooper, program manager, Dynamics CRM

Status of jQuery TestSwarm?

I hope You are more 'on the ball' than I am.
I remember getting news on the Mozilla labs TestSwarm (now jQuery TestSwarm) some time ago. It had active users then, but it was not more than 10 per a single browser+OS configuration.
I went there today expecting it to be far better and it turns out that there are NO active testing environments. Moreover, when I tried to view the http://testswarm.com service:
Invalid query: Lock wait timeout exceeded; try restarting transaction` once in every two or three queries.
Is this project dead? Are there any similiar community projects for JS testing that I could not only take part in, but use for my code? Or do I have to test JS myself?
The following website is still live.
http://swarm.jquery.org/
(The link on that site is old at the moment I'm writing this.)
And if you want the code:
https://github.com/jquery/testswarm
At FOWA Miami in February (2010) I asked John Resig about it and his answer was like this (not exact words but that's what I remember of it): Still very much high in his plans since the next steps were to get jQuery Core support on mobile really solid and part of achieving this goal will be the need to automate testing on various platforms as much as possible which is what test swarm is about.
The project is still alive. John last committed around April 13, 2011. The unit tests for jQuery core and QUnit both make use of the swarm and are updated at regular intervals.
It appears Microsoft either forked the code or recreated the project.
Check out BrowserSwarm
Another recent alternative seems to be CodeSwarm.

Categories