13 Feb 2012 9:01 AM #11
- Join Date
- May 2010
- Guatemala, Central America
- Vote Rating
I still think that they should develop Designer as an eclipse or netbeans plugin instead of making their IDE from scratch.
With those IDEs you already have a lot of facilities (server container -http or java-, version control, project management tools, source code editors -including mature JS-, etc.) those that Sencha could take advantage.
Java, as JS, is ubiquitous this days.UI: Sencha Architect 2.x / ExtJS 4 MVC
Server side: EJB 3.1 / CDI / JPA 2 / JAX-RS / JasperReports
Application Server: Glassfish 3.1.x
Databases: Oracle 10g & 11g / DB2 9 & 10 / Firebird 2.5
If you like my answer please vote!
13 Feb 2012 12:09 PM #12
We use the ExtDesigner for Agile style dev only - my front end guy does screen layout for mockup, I expose the data stores and once layout is complete, we wire it in. We don't require anything fancier than a stand alone GUI - all mid tier and back end code is done with GVIM, all application logic handled in PSQL at the database layer.
From a developer point of view, I support the idea of an Eclipse plug in. But from a business point of view, I can see the point of the stand alone tool - it is an easier licensing model. And if it is capable of what I need it to do, I'll put my sheckles on the counter and upgrade.
This eosoteric conversation is all lovely and good, but I still have an application built with a tool which will no longer open it. If I upgrade (which is my desire), I'll have to reimport everything from scratch, convert each file by hand and build the master file.
Any suggestions, Team Sencha?
13 Feb 2012 12:38 PM #13
Sencha Architect Development Team
13 Feb 2012 12:45 PM #14
Thanks Aaron. I've got a new MacMini server down here and will try opening with that - I only need to convert the existing file across to test the stability and from your comments earlier, which I believe is simply doing a Save As into a new folder. Once I get it to that point, I'll test the speed and stability and make my decision.
While you're taking suggestions, I'd really like to see the components and data stores in alpha order. And a way to import data stores from other projects would be nice as well. My current method is using GVIM - works but is a bit clunky.
Shout howdy to the team up there - its a good piece of kit and we use it daily.
13 Feb 2012 12:48 PM #15
16 Feb 2012 8:14 PM #16
16 Feb 2012 8:17 PM #17
16 Feb 2012 8:21 PM #18
Also note that for projects w/ 50+ stores. Many times there are ways to optimize now that we have Models. Those 50 stores can become 20. Of course other times you need exactly that many stores no bones about it. Designer can and will support this use case.
We already have some really easy wins in terms of performance tweaks lined up. However the engineering team will be discussing performance as a first class feature tomorrow morning so we can roll out a GA that is usable by teams and projects big and small.