Hello Gregg, creating an interface for existing communities (yahoo, google, etc...) is not easy, since they have interfaces user-oriented (I know only Google exposes web services to to the engine from other apps, but Rebol does not support web services... or better: basically it supply the instruments to support WS, but SOAP/WSDL are not so easy (I use them), and nobody created a library to use such protocols).
I think, if a project will start, we could buy a domain and a space, creating a new service (yahoo-like) from zero (php? java?), and creating a full-featured interface in Rebol and not HTML :-D (I opened a forum but... nobody goes there :-( even if I created specific area to discuss about this project; more: RSS can be used only to read information... but there is no way (RSS-like) to send info that we can use in Rebol. Don't you like existing RSS programs? Which are the problems you found? What are the features you don't like? etc... --Alessandro On 5/24/06, Anton Rolls <[EMAIL PROTECTED]> wrote: > > David, > > This looks really, really easy to make in rebol. > Don't wait any longer! I am sure you can > create a little function which takes a > variable number of strings in a block > to use for the text of buttons. > > request-choice: func [ > choices [block!] "block of title text followed by string,block pa= irs to use > for each button's text and action" > /local spec window > ][ > spec: compose [h1 (choices/1) across] > foreach [text action] next choices [repend spec ['button text joi= n action > 'hide-popup]] > ?? spec > inform window: center-face layout spec > ] > > choice: none > request-choice ["Choose one:" "apples" [choice: 'apples] "oranges" [choic= e: > 'oranges] "pears" [choice: 'pears]] > ?? choice > > For inspiration, also see: > > source request > > Anton. > > > put simply,its a tools problem, has been for years. > > > > the fact is , you can tell the average person how good rebol is and > > can be a great asset to their tool kits, but if there are no basic > > GUI tools you can point them too, to try, they will not give it a > > second look, never mind for instance, take the basic GUI front-end > > and use that as the basis for thier next great tool and expand it. > > > > for example from the requestchoice and requestfile GUI amiga days > > my friend made some base scripts that were expanded over time > > infact id like to use this format/style of scripting again with rebol > > once someone makes a good working base. > > fully working amiga cli command requestchoice example > > > > this form of self contained scripting worked great for linking > > shell/cli apps together once we had a good base to work from > > shame no ones done something like this a a full working package > > for rebol GUI front ends etc, perhaps one day, although iv been > > waiting a very long time so far.............. > > --------------------------------------------------- > > .key file > > ;$VER: SID_VIEW_GUIDE GUI > > failat 9999 > > > > ;- Setup Programs & paths > > Set Read=3D"Run SYS:Utilities/AmigaGuide" > > Set HedEd=3D"Run work:Editors/Heddley" > > Set GoCed=3D"work:editors/ceded" > > ;- End Setups > > > > if exists env:edosguide > > set req=3D$edosguide > > skip skipreq > > endif > > > > Lab start > > set req=3D`RequestChoice "SID_VIEW_Guide GUI" "Select type to > > read*N<file>" "Exit" "Read" "HEDDLEY" "Edit"` > > > > if $req eq "1" > > Skip Exit > > Endif > > > > lab skipreq > > if $req eq "2" > > $Read "<file>" > > endif > > > > if $req eq "3" > > $HedED "<file>" > > Endif > > > > If $req eq "0" > > $goced "<file>" -s > > endif > > > > if exists env:edosguide > > skip exit > > endif > > > > ;optionally ask and store a variable so as not to keep asking > > ;set storeq=3D`RequestChoice "SID_Guide GUI" "Use as default for > > this session" "Yes" "No"` > > ;if $storeq eq "1" > > ; setenv edosguide=3D$req > > ; skip exit > > ;endif > > > > ;skip back start > > Lab Exit > > --------------------------------------------------------- > > -- > > Best regards, > > david mailto:[EMAIL PROTECTED] > > -- > To unsubscribe from the list, just send an email to > lists at rebol.com with unsubscribe as the subject. > > -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
