<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent posts to blog</title><link>https://sourceforge.net/p/click-lib/blog/</link><description>Recent posts to blog</description><atom:link href="https://sourceforge.net/p/click-lib/blog/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 22 Nov 2016 19:46:43 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/click-lib/blog/feed.rss" rel="self" type="application/rss+xml"/><item><title>Version 0.2: do you need anything there? discussion</title><link>https://sourceforge.net/p/click-lib/blog/2015/10/version-02-do-you-need-anything-there/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Marco,&lt;br/&gt;
I was thinking of some way to do parameter checking before the actual callback.  Something that will help the next person working on my code to do the parameter checking in a consistent way.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;Sometimes the callbacks have more code for parameter validation then actual param handling.  Each person that works on the code does things just different enough to be confusing.   I looked at adding another char pointer to the your struct in click builder however, I got put on another project before I could figure out all the consequences of that change.   You did ask for suggestions. &lt;/p&gt;
&lt;p&gt;Now that I been using it more I found there are common conversions I need, like string to int or string to long long, or string to strings.  I don’t have any time constraint.  I'm just starting a new project, building up the infrastructure, build directories, and outlining everything that needs to be done.  So, January would be find.  &lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;I did a presentation for the group and my manager.  Everyone liked it and I got the OK to use CLIck for my current project.  I have integrated it into my build tree.   I am using Buildroot so next week I will create a Buildroot package for it and an item to be in menuconfig.  (section 17.5 and 17.6 in Buildroot).  Putting it in as a Buildroot package, I can change one line, the version number, and get your latest.&lt;/p&gt;
&lt;p&gt;Happy thanksgiving&lt;br/&gt;
Ray S. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ray Silagi</dc:creator><pubDate>Tue, 22 Nov 2016 19:46:43 -0000</pubDate><guid>https://sourceforge.net8730b271f58108750b34c48670ac9a3f129fcdaf</guid></item><item><title>Version 0.2: do you need anything there? discussion</title><link>https://sourceforge.net/p/click-lib/blog/2015/10/version-02-do-you-need-anything-there/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Ray,&lt;/p&gt;
&lt;p&gt;need to get back to you very quickly :)&lt;br/&gt;
Apart from bug fixing, let me understand better your suggestion: would you like to define in the XML file a default error message to be printed out when a required parameter is missing?&lt;br/&gt;
This can be done, it would require some changes, but can be done.&lt;/p&gt;
&lt;p&gt;Another approach would be to define per each command a single callback to be called in case of parsing errors like this, so leaving to the developer the task of writing the appropriate error message depending on the error.&lt;/p&gt;
&lt;p&gt;Do you have any time constraint for such a feature?&lt;/p&gt;
&lt;p&gt;Last question: I guess you have already started integrating CLIck into your system. How is it going so far?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Marco&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zacmarco</dc:creator><pubDate>Tue, 22 Nov 2016 15:28:29 -0000</pubDate><guid>https://sourceforge.net5ac91778331805e8c0774c9e496d5ef92df723ae</guid></item><item><title>Version 0.2: do you need anything there? discussion</title><link>https://sourceforge.net/p/click-lib/blog/2015/10/version-02-do-you-need-anything-there/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Ray,&lt;/p&gt;
&lt;p&gt;sorry for the delay, I just realized that my previous reply didn't arrive to you because of a mistake in the way I was replying.&lt;br/&gt;
So, back to us... I am currently preparing a new release that will contain all the fixes for problems found so far, including the one you are facing.&lt;br/&gt;
Planning to complete the packing and final testing by the end of this week.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Marco&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zacmarco</dc:creator><pubDate>Tue, 22 Nov 2016 15:19:50 -0000</pubDate><guid>https://sourceforge.netd64813d8f544498ddda7ec8b1f58bb4ac86ff0ee</guid></item><item><title>Version 0.2: do you need anything there? discussion</title><link>https://sourceforge.net/p/click-lib/blog/2015/10/version-02-do-you-need-anything-there/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Marco,&lt;br/&gt;
I'm looking for the changes that were put on the git "development" branch.  I don't know much about git so, I was not able to find them.  I did the "git clone .." of what you have in the code page.  That seems exactly the same as 0.1.  Am I missing something or are they the same?&lt;/p&gt;
&lt;p&gt;Thanks for all this work.&lt;br/&gt;
Ray S.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ray Silagi</dc:creator><pubDate>Wed, 12 Oct 2016 23:51:51 -0000</pubDate><guid>https://sourceforge.net0c70c87fd106649aee0ddb8195bc8b8ff77a89e4</guid></item><item><title>Version 0.2: do you need anything there? discussion</title><link>https://sourceforge.net/p/click-lib/blog/2015/10/version-02-do-you-need-anything-there/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'm starting a new product/project and will be using this CLI.  This product will be an embedded IoT type device so I need a minimum type of CLI.  I have a single suggestion for a new feature.  I would like the error mesage to inlcude the help message.  The current error message is too generic.  The current error message is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;MISSING VALUE FOR PARAMETER "time"&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;My suggestion:&lt;/p&gt;
&lt;blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;MISSING VALUE FOR PARAMETER "time"&lt;br/&gt;
DESCRIPTION:&lt;br/&gt;
Enter the time as yy mm dd hh mm ss&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;For my projects I would vote against your feature 1, "runtime change of the prompt"  I don't see any reason to do this.  The CLI is used to control the product by engineers and support, the user's will use a web browser.&lt;/p&gt;
&lt;p&gt;I hope this helps,&lt;br/&gt;
Cheers;&lt;br/&gt;
Ray &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ray Silagi</dc:creator><pubDate>Fri, 15 Jul 2016 17:40:31 -0000</pubDate><guid>https://sourceforge.netfcb163db6471677c40f27239e2ca62c70bf89ddc</guid></item><item><title>Version 0.2: do you need anything there?</title><link>https://sourceforge.net/p/click-lib/blog/2015/10/version-02-do-you-need-anything-there/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi everyone,&lt;/p&gt;
&lt;p&gt;as 0.1 has been already out for a while, I'm starting to plan the new features to add to the library.&lt;br/&gt;
So far this is what I have in mind, but not sure I'll be able to include everything in 0.2:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;runtime change of the prompt in command callbacks (to override the value of the prompt defined in the XML file)&lt;/li&gt;
&lt;li&gt;commands and parameters abbreviation&lt;/li&gt;
&lt;li&gt;implementation of back-search (like &amp;lt;CTRL-r&amp;gt; in BASH)&lt;/li&gt;
&lt;li&gt;definition of a XSD for the XML files (possibly to be used by clickbuilder)&lt;/li&gt;
&lt;li&gt;expand the helper macros to be used in the callbacks&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;as well as fixing bugs (no bugs reported so far) and creating new examples to show the features better.&lt;/p&gt;
&lt;p&gt;Also, please bear in mind I'm trying to enrich the wiki pages as much as I can, please be patient.&lt;/p&gt;
&lt;p&gt;But what I want from you guys is hints on what you'd like to see included in the library, I am quite flexible, so if your ideas match mine, I'll just arrange my spare time to implement what you need.&lt;/p&gt;
&lt;p&gt;Finally, if you want to contribute, just send me a message, I'll reply ASAP.&lt;/p&gt;
&lt;p&gt;Thanks everyone for your collaboration.&lt;/p&gt;
&lt;p&gt;Marco&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zacmarco</dc:creator><pubDate>Wed, 14 Oct 2015 13:08:46 -0000</pubDate><guid>https://sourceforge.net116c6901b7cf1e4a79af5807d2e93e87a9e5848f</guid></item><item><title>Welcome!!!</title><link>https://sourceforge.net/p/click-lib/blog/2015/04/welcome/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Welcome everyone to CLIck project.&lt;/p&gt;
&lt;p&gt;This project comes from a few years of ideas, that I finally put into code.&lt;/p&gt;
&lt;p&gt;At the time I'm writing this post, CLIck is at its first Beta release, that means that for the first release features are frozen, as my interest is having a very first stable version, that will work fine, despite some missing features that I already have in my mind ready for release 0.2.&lt;/p&gt;
&lt;p&gt;At this point in time, it would be VERY useful receiving from all the interested users feedbacks about quality, feature coverage, and mainly SUGGESTIONS on how to make this project more complete and suitable for your application.&lt;/p&gt;
&lt;p&gt;So this is a call to everybody interested in this project: PLEASE SEND ME ALL THE FEEDBACK YOU CAN!&lt;/p&gt;
&lt;p&gt;I'm trying to find some time to improve the Wiki page, as I think that the biggest gap to be covered is missing documentation, I've tried to put the basic stuff into the Wiki, but this is still on-going.&lt;/p&gt;
&lt;p&gt;Thanks everyone to the interest in this project!&lt;/p&gt;
&lt;p&gt;Enjoy your CLI&lt;/p&gt;
&lt;p&gt;Zacmarco&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zacmarco</dc:creator><pubDate>Fri, 03 Apr 2015 09:31:11 -0000</pubDate><guid>https://sourceforge.net9b0738d8afdace1e2948ad17666784b6919b6108</guid></item></channel></rss>