20 Dec 2012 12:42 PM #11
The following is promised as part of support at this very minute. The SVN access described has not been provided for a very long time. Sencha's development has transitioned from open source to a black box as far as their customers are concerned.
Access to Development SVN
Test bug fixes, preview new features, see every code checkin through direct access to the SVN HEAD.
Would you like to verify that the next version will indeed fix the bug you reported? Would you like to experience a new feature before it is officially released? Your paid support subscription gives you access to the SVN HEAD. This means you will have early access to test bug fixes and new features. Since you will be able to see every code checkin, you’ll know what will be coming in the next release.
20 Dec 2012 2:15 PM #12
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
You have access to nightly buildsMitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
20 Dec 2012 4:28 PM #13
Are there particular topics you have in mind? It's all fine and good to say "we need help doing advanced things", but I think the best approach for something like this is to take specific ideas from the community and address those needs. Otherwise we run the risk of creating very generic content which doesn't quite satisfy anyone.
I would love to hear some of your ideas, if you have some!
20 Dec 2012 7:30 PM #14
Well, I gave a few in the first message:
Get one of the grid or tree gurus to take an hour and give a "deep dive" into how they work. Get a layout guru to talk about those. Get a class expert to go into the guts of the class system, preprocessors, etc.. Have someone explain the do's and don't of bypassing the components and leveraging the underlying HTML elements. Cover the differences between Touch and ExtJS and the best ways to allow code reuse across them.
If you're looking for more, I'd focus on complex components that are typical targets for major customization: grids, trees, combobox, layouts, extending or creating grid/tree plugins, advanced XTemplates, etc.
Custom animations would also be great, both for ExtJS and for Touch. I came from Flex, where animating things and adding transitions to components was really easy. I've tried to wrap my head around animation in ExtJS and Touch but I haven't succeeded yet.
I'm sure any coverage of the details behind the Fastbook app would also be an instant hit.
20 Dec 2012 10:05 PM #15
- Join Date
- Nov 2007
- Stockholm, Sweden
- Vote Rating
Very good suggestions for topics! +1
20 Dec 2012 10:25 PM #16
We are a couple of guys hosting ExtJS/Sencha Meetups on a regular basis (See meetup.com) about stuff like this.
A more "online" type of meetup , covering the topics you mentioned, would be a perfect compliment for those who dont live nearby those hotspots.
27 Dec 2012 11:53 AM #17
I've been lurking in these forums for the past few years. Sencha's team and the users that are active have definitely worked to create a more "friendly" environment. (I remember the less friendly years LOL).
I hope Sencha's listening to this. In my case, I don't have questions (I read the code if I do), I like to see what's going on in the forums when I can though to see if anyone has anything new/neat/cool that's going on.
I agree that a user community would really benefit Sencha. I don't know what's going on at a national level, but companies seem to love people with ExtJS or Touch in their arsenal, but there just isn't enough of us in the area. I think providing more resources to developers that are interested in learning is only going to make Sencha grow as a company.
I'd love to see a new community push in conjunction with going back to free tools for non-commercial use.
27 Dec 2012 11:57 PM #18
+1 roadmap, bug tracker, enhancement requests needs to be more transparent. Not knowing what's coming in the next release or when a feature will be implemented is becoming difficult to plan our product development.✝♄ℯ ☮ηℯ
28 Dec 2012 3:38 PM #19
- I am suspicious of those who want to form committees and sit as representatives of the people. Good technitions want to create and not talk.
- Many of the education items you suggest are covered in the learn section here, I wonder if you have fully explored this?
- Pulling core product developers away from their main job is disruptive. They might not be regular presenters hence they will have to devote a disproportionate amount of time preparing to present. This is why the Microsoft's of this world have full time evangelists.
4 Jan 2013 5:41 PM #20