Home › Forums › General › News and releases › Ctrlr – Step by step guide (in DEV version)
Tagged: documentation stack-overflow
- This topic has 26 replies, 13 voices, and was last updated 6 years ago by goodweather.
-
AuthorPosts
-
August 1, 2015 at 9:17 pm #53939
*** This is an outdated topic; don’t use anymore ***
*** Look at the main Step by Step guide topic or contact me by PM for other suggestions ***Hi,
this is the “in development” topic for the Ctrlr – Step by step guide.Of course, all contributors are welcome but for easier management purpose I propose to publish the releases.
Use the styles I defined (Alt-Ctrl-Shift-S) so that we have an uniform look:- Normal: for all paragraphs
- Paragraph bullet: starting a new paragraph where next ones are bullets
- List bullet: level1 bullet
- List bullet2: level2 bullet
- Heading3: headers
- Picture: for pictures
- Code: for code extracts
The table of content is adapted automatically.
In the appendix, you can add new topics to be added later on, identified bugs to forward to Atom…
This first post will always contain the last “in dev” version in Word.
- This topic was modified 6 years ago by goodweather. Reason: Outdated topic
Attachments:
You must be logged in to view attached files.August 5, 2015 at 5:16 am #54203I’ll try to do some work on this tonight. I’ll mark my changes using Track Changes so you can incorporate the changes into the master document.
I’ll add a procedure on how to create and assign a method to a modulator/panel
I’ll add a number of code examples.
LUA Method for sending MIDI from a modulator.
Using Tables for Value Lookups from a custom list (because setMappedValue and getMappedValue doesn’t seem to work for fixed image sliders. This also shows how to build and use a general function in ctrlr
LUA Methods for setting Modulator and Panel Properties and how to work out how to reference them.
LUA Method for setting modulator values
Some discussion about Initializing the Panel, global variables and some strategies about being efficient with LUA programming (though I’ve still got lots to learn here).The Puppeteer
http://godlike.com.auAugust 5, 2015 at 5:20 pm #54262Have made some modifications. Please go through the changes and update your initial post.
Attachments:
You must be logged in to view attached files.The Puppeteer
http://godlike.com.auAugust 5, 2015 at 8:35 pm #54281Thanks Puppeteer!
August 7, 2015 at 11:39 pm #54456Thank you!!!
August 8, 2015 at 1:17 am #54464thank you
August 11, 2015 at 5:29 pm #54740Another update. Added a bit packing function example. It should be pretty efficient as it’s all and, or’s and bit shifting.
Attachments:
You must be logged in to view attached files.The Puppeteer
http://godlike.com.auAugust 11, 2015 at 5:55 pm #54742Missed a couple of minor formatting issues. Also did an intro.
Attachments:
You must be logged in to view attached files.The Puppeteer
http://godlike.com.auAugust 13, 2015 at 4:43 pm #54872Added a short section on exporting and solving some resource display issues.
Attachments:
You must be logged in to view attached files.The Puppeteer
http://godlike.com.auAugust 13, 2015 at 4:54 pm #54875Sorry about all the small edit changes. I save and upload, and find something else that needs fixing.
This time, added a note about using vertical rather than horizontal knob file exports from jKnobMan.
Attachments:
You must be logged in to view attached files.The Puppeteer
http://godlike.com.auAugust 25, 2015 at 1:59 am #55834Hi.
As my first post (after spending time trying to get a grip on things) this might be a bit “negative”, but I would suggest one thing:
Use version control software.
Wouldn’t it be better for the organization of all the changes and different contributors to use version control system, for example Git? This would make sure that all changes are tracked and diffs can be made easily, and things can be merged in ordinarily fashion. Thus it would make it easier to maintain the project and to have good document in one central location (GitHub?) that’s public on the net and one can easily find it using Google.
It took me many hours of just scourging through the forums to accidentally come across this thread. Google doesn’t find it, and since these forums don’t have stickies, it could easily get under a ton of other posts and be forever hidden / forgotten.
And this document is definitely something that shouldn’t be lost to the depths of the forum.
Thank you for your understanding and please, don’t take this too harshly. Just something that many years of software development and open source projects have thought:
* Centralize all information to one place.
* Make it easily available to all contributors.
* Make sure it can be found with Google.
* Use version control software, it saves lives.🙂
August 25, 2015 at 9:38 pm #55921Hi,
thx for all updates Puppeteer!TO ALL: please bear in mind that this is the IN DEV version! The idea with this thread was to gather info then publish it as a new version of the “official” thread (official is very bad naming…).
“Official” thread is: http://ctrlr.org/forums/topic/ctrlr-step-by-step-guide/
August 28, 2015 at 10:49 am #56214Thanks for working on this document.
But I agree with lcchan that open source development, which includes not only software but also documentation, should be done in an open source version control system like git. And I would expect to find stable versions of such documentation easily in the ctrlr website below the “Documentation” and/or the “Downloads”, not hidden inside a forum thread.Having said that: Keep up the good work! Good documentation is essential for the usability, power, and future of ctrlr!
September 3, 2015 at 3:31 pm #56953Maybe try github pages?
https://help.github.com/categories/github-pages-basics/Using it with Jekyll is pretty sweet.
September 4, 2015 at 6:11 am #57054Please bear in mind that this is a user originated tutorial, not an official manual, and we are far from Ctrlr experts. I’m having a look at github at the moment and it may be workable for us, but in the meantime while we are still authoring the main sections, we might put it on onedrive to make it easier for us to build.
Once we’ve filled out most of the current sections, I’ll try to get in touch with Atom about including it in the official documentation section.
The Puppeteer
http://godlike.com.auMay 13, 2017 at 6:52 am #72139Hi,
Are there any news about the wok process of that guide?
I appreciate your work a lot 😉Regards
RioMay 13, 2017 at 8:21 am #72140Thx. Actualy you should not look to this post but to the http://ctrlr.org/forums/topic/ctrlr-step-by-step-guide/ one.
Yes, I’m working on it but in parallel (besides my business work) I’m also modifying the Pro2 panel and making a P12 panel and learning my synths and…
But no worry, it will come out. I guess somewhere in August.
I have rewritten the existing part by adding more details and info. I’m using my Pro2 as example as I came to a dead end with the Sub37.
I have also added a lot of pages on Lua programming and methods (all tips and tricks I’m using in the Pro2 panel).
There is really a lot to explain…So, thx for your support and just be patient 😉
May 15, 2017 at 9:46 am #72160thx thx, can you pls add then an article about programming with mouse events too, like you have mentioned here:
http://ctrlr.org/forums/topic/how-to-get-the-mouse-event-object-in-any-method/
regards,
rioMay 15, 2017 at 3:42 pm #72165Yes. I had already foreseen the paragraph.
Thx for mentioning!May 15, 2017 at 9:46 pm #72166Maybe try github pages?
Recently there is a “Documentation” project on Stack Overflow. We could use it, but first we probably need some questions tagged “ctrlr”. Ctrlr is a sort of visual programming language, and a programming framework from Lua point of view. How many of you use Stack Overflow?
-
AuthorPosts
- The forum ‘News and releases’ is closed to new topics and replies.