Object code entry is in Engage trunk

[James William Yoon]

Hi Sveto,

I've reopened ENGAGE-305 and attached the new buttons (see
ENGAGE-305-newer-images.zip).

A few notes about these images:
- The buttons are sized 106 x 52 pixels
- The middle buttons (2, 5, 8, 0) should have 1 pixel of padding on either
side, while the rest should have 0 pixels ((106 * 3) + 2 = 320, the width of
the screen)
- Ideally, we should be using CSS to create the background gradient/colour,
and real text for the actual number, so this is really just a stopgap
solution

Let me know if these new buttons solve your issue.

Cheers,
James

On Wed, Feb 10, 2010 at 7:33 AM, Svetoslav Nedkov <
snedkov at asteasolutions.com> wrote:

>  Hi James,
>
> The changes to object code entry are not complete yet, but should be soon.
>
> The valid codes are from "1" (one digit here) to "70" with the exception of
> "32" which is missing for some reason.
>
> Yesterday I noticed that the button images are somewhat bigger than they
> should be - 129 pixels that including a transparent gap on each side of 10
> pixels. I was able to compensate this by using a negative margin, but FF
> lays out the code entry screen by wrapping the last column of buttons on a
> new line. Is it possible to get new buttons?
>
>
> Regards,
>
> Svetoslav
>
>
>
> James William Yoon wrote:
>
> Very cool!
>
> Once this is complete, could we get a list up of valid object codes and
> their respective artifacts somewhere? (we're writing up the QA test plans
> this week)
>
> Cheers,
> James
>
> On Sat, Feb 6, 2010 at 2:36 PM, Colin Clark <colinbdclark at gmail.com>wrote:
>
>> Hey all,
>>
>> I have merged Sveto's wicked Object Code Entry screen into Engage trunk,
>> and it's now wired up to the navigation bar and home screen. We're getting
>> closer!
>>
>> At the moment, you'll notice all object codes are invalid. This is because
>> I still need to implement the view in Couch DB for searching artifacts by
>> code. Sveto, your database uses a Lucene view for searching object codes,
>> but I'm thinking this can by achieved more simply with a standard Couch
>> view. Yura has already created such a view, called "viewByObjectCode." Take
>> a look at it in Futon:
>>
>> http://142.150.154.59:5984/_utils/document.html?mccord/_design/artifacts
>>
>> Any reason I shouldn't go ahead and modify Object Entry to use this view
>> instead?
>>
>> Colin
>>
>> ---
>> Colin Clark
>> Technical Lead, Fluid Project
>> http://fluidproject.org
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100210/933c422a/attachment.html>