I’ve been reading through Kaleidoscope in an attempt to understand the code, and I’ve got lots of little questions (e.g. “Where is KALEIDOSCOPE_HARDWARE_H defined? I can’t find that anywhere…”). I don’t feel like it’s appropriate to bring all those little questions up here, but I would like to get s…

I’ve been asking questions on the IRC channel (#keyboardio on irc.freenode.net ), personally.

Either IRC, or these forums, I’d sya. As long as the questions are in a single thread, it’s not a distraction. The forums have the advantage of being perhaps a little friendlier and easier to search back, and may prove more educational for others. We’ve had great success on IRC too, mind you. Only t…

Definitely a good idea to write your discoveries too — I’ve been trying to do the same as well so the next person to come along doesn’t need to spend a day reading source & asking Algernon & Jesse (my current crowning achievement being making the README for Ranges longer than the source …

I think here is fine. @jesse indicated in another thread that he’d like to see this forum become searchable living documentation: [image] Porting Kaleidoscope to other hardware Ask tons of questions! Especially in a nice, logged medium like this forum site. Every question answered in public is …

[image] merlin: “Where is KALEIDOSCOPE_HARDWARE_H defined? I can’t find that anywhere…” To answer this question in particular - it’s a tricky one, it’s actually defined by the Arduino build system based on which platform you’re compiling for. (In the Arduino IDE, this is controlled by the To…

[image] craigdissel: To answer this question in particular - it’s a tricky one, it’s actually defined by the Arduino build system based on which platform you’re compiling for. (In the Arduino IDE, this is controlled by the Tools->Board option.) So, every file is compiled with -DKALEIDOSCOPE_HA…

Under linux you could use grep -R <search_string> to search recursively in code. Or grep -R --include \*.cpp <search string> to search only in files of a particular type, e.g. C++ implementation files.

[image] merlin: Do you know what it gets evaluated to in the case of the Model01? Yep, it’s “Kaleidoscope-Hardware-Model01.h” (a file provided by the plugin Kaleidoscope-Hardware-Model01). Highly related is the plugin Kaleidoscope-Hardware, which provides a base class which defines the inter…

Naturally. Go ahead and do that recursive grep, and you’ll see why I was unable to find it. =)

[image] merlin: Go ahead and do that recursive grep, and you’ll see why I was unable to find it. =) Can’t do that right now as I am far away from any source code. My post was directed to all those that are new to exploring source code. That’s why I skipped all regex magic for more sophisticat…

Where to pose questions about Kaleidoscope code

Programming

Javaru (Mark Vedder) October 31, 2017, 8:38pm 5

I think here is fine. @jesse indicated in another thread that he’d like to see this forum become searchable living documentation:

Topic		Replies	Views
Kaleidoscope-CMake Programming	19	3128	December 9, 2017
Porting Kaleidoscope to other hardware Programming	21	2700	February 23, 2018
Kaleidoscope-Hardware library Kaleidoscope Internals question	1	613	December 9, 2017
Trouble Building Model01-Firmware (macOS Sierra) Help and Getting Started	18	1681	November 1, 2017
Kaleidoscope's implementation - possible improvements Programming	30	3016	January 6, 2018

Where to pose questions about Kaleidoscope code

Related topics