Hi Ryan, JSON will be surely my first choice :) and I think I'll provide also an easy way to convert the vocabulary from xml because would be really useful "sever side".
> I noticed a lot of css option in the class, having built several scripts that > did the same, I've found I always regret doing so. I end up refactoring it > to add and remove classes from elements and then I couple the script with a > css file. And yes, you're right! I have to refactor a bit. A css coupled with the script is the right way, thank you for the advice! I've started using a css for theme examples but I agree with you. I'll end just moving the default css proprerties into a "default" css file :) so, thank you all for your interest! :D -- Andrea Dessì Email: [email protected] Skype: nkjoep Blog: http://www.stealthefish.com/ LinkedIn: http://www.linkedin.com/in/andreadessi Jabber: [email protected] Twitter: http://www.twitter.com/NKjoep On Jul 7, 9:16 am, Ryan Florence <[email protected]> wrote: > This is great work! > > > I've started thinking on a JSON/XML structure for the vocabulary... > > JSON, because this is javascript. > > I noticed a lot of css option in the class, having built several scripts that > did the same, I've found I always regret doing so. I end up refactoring it > to add and remove classes from elements and then I couple the script with a > css file. > > Again, this is really great stuff. >
