Hi Ryan,
I have been working on the proposal. I have mentioned some points about the
given 6 features. Please provide your feedback on point given below, So
that I can come with the concise sub-feature set in these 6 features:
1.To add basic feature of a month-long calendar view of a milestone,
showing the milestone due date and due date for tickets
As given in the ticket #766 (1) we can use the modified trac ticket
calender plugin (2), I have installed and tried this plugin.
or
we can develop the calender view from scratch using basic web development
and combine it with the bootstrap to make it look beautiful.
Also we can also extend the calender view to google calender as a different
plugin in addition to the above plugin (4) but it will be requiring the
internet and it is not open source.
2. To Allow tickets to be scheduled by drag 'n drop onto the calendar view.
First I can make the tickets "div draggable true" and then I can add the
basic javascript function (7) i.e what to drag, where to drop and do the
drop.
or
I can use jquery plugin (5).
3. To Scale the view: week, month, year.
There is another library mentioned in the ticket #766 as trac week plan
plugin (3), I have installed and tried this plugin as well. I can extend
this plugin to the month calender as sub plugin and I can create the year
plugin similarly as well. So, It will be like calender view containing
three view: year, month, and week with month view as default.
4. To add Filters for the calendar view. For example: filter by user,
milestone, open/closed tickets.
trac calender plugin also contain several filter which are required or If
created alone, then also these filters can be done by simple database
queries.
5. To Embed the calendar views in the query page and milestone pages.
I can put a button in query and milestone page and when user click the
button
this will add the calender to the right side to the existing page by using
jquery. or It will go to the calender page or I can add some indexing based
on the jquery tab (6).
6. Allow the calendar to be annotated with arbitrary notes/events that do
not represent tickets.
a new class can be added to the existing trac plugins to support any note
feature,
these note can be off different color from ticket/milestones.
In my last email, I have attached the basic product edit template but that
file missing a link, so I am attaching it again. Other than that I am
working on the ticket #570.
(1) https://issues.apache.org/bloodhound/ticket/766
(2) https://trac-hacks.org/wiki/TicketCalendarPlugin
(3) https://trac-hacks.org/wiki/WeekPlanPlugin
(4) https://en.wikipedia.org/wiki/Google_Calendar
(5) http://jqueryui.com/draggable/
(6) http://jqueryui.com/tabs/
(7) http://www.w3schools.com/html/html5_draganddrop.asp
On Tue, Mar 11, 2014 at 6:18 PM, Devender <[email protected]> wrote:
> Hi Ryan,
>
> I have studied about the bootstrap 2.3 documentation and I have worked
> with some samples of the bootstrap. I am attaching the modified version of
> the signup (1) example of the bootstrap that can work for the basic product
> edit for the desktop. I have also read about the genshi (2) and I have done
> the above 3 points mentioned in last mail but I want some pointers to start
> merge this code to create the template for product edit and become
> familiarize with the bloodhound code.
>
> (1) http://getbootstrap.com/examples/signin/
> (2) http://genshi.edgewall.org/wiki/Documentation/xml-templates.html
>
>
> On Mon, Mar 10, 2014 at 9:00 PM, Ryan Ollos <[email protected]>wrote:
>
>> On Mon, Mar 10, 2014 at 2:23 AM, Ryan Ollos <[email protected]>wrote:
>>
>>> On Mon, Mar 10, 2014 at 2:02 AM, Devender <[email protected]>wrote:
>>>
>>>> Hi Ryan,
>>>>
>>>> I am a 4th year student of the Department of Computer Science and
>>>> Engineering at Indian Institute of Technology( IIT), Kharagpur, India.
>>>>
>>>> I am good at programming in Python, AJAX, PHP, MySQL, JavaScript,
>>>> jQuery, HTML, CSS and C++. I have worked on projects which used python
>>>> and web development technologies.
>>>>
>>>> I am very enthusiast to work with Apache in GSOC 2014. I have
>>>> installed and used the bloodhound and I am interested to work on this idea
>>>> (
>>>> COMDEV-112 <https://issues.apache.org/jira/browse/COMDEV-112>). I have
>>>> done setup for the basic development environment for Bloodhound. I
>>>> have been looking at the starter
>>>> ticket<https://issues.apache.org/bloodhound/query?status=!closed&keywords=~starter>
>>>> *,* but I don't know which ticket I should work on. Please guide me to
>>>> proceed for my proposal.
>>>>
>>>
>>> Hi Devender,
>>>
>>> Welcome!
>>>
>>> It might be good to familiarize yourself with Bootstrap by working
>>> ticket #570 (1). To get started,
>>> 1. Review the Bootstrap 2.3 documents
>>> 2. Copy the template
>>> bloodhound_multiproduct/multiproduct/templates/product_edit.html to
>>> bloodhound_theme/bhtheme/templates/bh_product_edit.html
>>> 3. Add bh_product_edit.html to the template map in
>>> bloodhound_theme/bhtheme/theme.py
>>> 4. Modify the markup in the template so that we get nice styling on
>>> multiple devices (desktop, tablet, mobile).
>>>
>>> You can study the other templates in bloodhound_theme to learn how the
>>> Boostrap markup can be used.
>>>
>>> For the COMDEV-112 project, it is a bit open-ended, which gives you a
>>> lot of room to work with the community to define the solution. You can get
>>> started by looking at the architecture of the plugins mentioned in #766 (3).
>>>
>>> (1) https://issues.apache.org/bloodhound/ticket/570
>>> (2) http://getbootstrap.com/2.3.2/
>>> (3) https://issues.apache.org/bloodhound/ticket/766
>>>
>>>
>> Devender, I didn't notice initially that you sent the email directly to
>> me. This is just a quick note to say that future emails should be directed
>> to the [email protected] list, which I've added to the Reply of
>> this email. This is to keep the whole Bloodhound community involved in your
>> project :)
>>
>
>
body {
padding-top: 200px;
padding-bottom: 40px;
background-color: #eee;
}
.form-signin {
max-width: 530px;
padding: 15px;
margin: 0 auto;
}
.form-signin .form-signin-heading,
.form-signin .checkbox {
margin-bottom: 10px;
}
.form-signin .checkbox {
font-weight: normal;
}
.form-signin .form-control {
position: left;
height: auto;
padding: 10px;
font-size: 16px;
}
.form-signin .form-description{
position: relative;
height: 200px;
width: 100%;
padding: 10px;
font-size: 16px;
}
.form-signin {
margin-bottom: -1px;
border-bottom-right-radius: 0;
border-bottom-left-radius: 0;
}
.form-signin {
margin-bottom: 10px;
border-top-left-radius: 0;
border-top-right-radius: 0;
}
