How should I learn Ext JS 4.2? [closed] - extjs

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I've been assigned to a legacy project which runs on Ext JS 4.2. I know JavaScript but I'm totally unaware of Ext JS and I'm having trouble in understanding it. Can someone please guide me on how to learn Ext JS, what approach should be followed and the important topics to be covered? Or what sequence should be followed?

I have been using ExtJS (7.2.0) in a corporate project for six months, these are some tips I would have needed some time ago.
You should start from the official docs and examples given by Sencha:
guide --> the main topics are The Class Systems, MVC Application Architecture and Components, which are the basis of ExtJS;
examples --> I find the KitchenSink example very useful, since you can briefly overview all the components available in the system - you can also give a look to MVC examples, in order to see more complex architectures;
forum --> you can also check out the Sencha forum, which has many interesting topics (many more that you can find here on Stack Overflow).
Since you are using an older version of ExtJS, you will find many materials on the internet, because it was widely used several years ago, while now it is difficult to find updated sources.
You can check out Saki website or fiddle explorer sorting by created date ASC:

I used to be a trainer for Sencha, and I left the company in 2013 right around the time when ExtJS 4.2 was the main version.
The fastest way to get up to speed on the framework is to take a training class from Sencha. I haven't worked for Sencha for 8 years, and many of my colleagues (who I respected highly as trainers) aren't there any more, so this is not a plug for their services, but it's the fastest way. You will learn shortcuts that will take you much longer if you were to do it yourself. The framework is huge an complicated, and it's nice to get an overview of how it works from an experienced guide.
Before I was hired as a trainer, I took both the ExtJS and Sencha Touch classes that they had available, and the difference between the "before" and "after" in my understanding was huge. Yes, it's a week of your time, and yes, it's $2500, so your manager may not agree with my recommendation, but like I said, it's the fastest way to get up to speed.
If you do decide to take the class, spend some time with your legacy app and write down where you're getting stuck, and ask those questions in class. Part of the class value is that you can get some free light consulting for any issues you may be having.
The fact that you know Javascript is a big plus. I've had people in my classes who were new to Javascript, and that was another hurdle that they had to get over.
Good luck with your app!

Related

Is learning AngularJS necessary before learning Angular 4-6? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I want to pursue towards becoming a FULL stack developer before that I want to get my grip on Angular.
I already know about the differences between AngularJS and Angular, my question is,
Is it necessary to learn AngularJS before learning Angular 4-6?
If not, can I apply for any project/job that has a listing requirement of AngularJS?
Summary: Can I directly learn Angular 4-6 from scratch without AngularJS?
Also, please suggest regarding which version of Angular (2-6) should be choosed to learn from scratch.
no it is not necessary to know AngularJs to lear Angular4-6 but i recommend you to first take a look on typeScript because it is necessary before you get started with Angular4-6 you should start with Angular5 because it is latest and there is not much difference in Angular5 and Angular6 which is better for getting familiar with Angular
You may skip AngularJS, though understanding vanilla, ECMA javascript and typescript is at must before you start to learn any kind of JS framework.
Talking about which version to start learning, I'd rather started upon learning the latest version possible, then invested some time reviewing changelog afterwards.
While you understand that tech, the latest version will become stable and popular.
While they share many concepts, AngularJS and Angular are two completely independent frameworks. There is no need to know one before learning the other.
Angular is very different from AngularJS. Ultimate version of AngularJS has been released so it is in sunset phase of it's life now...
http://www.codelord.net/2018/02/04/angularjs-1-dot-7-the-ultimate-version/
Google say that in October 2017 the number of active Angular (that is,
2+) developers has surpassed that of AngularJS developers, which was
their cue all along to when they can start wrapping up 1.x.
Regarding the job - I think that future of the angularJS projects is migration to Angular/Vue/React so your Angular skills might be relevant. You may apply and let them decide.
I suggest to start learning from the most actual version which is 6 now

Should I learn more javascript to learn Angularjs? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I've been programming on and off for about 2 years now with python and C++, and a little bit of other languages like html, css, etc. I'm familiar with object oriented design and basic syntax of many languages. One that I've recently gotten into is javascript. About two months ago I heard about Angularjs and its capabilities. However, I've never done javascript at the time so I thought I'd give myself a few weeks to get familiar with javascript before I tackle Angularjs. A few weeks turned into 2 months and getting familiar is harder than I thought. However, I didn't want to stick to learning javascript forever, I wanted to move on the real goal and that is to learn Angularjs. So I started doing tutorials on Angularjs about a week ago. Now I'm stumped. It is very confusing to me. All the directives, MVC, controllers and such are so difficult for me to grasp. Experienced developers don't seem to have trouble picking up the framework, but I am so lost. I'm forcing myself to grind on it every single day until it makes sense but I'm rapidly loosing motivation because I don't understand most of it. Is this due to the fact that I still don't know enough javascript to grasp it? Will I have to learn more javascript to learn it? Frankly, I enjoyed javascript that's why I was able to keep doing it for 2 months. But my future for Angularjs is not looking very good and it has only been a week.
It would definitely help to understand vanilla JavaScript more as well as having a better idea of what is going on "behind the scenes" in a web app. If your knowledge is fuzzy and you don't understand vocabulary / concepts being used, you cannot assimilate new information about those concepts. Take your time, no need to rush. Read a book or some articles about MVC - get a good idea of what is happening all the way around. And don't limit yourself to Angular (great as it may be). Some light beginner reading
I would pick up some books on MVC. The more "big picture" understanding you have the easier it will be to implement in AngularJS. Check out Amazon for well reviewed books.

releasing a javascript library for the first time [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm almost finished working on a useful (at least, in my opinion) JavaScript plugin. Having seen and used many JavaScript packages, both freely licensed (JQuery, YUI, etc) and partly or fully commercially licensed I'm not sure what other factors dictate which license I should release my own under and how to support the plugin.
Some background information on my JavaScript plugin:
Similar audience and plugin size/impact to addthis.com, although slightly more niche. My plugin doesn't provide any analytics though.
Uses JQueryUI for user interface, can be expanded upon with there themeing components, etc.
No other similar tool out there (at least that has become popular).
Can be easily integrated in to a website.
Questions I have:
Should I launch a dedicated website for the plugin, or use something similar to Google Groups? Would a dedicated website bring more kudos perhaps?
Would a Creative Commons Non-Commercial license be a suitable license considering I'm a young developer and perhaps reputation building is more important than my bank managers happiness?
These are the 2 big questions that have been puzzling me for a while now, and I don't know anyone who has been in a similar situation :(
Thanks for any advice.
Considering you seem community, rather than cash driven .. the community will hold the key to what they find best, simplest and acceptable (and what works)
What do other plugin developers do? Take their lead. They set the convention and it determines how other people find your plugin. If a Firefox extension only had it's own site then I probably wouldn't find it.
What do others use? GPL? LGPL? What does jQuery use? Ask them why?
It might be worth using an online revision control tool like github or launchpad so people can contribute bug reports and help your development.
If I were you I would definitely use something like launchpad or google code.
You get integrated (community enabled):
source version control
bug tracking
...
for free.
Considering this library is aimed at other (web) developers a shiny website seems a lot less important then the convenient features above (in a known format).
And: congratulations on your first release, of course ;-)
About running site:
For me running dedicated website gives your product more professional look. Hosting on Google groups isn't good choice for all products: you can't build screenshots gallery, own blog, etc. You can build forum by youself if you need it.

Silverlight developer wants to gain some designer chops - where do I start? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I'd like to reskin a Silverlight app to be more visually compelling. Unfortunately, I went to school for computer science, not design, and I have trouble deciding if two colors even match. How do I get started? Let me add that time and money are both factors so pursuing a design degree isn't an option (though it might be ideal).
EDIT: I also need to learn how to implement good design, so any guidance on the toolsets (Blend or Illustrator?) would be helpful too.
Design is one of those things that is very difficult to teach. Only a small percentage of it can be taught. The rest must be learned through experience and practice. If you have an inclination toward art / expression, your learning curve will be much shorter. Here are some things to get you started:
Color Theory:
http://www.tigercolor.com/color-lab/color-theory/color-theory-intro.htm
http://www.colormatters.com/colortheory.html
Design Basics:
http://desktoppub.about.com/cs/graphicdesign/a/designbasics.htm
http://www.online.tusc.k12.al.us/tutorials/grdesign/grdesign.htm
Software:
http://www.adobe.com/products/illustrator/
http://www.adobe.com/products/photoshop/compare/
Software Tutorials:
http://www.adobe.com/designcenter/video_workshop/
Visit the Cooper site. The books listed there are well worth a read. "About Face" in particular belongs in the library of anyone required to do UI work.
If you're really only interested in making your app look nicer, going with one of the built-in themes from the latest Silverlight Toolkit is probably a smart choice.
Check out the links below.
Toolkit -Themes
Jesse Liberty Blog - Themes
EDIT:
I'm not much of a designer myself, but I know if I wanted some insight on the subject, I would start by going to the Silverlight Showcase page and seeing some of the things that can be done, and drawing inspiration from these apps.
Silverlight Showcase

DotNetNuke Pros and cons for community blogging site [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I'm evaluating DotNetNuke for a project in which an offshore team is going to be doing the development. In short, the application will be a community blogging platform with many similarities to stackoverflow except no questions, just posts. Posts may include an image or video, tags, use info, title, body, community vote (up or down) comments, hotness, and a few other details. They should be taggable, sortable, categorizeable (beyond what a single set of tags provide) In the future the site will carry forums, a calendar, and a couple of other features for which there are modules available for DotNetNuke. Additionally, this site will incorporate a user experience that will include a lot of custom skinning.
Thoughts?
Using a web application framework (such as DotNetNuke) has a ton of benefits to help you get up and running faster and do less work when creating custom functionality.
However, you have to realize that you're basically incorporating tons of code into your project that you may not be familiar with. No matter how good the code is and how easy the framework is to learn, there's still going to be a significant learning curve for you and your team.
Your decision making process (if you're still deciding whether or not to use DotNetNuke), should include (in addition to reading, talking and other general investigation):
Downloading the application from Codeplex and checking out the source.
Investigating the third party modules that are out there.
Downloading a free module or two that comes with source, and try to reverse engineer the creator's development process. How did she integrate with the framework, what features did she take advantage of, what was written from scratch?
One place where DotNetNuke (or any other framework with tons of extensions) available can really shine is taking existing extensions that are available and customize them. If you need to implement a given feature, check out the solutions in the third party extension community first. You can probably find one that gets you a good percentage of the way there and use it as a foundation for your feature.
For example, if you want a photo gallery on your site, you probably don't want to write it from scratch. There are three major photo galleries out there that sell the source code. The core gallery module is free, simple gallery is cheap, and the source for ultra media gallery is available for a reasonable amount compared to writing it yourself. Any of these could give you a good head start in implementing your features.

Resources