We're currently developing big project using ExtJs 4.0 as a frontend framework. Backend is Entity Framework + SQL Server but it's not important to the matter of this question (I hope).
I'm looking to add mobile version of our application using Sencha Touch. I've read couple articles stating that somewhat 40-50% code can be reused. Does anybody have any real experience doing so?
If I'm using ExtJs MVC architecture will I reuse only models / stores classes? Or is there any way to also reuse for example some of business logic inside controllers?
What will be actually project organization and folders structure? Do I need to keep two different trees or is everything can be combined under one roof and only while building different projects I would get different app-all.js files?
There's some notes here:
Combining Sencha Touch and ExtJS in your Project
http://lanyrd.com/2012/sourcedevcon/srryz/
video no doubt coming soon, senchaworld.com is the place for vids.
Related
Not sure it's the right question for this forum, but I couldn't find another place for it.
Our design team built their design system based on fluent ui libraries as described here. They downloaded the design from here.
Unfortunately, our engineering team is using Angular, so we naturally reached for the option of web component but found out to our surprise that the library is completely different - different set of components, abilities, and of course - a completely different design.
I thought that all fluentui platforms are supposed to be an implementation / interface of the same design. Why is this not the case? What am I missing?
Is there a way we can use the design described in here in Angular? (Except actually using the react library inside my Angular project).
Thanks for helping and very sorry if this question is inappropriate for this forum.
fluent web components integrated with angular.
take a look at documents
i am right now exploring the capabilities of Monotouch (by Xamarin) with other solution such as
Monocross?
So can any one explain when to use Monotouch and when to Monocross.
What is the advantage & disadvantage of these framework w.r.t native app development?
Just to try to add visually to Stephane's answer, here's a diagram slightly adapted from one of my presentations:
Note that you don't have to use a shared library like MonoCross, MvvmCross, etc. You can always write your own architecture. This is like in web apps - you don't have to use WebForms, ASP.Net Mvx, FubuMvc, etc - you can just use Request and Response and talk more directly with the web server.
So, you can just write your own code to adapt your app to each platform like:
Which approach you should take - depends on the requirements of you and your app... and on personal opinion too.
Monocross is a cross platform MVC framework. As a framework, it's open source. But you need either monotouch or mono for android in order to deploy on the devices.
Those 2 stuffs doesn't compare. They sum up.
With tools like Monocross or MvvmCross, you really get a crossplatform code sharing framework, and that's your advantage over coding in native languages.
I am a newbie to extjs and kind of new to javascript world also. I have developed applications in jsp/servlet, JSF etc.
We are planning to use extjs along with Sencha Architect to develop UIs for our application.
Being new I have several questions for which I am searching answers
Q1. How should we use Sencha Architect in multi developer environment in terms of versioning. Shall we checkin the Architect project into svn and ask each developer to work on same project.
Q2. What should be the structure of Sencha Architect project (Basically how to make sure each developer is working on his/her individual module without affecting others component).
Is there any best practice for this.
Q3. What is the best practice for developing an application which contains several pages along with navigation. Should we create a single html file (with lot of javascript to modify the body) or should we have multiple html?
yes, it should certainly be in source control. you will want developer-specific settings to not be in source control however.
the best way is to create an application "shell" with menu bars, and load in modules/plugins and have them register with the application, adding their own menus etc.
definitely a single page application. security remains on the server though (for example in your REST API). security is irrelevant on the client as they have control over source code. you should just hide functionality that a user should not use.
How to load different views into viewport?
I am developing Sencha-Touch 2.0 MVC based mobile web-app. Can you please tell me disadvantages of sencha designer 2 in this development?
Sencha Designer 2 enforces that you build everything using Sencha Touch 2.0 MVC's best practices. It has support for the MVC features that you would get from standard coding.
Sencha Designer 2 / Sencha Architect is awesome! But it has it's disadvantages.
Meta data isn't source control friendly:
It's not just metadata but contains pieces of actual code. (this was a deal-breaker for my coordinator)
can't use arbitrary variables inside properties because the designerView can't resolve them.
The use of device profiles is not implemented (yet)
Update
My findings from the latest version (2.1)
Improved a lot. But still an issue.
This is improved significantly. But you will always need overrides to do advanced stuff.
Still not present
I'm not a javascript/css/html programmer. If anything I'm an objective-C, C#, C++, java programmer.
Looking at Dashcode there are features of the Utility project, Stacklayout project and some custom views that I'd like to combine into one webapp. This app would use 2 layers of stacklayout navigation, and use the infobutton to flip one of the views to get to the settings.
Is there a good way to combine dashcode projects? I notice the the generated "parts.js" file only contains dashcodePartSpecs for elements that Apple has included in that project. Can dashcode be used for non-trival projects? or this there a better way. (and yes I've already created an app store app, but Apple is trying to steal our subscription money.)
Cheers,
Gerry
There are similar to Dashcode tools that generate web "apps" Phonegap, iui, jqtouch, extjs and others.
They are essentially html/js/css frameworks from third parties. Dashcode does not get much attention from Apple where as both Phonegap and Extjs are actively supported. There is also an O-Reilly book covering Phonegap.