Re: LaunchPad 02
- Posted by Al Getz <Xaxo at aol.com> Apr 08, 2006
- 476 views
Antonio Alessi wrote: > > Al Getz wrote: > > > > Hi again Antonio, > > > > I'm beginning to see what you mean now. > > The only problem i see so far is that if the Launcher isnt used > > to open EVERY program (ie some are already open and we use a 'capture' > > command from the Launcher) then the Launcher will not know what *files* > > have been opened with the given programs. This doesnt matter when we > > go to close the programs (with the "close all" button) but it does > > matter when we go to reopen all the programs with their respective > > files. Again, the example i gave before: > > open Notepad Myfile.txt > > we know the program is Notepad and the file is Myfile.txt, but > > if this is already open we dont know what file has been open. > > (OK maybe with Notepad we can read the title bar, but this isnt > > always the case with other programs). > > > Yes, I know this problem, but there may be two cases: > > 1. the application is able to restore the last setting, loading its > own last files on startup, with no need to tell it what to do (eg. my > program does it, remember my old problem about sorting files on load?); > > 2. the LaunchPad can prompt the user for an entry, if it does not know what > > parameters to start with, possibly accepting a dropped link; this can help. > I don't know Windows enough to find out where and how to get such info about > > the running programs, if any, but perhaps somebody could answer to that too. > Probably somewhere in the Registry .. > > > The other part is what if the program opens two or more files? > > There must be a way to do this too, so if there isnt already > > a button to open that 'minor group' then how do we know what > > file to use, unless of course we resort to typing the user data in > > to the button edit box? I wanted to minimize typing on the users > > part. > > > > This should mostly pertain to the point 1. above, anyhow in such case > I consider this a problem of the applications (the user can choose), not our. > I agree with you on minimizing, since this is the scope of the LauchPad, > however the re-opening has not always to start with the same targets; > if yes, a single typing by the users is not the worst solution against > the global advantages of getting more windows ready at a time. > On the other side with many programs (eg. Photoshop) there is no way > to start loading certain files, so this could not lay as the main goal. > > .. .. > > > Does all this make sense? > > All that that exist make sense, it's our to try to disclose it. > > So, just try and see! > > antonio > > > > > > Al > > > > > > My bumper sticker: "I brake for LED's" > > > > From "Black Knight": > > "I can live with losing the good fight, > > but i can not live without fighting it". > > "Well on second thought, maybe not." > HI Al, Hi again Antonio, Oh yes, some programs dont accept a command line target file. So you say Photoshop doesnt allow this either? That's too bad. I guess there is nothing that can be done about this problem. Most of the programs i make myself accept command line arguments that are file targets to load on opening. In fact, i think all of the programs i use frequently allow that. Yes perhaps allowing drag and drop to extend the button functionality would be good, so the user can drag files to be opened with the program too. Sounds good. All this new functionality would summarize as follows: Drag a .exe (or exw) file to create a button and get it's path (and working dir when possible) [this is already working] Drag another file on top of new button to create an 'open with' list. The list would be editable of course. At the same time as the drop is made to the new button, a 'close' list is also maintained. Perhaps right click and menu select "close all". Make the 'close' list editable too. Sound good? Take care, Al And, good luck with your Euphoria programming! My bumper sticker: "I brake for LED's" From "Black Knight": "I can live with losing the good fight, but i can not live without fighting it". "Well on second thought, maybe not."