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

On Sat, Feb 4, 2017 at 4:28 PM, Jim Hall <jh...@freedos.org> wrote:

> 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
>
>
> On Sat, Feb 4, 2017 at 5:20 PM, Mark Olesen <markjole...@gmail.com> wrote:
> > 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.
> >
> > On Fri, Feb 3, 2017 at 6:22 AM, Alain Mouette <ala...@pobox.com> wrote:
> >>
> >> 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
> >>
>
> ------------------------------------------------------------
> ------------------
> 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