You can just have a small element near the color name that will display the
color. IMO that's enough, no need for anything more complex than that. We
just need an option to color the text into some colors, that's all.
On Tue, Jan 3, 2012 at 7:12 PM, Thomas Wrobel <darkfl...@gmail.com> wrote:
> In GWT it would be very simple to do a list too
>
> For a basic dropdown list:
>
> ListBox colorlist = new ListBox();
> colorlist.add("red");
> colorlist.add("blue");
> colorlist.add("#440066"); //or use hex
>
> Then just add the list box where you want it by adding it to the
> parent container you want.
> containerpanel.add(colorlist);
>
> This list wouldn't have the texts coloured correctly though, they
> would just be words.
> For coloured words you'd need to either extend the list box to support
> html on the elements, or, alternatively use a DisclosurePanel that
> contains a VerticalPanel, which then has rollover html elements.
>
> You could even just use the html code directly with a HTML widget -
> but Id advise against that as events would be harder to pick up.
>
> If anyone needs any gwt help, Id be glade to chip in as thats one
> thing I can help with!
>
> In fact, in the worst case, if you cant find an existing colourpicker
> to do the job, Id be happy to make one myself for the project.
>
>
>
>
>
>
>
>
>
> On 3 January 2012 17:51, Zachary “Gamer_Z.” Yaro <zmy...@gmail.com> wrote:
> > For at least a temporary solution, you could create a dialog like the one
> > in Google Wave with a few pre-defined colors. I do not know about the
> GWT
> > side of things, but doing the UI in HTML would be pretty easy if it were
> > just something like this:
> > <style type="text/css">.colorChoice{width:18px;height:18px;border:1px
> solid
> >
> black;display:inline-block;cursor:pointer;}.colorChoice:hover{border-color:blue;}</style>
> > <div style="display:inline-block;border:1px solid
> > blue;border-radius:5px;padding:4px;">
> > <div class="colorChoice" style="background-color:red;"></div>
> > <div class="colorChoice" style="background-color:orange;"></div>
> > <div class="colorChoice" style="background-color:yellow;"></div>
> > <div class="colorChoice" style="background-color:lightgreen;"></div>
> > <div class="colorChoice" style="background-color:blue;"></div><br/>
> > <div class="colorChoice" style="background-color:purple;"></div>
> > <div class="colorChoice" style="background-color:brown;"></div>
> > <div class="colorChoice" style="background-color:black;"></div>
> > <div class="colorChoice" style="background-color:gray;"></div>
> > <div class="colorChoice" style="background-color:white;"></div><br/>
> > <div class="colorChoice"
> > style="width:114px;text-align:center;">None</div>
> > </div>
> >
> > Obviously it would not be *quite* that simple, but something like that
> > would probably be easier to implement than a fancier color picker.
> >
> > —Zachary “Gamer_Z.” Yaro
> >
> >
> > On Tue, Jan 3, 2012 at 11:36, Ben Hegarty <heg...@gmail.com> wrote:
> >
> >> lol, already done just that, been having a look around too for an
> >> alternative too but havent seen anything appropriate yet, if you know
> of a
> >> good one I'm all ears :)
> >> Regards
> >> Ben
> >>
> >> On Tue, Jan 3, 2012 at 4:20 PM, Thomas Wrobel <darkfl...@gmail.com>
> wrote:
> >>
> >> > Might be worth just dropping an email to the developer asking if you
> >> > can use it under a apache licence or lgpl....assuming its one
> >> > developer.
> >> > Theres a few other gwt based colour pickers about, as I was browsing a
> >> > few last week for a project of my own, but I think they are all GPL.
> >> >
> >> > ~~~~~~
> >> > Reviews of anything, by anyone;
> >> > www.rateoholic.co.uk
> >> > Please try out my new site and give feedback :)
> >> >
> >> >
> >> >
> >> > On 3 January 2012 16:15, Yuri Z <vega...@gmail.com> wrote:
> >> > > AFAIK GPL is not compatible with Apache
> >> > >
> >> > > On Tue, Jan 3, 2012 at 5:07 PM, Daniel Danilatos <
> dan...@danilatos.com
> >> > >wrote:
> >> > >
> >> > >> Sorry, I was replying to the earlier email about deleting blips.
> There
> >> > >> is no connection between the undo stack and the colour picker :)
> >> > >>
> >> > >> To answer your question about external controls, there is no
> reason in
> >> > >> principle to avoid using them, but I would exercise caution:
> >> > >> - External controls may have lots of their dependencies, and using
> >> > >> just 1 external control may greatly increase the compiled code size
> >> > >> and compile time. Please measure the before & after to see if how
> big
> >> > >> the impact is (also, using SoyC is a big help)
> >> > >> - Consider adding a runAsync split-point to avoid pulling in the
> extra
> >> > >> code until the colour picker is required.
> >> > >>
> >> > >> In short, use your best judgement, taking into consideration the
> above
> >> > >> points, as a general rule.
> >> > >>
> >> > >> In this specific case there's the issue of the licence, I'm not an
> >> > >> expert but I think the GPL is not compatible with the apache
> licence,
> >> > >> i.e. we'd have to convert all the wave code to GPL in order to use
> >> > >> other GPL code (it would be different if the colour picker were
> LGPL).
> >> > >> Someone correct me if I'm wrong?
> >> > >>
> >> > >> Dan
> >> > >>
> >> > >> On Tue, Jan 3, 2012 at 10:14 PM, Ben Hegarty <heg...@gmail.com>
> >> wrote:
> >> > >> > ok, but I'm confused, what the connection between the
> undercurrent
> >> > undo
> >> > >> > stack and a color picker for the edit toolbar? I really just
> need to
> >> > know
> >> > >> > if we're allowed to use external controls within wiab.. or have I
> >> > missed
> >> > >> > the point? :)
> >> > >> >
> >> > >> > Ben
> >> > >> >
> >> > >> > On Tue, Jan 3, 2012 at 2:02 PM, Daniel Danilatos <
> >> > dan...@danilatos.com
> >> > >> >wrote:
> >> > >> >
> >> > >> >> A good UI principle is to make things really easy to do, but
> also
> >> > have
> >> > >> >> an easy way to undo them.
> >> > >> >>
> >> > >> >> This may end up being a large project, but: ideally I think
> >> deleting
> >> > a
> >> > >> >> blip should be as simple as hitting the delete key when the
> blip is
> >> > >> >> selected; as soon as that happens, a butter bar appears at the
> top
> >> > >> >> with a message such as "Blip deleted. _Undo_" (with "undo" being
> >> > >> >> clickable). Thus it's easy to delete, but also easy to revert an
> >> > >> >> accidental deletion.
> >> > >> >>
> >> > >> >> The "large project" part here is implementing wave-level undo,
> >> which
> >> > >> >> as far as I'm aware isn't done in Undercurrent (though it's
> done in
> >> > >> >> the editor). Google Wave had it implemented in a rather complex
> way
> >> > >> >> that tried to avoid sending certain types of actions that were
> >> undone
> >> > >> >> to the server, but we could probably do it fairly simply by not
> >> > >> >> worrying about those cases for now.
> >> > >> >>
> >> > >> >> Conceptually, I think it's straight forward, as we're mostly
> just
> >> > >> >> undoing/redoing changes to the manifest document; though in
> >> practice
> >> > >> >> the plumbing may or may not be simple, I'm not familiar enough
> with
> >> > >> >> that part of the code.
> >> > >> >>
> >> > >> >> I'm actually interested in this too so I'd be happy to help out
> if
> >> > >> >> anyone wants to work on it.
> >> > >> >>
> >> > >> >> Dan
> >> > >> >>
> >> > >> >> On Fri, Dec 30, 2011 at 8:59 AM, Zachary “Gamer_Z.” Yaro
> >> > >> >> <zmy...@gmail.com> wrote:
> >> > >> >> > I think it would help even to make the delete happen onclick
> >> > instead
> >> > >> of
> >> > >> >> > onmousedown. I have accidentally deleted blips when I just
> >> missed
> >> > the
> >> > >> >> > button I meant to click, but unlike Gwave, I cannot just drag
> my
> >> > mouse
> >> > >> >> away
> >> > >> >> > before releasing the button.
> >> > >> >> >
> >> > >> >> > —Zachary “Gamer_Z.” Yaro
> >> > >> >> > On Dec 29, 2011 7:00 PM, "Thomas Wrobel" <darkfl...@gmail.com
> >
> >> > wrote:
> >> > >> >> >
> >> > >> >> >> How about a popup tickbox for "enable delete", so the first
> >> delete
> >> > >> >> >> takes two clicks, but the rest only one?
> >> > >> >> >>
> >> > >> >> >> On 29 December 2011 23:28, Ali Lown <a...@lown.me.uk> wrote:
> >> > >> >> >> >> There was some starter project that wasn't fully
> implemented
> >> -
> >> > to
> >> > >> >> add a
> >> > >> >> >> >> verification popup when deleting a blip.
> >> > >> >> >> >
> >> > >> >> >> > I often end up moderating/cleaning-up the wave with my
> friends
> >> > in.
> >> > >> On
> >> > >> >> >> > Google wave this require opening the drop-down menu which
> >> takes
> >> > >> time.
> >> > >> >> >> > I really like the way it can easily be done on WIAB and the
> >> fact
> >> > >> the
> >> > >> >> >> > next blip's delete button auto-aligns into the same space
> >> > making it
> >> > >> >> >> > very efficient to delete whole chains of irrelevant blips.
> >> > >> >> >> > Opening a confirmation dialog would be a severe irritation,
> >> > when I
> >> > >> >> >> > feel the delete button is sufficiently clear as is.
> >> > >> >> >>
> >> > >> >>
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> > --
> >> > >> > blog:http://thelifeofbenhegs.blogspot.com/
> >> > >> > phone: +447767-322-122
> >> > >>
> >> >
> >>
> >>
> >>
> >> --
> >> blog:http://thelifeofbenhegs.blogspot.com/
> >> phone: +447767-322-122
> >>
>
