What are the differences between SproutCore 1.x and 2.0? - javascript-framework

If you look at the SproutCore framework right now, there are 2 versions to go with: A 1.7 beta and a 2.0 beta. The docs and guides seem to be different as they are served from different domains, but sometimes you just don't know if a tutorial or even the copy texts on sproutcore.com are referring to version 1.x or 2.
It's a bit confusing and so I am asking about the difference(s) of both. Is version 2 even comparable to the previous one? It seems to have a totally different approach.
Would be good to know, so someone could easily decide which version fits best for a certain usecase.

You are correct. SC1 and SC2 are very different.
Here's a good video I found that provides the background and reasoning behind SC2. http://vimeo.com/25210161
The recommendation for the SC team on the blog:
Remember: SproutCore 1.6 is still the best way to write desktop-style
apps, and will continue to be maintained and developed by the core
team and contributors. Right now, SproutCore 2.0 is the best choice
only if you are building web-style apps, or want to augment an
existing application.
Here's my own experience with SC1 v SC2: http://blog.chililog.org/2011/10/14/sproutcore-v1-vs-v2/
IMHO, use SC1 if you plan to write a native style ipad or iphone app. It has views and transitions that you can use "out of the box".
Use SC2 if you plan to write a web style app like the twitter UI.
Hope this helps.

Related

Yii2 ... Yii3 ... or Laravel?

I’ve been using Yii since version 1 … I’ve done lots of projects (i’d say about 50). I know Yii.
But I am being disappointed.
Yii was glorious and wonderful in 2014-2017, but after 2018 I’m not seeing same activity.
Forums are useless, old, inactive … there’s not more Yii2 extensions or modules. Everything is “old”, unfinished, discontinued …
Now I’m facing changes in my life as coder, and I was wondering whether to wait for Yii3 (because it will be a revolution), or to switch to Laravel.
Sincerely… what do you think if this “Yii environment” situation ?
Please, I would like comments from people who really know both environments, not only Laravel lovers.
Can you anyone tell me a WORKING and UPDATED extension
for social networks that works PERFECTLY ?
yii2-usuario was the best … WAS … linkedin works sometimes, facebook are not updated, and there’s no newer social since 2016
can you tell me other for datatables ?
nullref has awful support since it’s everything rewritten in Javascript so you can’t access properly relations and subrelations of models
for payments (stripe compatible for example) ?
for…
and so on…
These just last 3 examples has beautiful, crazy updated and reviewed plugins in Laravel, for example. Or even in NodeJS.
2amigos and kartiv were two perfect partners for Yii2 core … but they are not being continued … so they are pretty old
Anytime I search for any “extension” in github, all projects are 4 years ago (the newest!).
By the way … Yii3 started in 2019 … 60% done so far … and can’t be used yet for real working projects in live. So … waiting 2 years more with this so empty market of extensions ?
Let’s be clear, my problem with Yii is NOT the core (Thank you Sam and others for your infinite work!), but the community, extensions made (and/or updated) and “movement” of the ecosystem.
I know I can code myself (i’ve done lots of extensions), but it’s easy as a coder when you have good repositories with pretty new extensions and solutions, and a very active community behind. This forum has about 150 posts this year. Laravel (for example, 150 posts represents just the last 4 days). Have you notice tons of posts here with 0 replies ?
Also, Yii coders was easy to find in 2015 … now it’s 1 out of 100 maybe.
Let’s assume Yii environment has decreased drastically in the last 4 years.
I would suggest to move to laravel.
As yii and laravel uses almost similar behavior on basic level
MVC, Based on symphony, ORM
I honestly think you'll easily grap what laravel is offering.
Plus, laravel is upgrading day by day.
The answer to your question lies in your question .
Big community, Wonderful documentation, Enjoyable coding, Lot of feature and package, Popularity and ... all of them can describe Laravel.
Do not doubt and take a deep dive.
If you worked with Yii2, you should definitely use Yii3.
I'm using it for minor projects and I'm learning a lot.
The advantages are the same as always
Very fast (surely faster than Laravel)
Very complete
Very customizable
Very standard and modern (A bit difficult to start to understand it)
I recommend you to start with the demo application (it's a blog) or the base application (blank)
What's with the packages?
That on Yii2 you can only use Yii2 - compatible packages? take any package and use it, use the dependency injection container.
If we talk about the fact that the framework is outdated, then yes there is such ...
I myself wrote more than a dozen projects on Yii2.
I didn't really like Larevel, my opinion.
But the symphony, on the contrary, I was very pleased with.

Build new joomla Component in Legacy or Native classes?

I am starting to develop my very first joomla 3 component.
Should I choose legacy or native classes and why?
What about support in the future?
Joomla core components use Legacy classes. Are they gonna be removed in the future?
Thanks!
If you are starting Joomla! development right now, my opinion is to start using the legacy classes. From my knowledge, the legacy support will be in the next major release (3.5) as well in the current STS releases (3.1, 3.2).
What is going to happen in the future is rather a thing that will be discussed, software is evolving, so is Joomla.
You should learn using the legacy classes because:
you will find most of the documentation / books / support about them
core components are build using them (and understanding how core components work, is a key to your success in developing extensions).
Native classes:
are rather poorly documented
not so many examples (for example just the Joomla installer is using them)
not so many use them, so getting support might be rather difficult
it good to have a look at them one you have more experience with Joomla, so that you can understand the benefits
they don't have the powerful JModel that the legacy classes have, so building CRUD functionality will require more code to write and mentain
there are no clear rules on how the code should be organised, so this for a beginner may be confusing, not having a pattern to rely on.
Hope this helps.

Community Engine v. Social Stream?

Newb here learning rails... any advice/comparison of community engine v. social stream? I'll be writing a dating site, so especially if either lends themselves to that development I'd appreciate the advice.
I have tried CommunityEngine in the old days. Currently to use it with rails3, you will have to use a specific branch mainly updated by the community to make it stable. i'm not sure if that rails3 branch is production ready yet.
I don't know community engine, but have been looking at social stream and it looks very well put together.
We upgraded social stream to a mobile platform by exposing api end points - it took a couple of months. We built separate controllers for each call rather than modifying the core classes. The platform is now flexible enough to cater for any use case and we can hook in to updates on the trunk. It's really well thought architecture and has had iterations of refactoring. (I think the webviews / javascript is a bit of a mess though)
I suggest you have a look at this - it took my tech lead a couple of weeks to be comfortable with this.
https://github.com/ging/social_stream/wiki/Social-Stream-Base-database-schema
WRT communityengine - I abandoned this over 4 years ago.
https://github.com/jdp-global/communityengine/commit/31f9b267706157a63bfc103a290bd6e3d874066a
Any platform you choose needs to have a focus on APIs / web services.

Capuccino alternative with a comparable looking UI?

I'm looking for a set of Javascript based UI components for a web app I'm building and have found that many of the best looking web apps were built with the Capuccino framework; see http://www.getflow.com/, http://www.picsengine.com/home/ and http://timetableapp.com/ for examples.
However, I'm not a Cocoa developer and have no interest in learning Objective-J. Ideally, I'd find a set of components that provide the visual end result of Capuccino apps without the underlying weight of the framework.
I have seen the Aristo jQuery UI them (http://taitems.tumblr.com/post/482577430/introducing-aristo-a-jquery-ui-theme), but jQuery UI just doesn't seem to have the depth of components available in Capuccino.
I realize this may be a long shot, but I figured it can't hurt to ask. :)
Thanks.
As another option, there is jQuery UI: nice if you are already familiar with jQuery, with the plus side of not being too heavyweight, but may not have all the components you need pre-defined. A nice thing is that it encourages to write the HTML in a way that degrades gracefully when your application in older browsers.
Maybe sproutcore is an alternative for you, although it requires you to hand-code everything in javascript from scratch. It offers most basic components and is easily adjustable to your personal design goals. Sproutcore is used in Apples Mobile Me and in some other big projects.
Another possibility might by vaadin which offers a rich set of prebuild controls and is based on Googles GWT javascript compiler. But it only makes sense if you are developing in a java environment.

Which are the J2ME MVC frameworks?

I have to do a quite big project in J2ME for school.
I didn't used 'till now J2ME, so are there J2ME MVC frameworks
for which I can find books or at least very good online tutorials?
MVC is what I'm looking for because we have to do unit testing and
I'm familiar with MVC from ASP.Net MVC, Rails and Grails.
So, any good framework to use with this project?
We are developing this project for Blackberry cells.
With Java you don't really need a framework, creating MVC-based apps is just about using the principles correctly, so having controllers dictating the response to any action and so on. I'd think about using Observers to help by having your views observe your models and controllers observe your views (to get events and so on.) Unit-testing this then becomes quite simple.
If only, the fact is that every handset is very different - its extremely difficult to build an app that spans all the major J2ME-capable handsets that looks half way decent by following the basic principles. Which is why we end up doing things like using sprite based fonts (ugh). I don't think I've ever worked a mobile project using J2ME where we've managed to stick to just the standard J2ME (and, we try very hard). Even things that should be standard, like reading a JSON feed from a server, persistent storage or even really simple things like sprite rotation is really not very standard at all (yes, I'm looking at you RIM). And, then throw a requirement for Android into the mix and you're done.
I've used Polish, and its really very good. Commercial license is not cheap (but worth it), but for a school project its free. Flash (cough) is also a good alternative too. These days, personally, I find my projects need to span iPhone (Objective-C), Android (Java), Nokia (J2ME) and Blackberry (pseudo-J2ME) and it gets real tricky to not use a commercial framework (or roll your own, if you've the time and inclination). I'm open to ideas for frameworks that span all those platforms?
I'm not sure anything like this exist, as mentioned by previous poster, you just follow the principles of the pattern. However, look at J2ME Polish, it's a very nice framework which makes your life with mobile java much easier. Particularly strong features they offer is the usage of CSS for displays - this gives you pretty good "V" part in MVC pattern.

Resources