Quantcast

Going from Domite to Silk (was: Re: [amber-lang] Domite at: aSelector shows up as nil)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Going from Domite to Silk (was: Re: [amber-lang] Domite at: aSelector shows up as nil)

Herby Vojčík
Jörg Rade wrote:
> Hi Herby,
>
> thanks for your answer and I appreciate the recommendation!
>
> I'll look at silk again when I start polishing my code.

In fact this can be done in very small steps. Silk is subclass of
Domite, so you can swap any `Domite` with `Silk` in your code and it
should just work. Once you have swapped all of them, you can start to
use Silk's API instead (like, `'#navigator' asSilk` instead of `Silk at:
'#navigator', or `Silk DIV` instead of `Domite newElement: 'div'`).

> Best regards
> Jörg

Herby

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Loading...