[TIMOB-1503] KitchenSink Errors
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2017-04-28T20:50:41.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | iOS |
Labels | errors, jslint, kitchensink |
Reporter | jbrinkman |
Assignee | Ingo Muschenetz |
Created | 2011-04-15T02:54:33.000+0000 |
Updated | 2017-05-02T21:12:14.000+0000 |
Description
When I open KitchenSink application in Eclipse (JavaScript edition) it shows 151 errors and 427 warnings. As the baseline sample app, this seems like it should be fairly clean as it could add subtle errors to users code as they use elements of this code as a starting point. Also, I have found a number of files in the kitchensink application which are no longer used.
Attachments
File | Date | Size |
---|---|---|
kitchensink.diff | 2011-04-15T02:54:34.000+0000 | 133929 |
I have created a patch to reduce the number of warnings down to three, a more reasonable number. I agree, having a kitchensink app with so many warnings is not very confidence-inspiring.
How do we apply this patch to KS project files on Mac OS X/Titanium?
This is assuming you have cloned the git project.
If that says the patch is OK then apply it:
3. git-apply kitchensink.diff
NOTE: I created a new, separate project called PatchedKitchenSink and copied the patched KitchenSink/Resources dir into it, overwriting the base Resources dir that Titanium created. The files around the checked-out version (like what is in build/) are not well.
Step 1 should read:
Sorry about that.
I get the following errors. Can you just put a zip of the updated files up somewhere?
And just to be verbose, here's what happens with a --check:
It may be that the current version is newer than what is in the patch.
Do we even care about this? Going to put in Ralf's bucket.
I would like to request that, as the primary coding model and de facto Ti reference and teaching piece for all current and aspiring Titanium developers, Appcelerator should make it a priority item for improving the quality of the code and its embedded documentation. There is really no excuse for providing a reference app that generates hundreds of errors and warnings, since they can be avoided. Many of the examples need to be more robust, and the code quality is less than optimal, to say the least. There's little use of user-defined classes, the examples are in some cases overly trivial and unhelpful, there's a lot of redundant code with hardwired coordinates, etc. I would think that Appcelerator would want this to be a "best foot forward" advertisement for the platform, using coding best practices. It's been 6 months since this was raised, and I'm still getting 155 warnings from KS in 1.6.0.
I couldn't agree more. KitchenSink is a mess, both in structure and coding style.
It is important. Every new user use KitchenSink as a reference. So you're essentially promoting bad coding style.
reassigning
Closing ticket as invalid as this version of Kitchen Sink is no longer in use.