You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/12/10 22:20:19 UTC
[Apache Bloodhound] #296: Enhance ticket header according to
repsonsive mockups
#296: Enhance ticket header according to repsonsive mockups
------------------------+------------------------
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: major | Component: ui design
Version: | Resolution:
------------------------+------------------------
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/296>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #296: Enhance ticket header according to
responsive mockups (was: Enhance ticket header according to
repsonsive mockups)
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#296: Enhance ticket header according to responsive mockups
--------------------------+---------------------------
Reporter: olemis | Owner: jdreimann
Type: enhancement | Status: review
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: sticky ticket
--------------------------+---------------------------
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/296#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #296: Enhance ticket header according to
responsive mockups
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#296: Enhance ticket header according to responsive mockups
--------------------------+---------------------------
Reporter: olemis | Owner:
Type: enhancement | Status: review
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: sticky ticket
--------------------------+---------------------------
Changes (by jdreimann):
* owner: jdreimann =>
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/296#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #296: Enhance ticket header according to
repsonsive mockups
Posted by Jure Zitnik <ju...@digiverse.si>.
Hi,
On 12/12/12 8:21 AM, Peter Koželj wrote:
>> >PS: OTOH , I c Jure has proposed something akin to product
>> >environments while #115 is assigned to me in the issue tracker .
>> >
>> >Have you been working on #115 as part of #288 ? If so , how is the
>> >work started for #288 related to #115 ? I look forward to see your
>> >changes so as to review and compare with my current work on that
>> >direction .
>> >
>> >
> Jure will probably comment on this better then I. AFAIK he was more focused
> on Datamodel-Trac-Plugins backward compatibility for now, and I imagine (or
> hope) this should be inline with product environments. I'll talk to him
> today if I can help you two with multiproducts now that I am more or less
> finished with whitelabeling.
The #115 and #288 are actually complementary. The #288 solves the
database layer compatibility with trac code and existing plugins, as
described in
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003#database-schema-changes,
what I understood from the #115 description is that it addresses per
product configuration based on different (per product) .ini files (in
later stages iiuc this might be stored in the database).
As for the #115, I would suggest that the work being done on that ticket
is done on the bep-0003 branch I created yesterday. If you look at the
code, there is a BloodhoundEnvironment class that replaces
trac.Environment and is a good point to implement the per product
configuration.
Cheers,
Jure
Re: [Apache Bloodhound] #296: Enhance ticket header according to
repsonsive mockups
Posted by Peter Koželj <pe...@digiverse.si>.
On 11 December 2012 17:05, Olemis Lang <ol...@gmail.com> wrote:
> Hi !
> :)
>
> On 12/11/12, Peter Koželj <pe...@digiverse.si> wrote:
> > This is not strictly related to this ticket alone. I would like to get a
> > clear picture who is doing what to the ticket page concurrently at this
> > moment.
> >
> > I know Matevz is working on responsive layout. How is this ticket related
> > to that work?
>
> Ticket header is improved considering Joachim's mockups . There's no
> work in proposed patch for any responsive feature , as far as the
> meaning of responsiveness is concerned [1]_ .
>
> > And there is some ongoing work with inline editing/removing modify
> section
> > by Olemis?
> >
>
> yes , I'm working on this since September 26th and along the way many
> times the work on that ticket was paused . Now I'm solving some
> technical difficulties . Yesterday Joachim contacted me to provide a
> quick solution for #234 and there you have it .
>
> > Do we need some coordination on this?
> >
>
> What kind of coordination do you need ? AFAICS , there are only two
> tickets assigned to me #115 and #146 and afaics
>
> 1- Joachim has assigned #217 to mathevzb .
> 2- I've done nothing related to layout responsiveness [1]_
> 3- Updated look and feel is needed for #146 . Otherwise
> the same feature should be implemented twice .
>
> ... afaics , if Joachim approves the patch for #146 which really
> belongs to #296 (created after suggestions received from ) mathevzb
> should rebase work on responsive layout to include those changes . My
> changes have nothing to do with responsiveness .
>
> What exactly am I missing ?
>
> .. [1] Scaffolding - #Responsive design
> (http://twitter.github.com/bootstrap/scaffolding.html#responsive)
>
Ah, clear then. I was just a bit confused with the tickets and wanted to
check that parallel work would not take us in two totally oposite
directions.
>
> PS: OTOH , I c Jure has proposed something akin to product
> environments while #115 is assigned to me in the issue tracker .
>
> Have you been working on #115 as part of #288 ? If so , how is the
> work started for #288 related to #115 ? I look forward to see your
> changes so as to review and compare with my current work on that
> direction .
>
>
Jure will probably comment on this better then I. AFAIK he was more focused
on Datamodel-Trac-Plugins backward compatibility for now, and I imagine (or
hope) this should be inline with product environments. I'll talk to him
today if I can help you two with multiproducts now that I am more or less
finished with whitelabeling.
Maybe we can meet on BH IRC later today?
Regards,
Peter
Re: [Apache Bloodhound] #296: Enhance ticket header according to
repsonsive mockups
Posted by Olemis Lang <ol...@gmail.com>.
Hi !
:)
On 12/11/12, Peter Koželj <pe...@digiverse.si> wrote:
> This is not strictly related to this ticket alone. I would like to get a
> clear picture who is doing what to the ticket page concurrently at this
> moment.
>
> I know Matevz is working on responsive layout. How is this ticket related
> to that work?
Ticket header is improved considering Joachim's mockups . There's no
work in proposed patch for any responsive feature , as far as the
meaning of responsiveness is concerned [1]_ .
> And there is some ongoing work with inline editing/removing modify section
> by Olemis?
>
yes , I'm working on this since September 26th and along the way many
times the work on that ticket was paused . Now I'm solving some
technical difficulties . Yesterday Joachim contacted me to provide a
quick solution for #234 and there you have it .
> Do we need some coordination on this?
>
What kind of coordination do you need ? AFAICS , there are only two
tickets assigned to me #115 and #146 and afaics
1- Joachim has assigned #217 to mathevzb .
2- I've done nothing related to layout responsiveness [1]_
3- Updated look and feel is needed for #146 . Otherwise
the same feature should be implemented twice .
... afaics , if Joachim approves the patch for #146 which really
belongs to #296 (created after suggestions received from ) mathevzb
should rebase work on responsive layout to include those changes . My
changes have nothing to do with responsiveness .
What exactly am I missing ?
.. [1] Scaffolding - #Responsive design
(http://twitter.github.com/bootstrap/scaffolding.html#responsive)
PS: OTOH , I c Jure has proposed something akin to product
environments while #115 is assigned to me in the issue tracker .
Have you been working on #115 as part of #288 ? If so , how is the
work started for #288 related to #115 ? I look forward to see your
changes so as to review and compare with my current work on that
direction .
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: [Apache Bloodhound] #296: Enhance ticket header according to
repsonsive mockups
Posted by Peter Koželj <pe...@digiverse.si>.
This is not strictly related to this ticket alone. I would like to get a
clear picture who is doing what to the ticket page concurrently at this
moment.
I know Matevz is working on responsive layout. How is this ticket related
to that work?
And there is some ongoing work with inline editing/removing modify section
by Olemis?
Do we need some coordination on this?
Peter
On 10 December 2012 22:32, Apache Bloodhound <
bloodhound-dev@incubator.apache.org> wrote:
> #296: Enhance ticket header according to repsonsive mockups
> --------------------------+---------------------------
> Reporter: olemis | Owner: jdreimann
> Type: enhancement | Status: review
> Priority: major | Milestone:
> Component: ui design | Version:
> Resolution: | Keywords: sticky ticket
> --------------------------+---------------------------
> Changes (by olemis):
>
> * owner: olemis => jdreimann
> * status: accepted => review
>
>
> Comment:
>
> I'm forwarding this ticket to jdreimann for review to check if
> aforementioned patch is correct or something else needs to be adjusted
> from a UI/UX perspective .
>
> --
> Ticket URL: <https://issues.apache.org/bloodhound/ticket/296#comment:2>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound (incubating) issue tracker
>
Re: [Apache Bloodhound] #296: Enhance ticket header according to
repsonsive mockups
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#296: Enhance ticket header according to repsonsive mockups
--------------------------+---------------------------
Reporter: olemis | Owner: jdreimann
Type: enhancement | Status: review
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: sticky ticket
--------------------------+---------------------------
Changes (by olemis):
* owner: olemis => jdreimann
* status: accepted => review
Comment:
I'm forwarding this ticket to jdreimann for review to check if
aforementioned patch is correct or something else needs to be adjusted
from a UI/UX perspective .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/296#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #296: Enhance ticket header according to
repsonsive mockups
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#296: Enhance ticket header according to repsonsive mockups
--------------------------+---------------------------
Reporter: olemis | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: sticky ticket
--------------------------+---------------------------
Changes (by olemis):
* owner: nobody => olemis
* keywords: => sticky ticket
* status: new => accepted
Old description:
New description:
Sticky status and ticket header will change according to
[https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-
templates/ticket.html responsive mockup]. This ticket is for implementing
the look and feel before actually introducing layers for responsive
behavior .
--
Comment:
A [attachment:ticket:146:t146_r1418195_ticket_header.diff patch] has been
submitted for #146 in spite of implementing this feature . It has been
built against r1418195 and introduces the following enhancements :
1. Wrap date time values with `<time />` element
2. Single small line under ticket summary
3. Ticket type , status , reporter and creation date were moved down to
ticket fields list
4. minor cosmetic changes
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/296#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #296: Enhance ticket header according to
responsive mockups
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#296: Enhance ticket header according to responsive mockups
--------------------------+---------------------------
Reporter: olemis | Owner:
Type: enhancement | Status: review
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: sticky ticket
--------------------------+---------------------------
Comment (by jdreimann):
Replying to [comment:2 olemis]:
> I'm forwarding this ticket to jdreimann for review to check if
aforementioned patch is correct or something else needs to be adjusted
from a UI/UX perspective .
I've not got the environment set up to review this at the moment, so I'm
leaving this open for others to do.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/296#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker