I'm not sure whether I get what you are after? Anyway, I think for most widgets, you typically want any images etc. to be created upfront (by a designer/ downloaded from somewhere). Good for preview-ability and possibly for scalability too.
Do you have a list of widgets you'd like to see in the project you are thinking about?
Eelco
On Jun 16, 2006, at 1:54 AM, Ayodeji Aladejebi wrote: More on wicket widgets,
Now how powerful is the RenderedDynamicImageResource System?
Because from what i am thinking, isnt it possible to leverage the <map> tag in HTML specs to make small widgets?
How nice can it get and as a rough thought sketch...we have
<img name="menuWidget" src="" width="500" height="500" border="0" id="hotspot" usemap="" alt="" />
<map name="m_hotspot" id="m_hotspot">
<area wicket:id="menu1" shape="rect" coords="x1,y1,w1,h1" href="" alt="" />
<area wicket:id="menu2" shape="rect" coords="x2,y2,w2,h2" href="" alt="" />
new RenderedDynamicImageResource(40, 600) {
protected boolean render(Graphics2D graphics) {
graphics.drawXXXMenuBars
graphics.drawXXXMenuRegions
//pass Menu Dimensioning to <map> <area> tags to auto map your menu spot as hotspots
}
}));
I will draw the widget using RenderedDynamicImageResource and then use the mapping and area tags to define hot spot zones so that when it renders on the browser, an Image based Widget is ready and I think this idea may even be more useful than just menu widgets?
What du u guys think
On 6/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: Yep. Though we are limited in what we can except for extensions as we
agreed on keeping the licence ASF 2 for that. Set something up in
wicket-stuff if you want. I think the bottle neck to really make such
a thing flying is someone taking charge and putting a lot of energy in
it to make it succeed (thus not only the building, but also regularly
bringing out releases, harmonize efforts, keeping track of the
quality, doing some marketing, etc).
Eelco
>
> usually widgets start incubation as a wicket-contrib-<widget> project and
> once they mature we move them into extensions. this happened to quiete a few
> things already
>
> the repeaters package (dataview/datatable/etc)
> the upload progress bar
> the palette component
>
> etc etc
>
> -Igor
>
>
>
>
> On 6/14/06, Troy MacNeil < [EMAIL PROTECTED]> wrote:
> > These articles seem to address your CSS needs. The mark-up structure is
> > very similar to what you're aiming for.
> >
> > http://www.alistapart.com/articles/dropdowns
> > http://alistapart.com/articles/hybrid
> >
> > Background images and divider images are specified in the CSS, which
> > could be good or bad depending on your goals. It works for me;)
> >
> > There may be better ways, using AJAX for instance, but this should give
> > you a place to start at least.
> >
> > Troy
> >
> > On Wed, 2006-06-14 at 03:08 -0800, Ayodeji Aladejebi wrote:
> > > I know of Wicket Extensions and Wicket Stuff etc but I look forward to
> > > Wicket Widgets Stuff where users can donate all sorts of resuable
> > > widgets to wicket community that carry all sorts of behaviors needed
> > > to enrich Web user experience
> > >
> > > As an example, i have been trying to create Wicket Menu bar component
> > > by trying to reduce my effort to something close to Swing
> > >
> > > I am not talking of something like echo2 now, I am talking of all
> > > those common stuffs in web development packaged in a cross browser
> > > reusable wicket components.
> > >
> > > MenuBar bar = new MenuBar("web-app-menu", ...)
> > >
> > > MenuBar will be a customizable markupcontainer that will have vertical
> > > drop down capabilities
> > > Menus and MenuItem will simply be Wicket Links instances.
> > >
> > > My major headache started when i realized how horrible CSS can be
> > > across IE breeds and Mozilla and other browsers, IE expecially so i
> > > spent more time trying to sort out making cross browser CSS vertical
> > > menus for my wicket project. Now that should not be because for me if
> > > wicket were to fulfil its vision, developers should spend more time
> > > with Java than cracking thier heads on how to do common stuffs with
> > > CSS or _javascript_.
> > >
> > > Therefore I think encouraging widgets contribution will also be fine.
> > > I am not a cross browser CSS expert but there a lot out there willing
> > > to donate reusable CSS codes for creating common widgets on the
> > > browser
> > >
> > > Scrolling
> > > MenuBar
> > > etc...
> > >
> > >
> > >
> > > Anyway for me, it boils down to one thing,
> > > I am trying to create MenuBar, Menu and MenuItem for my project and i
> > > need cross browser CSS for vertical drop down menu,
> > >
> > > Something like this
> > > <div wicket:id="MenuBar" class="menubar">
> > > <ul>
> > > <li wicket:id="Menu"><a wicket:id="MenuItem"></a></li>
> > > <li wicket:id="MenuSeperator"></li>
> > > <li wicket:id="Menu"><a wicket:id="MenuItem"><img
> > > wicket:id="MenuImage"></img></a></li>
> > > </ul>
> > > </div>
> > >
> > > But i am scared of the CSS hell out there and i dont even know where
> > > to start digging for good cross browser CSS to use for this, so please
> > > who has a reference to the CSS library that can make this life easy
> > >
> > > Thanks :)
> > >
> > >
> > >
> > > _______________________________________________
> > > Wicket-user mailing list
> > > Wicket-user@lists.sourceforge.net
> > >
> https://lists.sourceforge.net/lists/listinfo/wicket-user
> >
> >
> > _______________________________________________
> > Wicket-user mailing list
> > Wicket-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wicket-user
> >
>
>
>
>
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
>
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
_______________________________________________ Wicket-user mailing list
|
