> On Feb 2, 2017, at 5:26 PM, Mark Olesen <markjole...@gmail.com> wrote:
> 
> Skinning at the moment can only be done by modifying code (skin.c). I left it 
> out because I do not know the best method of providing a decent configuration 
> file without adding allot of code bloat. FLTK has a preferences widget 
> (Fl_Preferences), which is a candidate. XML, JSON formats are other things to 
> consider. I really don't know the direction to take for it. Suggestions are 
> welcome.
> 

Simple INI format (or variant) is an option as well. Very little overhead to 
parse the file.


>> On Thu, Feb 2, 2017 at 4:56 AM, Alain Mouette <ala...@pobox.com> wrote:
>> I like that :)
>> 
>> Just one question: can default collors be configured? I would like something 
>> like "dialog" in Linux which has a gray background...
>> 
>> :)
>> Alain
>> 
>> 
>>> On 01-02-2017 21:49, Mark Olesen wrote:
>>> Hello,
>>> 
>>> I liked and made the changes you had pointed out.  Thanks for the input.
>>> 
>>> html pages affected:
>>> 
>>> http://www.nongnu.org/fdostui/page_compiling.html
>>> http://www.nongnu.org/fdostui/page_hello.html
>>> 
>>> 
>>> 
>>>> On Wed, Feb 1, 2017 at 10:01 AM, Rugxulo <rugx...@gmail.com> wrote:
>>>> Hi,
>>>> 
>>>> On Fri, Jan 27, 2017 at 8:07 PM, Mark Olesen <markjole...@gmail.com> wrote:
>>>> >
>>>> > FDOSTUI is a C++ library for creating text interfaces.
>>>> >
>>>> > The project homepage is:
>>>> >
>>>> > http://www.nongnu.org/fdostui/
>>>> >
>>>> > Comments and criticism are welcome.
>>>> 
>>>> Disclaimer: due to lack of C++ expertise, I may not do much with this.
>>>> Nevertheless, here's some comments anyways (BTW, nice work so far):
>>>> 
>>>> * Why bother with response file for simple uses of WLINK? Why not just
>>>> use, e.g. "wlink op stack=4096 ...", etc.?
>>>> 
>>>> * Compiling hello.cpp should normally output hello.exe, so explicitly
>>>> using "-fe=" is redundant.
>>>> 
>>>> * "-bt=DOS -l=DOS" is also redundant, use "-bcl" instead.
>>>> 
>>>> * "ncurses compiling" says you're using "cpp" (C preprocessor), which
>>>> can't be right. I assume "g++" here (or "gpp" for DJGPP).
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Freedos-devel mailing list
>>>> Freedos-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>> 
>>> 
>>> _______________________________________________
>>> Freedos-devel mailing list
>>> Freedos-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>> 
>> 
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Freedos-devel mailing list
>> Freedos-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to