I have to document main configuration related features that are present in wildfly 10 but not in 8.2 (as we are moving from 8.2 to 10).
I am trying to find the feature documentation but all I find is admin and developer guide. To find the difference between two versions, I have to compare guides of both of these two version, which may take some time.
Can any body suggest me some faster way to do this.
Many Thanks in advance.
Rahul
There are likely some blog posts on some highlights at wildfly.org. You could also run a JIRA release notes report. Other than that it just depends on what kinds of differences you're looking for.
Related
I Have Created A Beautiful Design Of My App Using Adobe XD. But Now I Want To Convert That Design Into App That Looks Exact The Same. How do I go from an Adobe XD prototype to a working app?
Your question sounds a bit like your searching for a way to convert your design into an app without dealing with the code a lot (in a kind of WYSIWYG-fashion similar to what Adobe Muse does for websites). My answer assumes that that's what you're asking. If not, please feel free to ignore my answer...
Adobe XD is only a design app. This means, that it doesn't really have code generation features. Having said that, there are now a few plugins that can support you in writing this code (e.g. Lightning Storm CC – to my knowledge – supports Android UI export).
Also, as Ash Ryan Arnwine mentioned before, design specs support you when developing the UI (you'll need to code it yourself, though).
All in all, there is no way around either knowing how to code or hiring a developer when creating an Android app. Therefore, these tools can only support you in development, not replace the technical aspect of developing an app. The answer to your question, therefore, is that there, unfortunately (or fortunately – depending on how you look at it?) isn't any way to quickly "convert" a prototype (which really is nothing more than a prototype) into a real app other than coding it yourself (possibly with the assistance of the tools mentioned by Ash Ryan Arnwine and me).
Since there are many unique workflows out there for designers and developers, there's no single answer to your question.
Here are a few things worth looking into:
Adobe XD design specs: View design specs published from Adobe XD, which enable you to inspect and comment on the flows, measurements, and styles.
Adobe XD for Jira Cloud: Associate XD prototypes and design specs with Jira issues to keep projects organized and provide developers with everything they need to know right within Jira.
Adobe XD plugins: Plugins are coming soon to XD. A couple of common use cases for plugins is designer-developer and design-to-code workflows. If the plugin you want to see isn't when plugins launch, the APIs will be open for anyone to build it.
The answer depends on your response to this question: Are you ready to spend money to make this happen? if so, there are two Adobe plugins that try to convert your prototype(anyway, you'll need to code and make efforts in Android Studio). Those plugins are:
Lightning Storm
Yotako
I am new to stackoverflow, so please forgive me.
I am trying to create a student timetable for a student information system as part of a University project that will display the times, dates, details of modules as well as the location of the events.
I have done endless research and I haven't found a solution to my problem. I know there are the likes of the DHTMLX scheduler and Daypilot scheduler (Which is exactly the sort of thing I have been looking for) but these do not really suit for a number of reasons:
Both only offer 30 day trials and I would need it for slightly longer than that as the project is needed right up to July
I have tried to follow the tutorials for the DayPilot scheduler lite version but it just does not seem to load for me no matter what I try.
I have looked everywhere but nothing seems to be working for me and that's why I would love some feedback/advice if there are any other methods that I should explore.
I am using MVC 4 in Visual Studio 2012.
Thanking you in advance :)
You can try JavaScript DHTMLX Scheduler. It is free under GPL license, which should be ok for a university project. You'll need to manually implement loading and saving of calendar data (which is done by helpers in ASP.NET version of the component), although it should be not that difficult. You can check this tutorial, it's quite outdated but still may be useful
http://www.dhtmlx.com/blog/dhtmlxscheduler-for-net-mvc/
Note that starting from the latest version the GPL package does not include several modes, such as Timeline or Units(resources) views
However, if you need them you can grab the previus version from a GitHub https://github.com/DHTMLX/scheduler/tree/v4.2.0
We have found the limitations of Saxon-HE (see table) at the point of using Extensibility using reflexion and EXSLT extension function.
We are evaluating to purchase few licenses for the servers and development team members and we are short of time to evaluate every tool, considering that purchasing and distributing the license will also consume our time.
Apparently there is a previous version of Saxon called Saxon-B that saxonica is not longer maintaining but it claims to support Extensibility using reflexion and according to this Q&A supports EXSLT too.
My question is, could we stick with Saxon-B (an open-source solution) for those features mentioned or should we purchase those licenses?
Finally I am replying myself.
We have given a try to Saxon-B during last few days and it works perfectly for the needs we have (mentioned in the question). We have not found any minor/major bug so far.
Thanks Saxonica team for keeping available as open-source the Saxon-B version.
Edit: Saxon-B is no longer compatible with Java 8 and above.
We are currently running rails 2.1.
My main motivation for the upgrade is the fear that gems/plugins will get rarer/unavailable/unsupported day by day for our version (,and the excitement of the latest technology).
I understand there are many-many improvements that come with rails3, but probably what my manager would want to listen is the advantages that he'd get, in terms of the business.
Ours is a Saas application, load on the app is not very high, but the demand for reliability is more.
Edit :
Looks like my inclination towards the upgrade needs rethinking, so answers to "should I upgrade" are welcome.
my original question also needs answers - how to describe the business advantages of an upgrade from rails2.1 -> rails3.
The app is under active development/enhancements.
The longer you go without upgrading, the harder it will be when the time comes. Sooner or later, any actively maintained project is going to have to move up to the more recent versions, and the more versions you have to skip along the way, the harder and more risky it will be. If you upgrade regularly, it becomes a fairly simple maintenance task.
I'm afraid that going from 2.1 -> 3.0 is going to be a fairly rough one unless your app is pretty simple. You might try going from 2.1 -> 2.3.9 as a first step. However, doing it now, instead of when it's 2.1 -> 3.1 will save you heartache. Right now, everyone is focused on helping people upgrade. A year from now, there will be fewer fresh resources available and fewer people going out of their way to help people upgrade.
If your application is under development and is likely to have more and more features over the months to come then you should migrate to the newer and actively supported version.
If your application only needs bug fixes occasionally then you should stick to the current version.
Upgrade!
I'd say that you should definitely upgrade, for the reasons you stated, but don't rush it. If you have a well defined test suite everything should be ok.
Most of core Rails 2.x code works with Rails 3, you can just read the deprecation warnings and fix things one by one. You can also use the official Rails Upgrade plugin to automate the bulk of the editing.
As for the gems and plugins you use, you can check their compatibility at railsplugins.org and decide if it's worth the trouble if any.
And the elevator pitch for the boss: You said the app is under development, so upgrading later when you absolutely have to means that you have to first deal with all the issues arising under 2.x and then deal with the upgrade issues plus 3.0 issues of a much bigger app. Upgrading now saves time by saving you the trouble of having to deal with 2.x issues. And you also avoid some of the upgrade issues since your app is probably much leaner now than the heavyweight it will be when you decide to upgrade later.
Since reliability is high on priority, you should probably not upgrade unless it's absolutely required. Some unforeseen issue is bound to come up.
To address the excitement of the latest technology, you can always try out new plugins and Rails 3 offline.
Businesses should not be sandboxes of developers. Nor should development be Resume Driven.
But that's just my opinion. :)
There are several reasons to upgrade, all of which are under the assumption that the app is and will continue to be under active development.
Integration with 3rd party software- for example, rails 1 did not have ActiveSupport. An app remaining on rails1 all through say rails 2 might want to integrate with a 3rd party API that primarily supports restful json. At that point, the sensibile path is to upgrade, but since you delayed it so long your risk of having lots of issues in the upgrade will be significantly greater than if you upgraded early.
Using plugins that will help with new features - if you want to add a new feature and someone has scratched your itch already, then if you are stuck on an older version of rails you will have to write that code yourself. The more code you have to write yourself, the greater the likelyhood of bugs and the more maintaince the code will likely require, depending on the function.
Fixing bugs in older verisons of the plugins/gems - if you encounter a bug in rails, or a plugin, or a gem, or some sort of other integration issue, it might be fixed in a later version, but what that depends on a newer version of rails. This will make your path to fixing said bug or implementing said enhancement greater the longer you wait to upgrade.
Searching online, I see lots of people asking for features to have multiple levels of sub-tasks, and proper sub-task functionality (like FogBugz). But I don't know if it's planned in future versions, or if plugins exist to provide this functionality.
Does anyone know?
we're working on a plug-in for multi-level subtasks. See details and follow us at http://h4j.almworks.com
As for current solutions, you may use links as a very limited workaround. There are also some hacks to allow creation of sub-sub-tasks, see comments to http://jira.atlassian.com/browse/JRA-4446
Update: the add-on has been released in 2011 and went far beyond just multiple hierarchy levels. Currently it's at version 4 and it's one of the most popular add-ons for JIRA. See https://marketplace.atlassian.com/plugins/com.almworks.jira.structure/server/overview