I don't know yet. All I know now is that I'd like to have this on our
list to try to fix/ solve. We'll nail down the details when we get
there (unless you want to give it a shot now :)).

Eelco


On 8/2/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> what input params should that factory method have?
> I guess the page else you don't have any context for what you create it.
> And with a factory method you could just return a current instance of the
> Window object.
>
> I am not a big fan of cloning the complete page. Because this could lead to
> all kind of models
> being out of sync (if the dev does keep reference to the page itself
> somewhere).
> If we removed the pagemap (that can only be done if we remove the
> AccesStackPageMap)
> then i would prefer not to clone the page..But just to attach it somehow to
> the right window.
> We needed to clone it with pagemaps because of the storing of the page (it
> was really tight to it)
>
> johan
>
>
>
>
> On 8/2/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> >
>  On 8/2/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> > But what data do you have in that Window 1?
> > And what happens if i just open that in a different window?
> > Will that then suddenly be windows 2??
>
> Exactly! It's a different window, and as it is new, some factory
> method would be called, probably by default trying to clone the window
> of the last rendered page or something.
>
> >
> > I still think that it is a different thing the serverside "window" thing
> and
> > the
> > client side window thing.
> > A server side window thing can be in any window on the client side.
>
> No, they can't, that's my whole point. They *should* be one-to-one,
> and currently, unless you deliberately circumvent our window.name
> check, this is exactly how it works.
>
> > Only pages made for that window (the functionality) do have that window
> > object
> > for some data.
> > At least i guess now that window object has state? Because if that is the
> > case
> > i don't like cloning that. That could be very confusing for developers
>
> Then we don't do that. I'm neutral on that as long as we provide an
> easy mechanism for customizing window creation (the factory method).
>
> Eelco
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wicket-develop mailing list
>  Wicket-develop@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> _______________________________________________
> Wicket-develop mailing list
> Wicket-develop@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to