|
#2
7th May 2008, 17:18
|
|||
|
|||
Hi uno,
You can get fairly far with simple search-and-replace, especially if you are coming from Ext 2.0, where the APIs for certain components are very nearly clones of SmartClient APIs for the corresponding components. For example, take the "Array Grid" Ext example source: new Ext.grid.GridPanel -> isc.ListGrid.create columns -> fields stripeRows -> alternateRecordStyles Then in each field: id/dataIndex -> name renderer -> formatCellValue sortable -> canSort header -> title If you come up with a more complete list, or even a code transform script, it would be great if you could share it with the community. Thanks! 
|
|
#4
13th May 2008, 10:21
|
|||
|
|||
|
I would say it would be great helpful to clone some of ExtJS samples(functionality, not visually), like FeedViewer and Grid sample. My coworker is looking for an alternative to ExtJS.
It is weird that I never heard smartClient before, even though I am keeping an eye on javascript library two years ago. Quote:
|
|
#5
16th May 2008, 12:40
|
|||
|
|||
|
I have a good experience with ExtJS. I think a guide showing how to port application from extjs to smarclient would be perfect.
Maybe something simple at the begging, like: Ext.grid.GridPanel -> isc.ListGrid.create Ext.DataView -> xxxxxxx Ext.data.Store -> xxxxxxx Someone with experience in there 2 libraries wouldn't take more than an hour to do a guide like that. So, one more vote to a guide :)
|
|
#6
20th May 2008, 17:58
|
|||
|
|||
|
Hi Krycek,
Unfortunately, as you might expect, we here at Isomorphic don't have a lot of hands-on coding experience in other frameworks :) However if you think it would take only an hour, we'd be more than happy to sponsor your creation of first draft once you've become familiar with SmartClient as well.
|
|
#8
21st May 2008, 08:32
|
|||
|
|||
|
Great - get back in touch then, we were not joking about sponsoring the creation of a basic migration guide.
|
|
#9
22nd May 2008, 11:45
|
|||
|
|||
|
An hour is definitely not enough. My coworker has been working on a prototype to compare SmartClient with ExtJS. We use ExtJS on the current internal project.
Overall, he likes smartclient. Pro. 1. layout is easier to use. 2. Live grid is very nice. 3. code seems more clear. Con. 1. form validation. When there is an error. Smartclient displays error information beside the form field. That often makes the form panel look mess. It is neat for ExtJS to use a red circle and qtip to show the error message. 2. Community is small. I think Smartclient needs more market exposure. Quote:
|
|
#10
22nd May 2008, 12:00
|
|||
|
|||
|
Hi ftftft (is that supposed to be the sound of arrows?),
We didn't actually think it would take an hour :) But we'd be prepared to sponsor the effort by a qualified person. On your con #1, you can present errors in multiple ways, including a compact way that does not reflow the form (an error icon only). See showErrorIcon, showErrorText, etc properties. On con #2, this community appears to be doubling weekly or so, and yes we're working on getting the word out. But it is already easy to find help, and to hire from this community (Isomorphic has done so, twice). On your pros - keep going - that's the tip of the iceberg :)
|
