search

jurisv / nodejs.extdirect

Ext.Direct connector for node.js (npm module)
41 stars 16 forks source link

Please check in a complete working sample under a separate extdirect.example repo. #9

Closed tohagan closed 10 years ago

tohagan commented 11 years ago

It's very painful to have to copy paste code from a README.md file. What's really needed is a complete working example that is versioned by source file. It's also important that this example code is not part of this repo so it's not included in any package dependency. Just update the README.md to point to this new example repo.

Thanks for extdirect for NodeJS ... really appreciated!

srguiwiz commented 11 years ago

I second the request. If this is someone's first use of Ext.Direct, given the added hurdle of Node.js being "different", this is very time consuming trying to make something run at all. Specifically if someone is aiming to use a different database than MySQL this becomes a very long stretch. Having a complete example than runs (ran in some version of Node.js) would make a huge difference. Even if it is only one model, one table.

jurisv commented 11 years ago

I have couple examples in the works, will add along with other feature requests.

srguiwiz commented 11 years ago

If you are quick I will attempt returning the favor, make a copy that runs with MongoDB and give it back. If you let us know an ETA I could save my energies until I see yours, and build on it, instead of trying to get to where you have been already.

jurisv commented 11 years ago

ETA >2 days, will free up some spare time today.

tohagan commented 11 years ago

This is really helpful. Thanks guys! There's great value in having both SQL and Mongo examples.

jurisv commented 11 years ago

Initial commit with node.js serverside. Full fledged demo applications for both ExtJs and Touch will folllow in coming days. Repo here: https://github.com/jurisv/code-examples

After I finish adding examples, I will update Readme file here to match location as well as docs itself.

tohagan commented 11 years ago

Just a thought ...

I think there's a naming convention of sorts in npm to include the original lib package name as a prefix for corresponding code samples repo (i.e. "extdirect-examples" rather than just "code-samples"). This will index it better in Google/GitHub search engines and also mean when you register the sample repo in npm people are more likely to find it and know it exists when they search for "extdirect" ... otherwise they might miss it.

jurisv commented 11 years ago

Initial idea was to put different examples in that repo. But I will keep it clean and store only extdirect related code there.

Renamed : https://github.com/jurisv/extdirect.examples