passing a view as an URL
Locked
 
|
for those more knowledgeable:
I am looking to implement a basic WISWYG for widgets, so I can design widgets without setup up all the rest of the code. I want to pass a view string into the URL and have it show. content\control\render?widget='<view-map name="composeEmail" type="screen" page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' I should be able to pass this into a event that makes it part of a context and calls the rendering for it? any thoughts |
|
|
are you wanting to modify the view response or the widget? If it's the view response, you need to pass/handle a webapp parameter and a name parameter. If it's the widget, you will need to pass/ handle a resource-location parameter and a screen-name parameter. Also, lookout for characters to be escaped/encoded properly.
----- Original Message ---- From: BJ Freeman <[hidden email]> To: [hidden email] Sent: Monday, December 24, 2007 1:01:41 PM Subject: passing a view as an URL for those more knowledgeable: I am looking to implement a basic WISWYG for widgets, so I can design widgets without setup up all the rest of the code. I want to pass a view string into the URL and have it show. content\control\render?widget='<view-map name="composeEmail" type="screen" page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' I should be able to pass this into a event that makes it part of a context and calls the rendering for it? any thoughts |
|
|
so your saying the URL example I show may not work?
I figured to pass it into a event and have it parsed then sent on as a view like the controller does. Chris Howe sent the following on 12/24/2007 11:24 AM: > are you wanting to modify the view response or the widget? If it's the view response, you need to pass/handle a webapp parameter and a name parameter. If it's the widget, you will need to pass/ handle a resource-location parameter and a screen-name parameter. Also, lookout for characters to be escaped/encoded properly. > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:01:41 PM > Subject: passing a view as an URL > > > for those more knowledgeable: > I am looking to implement a basic WISWYG for widgets, so I can design > widgets without setup up all the rest of the code. > I want to pass a view string into the URL and have it show. > content\control\render?widget='<view-map name="composeEmail" > type="screen" > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' > > I should be able to pass this into a event that makes it part of a > context and calls the rendering for it? > > any thoughts > > > > > > > |
|
|
In reply to this post by BJ Freeman
Can you give a more specific example of what you're wanting to happen?
----- Original Message ---- From: BJ Freeman <[hidden email]> To: [hidden email] Sent: Monday, December 24, 2007 1:31:27 PM Subject: Re: passing a view as an URL so your saying the URL example I show may not work? I figured to pass it into a event and have it parsed then sent on as a view like the controller does. Chris Howe sent the following on 12/24/2007 11:24 AM: > are you wanting to modify the view response or the widget? If it's the view response, you need to pass/handle a webapp parameter and a name parameter. If it's the widget, you will need to pass/ handle a resource-location parameter and a screen-name parameter. Also, lookout for characters to be escaped/encoded properly. > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:01:41 PM > Subject: passing a view as an URL > > > for those more knowledgeable: > I am looking to implement a basic WISWYG for widgets, so I can design > widgets without setup up all the rest of the code. > I want to pass a view string into the URL and have it show. > content\control\render?widget='<view-map name="composeEmail" > type="screen" > > > I should be able to pass this into a event that makes it part of a > context and calls the rendering for it? > > any thoughts > > > > > > > |
|
|
I paste the Url example
ofbiz renders the widget so I can see it. more as a visual aid to see what I coded. may be a tree, menu, or screen widget. Chris Howe sent the following on 12/24/2007 11:35 AM: > Can you give a more specific example of what you're wanting to happen? > > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:31:27 PM > Subject: Re: passing a view as an URL > > > so your saying the URL example I show may not work? > I figured to pass it into a event and have it parsed then sent on as a > view like the controller does. > > Chris Howe sent the following on 12/24/2007 11:24 AM: >> are you wanting to modify the view response or the widget? If it's > the view response, you need to pass/handle a webapp parameter and a name > parameter. If it's the widget, you will need to pass/ handle a > resource-location parameter and a screen-name parameter. Also, lookout for > characters to be escaped/encoded properly. >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:01:41 PM >> Subject: passing a view as an URL >> >> >> for those more knowledgeable: >> I am looking to implement a basic WISWYG for widgets, so I can design >> widgets without setup up all the rest of the code. >> I want to pass a view string into the URL and have it show. >> content\control\render?widget='<view-map name="composeEmail" >> type="screen" >> > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' >> I should be able to pass this into a event that makes it part of a >> context and calls the rendering for it? >> >> any thoughts >> >> >> >> >> >> >> > > > > > > > |
|
|
In reply to this post by BJ Freeman
How is what you're wanting to do different than simply making the normal request to the correct webapp?
----- Original Message ---- From: BJ Freeman <[hidden email]> To: [hidden email] Sent: Monday, December 24, 2007 1:42:31 PM Subject: Re: passing a view as an URL I paste the Url example ofbiz renders the widget so I can see it. more as a visual aid to see what I coded. may be a tree, menu, or screen widget. Chris Howe sent the following on 12/24/2007 11:35 AM: > Can you give a more specific example of what you're wanting to happen? > > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:31:27 PM > Subject: Re: passing a view as an URL > > > so your saying the URL example I show may not work? > I figured to pass it into a event and have it parsed then sent on as > view like the controller does. > > Chris Howe sent the following on 12/24/2007 11:24 AM: >> are you wanting to modify the view response or the widget? If it's > the view response, you need to pass/handle a webapp parameter and a name > parameter. If it's the widget, you will need to pass/ handle a > resource-location parameter and a screen-name parameter. Also, lookout for > characters to be escaped/encoded properly. >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:01:41 PM >> Subject: passing a view as an URL >> >> >> for those more knowledgeable: >> I am looking to implement a basic WISWYG for widgets, so I can >> widgets without setup up all the rest of the code. >> I want to pass a view string into the URL and have it show. >> content\control\render?widget='<view-map name="composeEmail" >> type="screen" >> > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' >> I should be able to pass this into a event that makes it part of a >> context and calls the rendering for it? >> >> any thoughts >> >> >> >> >> >> >> > > > > > > > |
|
|
I don't have to edit a controller and put it is the system till I am done.
so basically you saying it is not a valid Idea. thanks. Chris Howe sent the following on 12/24/2007 11:47 AM: > How is what you're wanting to do different than simply making the normal request to the correct webapp? > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:42:31 PM > Subject: Re: passing a view as an URL > > > I paste the Url example > ofbiz renders the widget so I can see it. > more as a visual aid to see what I coded. > may be a tree, menu, or screen widget. > > Chris Howe sent the following on 12/24/2007 11:35 AM: >> Can you give a more specific example of what you're wanting to > happen? >> >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:31:27 PM >> Subject: Re: passing a view as an URL >> >> >> so your saying the URL example I show may not work? >> I figured to pass it into a event and have it parsed then sent on as > a >> view like the controller does. >> >> Chris Howe sent the following on 12/24/2007 11:24 AM: >>> are you wanting to modify the view response or the widget? If it's >> the view response, you need to pass/handle a webapp parameter and a > name >> parameter. If it's the widget, you will need to pass/ handle a >> resource-location parameter and a screen-name parameter. Also, > lookout for >> characters to be escaped/encoded properly. >>> ----- Original Message ---- >>> From: BJ Freeman <[hidden email]> >>> To: [hidden email] >>> Sent: Monday, December 24, 2007 1:01:41 PM >>> Subject: passing a view as an URL >>> >>> >>> for those more knowledgeable: >>> I am looking to implement a basic WISWYG for widgets, so I can > design >>> widgets without setup up all the rest of the code. >>> I want to pass a view string into the URL and have it show. >>> content\control\render?widget='<view-map name="composeEmail" >>> type="screen" >>> > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' >>> I should be able to pass this into a event that makes it part of a >>> context and calls the rendering for it? >>> >>> any thoughts >>> >>> >>> >>> >>> >>> >>> >> >> >> >> >> >> > > > > > > > |
|
|
In reply to this post by BJ Freeman
Slow down there cowboy. There's no intonation in my questioning, just trying to get information so I can offer help.
you will want to pass the following url in your browser: http://localhost:8080/content/control/myWYSIWYGUri?screenName=myScreenName&screenLocation=myScreenLocation i'm not sure how you will need to escape all of the "/" and ":' in myScreenLocation but this should get you on your way you will want to create the following request, view and screen and <request-map uri="myWYSIWYGUri"> <response name="success" type="view" value="myWYSIWYGview" </request> <view-map name="myWYSIWYGview" type="screen" page="component://content/widget/myScreen.xml#myWYSIWYGviewRenderer"/> component://content/widget/myScreen.xml: <screen name="myWYSIWYGviewRenderer"> <section> <widget> <include-screen name="${parameters.screenName}" location="${parameters.location}"/> </widget> </section> </screen> ----- Original Message ---- From: BJ Freeman <[hidden email]> To: [hidden email] Sent: Monday, December 24, 2007 1:58:20 PM Subject: Re: passing a view as an URL I don't have to edit a controller and put it is the system till I am done. so basically you saying it is not a valid Idea. thanks. Chris Howe sent the following on 12/24/2007 11:47 AM: > How is what you're wanting to do different than simply making the normal request to the correct webapp? > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:42:31 PM > Subject: Re: passing a view as an URL > > > I paste the Url example > ofbiz renders the widget so I can see it. > more as a visual aid to see what I coded. > may be a tree, menu, or screen widget. > > Chris Howe sent the following on 12/24/2007 11:35 AM: >> Can you give a more specific example of what you're wanting to > happen? >> >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:31:27 PM >> Subject: Re: passing a view as an URL >> >> >> so your saying the URL example I show may not work? >> I figured to pass it into a event and have it parsed then sent on as > a >> view like the controller does. >> >> Chris Howe sent the following on 12/24/2007 11:24 AM: >>> are you wanting to modify the view response or the widget? If it's >> the view response, you need to pass/handle a webapp parameter and a > name >> parameter. If it's the widget, you will need to pass/ handle a >> resource-location parameter and a screen-name parameter. Also, > lookout for >> characters to be escaped/encoded properly. >>> ----- Original Message ---- >>> From: BJ Freeman <[hidden email]> >>> To: [hidden email] >>> Sent: Monday, December 24, 2007 1:01:41 PM >>> Subject: passing a view as an URL >>> >>> >>> for those more knowledgeable: >>> I am looking to implement a basic WISWYG for widgets, so I can > design >>> widgets without setup up all the rest of the code. >>> I want to pass a view string into the URL and have it show. >>> content\control\render?widget='<view-map name="composeEmail" >>> type="screen" >>> > >>> I should be able to pass this into a event that makes it part of a >>> context and calls the rendering for it? >>> >>> any thoughts >>> >>> >>> >>> >>> >>> >>> >> >> >> >> >> >> > > > > > > > |
|
|
In reply to this post by BJ Freeman
woops...
<include-screen name="${parameters.screenName}" location="${parameters.location}"/> should be <include-screen name="${parameters.screenName}" location="${parameters.myScreenLocation}"/> ----- Original Message ---- From: Chris Howe <[hidden email]> To: [hidden email] Sent: Monday, December 24, 2007 3:03:47 PM Subject: Re: passing a view as an URL Slow down there cowboy. There's no intonation in my questioning, just trying to get information so I can offer help. you will want to pass the following url in your browser: http://localhost:8080/content/control/myWYSIWYGUri?screenName=myScreenName&screenLocation=myScreenLocation i'm not sure how you will need to escape all of the "/" and ":' in myScreenLocation but this should get you on your way you will want to create the following request, view and screen and <request-map uri="myWYSIWYGUri"> <response name="success" type="view" value="myWYSIWYGview" </request> <view-map name="myWYSIWYGview" type="screen" page="component://content/widget/myScreen.xml#myWYSIWYGviewRenderer"/> component://content/widget/myScreen.xml: <screen name="myWYSIWYGviewRenderer"> <section> <widget> <include-screen name="${parameters.screenName}" location="${parameters.location}"/> </widget> </section> </screen> ----- Original Message ---- From: BJ Freeman <[hidden email]> To: [hidden email] Sent: Monday, December 24, 2007 1:58:20 PM Subject: Re: passing a view as an URL I don't have to edit a controller and put it is the system till I am done. so basically you saying it is not a valid Idea. thanks. Chris Howe sent the following on 12/24/2007 11:47 AM: > How is what you're wanting to do different than simply making the normal request to the correct webapp? > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:42:31 PM > Subject: Re: passing a view as an URL > > > I paste the Url example > ofbiz renders the widget so I can see it. > more as a visual aid to see what I coded. > may be a tree, menu, or screen widget. > > Chris Howe sent the following on 12/24/2007 11:35 AM: >> Can you give a more specific example of what you're wanting to > happen? >> >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:31:27 PM >> Subject: Re: passing a view as an URL >> >> >> so your saying the URL example I show may not work? >> I figured to pass it into a event and have it parsed then sent on as > a >> view like the controller does. >> >> Chris Howe sent the following on 12/24/2007 11:24 AM: >>> are you wanting to modify the view response or the widget? If it's >> the view response, you need to pass/handle a webapp parameter and a > name >> parameter. If it's the widget, you will need to pass/ handle a >> resource-location parameter and a screen-name parameter. Also, > lookout for >> characters to be escaped/encoded properly. >>> ----- Original Message ---- >>> From: BJ Freeman <[hidden email]> >>> To: [hidden email] >>> Sent: Monday, December 24, 2007 1:01:41 PM >>> Subject: passing a view as an URL >>> >>> >>> for those more knowledgeable: >>> I am looking to implement a basic WISWYG for widgets, so I can > design >>> widgets without setup up all the rest of the code. >>> I want to pass a view string into the URL and have it show. >>> content\control\render?widget='<view-map name="composeEmail" >>> type="screen" >>> > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' >>> I should be able to pass this into a event that makes it part of a >>> context and calls the rendering for it? >>> >>> any thoughts >>> >>> >>> >>> >>> >>> >>> >> >> >> >> >> >> > > > > > > > |
|
|
I want to pass the view string that would normally be in a controller
like <view-map name="composeEmail" type="screen" page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/> then content\control\render?widget= would then have a <request-map uri="render"> <event type="java" >myviewwidget</event> <response name="sucess" type="none" /> </request-map> this event would read the parm.get("widget") would retrieve <view-map name="composeEmail" type="screen" page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/> and send it to be rendered so I can see it on the webpage. note this is not something for distribution since it opens a major security whole. Chris Howe sent the following on 12/24/2007 1:07 PM: > woops... > <include-screen name="${parameters.screenName}" > location="${parameters.location}"/> > should be > <include-screen name="${parameters.screenName}" > location="${parameters.myScreenLocation}"/> > > ----- Original Message ---- > From: Chris Howe <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 3:03:47 PM > Subject: Re: passing a view as an URL > > > Slow down there cowboy. There's no intonation in my questioning, just > trying to get information so I can offer help. > > you will want to pass the following url in your browser: > http://localhost:8080/content/control/myWYSIWYGUri?screenName=myScreenName&screenLocation=myScreenLocation > > i'm not sure how you will need to escape all of the "/" and ":' in > myScreenLocation but this should get you on your way > > you will want to create the following request, view and screen and > <request-map uri="myWYSIWYGUri"> > <response name="success" type="view" value="myWYSIWYGview" > </request> > <view-map name="myWYSIWYGview" type="screen" > page="component://content/widget/myScreen.xml#myWYSIWYGviewRenderer"/> > > > component://content/widget/myScreen.xml: > > <screen name="myWYSIWYGviewRenderer"> > <section> > <widget> > <include-screen name="${parameters.screenName}" > location="${parameters.location}"/> > </widget> > </section> > </screen> > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:58:20 PM > Subject: Re: passing a view as an URL > > > I don't have to edit a controller and put it is the system till I am > done. > so basically you saying it is not a valid Idea. > thanks. > > Chris Howe sent the following on 12/24/2007 11:47 AM: >> How is what you're wanting to do different than simply making the > normal request to the correct webapp? >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:42:31 PM >> Subject: Re: passing a view as an URL >> >> >> I paste the Url example >> ofbiz renders the widget so I can see it. >> more as a visual aid to see what I coded. >> may be a tree, menu, or screen widget. >> >> Chris Howe sent the following on 12/24/2007 11:35 AM: >>> Can you give a more specific example of what you're wanting to >> happen? >>> ----- Original Message ---- >>> From: BJ Freeman <[hidden email]> >>> To: [hidden email] >>> Sent: Monday, December 24, 2007 1:31:27 PM >>> Subject: Re: passing a view as an URL >>> >>> >>> so your saying the URL example I show may not work? >>> I figured to pass it into a event and have it parsed then sent on as >> a >>> view like the controller does. >>> >>> Chris Howe sent the following on 12/24/2007 11:24 AM: >>>> are you wanting to modify the view response or the widget? If it's >>> the view response, you need to pass/handle a webapp parameter and a >> name >>> parameter. If it's the widget, you will need to pass/ handle a >>> resource-location parameter and a screen-name parameter. Also, >> lookout for >>> characters to be escaped/encoded properly. >>>> ----- Original Message ---- >>>> From: BJ Freeman <[hidden email]> >>>> To: [hidden email] >>>> Sent: Monday, December 24, 2007 1:01:41 PM >>>> Subject: passing a view as an URL >>>> >>>> >>>> for those more knowledgeable: >>>> I am looking to implement a basic WISWYG for widgets, so I can >> design >>>> widgets without setup up all the rest of the code. >>>> I want to pass a view string into the URL and have it show. >>>> content\control\render?widget='<view-map name="composeEmail" >>>> type="screen" >>>> >> > > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' >>>> I should be able to pass this into a event that makes it part of a >>>> context and calls the rendering for it? >>>> >>>> any thoughts >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> >> >> >> >> > > > > > > > > > > |
|
|
In reply to this post by BJ Freeman
What I suggested does the exact same thing. There's no need to create a java method to handle this.
----- Original Message ---- From: BJ Freeman <[hidden email]> To: [hidden email] Sent: Monday, December 24, 2007 4:12:36 PM Subject: Re: passing a view as an URL I want to pass the view string that would normally be in a controller like <view-map name="composeEmail" type="screen" page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/> then content\control\render?widget= would then have a <request-map uri="render"> <event type="java" >myviewwidget</event> <response name="sucess" type="none" /> </request-map> this event would read the parm.get("widget") would retrieve <view-map name="composeEmail" type="screen" page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/> and send it to be rendered so I can see it on the webpage. note this is not something for distribution since it opens a major security whole. Chris Howe sent the following on 12/24/2007 1:07 PM: > woops... > <include-screen name="${parameters.screenName}" > location="${parameters.location}"/> > should be > <include-screen name="${parameters.screenName}" > location="${parameters.myScreenLocation}"/> > > ----- Original Message ---- > From: Chris Howe <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 3:03:47 PM > Subject: Re: passing a view as an URL > > > Slow down there cowboy. There's no intonation in my questioning, > trying to get information so I can offer help. > > you will want to pass the following url in your browser: > http://localhost:8080/content/control/myWYSIWYGUri?screenName=myScreenName&screenLocation=myScreenLocation > > i'm not sure how you will need to escape all of the "/" and ":' in > myScreenLocation but this should get you on your way > > you will want to create the following request, view and screen and > <request-map uri="myWYSIWYGUri"> > <response name="success" type="view" value="myWYSIWYGview" > </request> > <view-map name="myWYSIWYGview" type="screen" > > > > component://content/widget/myScreen.xml: > > <screen name="myWYSIWYGviewRenderer"> > <section> > <widget> > <include-screen name="${parameters.screenName}" > location="${parameters.location}"/> > </widget> > </section> > </screen> > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 1:58:20 PM > Subject: Re: passing a view as an URL > > > I don't have to edit a controller and put it is the system till I am > done. > so basically you saying it is not a valid Idea. > thanks. > > Chris Howe sent the following on 12/24/2007 11:47 AM: >> How is what you're wanting to do different than simply making the > normal request to the correct webapp? >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:42:31 PM >> Subject: Re: passing a view as an URL >> >> >> I paste the Url example >> ofbiz renders the widget so I can see it. >> more as a visual aid to see what I coded. >> may be a tree, menu, or screen widget. >> >> Chris Howe sent the following on 12/24/2007 11:35 AM: >>> Can you give a more specific example of what you're wanting to >> happen? >>> ----- Original Message ---- >>> From: BJ Freeman <[hidden email]> >>> To: [hidden email] >>> Sent: Monday, December 24, 2007 1:31:27 PM >>> Subject: Re: passing a view as an URL >>> >>> >>> so your saying the URL example I show may not work? >>> I figured to pass it into a event and have it parsed then sent on >> a >>> view like the controller does. >>> >>> Chris Howe sent the following on 12/24/2007 11:24 AM: >>>> are you wanting to modify the view response or the widget? If it's >>> the view response, you need to pass/handle a webapp parameter and a >> name >>> parameter. If it's the widget, you will need to pass/ handle a >>> resource-location parameter and a screen-name parameter. Also, >> lookout for >>> characters to be escaped/encoded properly. >>>> ----- Original Message ---- >>>> From: BJ Freeman <[hidden email]> >>>> To: [hidden email] >>>> Sent: Monday, December 24, 2007 1:01:41 PM >>>> Subject: passing a view as an URL >>>> >>>> >>>> for those more knowledgeable: >>>> I am looking to implement a basic WISWYG for widgets, so I can >> design >>>> widgets without setup up all the rest of the code. >>>> I want to pass a view string into the URL and have it show. >>>> content\control\render?widget='<view-map name="composeEmail" >>>> type="screen" >>>> >> > > >>>> I should be able to pass this into a event that makes it part of a >>>> context and calls the rendering for it? >>>> >>>> any thoughts >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> >> >> >> >> > > > > > > > > > > |
|
|
thanks
Chris Howe sent the following on 12/24/2007 2:19 PM: > What I suggested does the exact same thing. There's no need to create a java method to handle this. > > ----- Original Message ---- > From: BJ Freeman <[hidden email]> > To: [hidden email] > Sent: Monday, December 24, 2007 4:12:36 PM > Subject: Re: passing a view as an URL > > > I want to pass the view string that would normally be in a controller > like <view-map name="composeEmail" type="screen" > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/> > > > then content\control\render?widget= > would then have a > <request-map uri="render"> > <event type="java" >myviewwidget</event> > <response name="sucess" type="none" /> > </request-map> > > this event would read the > parm.get("widget") would retrieve > <view-map name="composeEmail" type="screen" > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/> > and send it to be rendered so I can see it on the webpage. > > note this is not something for distribution since it opens a major > security whole. > > > Chris Howe sent the following on 12/24/2007 1:07 PM: >> woops... >> <include-screen name="${parameters.screenName}" >> location="${parameters.location}"/> >> should be >> <include-screen name="${parameters.screenName}" >> location="${parameters.myScreenLocation}"/> >> >> ----- Original Message ---- >> From: Chris Howe <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 3:03:47 PM >> Subject: Re: passing a view as an URL >> >> >> Slow down there cowboy. There's no intonation in my questioning, > just >> trying to get information so I can offer help. >> >> you will want to pass the following url in your browser: >> > http://localhost:8080/content/control/myWYSIWYGUri?screenName=myScreenName&screenLocation=myScreenLocation >> i'm not sure how you will need to escape all of the "/" and ":' in >> myScreenLocation but this should get you on your way >> >> you will want to create the following request, view and screen and >> <request-map uri="myWYSIWYGUri"> >> <response name="success" type="view" value="myWYSIWYGview" >> </request> >> <view-map name="myWYSIWYGview" type="screen" >> > page="component://content/widget/myScreen.xml#myWYSIWYGviewRenderer"/> >> >> component://content/widget/myScreen.xml: >> >> <screen name="myWYSIWYGviewRenderer"> >> <section> >> <widget> >> <include-screen name="${parameters.screenName}" >> location="${parameters.location}"/> >> </widget> >> </section> >> </screen> >> >> ----- Original Message ---- >> From: BJ Freeman <[hidden email]> >> To: [hidden email] >> Sent: Monday, December 24, 2007 1:58:20 PM >> Subject: Re: passing a view as an URL >> >> >> I don't have to edit a controller and put it is the system till I am >> done. >> so basically you saying it is not a valid Idea. >> thanks. >> >> Chris Howe sent the following on 12/24/2007 11:47 AM: >>> How is what you're wanting to do different than simply making the >> normal request to the correct webapp? >>> ----- Original Message ---- >>> From: BJ Freeman <[hidden email]> >>> To: [hidden email] >>> Sent: Monday, December 24, 2007 1:42:31 PM >>> Subject: Re: passing a view as an URL >>> >>> >>> I paste the Url example >>> ofbiz renders the widget so I can see it. >>> more as a visual aid to see what I coded. >>> may be a tree, menu, or screen widget. >>> >>> Chris Howe sent the following on 12/24/2007 11:35 AM: >>>> Can you give a more specific example of what you're wanting to >>> happen? >>>> ----- Original Message ---- >>>> From: BJ Freeman <[hidden email]> >>>> To: [hidden email] >>>> Sent: Monday, December 24, 2007 1:31:27 PM >>>> Subject: Re: passing a view as an URL >>>> >>>> >>>> so your saying the URL example I show may not work? >>>> I figured to pass it into a event and have it parsed then sent on > as >>> a >>>> view like the controller does. >>>> >>>> Chris Howe sent the following on 12/24/2007 11:24 AM: >>>>> are you wanting to modify the view response or the widget? If > it's >>>> the view response, you need to pass/handle a webapp parameter and > a >>> name >>>> parameter. If it's the widget, you will need to pass/ handle a >>>> resource-location parameter and a screen-name parameter. Also, >>> lookout for >>>> characters to be escaped/encoded properly. >>>>> ----- Original Message ---- >>>>> From: BJ Freeman <[hidden email]> >>>>> To: [hidden email] >>>>> Sent: Monday, December 24, 2007 1:01:41 PM >>>>> Subject: passing a view as an URL >>>>> >>>>> >>>>> for those more knowledgeable: >>>>> I am looking to implement a basic WISWYG for widgets, so I can >>> design >>>>> widgets without setup up all the rest of the code. >>>>> I want to pass a view string into the URL and have it show. >>>>> content\control\render?widget='<view-map name="composeEmail" >>>>> type="screen" >>>>> >>> >> > page="component://content/widget/content/communications/communicationsScreens.xml#composeEmail"/>' >>>>> I should be able to pass this into a event that makes it part of a >>>>> context and calls the rendering for it? >>>>> >>>>> any thoughts >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> >> >> >> >> >> >> >> > > > > > > > |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |