Have a go at my ideas for it
Current snapshot (980601)
Download sourcecode for AmiLog (30.5.99) ![]()
No time for this baby. Giving it away to the public.=(
Please send me your ideas, flames, encouragement, and tips. I work much faster if I get your response.
Also changed the Zone gadget in the statuswindow (showing current selected Zone) from a passive TEXT_KIND to an interactive CYCLE_KIND (Cycle-gadget). This means that I can use more than the first Zone. Also got rid of a stupid debug function to fake line status (Online/Offline) and added a menu called Line Status (as shown to the right) where the user can either let it be automagic or manually set the status. Used by me for debugging and also later on for non modem calls.After some sleep I added some checks for open windows (before using them) which makes it almost stable =). I added Show/Hide functions to shutdown GUI and to open an initalize it. Almost ready. I'm fixing the docs now to come closer to be able to release this thingy.
When I choose to make AmiLog available for download it will be updated here very frequently (when I work with it). Hopefully it will be ready by summer... I hope. =).
Noticed that the doubleclick-thingy mentioned in 98-01-06 only was added to the Zones-list. Added it to the other two too.
All editing functions in the Zone-editor are made Add/Delete/Edit in Zones/Days/Times.
Added menulending so that the menus are visible and accessible in/from all Windows.
I also made the Load/Save Zones-items work which made me discover that the startcost didn't get saved (I'd actuallt noticed this earlier) and added it to the loading and saving routines.
The Zone editor also has been given some functionallity such as doubleclicking on an item in the listviews brings up the edit-window and when clicking on another item the edit-window gets updated with the selected item (the GUI is totally multitasking!!!).
Anyway, the Zone editor still lacks a bit more errorchecking but I'll leave it for now to more concentrate on the logging. Everytime the program is started the log must be read and the total time and cost must be calculated... this is currently not done. After that the task of making AmiLog a Commodity is planned, as well as making the GUI font adaptive (I've done that with another program so it is of no problem for me).
I wonder how important it is to make the GUI scalable? I don't see much benifit in it.
Hmm... I'm out of Coke and I'm awfully sleepy so this is it for this time...
I'm thinking more and more to centralize the strings used to interact with the user and thus making localizing a piece of cake.
I'm also thinking of a program much like a programmers diary which could output logs such as this.