discussion:sidebar

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
discussion:sidebar [2017/06/06 01:53]
pier4r [newRPL desktop version and manual]
discussion:sidebar [2017/12/16 06:04] (current)
pier4r [Chapter 6 - Command Reference]
Line 55: Line 55:
  
 //Pier 2017/05/27// //Pier 2017/05/27//
 +
 +
 +-----
 +Any answer on this? Also Claudio I'm going to PM you my workflow on the 50g once I got through this period (I have to search for a relocation, so I won't be so active until August I think), I sent it already to smartin and he suggested me to show it to you. If it is not a problem I can post it here too.
 +
 +//Pier 2017 06 24 //
 +
 +----
 +
 +If I understand your concern, you are worried that the programming page may become too long because of code examples?  I would think a long page is ok since there is always the table of contents at the top for jumping to sections.  On the other hand, if you are going to include sample programs (more than just snippets) maybe having a separate page ('RPL Programs') under chapter 5 as well, which could be linked to from the 'basics of RPL' page would make sense.
 +
 +S.M. (2017-06-24)
 +
 +----
 +
 +(Sorry I'm not so active in those days. I hope to be back in August) \\
 +The Idea is from wikipedia and other wikis on which I contributed. In general one may fill a page and when this gets big (around 50 thousand chars), can be split in other pages. But here I wanted to avoid making the manual part boring.
 +
 +Like: this and this command, the syntax is this at glance. Then for examples look there.
 +
 +I guess your idea of making another page with examples with link, makes sense.
 +
 +Pier (2017-07-23)
 ==== Chapter 6 - Command Reference ==== ==== Chapter 6 - Command Reference ====
 For this chapter I was thinking it would be for newRPL commands only (not duplicating all commands in the 50g stock ROM).  Then, have the chapter organized by sections (categories), and newRPL commands listed alphabetically within the sections.  I'll throw up a change to the sidebar showing what I had in mind.  S. Martin For this chapter I was thinking it would be for newRPL commands only (not duplicating all commands in the 50g stock ROM).  Then, have the chapter organized by sections (categories), and newRPL commands listed alphabetically within the sections.  I'll throw up a change to the sidebar showing what I had in mind.  S. Martin
Line 61: Line 84:
  
 Ahh, if it's that automated, great!  S. Martin Ahh, if it's that automated, great!  S. Martin
 +
 +A list of commands (although without description at the start) could greatly help. Because one may assume that the commands have similarities with those in the userRPL standard lib. Otherwise a user is left, for what I know, with google searches or the autocomplete that may be tiresome. Hence, could we have a list of commands, updated every now and then? Many thanks and - in the case - merry Christmas!
 + --- //[[pierqr.aiello@yahoo.it|pier4r]] 2017/12/16 06:01//
  
 ==== Please help with section "Contributing to this wiki" ==== ==== Please help with section "Contributing to this wiki" ====
Line 297: Line 323:
 Ok good to know. Indeed I can see the desktop version as 50g simulator (although I think it has no emulation layer). Just because typing there is not so immediate, it is really like the calculator, like pressing **Ctrl-+** to insert the program brackets and so on. Plus one (like me) could decide to first develop a stable version of an algorithm on the simulator and then pass to the calculator to minimize sd card transfers. Although as I asked on the MoHPC forum it is a bit unclear how can I pass just one object (a program) from the simulator to the sd. It seems I can save the entire state of the simulator, but nothing else. Ok good to know. Indeed I can see the desktop version as 50g simulator (although I think it has no emulation layer). Just because typing there is not so immediate, it is really like the calculator, like pressing **Ctrl-+** to insert the program brackets and so on. Plus one (like me) could decide to first develop a stable version of an algorithm on the simulator and then pass to the calculator to minimize sd card transfers. Although as I asked on the MoHPC forum it is a bit unclear how can I pass just one object (a program) from the simulator to the sd. It seems I can save the entire state of the simulator, but nothing else.
  
 +Pier 2017/06/05
  • discussion/sidebar.1496739223.txt.gz
  • Last modified: 2017/06/06 01:53
  • by pier4r