@kas1e
@centaurz
Thanks for the information.
I did browse around and am close to what i wanted to do.
Not that i understand how applications point to their appropriate AISS toolbar icons.
To be practical:
What i was trying to do is use the AISS icons from within Gui4Cli scripts.
Gui4Cli scripts can be very sophisticated and cover practically all fields. So the set of needed toolbar icons can be as large as imagination goes.
Using existing Icons from applications is quiet straightforward
You only need those two lines
xICON L T iconname (path without the .info)
followed by the command sequence to be e?ecuted.
This works also for docky icons
I did have more problems with toolbar images (which i want to use most)
I could also use the toolbar images as in this demo script:
======
G4C
WINBIG 0 10 600 90 Icon.gc
SCREEN OrigynWebBrowser
WINTYPE 11110001
xONLOAD
Gosub #this Default
xONRELOAD
Gosub #this Default
xONCLOSE
GuiQuit #this
xROUTINE Default
LoadImage datas:AISS4.9/Images/home home OrigynWebBrowser
LoadImage datas:AISS4.9/Images/nav_west left OrigynWebBrowser ;NOREMAP
LoadImage datas:AISS4.9/Images/nav_east right OrigynWebBrowser ;NOREMAP
LoadImage datas:AISS4.9/Images/stop stop OrigynWebBrowser ;NOREMAP
LoadImage datas:AISS4.9/Images/reload reload OrigynWebBrowser
LoadImage datas:AISS4.9/Images/addressbookadd _add OrigynWebBrowser
GuiOpen #this
Image 0 0 left
xArea 0 0 20 20 NONE
EzReq left Ok var
Image 20 0 right
xArea 20 0 20 20 NONE
EzReq right Ok var
Image 40 0 stop
xArea 40 0 20 20 NONE
EzReq srop Ok var
Image 60 0 reload
xArea 60 0 20 20 NONE
EzReq reload Ok var
Image 80 0 home
xArea 80 0 20 20 NONE
EzReq home Ok var
Image 100 0 _add
xArea 100 0 20 20 NONE
EzReq add Ok var
xICON 140 0 datas:utilities/dockies/subdock.docky
EzReq "docky idon is presented OK too" OK var
xICON 200 0 datas:utilities/IBrowse/IBrowse
RUN "datas:utilities/IBrowse/IBrowse"
xICON 260 0 datas:utilities/OWB/OWBLauncher
RUN "datas:utilities/OWB/OWBLauncher"
xICON 320 0 datas:utilities/Netsurf/Netsurf
RUN "datas:utilities/Netsurf/Netsurf"
xICON 380 0 datas:utilities/Timberwolf/Timberwolf
RUN "datas:utilities/Timberwolf/Timberwolf"
=====
The result for the normal (.info) icons is not bad. The toolbar "icons" however are less sharp than when you use multiview. or as in OWB.
I then found that using the PNG_Icon_Editor i was able to transform a png file in tbimages: (in fact i redownloaded aiss49 and used the images there) in a directly viewable icon simply resaving it with a .info extension.
I then could use those icons more directly in Gui4CLi scripts and they also look sharper.
A typical 'toolbar icon' would then look like
xArea 0 22 20 20 NONE ; thes 2 lines are needed only if we want "local help"
GadHelp "GoBack" ; defines the local help
xICON 0 22 datas:AISS4.9/Images2Icons_/nav_west ; in fact pointing to a transformed nav_west.info vieuwable icon
;GadHelp "Goback" ; Local help does not work for icons
EzReq Goback Ok var ; a requester pops up as a dummy, here you would place the 'command sequence to be executed
See the grab in
http://users.online.be/AD/Icongc.jpgOne thing i regret is that PNG_Icon_Editor does not come with an arexx port, to automate the transformation from images to toolbar icons.
Maybe it can be done with shell scripts ?
Edited by JosDuchIt on 2010/6/15 11:59:24