Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 21 Jun 2018, 00:39
All times are UTC - 4
 Forum index » Off-Topic Area » Programming
Gtkwialog Development Thread continued
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [4 Posts]  
Author Message
wiak

Joined: 11 Dec 2007
Posts: 857
Location: not Bulgaria

PostPosted: Sat 09 Jun 2018, 00:08    Post subject:  Gtkwialog Development Thread continued  

Okay, I start a new thread to continue this work. I don't want to regenerate the largish number of usage examples and information I posted on the read-only old thread, so please refer to that for documentation only now.

Only technical discussions related to gtkwialog (and not gtkdialog) on this thread please. Also I would be grateful if you please only contribute positively (which includes bug reports and performance/functionality issues), or don't post to this thread at all is fine.
In particular, if you have something against gtkwialog, please express such opinions in threads of your own elsewhere, which I won't be responding to.


I mainly use all threads like this one for my own documentation purposes, though I also keep backup copies in case anything ever happens to the forum.

I won't be adding to this first new post for a while though. Having now some experience at converting Puppy apps to work on dash systems via gtkwialog, I'm adding some extra functionality to make the conversion process even more convenient (whilst keeping it 100% backwards compatible with the functionality I previously added and with legacy gtkdialog). Come back to this thread in a few weeks time maybe, if you are interested in the work, because I expect it to be at least that long before I publish more about it.

The final or should I say first ready to distribute version only will be added to DebianDog Organisation gtkwialog repository (which at that stage will include binary and source code) along with hopefully many converted traditional Puppy apps, either via their original author's permission, or forked if necessary to allow them to run when dash is the underlying system shell.

I won't be provided links to any test binaries this time out since that turned out to be a mistake. So downloads of any sort for testing only or actual distribution will only be available once I am myself satisfied with the final results of my own testing and have updated the github repository accordingly. The prealpha binaries, which were for early testing only, and not to be considered in any way as official releases, remain on the old locked thread. I would like to remove these now so please bear that in mind.

Work will also now recontinue in the temporarily suspended Precord and Cast2chrome, which depend on gtkwialog.

wiak

Last edited by wiak on Sat 09 Jun 2018, 00:44; edited 8 times in total
Back to top
View user's profile Send private message 
darry19662018

Joined: 31 Mar 2018
Posts: 184

PostPosted: Sat 09 Jun 2018, 00:27    Post subject:  

Wiak I wish you the sincerest best with this - your attention to detail and wanting perfection in your work is inspiring.
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 857
Location: not Bulgaria

PostPosted: Mon 11 Jun 2018, 00:43    Post subject: mixed action modes now allowed
Subject description: in latest development version of gtkwialog
 

I've expanded the [-a] and [-b] mode syntax of next version of gtkwialog to be eventually published to allow mixing of these blocking and non-blocking modes in the one dialog and some of the addition also simply for the convenience of the programmer. In particular, in present testing version:

Inside the <action>commandstring</action> tags the programmer can now use -b at start of any commandstring to indicate -b mode is to be used for that particular action (even if main dialog is specified as being in -a mode or in legacy gtkdialog mode). Similarly, -a can alternatively be specified at start of any such commandstring.

In addition, simply as a convenience, the programmer can use

-bs to indicate use -b mode but interpret the rest of the commandstring with /bin/sh -c
-bb to indicate use -b mode but interpret the rest of the commandstring with /bin/bash -c

-as to indicate use -a mode but interpret the rest of the commandstring with /bin/sh -c
-ab to indicate use -a mode but interpret the rest of the commandstring with /bin/bash -c

These are tiny changes that involve hardly any additional code, and full backwards compatibility with previous gtkwialog operation is being guaranteed, as is 100% compatible legacy gtkdialog mode; accordingly, gtkdialog can always simply be made a symbolic link to gtkwialog, which means that older gtkdialog Puppy apps will run 100% exactly as they did under legacy gtkdialog.

None of these very newest additions to my latest gtkwialog under development are set in concrete however. I'm just indicating my strong intention that the -a and -b mode behaviour of original gtkwialog testing will remain always stable.

In addition to these under-development versions I plan to experiment with a gtkwialog version that includes UNIX system message queues mode and also TCP/IP socket capability (including UDP connectionless and TCP connection-oriented) to allow remote client/service control, amongst other uses, where that is desired. I haven't decided yet if that enhanced version will ever be published for distribution.

wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 857
Location: not Bulgaria

PostPosted: Tue 19 Jun 2018, 06:48    Post subject:  

Just a progress report to myself and as a note in case anyone wondered if I was still working on gtkwialog development. Yes, I am.

Currently implemented mixed (legacy, -b, -a) mode dialogs, so programmer can pick and choose which mode they want for different <action>commandstrings in their dialog (previously a dialog could only use either a, b or legacy mode; not a chosen mix).

At least temporarily dropped the convenience idea: -bs, -bb, -as, -ab; think the idea is a bit messy, and certainly not essential; however, I'm still thinking about it.

Actually, in theory, I think I know how to make a version with an option that could run legacy gtkdialog apps, on dash system, without any mods at all (aside from using the appropriate as yet unwritten new gtkwialog mode) but I'm not sure there are enough good legacy gtkdialog apps to make so much legacy support worthwhile; better really to write/re-write new apps... and avoid legacy mode altogether since that dream-mode actually involves quite a lot of addon (messy) code that I don't actually like to support... better to use -a, or -b modes in practice.

In the meantime, I have figured out how <input>commandstring works; was actually easy but hadn't looked at it in detail before. So, in theory, I can now arrange -a and -b gtkwialog modes to work there now too (final piece of puzzle concerning getting gtkwialog working via bash -c on dash-based systems); only problem is that there are a lot of source code files involved in the change, so will take me a while to implement, assuming I get round to it.

Realistically, gtkwialog may be resisted and unwanted by many and never adopted other than by myself, so maybe not worth too much effort on my part, despite a certain amount of interest that the original test version generated. Current version actually fulfills my own needs (which is all I intended it for) despite not having that bash-related <input> handling code implemented, so it depends how enthusiastic I feel about spending more hours on this to complete that part.

I understand now that I probably made a mistake originally trying to develop forked gtkwialog on this forum, which resulted in some reactions that certainly limited my own enthusiasm too. I just had an old habit of recording my dev work on this forum, as an archive as much as anything, and should really have used github or similar instead and not involved Puppy forum at all. Wish I could delete the prealpha testing-only versions still though. Nevertheless, I'm tempted to 'fix' the <input>commandstring mode, despite the number of files involved, if only for the sake of some completion. But otherwise, current gtkwialog modes are sufficient for my own (slightly modified) programs to function on dash-based systems too.

Probably won't post any more about this now though, until and if I complete it to my satisfaction, which may be soon or may be a long time away.

wiak
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [4 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Off-Topic Area » Programming
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0380s ][ Queries: 14 (0.0054s) ][ GZIP on ]