AltME groups: search

Tests are running fine on Windows with master branch. I've tested 
them successfully with linux/v0.3.0 too. Will tray again with linux/master.

Gabriele, can we get tray enabled for the rebol.dll ?

Nice to hear about the grid. Sys-tray support in View can be done 
with the system port. I think Carl did a demo script.

Reichart, I know this is on the "list" but do you think we'll ever 
see the Altme "minimize to the system tray/little window notifying 
one of a message." for windoze? My MS compadres insist that they 
need it. Bill Gates must put some kind of addictive substance in 
icon tray. But I guess once you get used to being notified that way 
it's a hard habit to break.

Ingo: on the 'system port, no official doc. Some info:
rebolist thread (rebol.org) :

    http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-display-thread.r?m=rmlMYFJ
'signal demo script :

    http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-display-thread.r?m=rmlNFFJ
drag-and-drop demo script: 

    http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=sys-port-drag-accept.r
systray demo script:

    http://compkarori.com/vanilla/display/System+Tray+Functionality

It's different for each OS. For MS-WIn, there is:
    get-modes system/ports/system 'system-modes
    ;== [window winmsg tray endian]
where:
    'window : REBOL console window handle,
    'winmsg : OS message block,
    'tray : systray definition block
    'endian : CPU byte order ('big or 'little)

For Linux:
    get-modes system/ports/system 'system-modes
    ;== [signal read-fd write-fd except-fd signal-names endian]

Right. A lot of software does the split process thing nowadays, sometimes 
with the GUI running in the tray (or whatever the OS version if that 
is).

That usually works by having the core service run on its own, the 
the tray app starting at user login, or on demand.

Has anyone made a /View tray app that has no default window other 
than the tray app, and maybe a options dialog?

You can start a view app in the tray ...

How can I minimize a View window to a tray-icon only?

This I grabbed in Dec 2002
Rebol [
	title: "little custom tray exapmle"
	author: [cyphre-:-seznam-:-cz]
]

set-tray: does [
set-modes system/ports/system [
	tray: [
		add main [
			help: "Just some help line"
			menu: [
				desktop: "This is my tray"
				bar
				test: "test item"
				bar
				quit: "Quit"
			]
		]
	]
]
]
system-awake: func [port /local r][
    if all [r: pick port 1 (r/1 = 'tray)] [

        if any [(r/3 = 'activate) all [(r/3 = 'menu) (r/4 = 'desktop)]][

  view/new/offset layout [banner "you clicked the tray button 1"] random 
  200x200
        ] 

        if all [(r/3 = 'menu) (r/4 = 'test)] [view/new/offset layout [banner 
        "you clicked the tray button 2"] random 200x200]
        if all [(r/3 = 'menu) (r/4 = 'quit)] [quit]
    ]
    return false
]
system/ports/system: open [scheme: 'system]
append system/ports/wait-list system/ports/system
system/ports/system/awake: :system-awake 
set-tray
wait []

Do that, then look to your system tray for the rebol icon.

For Always-on-top, nothing else than digging in Win32 API !!

For system tray, may be this example can help understanding its usage

http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=simple-system-tray.r

Ssytem tray is availbale in view 1.3 (no license needed)

I have a system tray dialect in the script library - %simple-system-tray.r 
- if it's helpful.

On antons page was an issue regarding 'TRAY ..man o man..have I seached 
long for that info ;-) finaly found it too!!! great !!!

Rebolinth, glad you found it useful. I don't understand what the 
'TRAY issue was, though.

ah ok.. but didn't find "tray" on my page... ?

Thanks - already found!

What I am missing is what else words I could use for tray controls 
and messages received?
F.ex.
Can I activate tray meny un left click?
Is it possible to make submenus for systary icons?

Is it possible to change tray icon?

One that appears in the lower right corner of the screen, raises 
out of the system tray area and then fades

I mean system tray

Hi! How to upgrade rebcmdview with newer version of Rebol?

I would like to make an app with tray icon and menu, but the original 
rebcmdview shows:
** Script Error: Invalid argument: tray
** Where: set-tray
** Near: set-modes system/ports/system compose/deep/only [
    tray: [
        add main [
            help: getTextByLang "Truck messaging"
            menu: (menu)
        ]
    ]
]

While the newer rebview works good with tray, but lacks ODBC support.

I have one slow connection to nySql database by using ODBC. Why operations 
on that pauses also my face events? If I have many sql queries to 
be done than interface of my application stays unresponsive ( no 
reactions on any clicks on buttons, tray menus etc.)

What I found was - RAMBO Ticket #3593.
Is it that case?

I have simple interfaces, that normaly is unviewed, but I have tray 
incon. And in background there is two database connections.

anyone know how to change the system tray icon dynamically?  by this 
I mean... the winapi calls which play around with that?

REBOL []

; r/3 = 'activate = left-click
; r/3 = 'activate = rt-click+menu-item-sel

hex: func [
    {Returns the base-10 value of a hexadecimal number.}
    value [integer! string! issue!] "A hexadecimal number"
][

    ; Convert to an issue first, so integers can also be translated.
    to integer! to issue! value
]

make-elements: func [name count type /local result][
    if not word? type [type: type?/word type]
    result: copy "^/"
    repeat i count [
        append result join name [i " [" type "]" newline]
    ]
    to block! result
]

NOTIFYICONDATA: make struct! compose [
    cbSize  [integer!]
    hwnd    [integer!]
    uId     [integer!]
    uFlags  [integer!]
    uCallBackMessage [integer!]
    hIcon   [integer!]
    (make-elements 'szTip 64 #"@")  ; CHAR
] none
NOTIFYICONDATA/cbSize: length? third NOTIFYICONDATA

;change at third NOTIFYICONDATA 25 "New ToolTip!"
;probe NOTIFYICONDATA
;halt

;constants required by Shell_NotifyIcon API call:
NIM_ADD:     hex 0
NIM_MODIFY:  hex 1
NIM_DELETE:  hex 2
NIF_MESSAGE: hex 1
NIF_ICON:    hex 2
NIF_TIP:     hex 4
WM_MOUSEMOVE:       hex 200
WM_LBUTTONDOWN:     hex 201  ;   'Button down
WM_LBUTTONUP:       hex 202  ;     'Button up
WM_LBUTTONDBLCLK:   hex 203  ; 'Double-click
WM_RBUTTONDOWN:     hex 204  ;   'Button down
WM_RBUTTONUP:       hex 205  ;     'Button up
WM_RBUTTONDBLCLK:   hex 206  ; 'Double-click


;Public Declare Function SetForegroundWindow Lib "user32" (ByVal 
hwnd As Long) As Long

lib: load/library %shell32.dll

Shell_NotifyIcon: make routine! compose/deep [
    dwMessage [integer!]
    pnid      [struct! [(NOTIFYICONDATA)]]
    return:   [integer!]
] lib "Shell_NotifyIconA"


my-hwnd?: does [second get-modes system/ports/system [window]]

set-tray-tooltip: func [struct string] [
    change at third struct 25 string
    struct
]



system-awake: func [port /local evt][
    if all [evt: pick port 1  (evt/1 = 'tray)] [
        status/text: mold evt
        show status
;         if any [
;             (evt/3 = 'activate)
;             all [(evt/3 = 'menu)  (evt/4 = 'desktop)]
;         ] [
;             if not desktop-loaded [
;                 link-exec-start-desktop/force
;             ]
;         ]
;         if all [(evt/3 = 'menu)  (evt/4 = 'quit)] [quit]
    ]
    false
]

system/ports/system/awake: :system-awake
append system/ports/wait-list system/ports/system

view layout [
    style button button 200
    button "Add Tray Menus" [
        set-modes system/ports/system compose/deep [
            tray: [
                add main [

                    help: (rejoin ["REBOL/Link" any [""]]) ; tooltip

                    menu: [test: "Test" desktop: "Start Desktop" bar quit: "Quit"]
                ]
                add other [
                    ;help: (rejoin ["REBOL/Link" any [""]])
                    menu: [test-2: "Test-2" bar quit-2: "Quit-2"]
                ]
            ]
        ]
    ]
    button "Remove Tray Main Menu" [
        set-modes system/ports/system [
            tray: [remove main]
        ]
    ]
    button "Remove Tray Other Menu" [
        set-modes system/ports/system [
            tray: [remove other]
        ]
    ]
    ;button "Change Tray Other Menu" [
    ;    set-modes system/ports/system [
    ;        tray: [
    ;            change other [
    ;                help: "New Help!"

    ;                menu: [test-3: "Test-3" bar quit-3: "Quit-3"]
    ;            ]
    ;        ]
    ;    ]
    ;]
    button "Modify Tooltip" [
        nid: make struct! NOTIFYICONDATA none
        nid/hwnd: my-hwnd?
        nid/uid: 1
        nid/cbSize: length? third nid
        nid/uFlags:  NIF_TIP  ; NIF_ICON
        ;nid/hIcon:
        ;nid/szTip:  "New ToolTip!^@"
        set-tray-tooltip nid "New ToolTip A!"
        ;print mold third nid
        res: Shell_NotifyIcon NIM_MODIFY nid
        print [res to logic! res]
    ]
    button "Modify Other Tooltip" [
        nid: make struct! NOTIFYICONDATA none
        nid/hwnd: my-hwnd?
        nid/uid: 2
        nid/cbSize: length? third nid
        nid/uFlags:  NIF_TIP  ; NIF_ICON
        ;nid/hIcon:
        ;nid/szTip:  "New ToolTip!^@"
        set-tray-tooltip nid "New ToolTip B!"
        ;print mold third nid
        res: Shell_NotifyIcon NIM_MODIFY nid
        print [res to logic! res]
    ]
    button "Unview" [unview]
    status: text 200
]



free lib

Is there the equivalent of system tray functionality in Linux?

On gnome, you have this system tray which on Ubuntu is at the top 
right.  Anyone know how to place an icon there as in windows?

Little goodie for Windows users: http://www.colellachiara.com/soft/Misc/clips.r


It will stay in your system tray and keep track of your clipboard 
(remembers the last 5 clips). They are saved in a file so you get 
them back across reboots. You can also add notes that won't get pushed 
out from the clips. Selecting a note or a clip will copy it back 
to your clipboard so that you can paste it wherever you want.

Gabriele: got this when i tried clips.r    Script Error: Invalid 
path value: awake
** Near: system/ports/system/awake: func [port /local msg] [
    while [msg: pick port 1] [
        if find/match msg [tray main ...

It is my pleasure to announce, that Cyphre was contracted to bring 
what I regard latest limiting factor for RebGUI database experience 
- a grid. The grid should support following features - visible/non-visible 
columns, both vertical/horizontal scrolling, keyboard support, programmable 
navigation, tri-state columns sorting, possibility to put other styles 
in cells. Expect it being in the middle of capabilities of RebGUI 
table, and Henrik's grid. The grid should be also easily portable 
to VID. The license - BSD.


Other things Cyphre will look into with regards to Rebgui is, how 
to make RebGUI a bit more pretty, centralising other things or simply 
allowing gradients for tabs etc. That is subject to change.


On non RebGUI front, we should have better sys-tray support under 
Windows, probably via .dll ....

The time-frame is three weeks from today. Stay tuned!

It's a tray icon ... I don't think there is a popup now in windows 
.. at least I hope not.

Adobe AIR beta provides additional features to enhance operating 
system integration:

    * Background applications

    * System tray icon (Windows) / Dock bar bounce (Mac OS X) notification
    * Default windows menus
    * Z-order control for native windows
    * Bitmap drag-and-drop support
    * Customization of program folder entry
    * New Mac and Windows install location

Does anyone have an example of how to pop-up a little window in the 
Window's system tray? I've seen the system tray examples but I want 
to create a "reminder" like when Outlook does when gets a new email, 
etc.

Here's one that may be handy for those looking for a system tray-like 
feature

Actually, the VLC player (free) lets you do that, but you have to 
provide it the link to the stream, whereas with MySpeed, embedded 
videos play at a speed controlled by a little tool tray UI

keep in mind that R2 already supports the system tray in windows, 
and the way it does could be easily used for the same thing on linux 
kde or gnome.

in short: Factor is very interesting language but I was amazed at 
how productive I was with rebol + rsp, I need PDF: factor has some 
deprecated bindings to c lib for generating pdf-s, rebol has a dialect 
for that, I need to run in on a desktop standalone: factor can run 
standalone but is more heavyweight, cheyenne server starts and shows 
icon in tray "before I even click it" , I need a tray icon too for 
my app, I found example of it already and it works, in factor something 
like this doesn't exist yet ..

and many clients DONT want custom guis... they want OS look and features 
which are OS native, like D&D, spotlight menu integration on OSX, 
system tray on windows, etc etc.

with postscript you probably can't control what tray you need to 
print from...?

I showed this REBOL postscript thing to some work colleagues, and 
they asked about support for tray selection on the printer (you typically 
have different paper in each tray). Does anyone know, if it's possible 
to choose tray from postscript?

Another thing is paper type selection. With this you tell what paper 
type, you need, and the printer know, what type of paper is in each 
tray (it's possible to specify that on the printer). Paper type selection 
has some benefit over tray selection.

I didn't figure it out so I had to use the tray selector in the windows 
printer driver to do this.

It seems, the PostScript operator 'setpagedevice' can be used to 
set MediaType to e.g. 'Plain', 'Letterhead' or 'Preprinted' etc.. 
It's something like that, I'm after. That's better than specifying 
tray, but that can be done also. I'll investigate further and put 
it in the dialect.

REBOL PostScript Dialect v. 0.4.0 released: http://home.tiscali.dk/john.niclasen/postscript/postscript.r

Documentation here: http://home.tiscali.dk/john.niclasen/postscript/postscript.html

Added MediaType, ManualFeed and MediaPosition to control paper selection 
(tray). Also made Courier font ISOLatin1 encoded. And better PS comments 
in the output according to PostScript Language Document Structuring 
Conventions Specification.

It's now possible to produce PostScripts documents, where the first 
page is taken from e.g. tray 2 holding Letterhead paper and the rest 
from e.g. tray 3 holding Plain paper.

A couple of useful PS links:

How to generate portable Postscript: http://alumni.media.mit.edu/~szummer/postscript/

What is the physical size of the page?: http://www.postscript.org/FAQs/language/node64.html

How to use Adobe PostScript language files properly.: http://www-cdf.fnal.gov/offline/PostScript/AdobePS.html

(Look under "Paper bin, tray, size, feed mode, etc. selection", where 
you also find a link to:)
PostScript Sins: http://www.byte.com/art/9508/sec13/art3.htm
Gripes: http://www.cs.wisc.edu/~ghost/doc/gripes.htm

tray

tray removing this line at the end of mod-rsp: insert tail out "; 
HttpOnly"

Works nicely too.. sit in sys tray

fyi - in R0914 the example for the set-tray is a bit clearer so you 
can add some of the samples or other actions aside from Quit to the 
set tray (right mouse) menu.

oops ...

>> do %cheyenne.r
Script: "Cheyenne Web Server" (19-Feb-2008)
** Script Error: NT-service? has no value
** Where: boot

** Near: if all [NT-service? not flag? 'service] [set-flag 'tray-only]
>>

New Cheyenne 0.9.19 beta version available for testing at : http://cheyenne-server.org/tmp/cheyenne-r0919.zip


Tested only on Windows  (my Linux image network has currently some 
issues).

ChangeLog (diff-ed from last test version) :


 o RSP: an HTTP redirection in 'on-page-start won't evaluate the page 
 script anymore.
	

 o CGI: mezz function READ-CGI now patched to be compatible with Cheyenne. 
 That's
	  the right way of reading POST data in REBOL CGI scripts.
	  
	o RSP: fixed a bug in session/add when setting a block! value.
	

 o Task-handler: fixed a network error on first packet read (high 
 load + fast hardware).
	

 o Task-handler: TCP keepalive mode activated (test workaround half-closed 
 connections).
	
	o Task-master: 
			o 'no-delay mode removed and replaced by 'keep-alive mode

   o now forks a new process as soon as one dies (not waiting for a 
   new request)

   o fix a long standing bug in queued job module name mismatching (can 
   happen under extreme load)
			o minor code cleanup
	

 o Uniserve: 'no-delay TCP network mode now switched off for all connections. 
 Fixes a

   stability issue on Vista and probably on UNIX with very high load.


 o RSP: fix a bug in 'decode-multipart when there's no file received.
	

 o UniServe: new logger service. Now all info or error logs, and debug 
 messages from

   CGI/RSP scripts are written in %trace.log. Additionnaly, you can 
   now log messages
	  using :
	  
	  		- debug/print msg 	; msg [string!]
	  		- debug/probe value 	; any mold-able value
	  		- ?? word		; works like REBOL's '?? function
	  		- ? msg		; alias for debug/print
	  

 o RSP: in debug mode, page generation time and SQL queries stats 
 now added at bottom
	  of pages.
	  
	o RSP: error in events from %app-init.r now logged.
	

 o RSP: fix a rare RSP freezing issue when an error occurs in %RSP.r 
 (for example, by
	  a user script that breaks RSP sandbox).
	  

 o RSP: sanboxing now protects from Exit/Return/Break calls made outside 
 of a
	  function context.
	  
	o RSP: %misc/rsp-init.r file removed.
	

 o RSP/CGI: New config keyword added in global sections : 'worker-libs. 
 It lists the

   librairies to load when a worker process is started. An optional 
   'on-quit section can

   be added to call cleanup code when the process quits. Examples :
	  
	  		worker-libs [
				%libs/mysql-protocols.r
				...
			]
		or	
			worker-libs [
				%libs/mysql-protocols.r
				...
				on-quit [
					%/libs/free-resources.r
				]
			]
	

 o Task-master: now you can reset all worker processes without stopping 
 Cheyenne. This

   is usefull when you need to force non-RSP/CGI files reload (helper 
   scripts, 3rd party
	  librairies,...). 
	  
	  	Usage:
	
			Windows : tray icon -> Reset Workers
		

   UNIX : kill -s USR1 <pid>	(<pid> is Cheyenne's main process ID)
	 
	 

  o Added a -w command line option to set the worker processes number. 
	 
	   	Usage:
	   
	  		$ cheyenne -w <n>		(n [integer!] : CGI/RSP process number)
	   

    Use -w 0 to help debug CGI/RSP code by resetting worker processes 
    after each request.
	   (it's like calling "Reset workers" after each request).

How about instead just show in the system icon tray an information 
menu item to show what port it is listening on?

I've just started testing the latest cheyenne out of SVN.   No matter 
what port I run it on, it always says it is runing on port 80 when 
you hover over the system tray.

1/8-10:32:43.093-[boot] Cmdline args : -vv
1/8-10:32:43.093-[boot] Processed    : [verbosity 2]

1/8-10:32:43.093-[boot] Boot flags   : [no-screen verbose tray-only]
1/8-10:32:43.093-[boot] Data folder  : %./

1-Aug-2009/10:34:38-7:00 : make object! [
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'set-modes
    arg2: 'target
    arg3: [file! url! block! port!]
    near: [set-modes sys remote-mode]
    where: 'set-tray-remote-events
]

Latest now works on Windows 7 but still fails on Windows 2003

1-Aug-2009/11:54:59-7:00 : make object! [
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'set-modes
    arg2: 'target
    arg3: [file! url! block! port!]
    near: [set-modes sys remote-mode]
    where: 'set-tray-remote-events
]

'set-tray-remote-events is called only in 'do-tray-app which is called 
when Cheyenne is running as a service to install a standalone version 
of the tray icon with menus (for remote control of the Cheyenne service).

Ok, I right clicked on cheyenne in the system tray and set it as 
a service.  It exited immediately from the system tray, and i could 
not run it again wihtout the above error.

I looked in the running processes and don't see anything.  I think 
I'll have to reboot the windows 2003 server.

I'm seeing some odd root kit like behaviours ... cheyenne is clearly 
serving up pages,, but the icon is gone from the system tray and 
it does not appear in the processes list in the windows task manager!

Henrik: on Windows, you have a help message when the mouse pointer 
is over Cheyenne's tray icon. From RSP script, just use :

>> p: open http://localhost
>> p/locals/headers/server
== "Cheyenne/0.9.20"

rigth click on the chyenne icon in the system tray

Graham, I'm running Cheyenne on a remote headless Linux server, so 
no system tray. :-)

extend tray icon menu from mod : good idea.

Dunno .. the tray menu doesn't say

I used encmd now ... but it still appears in the system tray.  I 
right click on the system tray icon, and use "run as a service" and 
then it stops running

SVN r96 -> r103 (most of new features were suggested by Carl)  


FEAT: encapped Cheyenne binaries now returns 0 (or, in case of panic, 
a REBOL error code) on exit

FEAT: (UNIX) Added a new command line option: -V or --version. Displays 
Cheyenne's version, then quits.

FEAT: (Windows) Cheyenne's version is now displayed in the tray icon 
help message.

FEAT: RSP debug mode extended to display tail of trace.log file using 
a new [show trace] button.

FEAT: RSP debug bar look improved, menu horizontal alignment fixed, 
direct link to RSP API online
documentation added.

FEAT: RSP errors are now displayed in an overlay popup instead of 
being inlined in the page.

FEAT: RSP debug bar javascript code footprint reduced to a single 
object: rspdbg (avoids polluting global namespace)

FEAT: new RSP API function: debug. Switches the debug mode on or 
off, for the current RSP script.

FEAT: new API function: debug?. Returns TRUE if debug mode is active.

FEAT: 'debug config keyword definition extended to accept an optional 
block of parameters.

FEAT: RSP session/start now returns the session/active? flag as result.

FEAT: (UNIX) Added a new boot option: -h or --help. Displays the 
command line syntax help and quits.

FEAT: Improved RSP function 'validate to accept default values for 
optional parameters when using
the /full refinement.

FEAT: now plain REBOL scripts can also be run by the RSP engine! 
(see www/show.r)

FEAT: new RSP API function: emit. Does a REDUCE on its argument before 
APPENDing to response/buffer.

FEAT: added new RSP syntax for emit-action : <%? ... %>. Does the 
same as 'emit, but inlined in a
template page.

FIX: (Windows) improved child processes termination with a more graceful 
method using JobObject API

FIX: (UNIX) optimized child processes termination using a kill() 
routine! wrapper instead of CALLing the shell command
FIX: flush HTTP logs in cache on exiting.

FIX: mod-userdir was still commented in config file modules list, 
disabling user/group keywords in httpd.cfg

More info on the new RSP functions in changelog.txt file.

I ran a test of Cheyenne as a service on Windows 7 and have managed 
to lose the system tray icon to turn it back to running as an application. 
Any suggestions on where to find it?

This what I did in total:
1. Run cheyenne as administrator from my user account.

2. Use the system tray icon to change Cheyenne to run as a service.
3. Log-off.
4. Check  Cheyenne was runnning.

5. Log back in to my user account - no Cheyenne icon in the system 
tray.
6. Log into the Administrator account - it wasn't there either.

Peter: When Cheyenne is in Service mode, the tray icon app is a second, 
separated instance of Cheyenne. If Win7 is not starting the second 
instance, you need to start it manually to get the tray icon.

I'm getting a *very* weird problem launching cheyenne from win7.


using a clean download of the latest build sources, if I try to start 
up the cheyenne.r by double-clicking on it in windows, it fails. 
 

no tray icon appears, the rebol process is running buts its dead 
(no pages are served, and no workers are launched).


if I try to run it a second time, I get the console which tells me 
it can't open the rconsole and logger ports (so cheyenne actually 
did start)., but the "no response" flag appears on the window title 
and its as dead as the first instance (I even get the busy mouse 
cursor treatment). 


but if I start it from the command-line, using the exact same command-line 
that I see in the task manager, I have no problem!


to make this even more strange, dragging the cheyenne.r script icon 
on the rebol.exe icon, launches cheyenne without any issues!

launching it from my editor's automated script launching setups also 
works without issues.

all of these show the exact same command-line in the task-manager 
(which includes the -qs rebol flags).

note, I am *not* running cheyenne as a service.

Questions:
1) can any one else replicate this (am I going mad ?  ;-)
2) why does this happen?
2) can this be solved?

Even if I stop the service (or Quit from tray menu, if runs as app) 
one of the Cheyenne processes stays in the background.