relationship between Architect and SDK?
Would really appreciate some clarification on the relationship between Architect and SDK ... coming from Flex side, if Adobe added new components or updated components, we download the new sdk and point FlashBuilder to that sdk, and the IDE then uses/compiles from those classes.
Am using Architect 2 which comes up with Toolbox - Ext JS 4.0.x .... not sure whether the Flex comparison is valid, but how do I point to extjs-4.1.0-rc3 which has the classes I need e.g. enhanced border layout stuff. As always tia.
Ext 4.1.x support will come out as a target framework soon after 4.1 hits GA.
On the architect team, we are still working out things like how to handle seamless upgrading from 4.0 to 4.1.
Currently, you can link in the 4.1 rc's at execution time by updating your project preferences. This however will not update it at design time only at runtime.
so if e.g. 4.1 has added attributes/properties to a class, they will not show up in the Inspector but it would be possible to modify the .js file created by Architect manually to use these features?
Once you link 4.1 via the settings Ext Path, you can add handle using the additional attributes/properties in two different ways.
The first is to add a "custom" property via typing in the property that will exist in the future version and clicking add. By default this custom property will default to type of "string". You can add different types by defaulting it to a value. For example "myBoolean: true" and then clicking add will add a property called myBoolean and set the value to true.
The second is by creating an override of the class. Creating an override is generally for advanced usage and gives you complete control by providing you the ability to write raw source code. This raw source will never be interpreted in the design view. In most cases you will not need to do this and its for advanced users. This overrides file is capable of being manually edited outside of Architect once you exit it.