19 May 2012 10:18 AM #11
If you have a product to ship after just one week then you are doing amazingly well.-->
19 May 2012 11:01 AM #12
Add more Xda projects collection
Sencha-architect examples are great, but I think SA should provide additional MVC-driven examples.
A collection of simples and quick projects (.xda). e.g. Example of Architect 2 Master Detail Project, populate combox, more examples with Associations and validations, examples of ExtJS converted in MVC.
Not only focus onto producing great demos and examples to showcase the framework’s capabilities and
provide realistic sample code to draw from.
19 May 2012 11:30 AM #13
I'll chime in on this one.
The lack of current working examples in Sencha 2 MVC style that are non-trivial - and the extensive (but cryptic) documentation without syntax examples or Architect screenshots really make coming up to speed really frustrating. Also - all the prior 1.1 and non-MVC examples confuse the issue and a lot of them are just plain the 'Wrong Way' to really do things in the real world - IMHO.
Check out my recent Setting up Sass/Compass/Pictos Forum Post - as it turns out, a 'Complete Working Example' makes this a snap to really 'Get It' - and get down to the biz of building a real-world app.
We don't want to become experts at one-time setup & plumbing issues. I spent three days foraging around, and then got one good example and was up and running with the whole theming & pictos icons in 10 minutes - and I know I'm not alone here. The screencasts are great, but a working example that doesn't require chasing down all the slightly different and obtuse config details would totally make the difference in 'Dev Satisfaction'.
Savvy devs know what we're looking to do - and how to do it in native js or Jquery, Backbone, Knockout, Zeptos, Dojo, etc... but the lack of overview and foundational documentation for Sencha has us being dragged through a bed of nails. And out-dated techniques that are pretty much throw-away just make it even more aggravating - when you want to build an industrial-grade mobile enterprise app.
That said - this framework totally rocks and you guys are doing a great job of charging after the prize - I know this is a tough thing to get right.
You just really need to tie up some of these bleeding edge setup & example issues to make it simple to get up and running with a 'Professional Dev Environment' without all the negatronics.
Maybe a comprehensive 'dev environment setup' repo on GitHub would make this simpler?
21 May 2012 2:53 PM #14
I wish to share my first experience with the product, was not good but may be constructive.
I have registered to sencha community and installed for my first time sencha architect last Friday, during my first day I found the very cool approach of architect making my first UI(one view) all my exclamations was WoW!, cool! etc... all days after I starting to become every day I bit more frustrate I cannot do simple things I do not understand how to bind events with multiple view using controller. The example repeated many time in the docs and videos simply cannot be done in the architect, because I can't set "xtype" attribute, I can't set "controllers" attribute inside my controller, I can't edit that parts in the code view, etc.. docs also confusing me because as you describe is not clear how to identify an object or how we manage id,itemid, class name,xtype in the architect..to bind events.
I read a lot of docs and spent many hours, looking inside code examples (that simply cannot be made with architect!) and finally I also downloaded the zip "architect examples" opened "city bar", the architect say that is an old project (what?!?), than after converting this it say that there is an error etc.. and as expected it did not work!.
After all, I found your post and I TOTALLY agree with you! in all points, from 1 to 5 and inclusive of your final consideration, in the mean time I lost 4 days and now I can't hide that I'm feel a bit angry..
I think that the architect come out with very good ideas but simply still a beta product, lack a working examples, lack a real documentation to guide users and also may be useful to have autocompletion as free update in the next release .
My reasons to give a chance to sencha versus jquery mobile was the slightly better performances and this rad tool, and I'm sorry but after this marathon and stress all my initial enthusiasm was transformed in frustration
21 May 2012 3:05 PM #15-->
21 May 2012 3:20 PM #16
Thanks for sharing your experience.--
22 May 2012 12:51 AM #17
Still to improve!
Please improve your docs and examples. Link (or create) new things and delete old things, please.
Don't only say we can do it like this, explain why and the different approach for each different reason.-->
22 May 2012 1:23 AM #18
perhaps we should display this as xtype
I'm betting their are a ton of "I can't do that in Architect" moments where 90% of the time it can be done.
A bunch of things become easier when you understand how each of the frameworks work.Phil Strong
22 May 2012 1:34 AM #19So I tried this. I associated my view with my controller. I added an action in the controller with target Ext.button and event touch. Great. However this gets every single button touch in the application. Not really useful. How do I make it more specific? And what is a control query?
Most specific to least specific
Set an id on the button and using #theId for the query
Set an itemId on the button and use [some parent view selection] > #theItemId for the query (scoped to the top level view and not global) e.g. #myForm > #cancelButton
Set a class or cls on the button and use .className for the query (.cancelButton) -> any observable with the class cancelButton will trigger this.
Also using class but be more specific to buttons button.cancelButton
Use an xtype form > button (all buttons that belong to a form)
button (all buttons)Phil Strong
22 May 2012 1:38 AM #20
Selectors, yes but how?
What's the difference between:
- #myForm > #cancelButton
- #myForm #cancelButton
Where can we find documentation about selectors usage?-->