[Freedos-devel] Announcing FDOSTUI

Discussion:

Mark Olesen

2017-01-28 02:07:43 UTC

FDOSTUI is a C++ library for creating text interfaces.

The project homepage is:

http://www.nongnu.org/fdostui/

Comments and criticism are welcome.

Rugxulo

2017-02-01 17:01:23 UTC

Permalink

Hi,

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
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).

Mark Olesen

2017-02-01 23:49:19 UTC

Permalink

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

Post by Rugxulo
Hi,

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
http://www.nongnu.org/fdostui/
Comments and criticism are welcome.

Alain Mouette

2017-02-02 11:56:59 UTC

Permalink

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

Post by Mark Olesen
Hello,
I liked and made the changes you had pointed out. Thanks for the input.
http://www.nongnu.org/fdostui/page_compiling.html
http://www.nongnu.org/fdostui/page_hello.html
Hi,
On Fri, Jan 27, 2017 at 8:07 PM, Mark Olesen

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
http://www.nongnu.org/fdostui/
Comments and criticism are welcome.

Disclaimer: due to lack of C++ expertise, I may not do much with this.
* 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
https://lists.sourceforge.net/lists/listinfo/freedos-devel
<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
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Mark Olesen

2017-02-02 22:26:57 UTC

Permalink

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.

Post by Alain Mouette
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
Hello,
I liked and made the changes you had pointed out. Thanks for the input.
http://www.nongnu.org/fdostui/page_compiling.html
http://www.nongnu.org/fdostui/page_hello.html

Post by Rugxulo
Hi,

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
http://www.nongnu.org/fdostui/
Comments and criticism are welcome.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
------------------------------------------------------------
------------------
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
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Jerome Shidel

2017-02-02 23:10:39 UTC

Permalink

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.

Post by Alain Mouette
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

Post by Mark Olesen
Hello,
I liked and made the changes you had pointed out. Thanks for the input.
http://www.nongnu.org/fdostui/page_compiling.html
http://www.nongnu.org/fdostui/page_hello.html

Post by Rugxulo
Hi,

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
http://www.nongnu.org/fdostui/
Comments and criticism are welcome.

Mark Olesen

2017-02-03 05:53:43 UTC

Permalink

INI has my upvote. Just not sure of how much scope I would include.

what if you want a class that can be used to read and write to it
(maintaining comments and such)? Complexity is added. I can see code creep.

If it was read only it would be fairly simple and inexpensive. However,
then other code would be scattered throughout to write out there own ini
files.

XML is easy to read/write and is extensible. However, it has allot of
bloat. And user editing is not as straight forward as INI.

After some reading, I dropped JSON as a potential format.

Thanks for the suggestion.

Post by Mark Olesen
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.

Post by Rugxulo
Hi,

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
http://www.nongnu.org/fdostui/
Comments and criticism are welcome.

------------------------------------------------------------
------------------
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
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
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Alain Mouette

2017-02-03 13:22:43 UTC

Permalink

I believe that changing a config file is just great for that! Avoinding
bloat is important

At most, there could be 2 or 3 sets of parameters, not only that would
help but it can also serve as aguide for creating a new one

Alain

Post by Mark Olesen
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.
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

Post by Mark Olesen
Hello,
I liked and made the changes you had pointed out. Thanks for the input.
http://www.nongnu.org/fdostui/page_compiling.html
<http://www.nongnu.org/fdostui/page_compiling.html>
http://www.nongnu.org/fdostui/page_hello.html
<http://www.nongnu.org/fdostui/page_hello.html>
Hi,
On Fri, Jan 27, 2017 at 8:07 PM, Mark Olesen

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
http://www.nongnu.org/fdostui/
Comments and criticism are welcome.

Disclaimer: due to lack of C++ expertise, I may not do much with this.
* 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
https://lists.sourceforge.net/lists/listinfo/freedos-devel
<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
https://lists.sourceforge.net/lists/listinfo/freedos-devel <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
https://lists.sourceforge.net/lists/listinfo/freedos-devel
<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
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Mark Olesen

2017-02-04 23:20:43 UTC

Permalink

Your right about that. Thanks.

I am looking into building an INI library (public domain). It's tempting to
just rip something off the shelf for this.

Post by Alain Mouette
I believe that changing a config file is just great for that! Avoinding
bloat is important
At most, there could be 2 or 3 sets of parameters, not only that would
help but it can also serve as aguide for creating a new one
Alain
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.

Post by Rugxulo
Hi,

Post by Mark Olesen
FDOSTUI is a C++ library for creating text interfaces.
http://www.nongnu.org/fdostui/
Comments and criticism are welcome.

Jim Hall

2017-02-04 23:28:59 UTC

Permalink

Sounds cool!

I've tweeted your project from the FreeDOS Project twitter. Once
you've added the INI support, I'd be happy to mention it as a news
item on our front page to get more exposure.

Jim

Post by Mark Olesen
Your right about that. Thanks.
I am looking into building an INI library (public domain). It's tempting to
just rip something off the shelf for this.

Mark Olesen

2017-02-05 06:11:37 UTC

Permalink

I appreciate that and will update via the forum when I have an INI/Config
implementation. Thanks for the tweet.

Post by Jim Hall
Sounds cool!
I've tweeted your project from the FreeDOS Project twitter. Once
you've added the INI support, I'd be happy to mention it as a news
item on our front page to get more exposure.
Jim

Post by Mark Olesen
Your right about that. Thanks.
I am looking into building an INI library (public domain). It's tempting

Post by Mark Olesen
just rip something off the shelf for this.

Mark Olesen

2017-02-08 06:01:03 UTC

Permalink

Hi Folks,

As suggested, I implemented an INI parser (read only):

http://www.nongnu.org/fdostui/ini_8h.html

Following, themeing was fairly straight forward:

http://www.nongnu.org/fdostui/page_themeing.html

Thank you all for your previous suggestions. I look forward to your
comments. Have a great day.

Regards,
Mark

Post by Mark Olesen
Your right about that. Thanks.
I am looking into building an INI library (public domain). It's tempting

Post by Mark Olesen
just rip something off the shelf for this.